What to Test - UM 3.5.0 Beta

What to Test

UM 3.5.0 beta participant, please follow these steps in order to help us perform customer acceptance testing on the beta product.

Common Setup

1. Continue to operate UM 3.3.x that you should have currently deployed, viz. UM-Production
2. In parallel install, UM 3.5.0 beta, viz. UM-35-beta
3. Complete

Licenses

1. Perform the common setup
2. Register all product instances with UM-35-beta that you have currently registered with UM-Production
3. Navigate to Licenses on both UM-Production and UM-35-beta.
4. Verify that the licenses reported by UM-Production and UM-35-beta match.
5. Complete.

vRealize Operations Manager

1. Perform the common setup
2. Ensure that all vCenter servers associated with your vROps servers are registered with UM-35-beta
3. Navigate to Manage→Products and click Rebuild
4. Verify that the vROps instances that exist in your infrastructure associate show up in the list below the Rebuild button.
   1. Register vROps with vCenter
   2. Click the edit button that exists against each vROps instance and supply vROps credentials and press OK.
   3. Refer to release notes and known issues notes.
5. Ensure that under the "Product Name" column the text "Not yet discovered" is not present.
6. Either wait for the collection time or change the collection time to current + 1 min and after collection generate reports
   1. Detail the steps to change collection time to current + 1min
7. Generate a Monthly Usage report
8. Ensure accurate vROps standalone and bundled reporting
   1. If standalone, verify the count of machines managed by vROps is what's reported
   2. If bundled, verify the usage falls into Premier-Plus or Premier-X Plus.
9. Complete.

NSX

1. Perform the common setup
2. Add one ore more NSX managers
3. Ensure that NSX is added successfully.
   1. Refer to release notes and known issues notes.
4. Either wait for the collection time or change the collection time to current + 1 min and after collection generate reports.
   1. Detail the steps to change collection time to current + 1min
5. Generate a Monthly Usage report
6. Ensure accurate NSX standalone and bundled reporting
   1. If standalone, verify the count of machines in clusters managed by NSX is what's reported
   2. If bundled, verify the usage falls into Premier-X or Premier-X Plus.
7. Complete

Usage Reports

1. Perform the common setup
2. Register all products with UM-35-Beta that you have registered with UM-Production
3. Confirm the accuracy of metering
   1. Create "Virtual Machine History" report on UM-35-Beta
   2. Compare "Virtual Machine History" report with what you see in your environment. Ensure that:
      1. All VMs are accounted for exactly once.
      2. There is no overlap of times when a VM is considered powered on.
   3. Create "Detailed Usage" report on UM-Production
   4. Compare "Virtual Machine History" with "Detailed Usage"
      1. Each machine mentioned in "Virtual Machine History" for the listed duration is also mentioned in "Detailed Usage" at the time mentioned in the "Detailed Usage" report.
4. Complete

Common Teardown

1. Power off and delete UM-35-Beta
2. Complete