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:

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

VMware vSphere: how to create tags - Part I

What is a tag?

A tag is a label that you can apply to objects in the vSphere inventory. Tags allow you to attach metadata to objects to make them more sortable and searchable.

Tags are grouped into categories, which define how the tags can be applied to inventory objects.

What is a category?

A category groups together related tags in the vCenter Server inventory.

When you create a category, you specify whether multiple tags in that category can be assigned to a given object at one time, or whether only one tag can be assigned to an object at a time. For example, a category called Priority might contain the tags High, Medium, and Low, and be configured to allow only one tag in the category to be applied to an object at a time.

You also specify whether tags in a category can be applied to all objects, or only to specific object types, such as hosts or datastores.

...yes, this is just a Copy&Paste from the original explanation from tags and categories on the VMware documentation....but i´m sure that no one read it...or at least...just a few docu-addicts :-)

Once we have a crystal clear the idea about what Tags and Category are....let´s show how to create them:

continue reading....

Ediciones de VMware vCloud Suite

VMware en su version vCloud Suite dispone de tres ediciones: Standard, Advanced y Enterprise.

En cada una de ellas se incluyen diferentes soluciones: vSphere Enterprise Plus, vRealize Operations (vROps), vRealize Automation (vRA), vRealize Business y vCenter Site Recovery Manager (SRM): 

vRealize Operations es el antiguo vCenter Operations
vRealize Automation es el antiguo vCenter Automation
vRealize Business es en antiguo IT Business Management

Mas info en:  http://www.vmware.com/files/pdf/vCloud-Suite-Pricing-Packaging-Whitepaper.pdf

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

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

vRealize Operations Manager 6 - Part III - Manage Solution

Video about how to Manage solution  or how to add vCenters to vROps monitoring


See previous Part I - vRealize Operations Manager 6 - Part I - OVA deployment
See previous Part II- vRealize Operations Manager 6 - Part II - Express Installation

vRealize Operations Manager 6 - Part I - OVA deployment

See next step Part II  - vRealize Operations Manager 6 - Part II - Express Installation
See next step Part III - vRealize Operations Manager 6 - Part III - Manage Solution

.

vRealize Operations Manager 6 initial deployment

vRO is finally here (old vCOps). There is a lot of changes in the new GA so try to review the releases notes and the new documentation:

https://www.vmware.com/support/vrops/doc/vrops-60-release-notes.html

https://www.vmware.com/support/pubs/vrealize-operations-manager-pubs.html

There is a new sizing guide with 4 new sizes from Extra-Small to Large 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2093783

The main different with the las releases is that right now there is only one VM instead the older 2 VM in the the vApp version.

The first screen when you deploy the new vRO6 is a new helpfully wizard for an Express Installation, a New Installation(clustering) or Expand an Existing Installation adding new nodes:

CONTINUAR

VMware vCenter Operations Manager (vCOps): how to create specfic Groups

In this case, Groups are refereed to items which are suitable to be monitoring, not for user groups or similar as i just wrote in other post
Let´s go! From the vSphere UI portal (https://ip/vcops-vsphere) click on the top option "Configuration" and the select the tab "Manage Group Typs" and add a new one by click on the plus button:

Now, in the top page, next to  the World icon, click on "Actions" and select Create new group..."

Follow the wizard and add the group  created on the Type option:

On the second step add the VMs or the object/item that you want to add to the Group:

Now, you can see the specific group holding on the Groups icon:

VMware vCenter Operations Manager (vCOps): assign user access to custom dashboards

From the Custom UI portal (https://ip/vcops-custom) and with admin rights, go to de ADMIN tab and select SECURITY.

Create a new Accoun Group first and after a User Account as shown below:

 Once we have the Group and the User, it´s time to assign access to the custom dashboard.

Go to the HOME tab, select the dashboard and click on SHARE:

Select the dashboard that you want to share and "drag-an-drop" to the Group (from the right pane to the left pane).

 Let´s go to test it! Open the Custom UI portal with the credentials of the new user and verify that this user only have access to the specific custom dashboard:

 

VMware vCenter Operations Manager (vCOps): import users from LDAP

As you can´t add the vCOps vApp to an Active Directory domain or LDAP system, you have two options: create local user and groups on the vCOps or import users from an LDAP.

Let´s go! Connect to the Custom UI portal (https://ip/vcops-custom) and click on the Security option on the ADMIN tab (top pane) as shown below:

After click o0n the "Import From LDAP" button, you must add the IP, the Base DN of your AD and an user and pass with enough rights to access.
Once you fill the blanks, click on Load LDAP Groups and add the groups on the down-right pane:

Click the in OK and  return to the previous screen. Click "Lookup" and select the users/groups found:

Now you can view the user and add it to the specific Account Groups on the User Management:.

It´s time to test it!  Go to the Custom UI portal or vSphere UI portal and try to access with the user name as it appears on the Account Groups (format: user@domain)

Voila!!!!