This post continues from the Operationalize Your World. Do read it first to get the context.
Read the whole instruction first, before executing the steps.
- Decide which clusters and datastores are on what Service Tier. This is the most crucial step.
- If you are doing IaaS business, you should have at least 2 policies. That’s why I have not thought of a business scenario where you only have 1 policy.
- You choose per cluster, not per resource pool. The Policy is applied at cluster level. I do not use Resource Pool. It complicates matters operationally.
- If you have no Performance SLA, you have a bigger problem than IaaS monitoring.
- You can place VM on Tier 1 Compute and Tier 2 Storage, although that just makes your operations complex. It’s like giving economy class passenger a business class TV & meal.
- vR Ops Advanced edition or higher. Standard edition does not allow custom dashboard.
- vR Ops 6.7.
- It does use 6.7 specific properties.
- I’m afraid it will not work with 6.6
- Hands-on with vR Ops 6.7. I assume you know what you’re doing.
- Have an ID with admin privilege.
- Do not use the built-in Admin account. It creates confusion between OOTB content and what you create.
- Download the files here.
- The zipped files contain zipped files. No need to unzip the zipped files.
The steps can be grouped into 4 parts:
- Part 1: Metrics
- Enable these metrics (they were disabled in 6.7)
- Part 1: Super Metrics & Policies
- Import the super metrics
- In your active base policy, enable the
- super metrics
- metrics stated here.
- Create 1 policy for each service tier.
- Ensure it’s a child of your active/base policy. It’s the one with the D.
- Part 2: Group
- Create the group types.
- Import the groups.
- Modify the group selection criteria. I use a Custom Datacenter as it’s easier.
- Part 3: View & Dashboards
- Import the Views
- Do this prior importing the dashboard as there is dependency
- Import the Dashboards.
- Importing dashboard automatically creates the menu structure
- Recreate the XML files
After import, you can customise the Large VMs, Idle VMs, Powered Off VMs group. For example, I used large VM as those with >8 vCPU or >24 GB RAM.
Watch the 12 minute video, then read the steps below. Apology that the video is based on 6.6, not yet updated to 6.7. Some screenshots are from earlier version, as they are still functionally the same.
Follow the names exactly. They are hardcoded in the dashboards.
Names are Case Sensitive!
If you do not follow, import will work, but you get hourglass icon.
Part 1: Super Metrics and Policy
Import the super metrics. If you are curious the list of super metrics you are getting, the list looks something like this. Yes, heaps of them!
Once imported, enable the super metrics in your Default policy. Yes, you can bulk enable by selecting multiple lines (as shown below). Use the Actions menu to enable them all.
Optional step: review the Performance SLA super metrics settings. Adjust the SLA accordingly if you know the performance of your IaaS. If you are running Balance power management, change the CPU SLA to 10, 20, 30 accordingly.
Create 1 policy for each Tier. This has to be based on your active policy, so the inheritance works properly. Make sure you choose the right one.
You must use the following names for the Policy:
Enable the correct SLA for each tier. In the example below, I’m enabling Tier 2. From the big red number 1, you can see I’m editing a policy named Tier 2. You can see it’s being selected in the background, behind the dialog box.
See the big red number 2: It shows the Performance SLA that should belong to Tier 2. As a result, I only enabled them (see the big red number 3). The easiest is to specify “Tier 2” in the filter, so only Tier 2 super metrics are shown. I do not enable the super metrics for Tier 1 (see the big red number 4).
Here is the Enable example:
Click Save to end the editing.
Part 2: Group Type and Group
Create these group types carefully:
- Class of Service
- VM Types
- Multi-tier Applications
- Application Tier
Your group import will fail if you do not have the group type.
If you mistyped and saved it, do not edit it to correct it. Delete it, and create a new one. The reason is the key wasn’t updated when you edit, only the label.
Once created, import the groups.
For the Service Tiers groups, you need to associate them to the correct policy. To do that, edit the group, and choose the respective policy. The following example shows for Tier 2.
Do the same steps for Tier 1 (Gold) and Tier 3 (Bronze).
BTW, you can also assign the policy to its associated group via the policy library. Your choice. Below is an example. Use the green plus sign, as I circle it below:
You know you got the policy associated when it appears in the Active Policies. The screenshot below show I’ve activated all 3 Tiers
Part 3: View and Dashboard
Import the view, then the dashboard. Choose Overwrite if you’re importing for the 2nd time, or have the old Operationalize Your World views/dashboards.
The lists shown below is partial. There are >100 in total.
Import the Dashboards. When you are done, it looks something like this.
Recreate the XML files. They cannot be imported. I use copy paste, even on the file names.
Once imported, take your well deserved coffee break! It you have a large environment, it can take an hour for all the dashboards, super metrics, policies, groups, to be applied. During the process, you may see the known error while trying to open a dashboard. Just wait an hour or so.
When things go wrong
If your dashboard has hourglass icon, likely it’s because a metric or object is missing. The root cause is likely a missing group.
You should not need to do any of these things. But if things go wrong, there are a couple of things you can check. First, ensure each Policy actually applies to the correct object. For example, you can see below that I’ve applied the policy named Tier 2 to a group called Tier 2. Under the Assigned Groups, column, it shows it’s being applied to 1 group and it impacts 302 objects.
The same goes with super metrics. In the following example, a super metric is being applied to Tier 2 policy. It’s not applied to other policies, as it does not make sense.
If import fail, you will see the error message. Simply rename the duplicate object, then reimport.
You cannot re-import. The reason is the ID remains the same. Delete the existing object, then reimport. It is safe to delete.
Hope you find the material useful. If you do, go back to the Main Page. It gives you the big picture so you can see how everything fits together.