Table of Contents HOL CMP - PDF Free Download

Table of Contents Lab Overview - - Optimize vsphere Capacity and Cost Savings with vrealize Operations... 2 Lab Guidance... 3 Module 1 - Assess Capacity of Your vsphere Datacenters with vrealize Operations (45 minutes)... 9 Introduction... 10 Hands-on Labs Interactive Simulation: Understanding and Forecasting vsphere Capacity... 11 Log in to the vrealize Operations Live Instance... 12 Capacity Allocation Dashboard... 16 Conclusion... 20 Module 2 - Identify Cost Savings and Automate Reclamation of Resources with vrealize Operations - (30 minutes)... 21 Introduction... 22 Log in to the vrealize Operations HVM instance... 23 Assess Cost Overview... 26 Cost Settings in Detail... 38 Conclusion... 44 Module 3 -Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations (30 minutes)... 45 Introduction... 46 Log in to the vrealize Operations HVM instance... 47 Reclaiming Capacity... 50 Reclaiming Resources from Oversized VM(s)... 62 Conclusion... 72 Module 4 - Capacity Planning with vrealize Operations (45 minutes)... 73 Introduction... 74 Log in to the vrealize Operations Live Instance... 75 Make a new Workload Scenario... 79 Private and Public Cloud What-If Scenarios... 90 Conclusion... 98 Page 1

Lab Overview - - Optimize vsphere Capacity and Cost Savings with vrealize Operations Page 2

Lab Guidance Note: It may take more than 90 minutes to complete this lab. You should expect to only finish 2-3 of the modules during your time. The modules are independent of each other so you can start at the beginning of any module and proceed from there. You can use the Table of Contents to access any module of your choosing. The Table of Contents can be accessed in the upper right-hand corner of the Lab Manual. In this lab we will cover customer scenarios for our new Capacity Management Engine as well as embedded costing information in vrealize Operations 6.7. Lab Module List: Module 1 - Assess Capacity of your vsphere Datacenters with vrealize Operations (45 minutes) Module 2 - Identify Costs Savings and Automate Reclamation of Resources with vrealize Operations (30 minutes) Module 3 - Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations (30 minutes) Module 4 - Capacity Planning with vrealize Operations (45 minutes) Lab Captains: Modules 1-4 - Nathan Schroeder, Cloud Management Engineer, USA This lab manual can be downloaded from the Hands-on Labs Document site found here: http://docs.hol.vmware.com This lab may be available in other languages. To set your language preference and have a localized manual deployed with your lab, you may utilize this document to help guide you through the process: http://docs.hol.vmware.com/announcements/nee-default-language.pdf Page 3

Location of the Main Console 1. The area in the RED box contains the Main Console. The Lab Manual is on the tab to the Right of the Main Console. 2. A particular lab may have additional consoles found on separate tabs in the upper left. You will be directed to open another specific console if needed. 3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All your work must be done during the lab session. But you can click the EXTEND to increase your time. If you are at a VMware event, you can extend your lab time twice, for up to 30 minutes. Each click gives you an additional 15 minutes. Outside of VMware events, you can extend your lab time up to 9 hours and 30 minutes. Each click gives you an additional hour. Alternate Methods of Keyboard Data Entry During this module, you will input text into the Main Console. Besides directly typing it in, there are two very helpful methods of entering data which make it easier to enter complex data. Page 4

Click and Drag Lab Manual Content Into Console Active Window You can also click and drag text and Command Line Interface (CLI) commands directly from the Lab Manual into the active window in the Main Console. Accessing the Online International Keyboard You can also use the Online International Keyboard found in the Main Console. 1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar. Page 5

Click once in active console window In this example, you will use the Online Keyboard to enter the "@" sign used in email addresses. The "@" sign is Shift-2 on US keyboard layouts. 1. Click once in the active console window. 2. Click on the Shift key. Click on the @ key 1. Click on the "@ key". Notice the @ sign entered in the active console window. Page 6

Activation Prompt or Watermark When you first start your lab, you may notice a watermark on the desktop indicating that Windows is not activated. One of the major benefits of virtualization is that virtual machines can be moved and run on any platform. The Hands-on Labs utilizes this benefit and we are able to run the labs out of multiple datacenters. However, these datacenters may not have identical processors, which triggers a Microsoft activation check through the Internet. Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft licensing requirements. The lab that you are using is a self-contained pod and does not have full access to the Internet, which is required for Windows to verify the activation. Without full access to the Internet, this automated process fails and you see this watermark. This cosmetic issue has no effect on your lab. Look at the lower right portion of the screen Page 7

Please check to see that your lab is finished all the startup routines and is ready for you to start. If you see anything other than "Ready", please wait a few minutes. If after 5 minutes you lab has not changed to "Ready", please ask for assistance. Page 8

