vRealize Business Standard 7.0 Release Notes

vRealize Business Standard | 17 December 2015 | Build 3299258

Last updated: 06 January 2016

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes covers the following topics:

What's New

  • Changes to the vRealize Business Standard Architecture:
    • Accesses VMware Identity Management (VIDM) from vRealize Automation appliance. vRealize Business Standard does not need a separate SSO appliance or server.
    • Supports two versions of vRealize Automation releases, the latest version of vRealize Automation 6.2.3 and vRealize Automation 7.0.
    • Separates the data collectors from the vRealize Business Standard server. You can now deploy a remote data collector across geography and collect data from private, public and hybrid cloud providers.
  • Enhancements to the installation and upgrade process:
    • The installation process enables you to deploy the vRealize Business Standard 7.0 server with a data collector or to deploy only a data collector.
    • The upgrade process involves deployment of the vRealize Business Standard 7.0 server and then migration of data.
    • The deployment process supports two additional currencies, Saudi Arabian Riyal and Swiss Franc.
  • Enhancements to Cloud Cost:
    • Integrated with Virtual Storage Area Network (Virtual SAN) for data collection and cost analysis of datastores and storage profiles that are associated with Virtual SAN.
    • Displays the total projected cost, virtual machine count, and the projected cost based on the consumption from all private, public, and hybrid cloud infrastructure types.
    • Supports storage datastore cost based on tags in addition to profile and type.
    • Increases the depreciation period for cost calculation to two to seven years in Calculation Preferences.
  • Enhancements to the consumption analysis:
    • You can group business units from different sources such as vCenter Server, vCloud Director, and vRealize Automation.
    • You can group business services from different sources such as vCenter Server, vCloud Director, and vRealize Automation.
    • You can set logical names for business units.
    • You can generate an enhanced showback statement with charge budget comparison values and advanced reporting capabilities of private and public cloud.

  • Tighter integration with vRealize Operations:
    • Provides the reclamation opportunities based on vRealize Operations and vRealize Automation integration. You can get information about the virtual machines that are powered off, idle, and oversized for quantifying the potential savings.
    • Displays the costs of used and remaining capacity by data center based on vRealize Operations integration.

  • Enhanced pricing support:
    • Auto-generates pricing policies based on the reference database values. These policies provides pricing recommendations for private, public, and hybrid cloud, by default.
    • Sets pricing policies by additional constraints: vCenter Server, datastore cluster, vRealize Automation blueprint, vRealize Automation Storage Reservation Policy.
    • Calculates price to virtual machines provisioned by vRealize Automation including the virtual machines that vRealize Business Standard does not monitor (for example, KVM, Openstack and HyperV).
    • Replaces the vRealize Automation cost profiles by including advanced pricing policies. You can see the price on the vRealize Automation catalog UI based on vRealize Business Standard policies.
    • Provides an option to define cross infrastructure charges and to define additional charges of vRealize Automation custom attributes.
    • Handles Virtual SAN cost separately from storage expenses by excluding datastores that the Virtual SAN identifies and grouping them under Virtual SAN category.
  • Enhancements to Cloud Comparison:
    • Supports advanced cloud planning abilities based on data collected from vCenter Server and vRealize Operations.
    • Provides two additional providers for comparison, Amazon Government Services and vCloud Government services, by default.
    • Allows you to add additional services that AWS provides such as load balancers for accurate comparison.
    • Supports data center optimization by displaying the cost of remaining capacity with the used capacity for each data center and helping you to verify the cost variance when you add additional virtual machines.

  • Enhancements to the public and hybrid cloud infrastructure:
    • Supports both Microsoft Azure Enterprise Account (EA) and Non-Enterprise Account (Non-EA).
    • Supports vCloud Government services in addition to the earlier vCloud Air service offerings such as On Demand services and Disaster Recovery services.
  • User Interface (UI) changes:
    • Redesigned the main page with four main categories, Infrastructure, Consumption, Planning, and Reports for better coherent and unified data model support.
    • Added a single pane to view the cloud cost from all cloud providers, public, private, and hybrid.
    • Updated the dashboard with quick and easy data points, Expenses, Operations, and Consumption.

  • Enhancements to the reports:
    • You can generate additional reports such as Virtual SAN Datastores report, vCloud Air Charges report, AWS resources, and AWS charges report.
    • You can edit the report view by using the new report features such as show or hide columns, group by values, search, sort, rearrange and freeze column positions.
    • You can create new columns based on tags or custom properties.
    • You can aggregate or group-by to the existing grid reports and create ad-hoc charts based on grid reports.
    • You can save a report as a custom report with your customizations and filters for later use.
    • You can generate historical showback reports that includes deleted virtual machine information also.

  • Localization support:
    vRealize Business Standard 7.0 is available in following languages:
    • English
    • French
    • German
    • Japanese
    • Korean
    • Simplified Chinese
    • Traditional Chinese

