The Automation Action Framework (AAF) is one of these, a really powerful vROps in-built automation tool.
Now when I have discussed this capability with my peers and friends many ask why not use vRO etc? My reply is quite simple, “what if you do not have vRO or the in house skills to utilise it properly?” also “With the AAF you do -not- need any scripting knowledge or have to setup any workflows.”
Make no mistake vRO is the daddy when it comes to serious automation in your environment and the AAF has a set number of actions available to it, however vRO requires a good deal of time and effort to get up and running and working while in comparison the AAF can be setup and ready to roll in a short space of time.
So what can the AAF actually do?
The following actions are available in vROps and can be manually initiated or automated:
- Delete Powered Off VM
- Move VM
- Power Off VM
- Power On VM
- Set CPU Count And Memory for VM
- Set CPU Count And Memory for VM Power Off Allowed
- Set CPU Count for VM
- Set CPU Count for VM Power Off Allowed
- Set CPU Resources for VM
- Set Memory for VM
- Set Memory for VM Power Off Allowed
- Set Memory Resources for VM
- Shut Down Guest OS for VM
With vROps you can either have it recommend actions as listed above and then click manually click a button or fully automate it, the latter should be planned carefully but you can learn more about how to do so in a recent webinar I presented “Building self-healing environments” along with my good friend Sunny Dua.
As with many things in vROps you can define permissions on who can do what so you can pick and choose who can do what. (support staff/admins/etc)
The bottom line here is there is some real strength you can utilise here in vROps it’s up to you how you wish to use it.