Module 1 - Assess Capacity of Your vsphere Datacenters with vrealize Operations (45 minutes) Page 9

Introduction Rainpole Company Scenario Rainpole has recently experienced some issues managing their capacity for their virtual infrastructure. Due to the increase of demand for capacity and workload placement, they have seen hotspots inside their infrastructure and they need a way to monitor what areas need capacity based on workload demand. The new Capacity and Cost Engine in vrealize Operations 6.7 uncovers many new usecases for driving efficiencies as well as staying ahead of demand. In this module, we will identify how you can react better to these scenarios and promote better forecasting with cost visibility. This Module contains the following lessons: [Lesson 1 & 2] [Understand Capacity Management Overview] [Lesson 3] [Capacity Allocation Dashboard] Page 10

Hands-on Labs Interactive Simulation: Understanding and Forecasting vsphere Capacity This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment. 1. Click here to open the interactive simulation. It will open in a new browser window or tab. 2. When finished, click the Return to the lab link to continue with this lab. The lab continues to run in the background. If the lab goes into standby mode, you can resume it after completing the module. Page 11

Log in to the vrealize Operations Live Instance This lab environment is running three different instances of vrealize Operations and one instance of vrealize Log Insight. We have the different vrealize Operations instances in order to be able to work through different use cases that have unique requirements. The lab instances are as follows: Live Instance: Connected to the small running vsphere environment in the lab. There isn't a large inventory of objects in this instance but it allows us to interact with vcenter. Historical Instance: Running a 30-minute time loop of data that was captured in the past. This instance has a much larger inventory of objects but since it is not currently connected to a vcenter, we can't perform any actions here. Blue Medora Management Packs: Also running in historical mode, this instance has a large number of management packs from Blue Medora that allow us to see information from adjacent infrastructure (storage and physical servers) as well as operating system and application information. In this lesson we will be using the Live Instance of vrealize Operations. If you are already logged into the live (not historical) instance of vrealize Operations, click to skip ahead. Open the Chrome Browser from Windows Quick Launch Task Bar If your browser isn't already open, launch Google Chrome 1. Click the Chrome icon on the Windows Quick Launch Task Bar Page 12

Open the vrealize Operations - Live Instance Tab The browser home page has links to the different instances of vrealize Operations that are running in the lab. 1. Click the vrealize Operations - Live Instance link to open the UI in a new browser tab Page 13

Log in to vrealize Operations vrealize Operations is integrated with VMware Identity Manager which we will use for user authentication in this lab. VMware Identity Manager should be pre-selected as the identity source. However, if it is not you will choose it. Click the drop-down arrow 1. Select VMware Identity Manager 2. Click REDIRECT to take you to the user login page Page 14

VMware Identity Manager Login The user and password information should already be filled out. However, if needed type them in. USER: hol PASSWORD: VMware1! 1. Click Sign in Page 15

Capacity Allocation Dashboard Now that we have changed our Capacity Engine to look at only demand-based performance in vrealize Operations, there are many customers who still use an Allocation oversubscription model for virtualized environments. VMware recommends that you use the demand based modeling but switching over to a demand-based model cannot happen overnight. That is why we have created the Capacity Allocation Dashboard to rank how you are performing at the various tiers of oversubscription. Navigate to Capacity Allocation Dashboard 1. Click Dashboards at the top Capacity Dashboards 1. Click Capacity and Utilization from the Dashboards Start Page Page 16

Select Capacity Allocation Overview 1. Scroll down 2. Click Capacity Allocation Overview to navigate to that dashboard Capacity Allocation Overview Summary In this Allocation Summary, we see an inventory list of the various objects we have connected to vrealize Operations. For the purpose of resource allocation, vrealize Operations calculates vcpu/pcpu and vmem/pmem ratios to determine the amount of oversubscription across the environment. This is now out of the box in version 6.7! Page 17

Capacity Allocation Tiers Now we have our guidelines for oversubscription model for certain tiers of workload. Tier 1 applications that require dedicated performance Tier 2 workloads will have some oversubscription for CPU Tier 3 is meant for staging and test environments, not customer facing workloads Current Allocation Percentage for Clusters Here is where we get the most value out of this dashboard! We break down each cluster and identify where they fit into each oversubscription tier and by how much. This table view shows us inventory levels for resources. Looking at the CPU Allocation % 1:1 column, we see that the RegionA01-COMP02 cluster is 150%. That means we are 1.5:1 oversubscribed for CPU resources, which puts the cluster between Tier 1 and 2 from our Allocation guidelines in the previous page. Perhaps we would need more CPU resources if this were a Tier 1 workload. Page 18