Documentation

VMware vRealize Business Standard Installation and Administration Guide

VMware vRealize Business Standard User's Guide

Known Issues

The following issues are known to occur in vRealize Business Standard 7.0 release, which are grouped as follows:

Upgrade Issues

  • Any changes to the DRL file are lost after migrating to vRealize Business Standard 7.0
    After an upgrade to 7.0, the DRL files of your earlier vRealize Business Standard version are deleted, and so your changes are lost.
    Workaround: Reconfigure the DRL file manually and upload the file into vRealize Business Standard. For more information, see the Update the DRL file for Cloud Comparison section in the installation guide.
  • After you deploy vRealize Business Standard 7.0, DNS server is not auto-detected
    If you are deploying vRealize Business Standard 7.0 on vCloud Director, the DNS settings are not updated automatically.
    Workaround: Navigate to the /opt/vmware/share/vami/vami_set_dns tool and set the DNS server manually during vRealize Business Standard deployment.
  • After upgrading to vRealize Business Standard 7.0, the customized utilization values defined for CPU and memory in an earlier version are not carried to the 7.0 version
    After an upgrade 7.0, the expected CPU and memory utilization values set on an earlier vRealize Business Standard version are not migrated to vRealize Business Standard 7.0.
    Workaround: Reconfigure the customized values on the 7.0 setup.
  • The budget defined in vRealize Business Standard 6.2.x are not migrated to 7.0 upgrade
    If you upgrade your vRealize Business Standard 6.2.x setup that is categorized based on vCloud Director, the budget values are not migrated to the 7.0 setup.
    Workaround: Import the budget values manually into vRealize Business Standard 7.0.
    1. Upgrade to vRealize Business Standard 7.0.
    2. Open the Edit Budget page on the vRealize Business Standard 6.2.* setup and export the budget details to the .xls format.
    3. Open the Edit Budget page on the vRealize Business Standard 7.0 setup and create a template.
    4. Copy the budget lines from the .xls file and replace the lines in the template file.
    5. Import the updated template file into the vRealize Business Standard 7.0 setup.
  • The advanced pricing policies defined are not migrated during vRealize Business Standard 7.0 upgrade
    When you upgrade to vRealize Business Standard 7.0, the advanced pricing policies based on vRealize Automation or vCloud Director categorization are not migrated.
  • The virtual machine up-time data is not migrated after upgrading to vRealize Business Standard 7.0
    After you upgrade to vRealize Business Standard 7.0, the information about the total duration of the powered-on virtual machines are not migrated.
  • After upgrading to vRealize Business Standard 7.0, the server hardware batch information is not migrated
    When you upgrade your vRealize Business Standard 6.0 setup to 7.0, the server hardware batch information is not migrated.
  • After vRealize Business Standard 7.0 upgrade, some AWS reports do not display data
    After upgrading to the vRealize Business Standard 7.0 version, AWS resources are not migrated. So the AWS charges page and the AWS Resources report do not display data. However, you can see data in the AWS Overview page and the AWS Instances reports.
    Workaround: You must wait for the data collection and cost calculation process to complete, which updates all AWS data into the 7.0 version.
  • After upgrading your vRealize Business Standard 6.0 to 7.0, the vCloud Air virtual machine data is not migrated
    After you upgrade vRealize Business Standard 6.0 to the 7.0 version, the vCloud Air virtual machines report does not display any data.
    Workaround: You must wait for the vCloud Air data collection and cost calculation processes to complete successfully.
  • After vRealize Business Standard 7.0 upgrade, certain vCenter Server polices types are migrated
    Though you have vCenter Server policies defined by hosts, clusters and resource pools in your vRealize Business Standard 6.2.3, the pricing policies defined by clusters and hosts are only migrated to the 7.0 setup. The vCenter Server policies defined by resource pools are not migrated.

  • After vRealize Business Standard 7.0 upgrade, the vRealize Automation and vCloud Director policies are not migrated
    After you upgrade your vRealize Business Standard 6.2.3 to 7.0, the vRealize Automation and vCloud Director pricing policies are not migrated.
  • After vRealize Business Standard 7.0 upgrade, the vCloud Air Overview page does not display the accounts with special characters
    If you have added vCloud Air accounts having special characters in its names, the account details are not displayed in the Service ID section of the vCloud Air Overview page.
    Workaround: Before your upgrade to 7.0, perform the following steps:
    1. Rename or modify the vCloud Air account names by deleting the special characters in the vRealize Business Standard 6.x setup.
    2. Run the vCloud Air data collection process to refresh the name changes.
  • After vRealize Business Standard 7.0 upgrade, the data synchronization does not happen
    After you you upgrade to vRealize Business Standard 7.0 and register with vRealize Automation, the data synchronization is not seen on the UI. And also, you cannot trigger the process manually.
    Workaround: You must wait for at least twelve hours after registering with vRealize Automation or wait for the data collection process to complete. Later, you can see the data synchronization or run the collection process manually.
  • After you upgrade vRealize Automation to 7.0 and then upgrade vRealize Business to 7.0, the upgrade complete with the system synchronization error
    After upgrading vRealize Business Automation and vRealize Business from 6.2.3 to 7.0 version, you see the Can't find 'Blueprint' error in the itfm-server.log file. For more information, see KB 2141411.
  • vRealize Business Standard 7.0 migration might fail in a large environment that has around 10000 virtual machines.
    In a large environment with approximately 10000 virtual machines, the vRealize Business Standard 7.0 migration process might stop responding without any notification.

