vRealize Business for Cloud 7.2 Release Notes
vRealize Business for Cloud | 15 November 2016 | Build 4635843
Last updated: 11 January 2017
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
- Compatible with latest versions of VMware solutions. vRealize Business for Cloud 7.2 is compatible with the latest versions of vRealize Automation, VMware Identity Manager and vCenter Server. To see the list of all supported versions, see the Interoperability matrix.
- Upgraded JRE to 1.8 update 102. JRE has been upgraded to 1.8.0_102 in this release.
- Upgraded Postgres database to 9.5 version. vRealize Business for Cloud Postgres appliance database has been upgraded to 9.5 version in this release.
- Supports new currencies. vRealize Business for Cloud 7.2 supports several additional currencies for cost calculation, which you can set during vRealize Business for Cloud deployment. To see the list of supported currencies, see the Installation Guide.
- Calculates price of the short-lived virtual machines. Earlier releases of vRealize Business for Cloud calculated the price for the virtual machines that were live during cost calculation. vRealize Business for Cloud 7.2 considers the virtual machines that were powered on for short period also.
- Exports a report for specific period using API. You can generate a report for a specific period by providing the date filters in the API.
- Enables to price network services. vRealize Business for Cloud 7.2 provides an ability to price network services at two levels such as fixed price and recurring price, which can be mapped to business units.
- Enables pricing for fault tolerance vCenter Server virtual machines. vRealize Business for Cloud 7.2 can apply price on the fault tolerance property of virtual machines that are part of vCenter Servers.
- Provides AWS EC2 and EBS operational statistics. You can view the total cost and operational statistics of Amazon Elastic Compute Cloud (EC2) services and Elastic Block Store (EBS) in vRealize Business for Cloud 7.2.
- Allows to generate a new reports. You can generate additional reports in vRealize Business for Cloud 7.2.
- Cloud Business Analysis Report: Provides a detailed expenditure information and operational details of your infrastructure on private and its comparison information with public cloud environments.
- Daily Price Report: Provides the price of all virtual machines on vCenter Servers for last three months.
- Power State Change for VMs. You can track the power-on and power-off states of vCenter Server virtual machines for each day of a specific month and its corresponding duration.
- Displays uptime of virtual machines. You can see the total duration of the vCenter Server virtual machines that were up and running for a specific month.
The following issues have been resolved in this release of vRealize Business for Cloud.
- After upgrade, the earlier month costs of an Azure EA account do not appear
After you upgrade vRealize Business for Cloud 7.0.1, the cost of an Azure EA account for the months prior to the current month do not appear.
- After migration, the cost calculation does not run automatically
After you migrate from 6.2.3, the cost calculation process does not run automatically and displays inconsistent data on the UI.
- The vRealize Automation user session does not timeout
When you have registered vRealize Business for Cloud with vRealize Automation, vRealize Automation ignores its default timeout interval and keeps the user session active indefinitely even without user actions.
User Interface Issues
- The UI text is truncated on the add and edit pages of the public cloud accounts
You might not see the complete text on the add or edit page for the public cloud accounts in the Administrator section. For example,
- Add or Edit AWS account page
- Add or Edit Azure account page
- Add or Edit Cloud Providers for Comparison
You cannot export the filtered reports
When you click Search on a report and enter a string to filter a report, you can see the matching records on the UI. However, when you export the filtered report, all the records appear in the XLS file, instead of only the matching records.
The following issues are known to occur in vRealize Business for Cloud 7.2, and are grouped as follows:
- After you upgrade vRealize Business for Cloud, the network configurations are lost
If you have deployed vRealize Business for Cloud on vCloud Director, later when you upgrade vRealize Business for Cloud, the configured network settings are deleted.
Workaround: To fix the issue, you must configure the network settings manually.
- Log in to the vCloud Director.
- Select the vRealize Business for Cloud virtual machine, right-click, and select Popout Console.
- On the console window, navigate to the vami directory:
- Run the ./vami_config_net script.
- Enter the network configurations for all the required settings.
- After migration from 6.2.3 to vRealize Business for Cloud 7.2, you cannot see the updated names of AWS accounts
After you migrate from 6.2.3 to vRealize Business for Cloud 7.2, if you modify the names of AWS accounts, the updated names will not appear on AWS Overview page or under the Pricing section even after completion of data collection.
- 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.
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.
- You see blank entries in the Daily Price report.
When you generate the Daily Price report, you see the price for the virtual machines only till the previous day. The price of the virtual machines for current day are 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:
- Set the proxy in VAMI.
- 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.
- Run ps -ef|grep bifrost.
- Run kill -9 , where pid is the process that is running the WAR file.
- 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 &.
- To verify the fix, run the following commands:
- ps -ef|grep bifrost.
- cat /proc//environ
- Find the http_proxy variable in the output.