Capacity Allocation Percentage Continued 1. Scroll to the right in the table. As we look further to the right we also see Memory allocation. Note how we are within the Tier 3 guidelines for memory in both clusters. Also note that this view is named Current Allocation Percentage for Clusters. This would be a great report to send to your management within the Rainpole organization to help identify when you need to procure more resources. Page 19

Conclusion In this module, we provided an overview of what is new with Capacity Management in vrealize Operations 6.7. We learned about the difference between Demand and Allocation capacity modeling. In the next modules, we will focus on how to apply cost information to these objects and run What-if Capacity Management scenarios that you can take back to your organization. You've finished module 1 Congratulations on completing the module. If you are looking for additional information on vrealize Operations, you can start here: https://www.vmware.com/products/vrealize-suite.html If you want to jump to a particular module, follow one of the links below. Module 2 - Identify Costs Savings and Automate Reclamation of Resources with vrealize Operations Module 3 - Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations Module 4 - Capacity Planning with vrealize Operations Or if you want to end your lab, 1. Click on the END button at the top of the page. Page 20

Module 2 - Identify Cost Savings and Automate Reclamation of Resources with vrealize Operations - (30 minutes) Page 21

Introduction In the new release of vrealize Operations 6.7, we have added a cost engine to help calculate basic infrastructure costs. This is meant for the Infrastructure admin to understand their current costs broken down by each infrastructure component. This does not replace what vrealize Business currently does, which provides more capability like show-back, cloud, and data center cost comparison analysis. Rainpole has also been caught by the ever-increasing budget requirements for adding capacity, and they would like to do some very simple cost modeling on the requests they get from the organization. This will help the IT Director communicate back to the business what growth costs are. Page 22

Log in to the vrealize Operations HVM instance This lab environment is running three different instances of vrealize Operations and one instance of vrealize Log Insight. We have the different vrealize Operations instances in order to be able to work through different use cases that have unique requirements. The lab instances are as follows: Live Instance: Connected to the small running vsphere environment in the lab. There isn't a large inventory of objects in this instance but it allows us to interact with vcenter. Historical Instance: Running a 30-minute time loop of data that was captured in the past. This instance has a much larger inventory of objects but since it is not currently connected to a vcenter, we can't perform any actions here. Blue Medora Management Packs: Also running in historical mode, this instance has a large number of management packs from Blue Medora that allow us to see information from adjacent infrastructure (storage and physical servers) as well as operating system and application information. In this lesson we will be using the Historical Instance of vrealize Operations. If you are already logged into the historical (not live) instance of vrealize Operations, click here to skip ahead. Open the Chrome Browser from Windows Quick Launch Task Bar If your browser isn't already open, launch Google Chrome 1. Click the Chrome icon on the Windows Quick Launch Task Bar Page 23

Open the vrealize Operations - Historical Instance Tab The browser home page has links to the different instances of vrealize Operations that are running in the lab. 1. Click the vrealize Operations - Historical Instance link to open the UI in a new browser tab Page 24

Log in to vrealize Operations 1. If Local Users is not the default, click the drop down as shown and click Local Users Enter user credentials. Username is admin and password is VMware1! 2. Click LOG IN Page 25

Assess Cost Overview In this section, we will learn more about what is available in the Assess Cost link from the Quick Start page. We want to do this now so we understand the costs and make sure they are relevant in regards to the Rainpole infrastructure environment. We then can use this data to understand how much benefit there is for reclamation, capacity scenarios, and overall reporting. Click Assess Cost 1. Click Assess Cost Assess Cost information Page 26

We get an overview of assets and total cost of ownership for assets connected to vrealize Operations. This includes Total Cost of Ownership and Potential Cost Savings for all vcenter children objects connected to vrealize Operations. TOTAL COST OF EACH DATACENTER In this screen, we see a breakdown of each data center with its associated configuration and reclamation opportunity. Items included here are... 1. Total cost for each Datastore 2. Reclaimable vcpu's 3. Reclaimable Memory 4. Click the column name at the top, this will sort via ascending/descending. Make sure to scroll to the right to see reclaimable disk space as well! List of Most/Least expensive clusters We also have a couple of views that sort the most and the least expensive clusters. Think of this as How well am I driving density inside my infrastructure? or Why are the costs so much more expensive in this cluster compared to another? This will lead to more discussions with your peers and leadership to make your infrastructure more efficient. Page 27

1. Double-click the most expensive Cluster (east-comp) Looking for Cost detail Now we will understand why the east-comp cluster is the most expensive. 1. Select All Metrics All Metrics 1. Open All Metrics 2. Open Cost Page 28

Monthly Cluster Cost 1. Double Click Monthly Cluster Total Cost 2. Double Click Monthly Cluster Total Memory Cost 3. Double Click Monthly Total Cluster CPU Cost Page 29