Integration Issues

  • An out-of-memory error might occur when multiple instances are connected to vRealize Business Standard
    When multiple types of connections (such as vCenter Server, vCloud Director, SRM, AWS, Azure, vCloud Air) are added to vRealize Business Standard, you might see an out-of-memory error. This error occurs because the configured value for JAVA PermGen is insufficient.
    Workaround: To avoid the issue, increase the PermGen size to 512MB, which is 256MB by default.
    1. Log into the vRealize Business Standard virtual appliance.
    2. Open the setenv.sh file in /usr/local/tcserver/vfabric-tc-server-standard/itbm-data-collector/bin/.
    3. Change the value of MaxPermSize from 256m to 512m.
      -Xms512m -Xmx1024m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError
    4. Save the changes.
    5. Restart the data collection process by running the monit restart itbm-data-collector command.
  • An internal server error appears when you select a vCloud Director identification or tag for adding a cross-infrastructure policy
    Though vCloud Director is not connected, the vCloud Director identifications and tags appear for selection while adding additional services to the pricing policy. This results in an internal server error.
  • Issue with edit pricing functionality on Mozilla Firefox
    If you have registered vRealize Business Standard 7.0 with vRealize Automation 6.2.3, the edit pricing page does not open in the Firefox browser.
    Workaround: Use a different browser such as Internet Explorer or Google Chrome. To resolve the Firefox issue, perform the following steps.
    1. Open a Firefox browser and enter about.config in the address bar.
    2. Search for the dom.url.getters_decode_hash preference name in the list.
    3. Right-click on the preference name and click Toggle to change the value to true.
  • 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 SLES11 to SLES12, the bifrost service is unable to use environment variables like 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 procedure:
    1. Set the proxy in VAMI.
    2. Enable SSH for the vRealize Business Standard.
    3. Run ps -ef|grep bifrost.
    4. Run kill -9 < bifrost_pid > , where pid is the process which 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, run the following commands:
      1. ps -ef|grep bifrost.
      2. cat /proc//environ
    7. See the http_proxy variable in the output.

Configuring and Provisioning Issues

  • Exporting the virtual machine report might fail
    If you have a large data in the virtual machine report (more than 10,000 records), the export report action might fail.
    Workaround: Filter the report to reduce the number of records and export the report.
  • 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 with a non-Latin 1 character, the 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 UTF-8 format.
  • An incorrect charge value is displayed on the Business Unit Details page
    When you click a business unit on the Business Unit List page, the CPU charge includes both CPU and RAM charges in the Charge Distribution widget and its tooltip, instead the CPU value must include only CPU charges.
  • When you click the search icon, the search operation does not work
    After you enter a string in the search text box, when you click the search icon, vRealize Business Standard does not search for the matching records.
    Workaround: After you enter a string in the search text box, press the Enter key to see the search result.
  • Unable to open the custom reports saved with HTML tag names
    If you have named a report using the HTML tag names while saving, for example scripts, HTML tags, SQL injection, you cannot open the report from the Custom Reports page.
    Workaround: Do not save the reports by using the HTML tags.
  • vRealize Business Standard does not save the manually updated percentage value for the Total cost surcharge field on the Pricing page
    When you modify the percentage value in the Total cost surcharge field on the Pricing page, the updated value appears on the UI. However, the value is not saved in the server.
  • While importing a virtual machine for cloud comparison, you cannot search for the virtual machine
    The Search VMs option for importing the virtual machine under Cloud Comparison does not work.
    Workaround: Use the Browse option and select the virtual machine that you want to import.

  • Unable to access the vRealize Business Standard server, when the server is overloaded
    If the vRealize Business Standard server is overloaded, you see an internal server error.
    Workaround: Access vRealize Business Standard after some time.
  • The AWS virtual machine count on AWS Overview page is different from the count shown on the Pricing and Edit Hierarchy page
    The AWS Overview page includes the deleted virtual machines count for the current month. But the Pricing and Edit Hierarchy pages do not include the deleted virtual machines, which results in a different count.
  • The vRealize Automation data collection fails if vRealize Automation has multi machine blueprints
    vRealize Business Standard ignores machines that do not collect blueprints or whose external reference ID is null.