vRealize Business for Cloud 7.2.1 Release Notes

|

vRealize Business for Cloud | 02 March 2017 | Build 5101870

Last updated: 04 May 2017

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Tighter integration with vRealize Operations Manager. If you have registered vRealize Business for Cloud with VMware Identity Manager, you can access vRealize Business for Cloud 7.2.1 on the vRealize Operations Manager. vRealize Business for Cloud appears as a tab named as Business Management in the vRealize Operations Manager 6.5 user interface.
    Note: If you have registered vRealize Business for Cloud with vRealize Automation, you cannot see the vRealize Business for Cloud user interface on vRealize Operations Manager.

  • Compatible with latest versions of VMware solutions. vRealize Business for Cloud 7.2.1 is compatible with the latest versions of vRealize Operations Manager, vRealize Automation, VMware Identity Manager and vCenter Server. To see the list of all supported versions, see the VMware Product Interoperability Matrix.

  • Upgraded JRE to 1.8 update 121. JRE has been upgraded from 1.8.0_102 to 1.8.0_121 in this release.

  • Reduction in the vRealize Business for Cloud OVA file size. The size of the OVA file that you use for vRealize Business for Cloud deployment is reduced from 3.5 GB to 1.8 GB.

  • Renamed Cloud Business Analysis Report. The Cloud Business Analysis report that was introduced in vRealize Business for Cloud 7.2 has been renamed to Hybrid Cloud Assessment. A new summary page is added to the Hybrid Cloud Assessment report, which provides:
    • the current monthly cost and average VM cost of your private cloud
    • the total cost of ownership and the allocated cost that represents the percentage of private cloud utilization
    • the estimated monthly cost of public cloud (AWS and Azure)
    • the reclaimable opportunities with cost savings on private cloud

  • Additional access to vRealize Suite Standard license key. If you log in to vRealize Business for Cloud by using the vRealize Suite Standard license key, you can see additional details such as:
    • The reclaimable virtual machines information on the Overview page.
    • The datacenter optimization information under the Planning section.
    • The cost savings opportunity information in the Hybrid Cloud Assessment report.

Documentation

Resolved Issues

The following issues have been resolved in this release of vRealize Business for Cloud.

User Interface Issues

  • You could not add more than 20 items for Additional Costs under Expenses
    After you add 20 rows under Expenses > Additional Costs, the scroll bar disappears and you cannot add more items.

Reports Issues

  • You could not download the Cloud Business Analysis report
    When you click Download PDF Report to download the Cloud Business Analysis report, the PDF file is not downloaded. You see the following error in the itfm-server.log file.
    Failed to execute task voa NumberFormatException
  • You see multiple entries for a virtual machine on a single day in the Daily Price Report
    When you have historic data, you see duplicate entries in the Daily Price Report for a virtual machine in a single day.

Known Issues

The following issues are known to occur in vRealize Business for Cloud 7.2.1, and are grouped as follows:

Integration Issues

  • The upfront cost for Azure blueprint is not supported
    When you attempt to view the cost details for Azure blueprint on the vRealize Automation UI, you see the following error:
    Cannot calculate cost. Contact your system administrator to review the vRealize Automation appliance logs.
  • The monit command shows incorrect status about data collectors.
    Though the data collectors are running, the monit summary command might show incorrect status stating that the service is not running.
    Workaround: The issue occurs when the PID file for data collectors is missing in the /usr/local/tcserver/vfabric-tc-server-standard/itbm-data-collector/logs directory. To fix the issue, restart the vRealize Business for Cloud virtual appliance.

Configuring and Provisioning Issues

  • Incorrect endpoint name is displayed for vCloud Director provisioned virtual machines in the vRealize Automation Virtual Machine report
    vRealize Automation Virtual Machine report displays vCloud Air as the endpoint for the virtual machines provisioned in vCloud Director through vRealize Automation 6.2.5.
  • Incorrect count of network service policy is displayed after deletion of a policy.
    After you delete a network policy from the Edit Pricing page, the count is not reduced under the Pricing > Other Private Cloud Services section.

Report Issues

  • You see blank entries in the Daily Price report.
    When you generate the Daily Price report, you see the price for the virtual machines till the previous day only. The price of the virtual machines for current day is blank.

Known Issues From Earlier Releases

In addition to these new issues found in this release, some known issues from the earlier releases are also applicable. Click here.

Integration Issues From Earlier Releases

  • The Running price values might not match in vRealize Business for Cloud and vRealize Automation
    The Running price that is shown in the Consumption Analysis in vRealize Business for Cloud might be different from the running price values displayed in vRealize Automation.
    This is because, vRealize Business for Cloud calculates the running price on daily basis based on power state of virtual machines. However, vRealize Automation displays the running price based on the upfront cost which is multiplied with the lease days.
  • Two AWS services with the same name can have two different policies in vRealize Business for Cloud
    When two different AWS accounts have the same service names (for example, Amazon Kinesis) in Edit Pricing -> Public Cloud (AWS), they can have two different policies set corresponding to these services.
    Note: Currently you cannot identify the account to which the service is associated with.
    In case of multi-machine blueprint, it is classified both under Private and Hybrid Cloud (vCloud Air). To set the prices for multi-machine blueprint, you must define the prices for the blueprints that are classified under the Private category.

Configuring and Provisioning Issues From Earlier Releases

  • An error might appear when you click a business unit on the Business Units List page
    On the Business Unit List page, when you click on a business unit name that has a non-Latin 1 character or a slash ("/"), an HTTP Status 404 error appears.
    Workaround: Use the ISO-8859-1 character set for defining the business unit names. vRealize Business Standard supports only the Latin-1 format, and not the UTF-8 format. And, do not use a slash ("/") in the business unit names.
  • The secure channel is unable to use HTTP proxy environment variables, which results in failure of user creation and token
    Due to the operating system upgrade from SUSE Linux Enterprise Server (SLES) 11 to SLES12, the bifrost service is unable to use environment variables such as http_proxy. When vRealize Automation is integrated with IaaS, the proxy configuration might block certain calls related to IaaS because of the configuration through the system properties.
    Workaround: To resolve the issue, perform the following steps:
    1. Set the proxy in VAMI.
    2. Enable SSH for the vRealize Business for Cloud. For more information, see the Enable or Disable SSH Settings section in the vRealize Business for Cloud Install Guide.
    3. Run ps -ef|grep bifrost.
    4. Run kill -9 , where pid is the process that is running the WAR file.
    5. Run nohup /usr/java/jre-vmware/bin/java $JAVA_OPTS -Daccess.token.file=/usr/local/bifrost-client/access.token -jar /usr/local/bifrost-client/bifrost-client-1.0.0.war --server.port=9876 > /dev/null 2>&1 &.
    6. To verify the fix, run the following commands:
      1. ps -ef|grep bifrost.
      2. cat /proc/ /environ
    7. Find the http_proxy variable in the output.