Cost Breakdown Now we see each metric represented graphically on the right side of the screen. 1. Total Cost 2. Cost for Memory 3. Cost for CPU Example: CPU Cost (1568.84) > Memory Cost (1175.27) We can then come to the conclusion that CPU costs more in this cluster. Go back and repeat for the least expensive cluster (the lab-auto cluster). How do they compare? Page 30

Can we reclaim? Since east-comp is the most expensive cluster, lets go see if we can reclaim some resources and eventually perform some workload optimization to consolidate some of our clusters. 1. Select the Home Button Select Reclaim 1. Select Reclaim Page 31

Open the Datacenter 1. Click msbu-east is selected if not already Open east-comp Cluster 1. Select Oversized VMs 2. Open east-comp Page 32

Review Right-Size List 1. Scroll down to review the reclamation list Review the Oversized VM's Review the long list for reclamation. 1. Scroll back up Page 33

Select All and Reclaim 1. We can reclaim up to 28 vcpu's in this cluster 2. Select all to reclaim. 3. Select RESIZE VM(S). Resize Screen Once the Resize VM(s) screen comes up. 1. Click Cancel Since this is not a live environment, we will not be able to actually resize the VM's. If you would like to run this action, please change to the live vrealize Operations enviroment. Page 34

Identify Cluster CPU Capacity Now, continuing with this scenario, I wonder how much demand there is on CPU for this cluster, since it is more expensive compared to memory? 1. Click the Home Button again. Assess Capacity 1. Click Assess Capacity Page 35

Select Cluster 1. Scroll Down and select east-comp again Page 36

Review CPU Demand 1. Make sure CPU is selected 2. Look at the CPU utilization for this cluster. It is at 23%, and the projected range is very flat. Do we need this cluster to be this large and expensive? Based on the data and the cost analysis that highlight how expensive the cluster is, we do not need this much capacity. Perhaps we should consolidate some workloads to this cluster or repurpose somewhere else? Lesson Conclusion In this Lesson, we used the Assess Cost feature to determine where the most expensive cluster is in this environment. We then identified what was the most expensive resource (CPU) in this cluster and wanted to see CPU utilization. The CPU utilization was low, and we identified that we could remove a host or implement workload optimization to use up the expensive CPU resources. Page 37

Cost Settings in Detail Now we dive a little deeper into the cost settings that vrealize Operations is applying to objects. Navigate to Cost Savings To access the costs settings, click on: 1. Administration at the top 2. Expand the Configuration section 3. Select Cost Settings Cost Settings - Financial Account Model The costs represented in this screen are downloaded from a VMware reference database. This may not be what you paid for your internal infrastructure. Lets get it more accurate for reporting purposes. Before we start changing server costs and etc, Page 38

we must first change how we are depreciating the assets effectively. If you do not know the answer to this question, please contact your leadership or IT finance department. 1. Select the Gear symbol next to Cost Settings. Financial Account Model Within the Cost Settings we can change the years of depreciation (How long before you refresh your servers?). We also have Straight Line and Double depreciation calculation. 1. Modify to 4 years depreciation 2. Select Straight Line depreciation model 3. Click Save Cost Drivers Page 39

As we look at the Cost Drivers we get a breakdown of cost per infrastructure component. For our Rainpole organization we want to start very simplified so we can show infrastructure costs as new projects are planned. Modify Cost Settings For this scenario we are going to $0 out some of the subjects here since the Rainpole organization would like to focus on compute costs. 1. Select Facilities Facilities Detail 1. Scroll Down to the bottom to enter detailed cost of facilities. Page 40

Modify Facilities Costs Here you can modify your facility costs for your data center. For this scenario, since the Rainpole organization only wants to report Compute Costs, we will $0 these numbers. 1. Input 0 for Power and Cooling monthly cost 2. Input 0 for Total Operational monthly cost per rack unit 3. Select Save Back to Cost Drivers 1. Scroll up 2. Select Back To Cost Drivers Page 41

Comparison with Industry benchmark Now we see a new graph in the middle of the list that shows us how our modified changes compares to the reference database. 1. We see an existing change with Server Hardware that is 7.55% less than industry benchmark 2. We see our change to Facilities, which is 100% less than industry standard. Total Cost Now we see the total cost for all adjusted components. Page 42

Cost Calculation Status Now that we have changed the cost settings, we need to run a manual re-calculation to propagate these changes through the rest of the objects. 1. Click Cost Calculation Status 2. Select Run Depending on the size of your environment, this may take some time to complete. We will let this run in the background to propagate our cost settings. By default, vrealize Operations will run this updated calculation everyday at 9:00PM (Appliance Time). Page 43

