In this section, we will focus our efforts on how do we quickly understand how all of our data centers are performing from a Capacity management standpoint. How can we quickly understand

• Which Datacenters are out of capacity?
• Which Datacenters are not sized correctly?
• Which Datacenters have the most opportunity for cost savings?

1. Click Assess Capacity
2. Click Criticality in the Group By section to view grouping options
3. Click the Dollar Sign to sort datacenters by cost.  In this Overview section, we get a list of Data Centers that are sorted by Capacity Time Remaining. We will detail cover how to modify these time remaining settings in the next lesson. In the next steps, we will cover how to change the view based on your capacity management intent. Lets try to find some issues between the Datacenters listed.
4. Click the Weight Balance icon to view Datacenters that are optimized
5. Click the Dollar Sign to go back to cost savings
6. Click lab-dc since that is the most expensive datacenter.  There is a potential of US $649 savings.  We can dive deeper into the cost savings more by reviewing the Optimization Recommendations.
7. Click msbu-east inside the Datacenter review screen.  We chose the msbu-east data center because it is red and time remaining is 0 days. This should be an area of focus as you go to this screen to identify capacity issues inside your environment.
8. Click right to see other Datacenters.  We can now quickly review other Datacenters in the list and toggle back and forth to compare Reclamation, Optimization, Cost, and forecast demand.
9. Click left to scroll back

Take a moment to understand what you can do in this Overview dashboard. Here are some use-cases you can think about. This can be more of an Operations dashboard that is actively working towards an SLA to ensure capacity is available but also looking for inefficiencies. That analysis can be difficult for an organization to identify.

Note how we see the datacenter msbu-east that has plenty of capacity and overall has the highest opportunity for cost savings by reclaiming resources.

When we look at the reclaimable opportunity for the lab-dc, there are plenty of different actions we can take drive more efficiencies. We will cover more about reclaimable capacity in Module 3.

In the Datacenter list at the top, we show a good amount of detail regarding

• How many days do you have left for capacity remaining
• What is the cost saving opportunity
• Is the Datacenter optimized?

You might want to group a handful of vCenter environments together that reside in the United States for licensing purposes. You can aggregate those instances in one Custom Data Center to simplify capacity management and reporting for the entire United States location.

1. Click ALL DATACENTERS to create a Custom Datacenter
2. Click ADD NEW CUSTOM DATACENTER
3. Type in US vCenters
4. Type in Aggregate of US vCenters for the description
5. Click to open vSphere World
6. Click msbu-vc-east
7. Click msbu-vc-west
8. Click OK
9. Click on the US vCenters Custom Datacenter
10. Click to Scroll Down

Now you can see clusters inside this custom data center for the US and predict their demand capacity remaining together.  You can also aggregate the Reclaimable VM's, view Cost Savings, and apply Optimization settings to this Custom Datacenter.

1. Click east-comp cluster
2. Click Down to review utilization
3. Click Up
4. Click Left to see more vCenters
5. Click msbu-east
6. Click the Memory Tab
7. Click to Scroll Down to cluster utilization. in this area, we highlight the new capacity management engine in vRealize Operations 6.7. By default, the system will navigate to the most constrained resource which is CPU in this case.
8. Click the Utilization Graph
9. Click the Projected Utilization.  Now on the lower portion of the screen, we have the new capacity demand confidence band. In version 6.7 we overhauled our capacity analytics engine and introduced a new AI Engine to give you a range of possibility based on the past utilization behavior. As soon as you complete a job of adding a host or a new workload to the infrastructure, you can immediately see the impact on your utilization. No longer do you need to wait a day for that impact to be assessed or apply many different policies to different workload types.  In this scenario, we are looking at memory utilization. The high and low probability are wide due to the variability of demand on this cluster.
10. Click east-comp Cluster
11. Click Memory tab
12. Click on the Current Utilization graph
13. Click on the Projected Utilization graph
14. Click Most Constrained from the drop down
15. Click Memory from the drop down

1. Type  mgmt into to filter
2. Click the Show History For drop down
3. Click 3 Months to see more history and align that with the projection
4. Click 1 Month since we only have data for one month
5. Click Show Forecast For drop down
6. Click 1 Month to make the graph half history, and half projected
7. Click on the projected growth to see the projected range of demand
8. Click CPU Tab
9. Click the top dotted line for utilization.  The dotted line is used for the time remaining metric.  Note how the projected utilization is now over 100 which makes the graph red
10. Click the Disk Space tab
11. Click to Scroll Down
12. Click to Scroll Back up
13. Clear out the Filter for mgmt
14. Click the Memory Tab
15. Click to Scroll Down

1. Click the Notepad
2. Click to Unlock Criticality Threshold
3. Click to Change Critical Threshold: Type 60
4. Click to Change Warning Threshold to Type 90
5. Click to Change time remaining level to Aggressive
6. Click Save.   As we move down the page, we see a Time Remaining for this data center which encompasses all the clusters and provides a quick way to see if we have capacity for the next 120 days. If we have 90 days of capacity, the score will move to red. In the previous releases of vROPs, you had to navigate through the policies to modify these settings.  You can now do that right here.
7. Click to Scroll Down
8. Click the New Projected Graph with the dotted line in the middle.
9. Click the CPU Tab and review the new time remaining Risk level.  The default Risk level is set to conservative. This setting will make sure that you have enough capacity for a worst case scenario based on workload utilization. Use this setting for ultra-conservative Production workloads.  Now that we have selected Aggressive, this setting uses the mean value of your resource utilization. Use this for Non-prod or for Production environments that are more mature with dynamic resource allocation like Automated Workload Balance covered in another module.
10. Click to Scroll Down
11. Review the Recommendations for Option 1 (Reclaim Resources) and Option 2 (Add Capacity).