vRealize Operations Manager 6: How to create Projects

vRealize Operations Manager 6: Resource Capacity Concepts

One of the primary things you must learn to use  in the correct way the vROps Capacity Planning is understand the capacity concepts.

An image is worth a thousand words:

Having this concepts crystal clear, the next lesson is the 3 capacity models:

1. Demand based > dynamic
2. Allocation based > static
3. A combination of demand and allocation models 

With the first method, demand, the resources are assigned to the objects based on their demand and with the second mode, allocation, the resources are assigned to objects in static way.

Usually the allocation model is used for production environments (and the other both for test environments). The main objective is maximize the density optimizing the use of the resources based on demand.

The allocation model reduce the risk of insufficient capacity based on teh assigned resources for objects.

See an example how a trend analisys is different from a demand to an allocation based model:

VMWORLD 2015 PRE-REGISTRATION

VMworld 2015 pre-regisytration is open for Sanf Francisco and Barcelona. Key dates:

• Europe Registration: June 9
• US and Europe Content Catalog: June 23
• US Schedule Builder: July 14
• Europe Schedule Builder: August 18 

https://www.vmworld.com/registration.jspa?src=vmw_so_vex_pcruc_131

vRealize Operations Manager 6 - Part V - Create Custom Groups with vSphere Tags

One of the best vROps (old vCOps) features is the option to create custom groups where you can define the criteria membership and apply a policy rule to them.

There is a lot of environments where the Virtual Machines are not properly configured and defined, with the vSphere Folders or inventory VM names, no naming convention, etc.... 

Is here where the "vSphere Tags" win the game! You can easily tag your VMs!  ..use PowerCLI!!!! (next post incoming)

Imagine that you need to create a policy rule and a Custom Group but your VMs in vSphere are not organized...  Are you thinking in add one-by-one to a Custom Group? and what if tomorrow you add new VMs? ...manually adding Vms is not a good idea, so try to tag your VMs when you create it on the vSphere environment and keep it updated with your CMDB database.

But, how to tag your environment properly?  First of all, you "must" have clear the tags you want to add and how to categorize it.  Just an example, filter you DDBB Vms  (SQL, Oracle, MongoDB, etc) or filter by App Vms, or Bckp environment, or AV environment... and so on.....

Once you have your VMs tagged, you can create a custom group as shown below:

See previous Part I    -vRealize Operations Manager 6 - Part I - OVA deployment

See previous Part II   - vRealize Operations Manager 6 - Part II - Express Installation

See previous Part III  - vRealize Operations Manager 6 - Part III - Manage Solution

See previous Part IV  - vRealize Operations Manager 6 - Part IV -  How import LDAP users

Related with:  VMware vSphere: how to create tags - Part I

http://virtualshocks.blogspot.com.es/2015/04/vmware-vsphere-how-to-create-tags-part-i.html

VMware vSphere: how to create tags - Part II with PowerCLI

On the Part I post we learn how to add a Tag and a Category trough the GUI interface with vSphere Web Client, now, let´s take a look about how to do it with PowerCLI.

Remember that Tags are a new feature available from vSphere 5.1 and the cmdlets are available from PowerCLI 5.5, so, we need at least a vCenter on vSphere 5.1 and the PowerCLI 5.5 installed but much better use las version PowerCLI 6 (not all cmdlets are present in PowerCLI 5.5 initial release)

Use this to verify the version you have installed: 

PowerCLI C:\> Get-VIToolkitVersion

Now with the New-Tag we can review the Tags configured, and with "New-TagCategory" create a Category and after with "New-Tag" the Tag

Now, we are ready to assign Tags to objects, in this case to Virtual Machine:

It´s time to verify it trough Web Client:

Something i didn´t mention jet, is that you can assign multiple Tags to an objet in vSphere , in our case to a Virtual Machine. It means that you can for example tag a VM with the "DDBB_tag" because it´s a SQL DDBB, and Tag it with "Cluster_tag" because it´s a Microsoft Cluster, or with another tag like "Test_tag" because it´s a DDBB SQL Cluster from the Lab Environment.

Why multiple Tags? For vROps it will be useful to create custom groups using different Tags criteria and fix different policies if its a VM from DDBB servers, or if its a VM from Lan Environment..... one VM could be placed in different Custom Groups at the same time :-)

First Part of this post: VMware vSphere: how to create tags - Part I

http://virtualshocks.blogspot.com.es/2015/04/vmware-vsphere-how-to-create-tags-part-i.html