Conclusion In this module, we provided an overview and went into detail how you would use the embedded cost engine that is now part of vrealize Operations 6.7. We also went into the cost settings, and modified the depreciation model as well as adjusted certain infrastructure cost settings to align with the Rainpole organization. You've finished module 2 Congratulations on completing the module. If you are looking for additional information on vrealize Operations, you can start here: https://www.vmware.com/products/vrealize-suite.html If you want to jump to a particular module, follow one of the links below. Module 1 - Assess Capacity of your vsphere Datacenters with vrealize Operations Module 3 - Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations Module 4 - Capacity Planning with vrealize Operations Or if you want to end your lab, 1. Click on the END button at the top of the page. Page 44

Module 3 -Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations (30 minutes) Page 45

Introduction Due to the rapid velocity of demand at Rainpole in the last year, they know they have over allocated VM(s) now that are not consuming all their resources. In parallel, with the new capacity management initiative, they would like to start reclaiming resources based on VM demand. Another side effect of their growth has been the negative impact to their organizational activities. Common activities like maintaining snapshots, identifying idle workloads, and managing powered off systems have been forgotten. In this Module, we will show how you can automate these activities. This Module contains the following lessons: [Lesson 1] Reclaiming Capacity [Lesson 2] Reclaiming Resources from Oversized VM(s) Page 46

Reclaiming Capacity In this Module, we will work on reclaiming old and oversized resources at the Rainpole organization. We will work on understanding the new reclaim resources page on the new Quick Start page in vrealize Operations 6.7. Home Screen 1. Select the Home button if continuing from the previous module. Go to Reclaim 1. Go to Home if continuing from previous module 2. Select Reclaim on the Quick Start Page Page 50

Open All Datacenters 1. Click ALL DATACENTERS Reclaim Settings In the Reclaim screen, we can see a list of vsphere Data Centers, Custom Data Centers, and VMware Cloud on AWS. Just like the Capacity screen, we can sort these Data Centers by Time Remaining Cost Optimized Reclaim Filter In the drop down filter Page 51

1. Select the drop down. 2. Select vcenter New Criticality View You can see each break down by vcenter or by datacenter. Reclaim Settings Now go and click the gear icon next to the Reclaim screen title. Page 52

Settings in Detail This is where we select how long we want to look for the reclamation opportunities to be reported. Also note that you need 7 days of data for a resource to populate this list. Make sure to have cost settings enabled so you can see how much money can be saved for each reclamation opportunity. If you don't want to have one of the reclamation opportunities listed, go ahead and uncheck the box and click Save. 1. Click Save Select Resource Since the msbu-east virtual center has 0 days remaining. 1. Click the msbu-east virtual center. Page 53

Overall Reclamation opportunity For the msbu-east datacenter, we can see the overall reclamation opportunity. Since this resource has the lowest time remaining, going through reclamation opportunity is the best way to add capacity without purchasing new hardware. Filter Reclamation resources In this scenario, for the Rainpole organization, rather than execute reclamation for all workloads, the organization would like to test out the reclamation for a subset of workloads. For this scenario we will filter for workloads with the name "east". 1. Select the filter area and type " east " 2. Hit Enter Page 54

POWERED OFF VM RECLAMATION Now that we have filtered for "east", we will look at the reclamation opportunities starting from left to right. Notice the options near the bottom of the screen (Powered Off VMs, Idle VMs, Snapshots and Oversized VMs). We displayed these reclamation opportunities in this order for a reason. We recommend starting with Powered Off VMs, because this is usually the easiest place to reclaim resources. In most cases, these VMs are often the result of forgotten projects. Reclaiming these will free up storage space. 1. Click on Powered Off VM(s) 2. Open the Cluster east-comp 3. Select the VM to delete. 4. Select DELETE VM(S) button Since this is not a real a live environment, we won't be able to actually delete the VM(s). Delete VMs In the Delete VMs pop up, you can see how many VM's will be deleted, how much savings are possible, and the disk space savings. Page 55

Since this is not a real a live environment, we won't be able to actually delete the VM(s). 1. Select Cancel IDLE VM RECLAMATION Next Tab is Idle VMs. Idle VMs identify workloads that are not showing much demand inside the datacenter. In this selection, we have another action button, Power Off VM(s). If you are not sure if the user is actively using the VM(s), you can first start with the power off option. 1. Click the Idle VMs tab 2. Open east-comp 3. Select all 4. Select Power Off VM(s) Reclamation Action 1. Select POWER OFF VM(S) Note that you cannot actually Power Off these VM(s) since this is a historical instance. Page 56

Snapshots Next, we will look at the Snapshots tab. In this list, we are looking for snapshots that are older than 2 days old. With the east filter we don't see any workloads that have old snapshots for these VM's. 1. Select Snapshots Tab Remove Filter 1. Delete the " east " filter in the highlighted section 2. Hit enter Clear Filter Now we see workloads in the east-mgmt datacenter. Page 57

