Skip to main content

vROPS- Capacity Remaining What Will Fit?

I have been using vROPS for a few months now and noticed that under "Capacity Remaining" tab there is a section "What Will Fit". 


As you can see vROPS has already done some analysis based on the metrics it has collected in your environment. If you click on the down triangle it will tell you what metrics it is using to base on that assumption


From the above diagram "Average Profile" it tells us that my cluster is over provisioned by 81 VMs and the specs it has used to help give the number. As you can see this is based on "Demand". In my environment we are doing capacity by "Allocation" and also we deploy VMs with specific configurations for different clusters. So how do we do that ?

On the same screen click on the right or left arrows until you see the "+" sign and click on this


A new screen will prompt up

  • Give the profile a name which will be display name as well
  • Leave the object type as "Virtual Machine" 
  • Decide if you want this to be used for all policies and if they are then tick box "Enable this profile for all Policies" otherwise under the "Advanced" section decide which policies you would like to enable or hide the profile from.
Use the scroll bar to go further down the options


  • Under Metrics section decide on the filter (model) which is either "Allocation" or "Demand". In my case we are using "Allocation" so I will select this one. 
  • You have a option to then either import metrics from an existing VM or type in the values you wish to set then click "OK"
You will now see your newly added profile under the "What Will Fit" but the number of VMs are shown as "?". Depending on the size of your environment that should change to a number once it has worked out what is should be


What if I want to change the setting of this?
  • Click on  "Content" icon

  • Select "Custom Profile" and on the right navigation panel highlight the server you wish to edit. Click on the "Pencil" to edit
 

  • You can now editing the settings and then click "OK"
 



Comments

  1. Have you ever noticed that the calculation done gives you different results depending on where you click? Happens in the current version 6.2 for example.

    Let's say you have a cluster of two hosts:

    It might be (or better: it is the case in my environment) that the overall cluster object says "Only 1 VM sized XL will fit" into that Cluster, but if you click on either of the hosts in that cluster each host alone one would allow 6, 7 or 8 VMs that could be deployed. So instead of showing 14 VMs on this Cluster it would show 1 VM only. Makes no sense and we're having this investigated by VMware currently.

    ReplyDelete
  2. Did VMware get back to you on your problem. When you say different result depending on where you click, which objects are you clicking?

    ReplyDelete

Post a comment

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net