vRealize Business for Cloud 7.3 Release Notes
vRealize Business for Cloud | 13 June 2017 | Build 5675340
Last updated: 13 June 2017
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
- Tighter integration with vRealize Operations Manager. You can access vRealize Business for Cloud 7.3 through the vRealize Operations Manager.
vRealize Business for Cloud appears as a tab named as Business Management in the vRealize Operations Manager 6.5 and later.
Note: If you have registered vRealize Business for Cloud 7.3 with vRealize Automation, you can see the vRealize Business for Cloud user interface on vRealize Operations Manager.
- Compatible with latest versions of VMware solutions. vRealize Business for Cloud 7.3 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.
- Support VMware NSX Manager. vRealize Business for Cloud can integrate with VMware NSX Manager and enables you to define price for network services.
- Partial vCenter Server support. You can select a set of virtual machines or clusters to add into vRealize Business for Cloud, instead of adding the complete vCenter Server.
- Enhancements to Azure.
- Azure is considered as a first class citizen in vRealize Business for Cloud 7.3, which provides the detailed costing, pricing mechanism, showback information, and VM Statistics for Non-EA accounts.
- You can now define pricing policies for Azure virtual machines that are deployed directly on Azure and are deployed by vRealize Automation.
- vRealize Business for Cloud 7.3 can provide upfront price for Azure blueprint and if a Azure machine is deployed from vRealze Automation, vRealize Business for Cloud can compute cost-to-date.
- Enhancements to AWS. You can now see the detailed consumption data of compute, storage and network resources at the AWS instance level.
- Support import from blueprint for cloud comparison. If you have registered vRealize Business for Cloud with vRealize Automation, you can import the blueprints from vRealize Automation, which will be mapped to virtual machine groups. This helps you to perform cost comparison across public cloud.
- Procurement Planning support. You can simulate a virtual machine group configuration to compare its cost on all data centers that exists in vRealize Business for Cloud. If your virtual machine group configuration does not match a data center configuration, you can see the recommendations about additional data center configuration required to match your requirements.
- Support for VMware Cloud on AWS. Procurement planning (What-If Analysis) in vRealize Business for Cloud 7.3 supports cost comparison with VMware Cloud on AWS and enables you to assess placement of new or existing workloads across private cloud and public clouds, including VMware Cloud on AWS.
- Import from Blueprint in for cloud comparison. If you are using the vRealize Automation integrated vRealize Business for Cloud setup, you can import the virtual machine data from a blueprint in vRealize Automation and perform the cloud comparison (What-If Analysis) for public cloud.
- Calculate expense-to-date value for virtual machines. vRealize Business for Cloud 7.3 populates the expense-to-date value for the virtual machines on vRealize Automation user interface.
- Calculate price of deployment constructs. vRealize Business for Cloud can identify deployment constructs present in vRealize Automation and calculate price for those objects.
- Enable utilization based pricing. You can now calculate price based on actual usage of resources such as CPU, Memory, and Storage.
- Configure pricing method for resources. You can configure the pricing method for resources such as CPU, memory, and storage to calculate the price of virtual machines accurately based on allocation and utilization selected for each resource.
- Configure Pricing Update Strategy. You can configure to assign the running cost value to compute rates of CPU an memory on daily basis or manually update the compute rates. If you select the Auto option, vRealize Business for Cloud automatically assigns the running cost to the CPU and memory compute rates every day. If you select the Manual option, you can edit the compute rates while editing the vCenter Server pricing policy.
- Configure network pricing. You can now price network components discovered by vRealize Business for Cloud from NSX Manager via vCloud Director.
- Track daily change in utilization for price calculation. vRealize Business for Cloud 7.3 has the ability to price the resources accurately based on change in utilization or configuration within a day.
- Compute pricing at Organization Virtual Data Center (Org VDC) level. In addition to virtual machine level pricing, you can now set and view the price at Org VDC level for different allocation models in vCloud Director.
Licenses and Roles
- Support multiple license keys. You can now enter multiple license keys as part of license administration.
- Additional access for vRealize Suite Standard license key. If you log in to vRealize Business for Cloud by using the standard edition license key, you can see additional details or options such as:
- The reclaimable virtual machines information on the Infrastructure Utilization widget on the Overview page.
- The private cloud reclamation information that provides details of the the idle, powered-off, and oversized virtual machines on the Private Cloud Reclamation on the Overview page.
- The data center optimization information under the Planning section.
- The cost savings opportunity information in the Hybrid Cloud Assessment report.
- An option to view, edit and save the reports as custom reports.
- Support Business Controller Role for Standalone vRealize Business for Cloud. In addition to administrator privileges and read-only privileges, you can now assign Business Controller role (vRBC_Controller) to the VMware Identity Manager users to access vRealize Business for Cloud standalone user interface.
Note: The earlier roles are renamed to vRBC_Administrator (earlier vCBM_ALL), and vRBC_ViewOnly (earlier vCBM_View).
- Schedule a Report. You can now schedule and email a custom report or the out-of-the-box reports to a set of recipients on daily, weekly or monthly basis.
- Updates to the Daily Price Report. vRealize Business for Cloud 7.3 calculates the virtual machine price accurately based on its CPU, storage and memory resource utilization or allocation and its change within a day.
- New Reports. Additional reports are added in vRealize Business for Cloud 7.3:
- Azure Instances
- Azure Resources
- Several out-of-the-box reports (that provides operational and cost visibility)
- Enhanced Public APIs of Reports. You can now use the Public APIs to generate reports in the VMware Identity Manager integrated vRealize Business for Cloud setup.
- Enhancements to User Interface. vRealize Business for Cloud 7.3 is updated with the clarity theme to provide enhanced and consistent user experience.
- Addition of Launch pad. A new page is introduced with Business Insight, Cloud Operations, and Cloud planning sections to quickly navigate and get the specific required information.
- Renamed options: The Planning section is renamed to What-If Analysis. And also you see additional renamed options within the section, Public Cloud (earlier Compare with new VMs), Migration (earlier Compare with existing VMs), and Data Center Comparison (earlier Compare Data Centers).
- Change in Report Navigation. The Reports page is reorganized with links to additional reports.
- 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 7.3 deployment is reduced to around 1.98 GB.
- Simplified the reference database update workflow. For better experience, the manual process of updating the reference database is simplified.
- Enhanced salability. By default, vRealize Business for Cloud can scale up to 20,000 virtual machines. However, you can increase the scale up to 30,000 virtual machines by increasing the memory size. For more information, see vRealize Business for Cloud System Requirements.
The following issues are known to occur in vRealize Business for Cloud 7.3, and are grouped as follows:
- If you are using the VMware Identity Manager integrated vRealize Business for Cloud setup, after 7.3 upgrade, the administrator user has read-only permissions, instead of all permissions.
After you upgrade VMware Identity Manager integrated vRealize Business for Cloud setup to 7.3, though you log in as an administrator user, you cannot perform administrator tasks.
Workaround: vRealize Business for Cloud 7.3 creates a new user group by the name vRBC_Administrator. You must add the administrator user to this new group to perform all administrator tasks.
- After vRealize Business for Cloud 7.3 upgrade, vCloud Director pricing policies are not retained.
When you upgrade vRealize Business for Cloud 7.3, vCloud Director pricing policy values that you had defined are not available.
Workaround: You must redefine the pricing values.
- After vRealize Business for Cloud 7.3 upgrade, the addition of NSX Manager does not trigger the cost calculation automatically.
After you upgrade vRealize Business for Cloud 7.3, when you add a NSX Manager, the data collection completes and shows green indication. However, cost calculation does not trigger automatically and you do not see the cost changes on the UI.
Workaround: Trigger the cost calculation for NSX manually or wait until the next default cost calculation completes.
- After upgrade, you do not see Azure endpoints that were added in the earlier version of vRealize Business for Cloud.
After you upgrade vRealize Business for Cloud, you do not see the Azure endpoints on the upgraded setup.
This issue happens when you have an Azure endpoint without completing the data collection process. All Azure endpoints must have completed the data collection process at least once (irrespective of successful or unsuccessful process). You must add all the Azure endpoints in the upgraded vRealize Business for Cloud setup.
- After migration, the public cloud costs for the sample group virtual machines are reduced.
After you migrate from 6.2.3, you see the reduced costs for the public cloud sample groups under the Planning section. Also, though you had set the service offerings as Dedicated Cloud or Virtual Private Cloud, the service offering is changed to On Demand after migration.
Workaround: To get the correct cost, you must manually change the service offering according to the previous setting after migration.
- After migration, the pricing policy names are not visible in the vRealize Automation virtual machines report.
Since the 6.2.3 version did not support pricing policies, after you migrate 6.2.3 to the later releases, the Pricing Policy Name column displays an empty field value.
Note: The empty policy name appears only for the month when you completed the migration or when or the pricing policy has changed. However, you see the policy names in the later months.
- 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.
Workaround: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.
User Interface Issues
- You see an internal error message on the user interface intermittently.
During the vRealize Business for Cloud processes such as cost calculation, policy creation, or cloud comparison, though the process is running correctly, you might see the following error on the user interface:
System unable to process your request at this time due to some internal error. Please reload the page and try gain later.
Workaround: Ignore the error and wait until the completion of the respective process.
- You do not see the VMware Cloud on AWS (VMC) logo on Internet Explorer.
If you are using Internet Explorer, when you attempt to add VMware Cloud on AWS (VMC) for cost comparison on the Manage Cloud Providers screen, you do not see an icon.
Workaround: Use a different browser such as Mozilla Firefox, Google Chrome, and Microsft Edge.
- 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:
- 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.