1. Expand east-mgmt datacenter Select VM to Exclude What if we want to keep Snapshot from this list? We now have a simple exclusion list. We can identify VMs that we do not want to include in the select all DELETE SNAPSHOTS reclamation action. 1. Scroll down to the bottom 2. Find the resource that has the most recent snapshot 3. Select SAP-HM13 Exclude VM 1. Scroll Back up 2. Select EXCLUDE VM(s) Page 58

Review Exclude VM Message Review the information from the Exclude message. 1. Select EXCLUDE VM(S) Show Excluded VM's Now we will review the Exclusion List. 1. Scroll Down 2. Select SHOW EXCLUDED VMS Page 59

Review Excluded VM's Note that we now see the SAP-HM13 machine again in the exclusion list. But if we change our mind, we can add it back to the Snapshot Reclamation list by following the procedure below. 1. Select SAP-HM13 2. Select INCLUDE VM(s) Back to Snapshot List 1. Scroll Back down 2. Open east-mgmt Cluster East DC List of Snapshots Page 60

1. Select Snapshots 2. Select the box to select all VM's 3. Select Delete Snapshots Savings for Snapshot Reclamation When we select Delete Snapshots, we now see... How Many VM's Costs Savings for this reclamation Storage Space Saved by deleting these snapshots Note- If you select Delete Snapshot there will be an internal error since this is a historical instance of vrealize Operations. Page 61

Reclaiming Resources from Oversized VM(s) In this scenario for RainPole organization, rather than execute reclamation for all workloads, the organization would like to test out the reclamation for a subset of workloads. We made some enhancements in regards to the Reclaiming of resources as well as how we identify reclamation inside of vrealize operations 6.7. Automated Right Size Actions As you will see in this module, it is much easier to perform rightsizing capabilities easily at scale, with enhanced filtering, and automated actions. New Right Sizing Capabilities Page 62

In this version, we now investigate OS Metrics for Right Sizing recommendations without an agent! To automate and speed up reclamation, we have implemented a stepped approach for Right Sizing. Total Reclaimable Capacity In this scenario, for RainPole organization, rather than execute reclamation for all workloads, the organization would like to test out the reclamation for a subset of workloads. 1. Type east to filter 2. Press Enter to initiate the filter Select Oversized VM(s) For our final reclamation opportunity, we will look at... 1. Select Oversized VM's Page 63

2. Open up the east-mgmt data center 3. Select the selection box at the top and click resize VM's. 4. Select Resize VM(s) Review Reclamation Changes Now we get an overview of the recommended changes for the selected VM's. If we select the pencil, we can edit the actual recommendations inside this screen. 1. Click the pencil to edit the recommendation. Edit Reclamation Recommendation 1. Change the size of the memory from 4 to 6GB and press Enter. Understand Reclamation Changes At the bottom of Resize VM's overview we understand Page 64

1. How much resources will be reclaimed 2. A disclaimer that states if you continue the VM will be restarted 3. Click Cancel to close the dialog Note - since this is a historical lab, the reclamation will not work. If you would like to try resizing, you can repeat this process in the live instance of vrealize Operations. Navigate to Overview of Optimize Performance Now that we have reclaimed some VMs and we like how the new features perform in vrealize Operations 6.7. Let's run a report for the Rainpole leadership that summarizes how much resources can be reclaimed. First, let's look at other areas where vrealize Operations lists oversized VMs, Optimize Performance. 1. Click to open Optimize Performance 2. Click Overview Page 65

Review Total Reclamation List Scroll down to the bottom of the page where we see the Oversized Virtual Machines View. This is the same view used for the Oversized VM report. Back to Dashboards 1. Click on the Dashboards link at the top of the menu. Reports 1. Select Reports on the left side menu. Page 66

Filter for Oversized Report 1. In the filter section on the right type in oversized Run the Report 1. Run the report by clicking Run Template Page 67

Configure Source 1. Select vsphere World, which is an aggregate of all vcenters 2. Select OK Generated Report 1. Click on Generated Reports Page 68

Review the Report When the Report status changes to Completed... 1. Review the report via pdf or csv on the links to the right Report Formats 1. Save to default location Page 69

Open the Reports 1. Click the download link at the bottom of Google Chrome. Review Reports 1. Scroll down to review your results as well as the sum total at the bottom of the report. Close the HVM Instance Page 70

1. Close the tab in Google Chrome Page 71

Conclusion In this module, we learned how to effectively reclaim resources with ease using vrealize Operations. We saw that, with the Capacity Management module, we can reclaim these resources while decreasing the potential for mistakes. We also learned that, with the new Cost Engine now included with vrealize Operations, we can more quickly focus our efforts on workloads that are costing us the most money. You've finished module 3 Congratulations on completing the module. If you are looking for additional information on vrealize Operations, you can start here: https://www.vmware.com/products/vrealize-suite.html If you want to jump to a particular module, follow one of the links below. Module 1 - Assess Capacity of your vsphere Datacenters with vrealize Operations Module 2 - Identify Costs Savings and Automate Reclamation of Resources with vrealize Operations Module 4 - Capacity Planning with vrealize Operations Or if you want to end your lab, 1. Click on the END button at the top of the page. Page 72

