vRealize Business for Cloud | 12 April 2018 | Build 8067368
Last updated: 28 March 2018
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
Enhancements to VMware Cloud on AWS Assessment
- Two new parameters, number of host failures to tolerate and failure tolerance method, are included along with vSAN metadata overhead and a recommended slack to increase the accuracy in calculating the effective available storage capacity.
- The operational insights are enhanced with information such as the number of VMs that can be packed in a host, and percentage utilization of host based on constrained resource.
- The latest list prices are considered for cost calculation for on-demand, one-year, and three-year plans.
Enhancements to Pricing and Chargeback Capabilities
- Storage policy driven pricing for vCloud Director infrastructure. You can apply rate cards for storage policies that are discovered by vCloud Director and have differential pricing for the storage tiers.
- Network enhancements
- You can apply fixed one-time charge and daily recurring charge for data ingress and egress for each business unit or tenant.
- You can apply fixed one-time charge and daily recurring charge for the used network bandwidth (MBps).
- You can apply fixed one-time charge and daily recurring charge for the dynamic routing and distributed firewall services.
- You can define T-shirt sizes for the PAYG VMs based on your requirement and price the VMs based on the sizes instead of vCPU and RAM.
- You can apply a differential rate for the vCPU and RAM usage that is beyond the guaranteed resources (overage) for the allocation pool model.
- You can apply daily pricing for OS license consumption based on one of the following rules:
- VM up time
- VM is powered on at least once a day
- Regardless of VM power up state.
- The storage elements such as media and template are discovered automatically and you can apply a rate card for the elements.
- You can get the following comprehensive information about vCloud Director usage and charge details when using the report APIs:
- vCloud Director data at organization level
- vCloud Director data specific to an organization
- vCloud Director MTD and daily data at organization vDC level
- vCloud Director data specific to an organization vDC
- vCloud Director data at vApps level
- vCloud Director data specific to a vApp
- vCloud Director MTD and daily data at VMs level
- vCloud Director data specific to a VM
- Updated multiple open source components to resolve CVE-2017-1000364, CVE-2017-1000365, and CVE-2017-1000367.
- Before upgrading to vRealize Business for Cloud 7.4, you must read the KB article 2151835.
- If you are running a vRealize Business for Cloud 6.x.x version, a direct upgrade is not supported. You must first upgrade to vRealize Business for Cloud 7.3.1 and then upgrade to 7.4 release.
- VMware vRealize Business for Cloud Installation and Administration Guide
- VMware vRealize Business for Cloud User's Guide
- VMware vRealize Business for Cloud Troubleshooting Guide
The following issues have been resolved in this release of vRealize Business for Cloud.
- Upgrade Issues
- Migration Issues
- Integration Issues
- Configuring and Provisioning Issues
- User Interface Issues
- If you are using the VMware Identity Manager integrated vRealize Business for Cloud setup, after 7.3.1 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.1, though you log in as an administrator user, you cannot perform administrator tasks.
Workaround: vRealize Business for Cloud 7.3.1 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.1 upgrade, vCloud Director pricing policies are not retained.
When you upgrade vRealize Business for Cloud 7.3.1, 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.1 upgrade, the addition of NSX Manager does not trigger the cost calculation automatically.
After you upgrade vRealize Business for Cloud 7.3.1, 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.
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.
- 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.
Incorrect count of VMs or virtual data centers (vDC) is displayed after deletion of VMs, vDCs, or organization.
After you delete a VM, vDC, or an organization, the VM count does not reduce under the Consumption > Pricing > Edit Pricing section.
- You do not see the VMware Cloud on AWS logo on Internet Explorer.
If you are using Internet Explorer, when you attempt to add VMware Cloud on AWS 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.
The following issues are known to occur in vRealize Business for Cloud 7.4, and are grouped as follows:
- Upgrade Issues
- Deployment Issues
- Configuring and Provisioning Issues
- User Interface Issues
- Report Issues
- Known Issues From the Earlier Releases
After upgrading the vRealize Business for Cloud appliance, a few configurations such as heap size (-XMs and -Xmx) are reset to the default values.
If you had changed the default values of the following vRealize Business for Cloud configurations, the changed values are reset to the default values after an upgrade:
Workaround: Modify the default values to the required values after the upgrade.
When powering on the vRealize Business appliance, the vSphere Web Client issues the following question: "Cannot connect the virtual device IDE0:0 because no corresponding device is available on the host. Do you want to try to connect this virtual device every time you power on the virtual machine?"
By default, the vRealize Business appliance's virtual CD/DVD drive is set to connect at power on. When the appliance fails to find media at bootup, the question described in the symptom is issued.
Workaround: See VMware knowledge base article 2151287.
VMs provisioned through vRealize Automation are listed under vCloud Director.
If you have added a vCloud Director endpoint to vRealize Automation and vRealize Business for Cloud and then provision VMs through vRealize Automation using the reservation pool or allocation pool model in vCloud Director, the VMs are listed under vCloud Director instead of being listed under vRealize Automation private cloud pricing.
If you use a HTTP proxy server in your environment, the automatic reference database update fails.
HTTP proxy server is not supported by vRealize Business for Cloud for automatic update.
Workaround: You must manually update the reference database. For instructions see, Update the Reference Database for vRealize Business for Cloud section in the vRealize Business for Cloud Install Guide.
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.
The Re-calculate Pricing dialog box might not close after updating the prices.
After you update the vCPU and RAM prices from Business Management > Consumption > Pricing > Edit Pricing and click Re-calculate > Save, the dialog box does not close. However, the information is saved and recalculation happens in the background.
- Additional services report is not complete.
When you generate the previous month's additional services report, it does not include the last day's price for the services.
In addition to these new issues found in this release, some known issues from the earlier releases are also applicable. Click here.
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 up front 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.
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.