Module 4 - Capacity Planning with vrealize Operations (45 minutes) Page 73

Introduction In this module, you will use the new Workload Scenario feature which is integrated with our new Capacity Engine to understand how a new project inside your organization may impact capacity. Additionally this tool will provide guidance for workload Placement in your data center. Lesson 1: Make a New Workload Scenario Lesson 2: Public and Private Cloud What-If Scenarios Page 74

Log in to vrealize Operations vrealize Operations is integrated with VMware Identity Manager which we will use for user authentication in this lab. VMware Identity Manager should be pre-selected as the identity source. However, if it is not you will need to choose it. Click the drop-down arrow 1. Select VMware Identity Manager 2. Click REDIRECT to take you to the user login page Page 77

VMware Identity Manager Login The user and password information should already be filled out. However, if needed type them in. USER: hol PASSWORD: VMware1! 1. Click Sign in Page 78

Make a new Workload Scenario Rainpole has recently experienced some issues managing their capacity for their virtual infrastructure. Due to the increase of demand for capacity and workload placement, they have seen hotspots inside their infrastructure, and they need a way to monitor what areas need additional capacity based on workload demand. Another issue in addition to forecasting capacity management is which clusters should they land the additional workloads? Rainpole has experienced contention issues because they do not know holistically which cluster these workloads should land. In vrealize Operations 6.7 since we overhauled the new capacity engine there are new enhancements in how we calculate capacity from the Guest OS perspective. With that change, we have added new scenarios for adding VM workloads. In this scenario, we will replicate all workloads. Navigate to Plan 1. Click the Plan link to go into workload planning Page 79

New What-if Analysis In the workload scenario screen, you can work out scenarios to see if a certain project can fit in any of your clusters inside a data center. For this example, we are first going to create a new scenario that will include expected utilization for a certain size. 1. Click Select inside the Add Workload box Add Workload Scenario 1. New Rainpole Project 2. Select the Datacenter RegionA01 (vcsa-01a.corp.local) 3. Allow this workload to be on Any cluster Page 80

New VM Configuration Scenario Now we will build out the configuration Make a VM configuration 1. 1 vcpu 2. 2 GB Memory 3. 20 GB of storage Expected Utilization Since the capacity engine bases capacity statistics from demand, we should add what the expected utilization is for this project. If you don't have that information, you could always select 100% to be on the safe side. However, since we rarely experience that level of utilization, for this scenario, we will set our expected utilization to 20%. 1. Change Expected Utilization to 20% Advanced Configuration 1. Select ADVANCED CONFIGURATION Page 81

Advanced Utilization When you think of demand again, you rarely have a consistent demand utilization across all compute resources. In the Advanced Configuration dialog, you granularly set utilization for each compute resource. In this scenario, we will modify utilization to the settings below. You can also configure the scenario to reserve storage space based on thin or think provisioning. 1. Click the radio button for Thin. 2. CPU = 50% 3. Memory = 20% 4. Storage = 20% Save Scenario 1. Click Save so we can come back to this scenario Page 82

Open Scenario 1. Select the New Rainpole Scenario 2. Click Run Scenario Will it fit? A screen will appear that will indicate the impact of this What-if Analysis. As you will see, there is NOT enough capacity in RegionA01-COMP01 Will Additional Cluster Fit? There is also an option to look at other clusters that could fit the project. 1. Click the drop down arrow to view additional clusters Page 83

Review detail on other clusters Additionally, we can see that the cluster 'RegionA01-COMP02' also does not appear to have enough capacity for this workload. Change the capacity forecasting settings We do not have enough capacity in either cluster. In Module 1 of this lab, we used an interactive simulation to show how setting Risk Level to Aggressive would allow for more capacity while adding some additional risk for contention. Let's go back and change it to the aggressive setting to see if any of the clusters will now have capacity. 1. Select Overview on the left Menu screen Open Datacenter 1. Click RegionA01 Page 84

Edit Risk 1. Click the Edit button next to 0 days remaining until Memory runs out. Page 85

Change Risk Level Change the Risk level to Aggressive. 1. Click the little lock icon 2. Select Aggressive 3. Select Save When set to Conservative, capacity forecasts for our clusters are made per the peak demand levels of our resources. If this was a non-prod environment, we could possibly fit more workloads in the clusters by changing the Risk Level to Aggressive, since vrealize Operations would forecast available capacity per the mean level of demand for each cluster. Page 86

Go back to What-if Analysis We will now go back and run the analysis and see the results again. 1. Select What-if Analysis Run Scenario Again 1. Select New Rainpole Project 2. Run Scenario View Details Now that we changed the capacity settings, we now have adequate capacity! Lets view the details with the new capacity scenario. 1. Click View Details Page 87

Detail on Demand Growth In the Scenario Results we see: Cost Impact of the project CPU Demand Increase Memory Demand Increase Storage Demand Increase Forecasted Demand Growth 1. Continue to scroll down to the bottom Page 88

2. Hover your cursor over the line so we can see the Projected Utilization with and without the Scenario. Click the Home button to return to the Quick Start page. Page 89

Private and Public Cloud What-If Scenarios In this lesson, we will get more advanced with the capabilities of the What-if Scenarios that are possible in vrealize Operations 6.7. By adding existing workloads to a What-if scenario plan, we can quickly compare costs of cloud providers. For the Rainpole organization, they are experiencing real frustrations on how long it takes to deploy new infrastructure capacity. Currently, there is a long lead time to procure hardware, as well as getting it racked and stacked in their environment. This, in turn, has had an impact on the ability to start new projects that were important to their business of developing new services. With new technologies like VMware Cloud on AWS, vrealize Operations can help their organization to understand capacity and the costs for bursting out to the Public cloud providers. Plan 1. Select Plan Page 90

Add Advanced Workload Scenario 1. Click Select Add Advanced Workload 1. Add Rainpole Advanced Project in the Scenario Name 2. Select RegionA01 3. Keep Any cluster in the drop down Configure the Application Profile Page 91

1. Select Import from existing VM Select VMS 1. Select VMS Make a full App Tier Scenario Page 92

Double-click 1. Double Click "app-01a", "db-01a", and "web-01a". 2. Select OK Review the Selections After we have selected the workloads for the project, we can see the actual demand of the workloads. On the right side of this screen, we can also select the pencil button to add to the quantities for each of these workloads. Run Scenario Select Run Scenario Page 93

Scenario Results As you see, we do not have enough capacity for this project scenario. Utilize Public Cloud Modeling 1. Scroll Down Page 94

VMWare Cloud Capacity We will now explore the Public Cloud Modeling capabilities. 1. Click on LEARN MORE within VMware Coud. While exploring the new vrealize Operations, the Rainpole organization was able to find a potential solution inside of the new Public Cloud capabilities. Perhaps the Rainpole organization would like to burst out to a cloud provider and research what that would cost? With the embedded cost engine, and our integration with VMware Cloud on AWS, and AWS EC2, we can understand those differences. Public Cloud Demand After selecting LEARN More, we get a breakdown of the costs and the impact this workload scenario would have on the VMware Cloud on AWS solution. We see... 1. What the project utilization will be (note that your values may vary in the lab environment) Page 95

2. The demand for this project per host 3. The Capacity overall on each host Please keep in mind that the overall cost is for a minimum of 4 hosts in AWS. There will be much more capacity to consume after your first project. Total Cost for VMC on AWS Now we have a breakdown on the different consumption models you can deliver with VMware Cloud on AWS. Here is a breakdown on each consumption model. 1. On Demand - Use this for adhoc builds that you do not have capacity for, but don't need very often. 2. 1 Year Subscription- You know you have a lot of demand but want to evaluate VMware cloud for 1 year and plan to utilize these resources to fill up the 4 hosts required. 3. 3 Year Subscription - You decide you are making management of your infrastructure easier with VMC on AWS and are planning to move workloads to this offering in scale and you want to get the best price by subscribing to the 3 Year agreement. Page 96

Understand costs between different subscription models Please take note of the guidelines for these What-If Scenarios, particularly if you have a special discount that needs to be applied. 1. Select Edit Discount to enter your discount. Add Discount Percentage 1. Enter your discount as is appropriate 2. Click save Page 97

Conclusion In this module we went deep into the new Capacity Planning What-If scenario. We explored the new enhanced capabilities within vrealize Operations 6.7 and also mentioned some of the items that are not available compared with earlier versions of vrealize Operations. You've finished module 4 Congratulations on completing the module. If you are looking for additional information on vrealize Operations, you can start here: https://www.vmware.com/products/vrealize-suite.html If you want to jump to a particular module, follow one of the links below. Module 1 - Assess Capacity of your vsphere Datacenters with vrealize Operations Module 2 - Identify Costs Savings and Automate Reclamation of Resources with vrealize Operations Module 3 - Predict Resource Demand and Identify Capacity Shortfalls with vrealize Operations Or if you want to end your lab, 1. Click on the END button at the top of the page. Page 98

Conclusion Thank you for participating in the VMware Hands-on Labs. Be sure to visit http://hol.vmware.com/ to continue your lab experience online. Lab SKU: Version: 20181104-102941 Page 99