Home > Blogs > vCloud Architecture Toolkit (vCAT) Blog > Tag Archives: vCenter Orchestrator

Tag Archives: vCenter Orchestrator

Enforce System Wide CPU/Memory limits in vCloud Director

Have you ever wished you could prevent users from powering on VMs in your vCD environment with 4 or more CPUs? How about preventing VMs with more than 8 GB of memory from powering up? There may be performance benefits to enacting such limitations depending on the number of CPUs and cores the physical hosts in the underlying cluster have available.

While neither of the above items are possible with any basic settings, such control can be enforced in your vCloud Director environments. Laying out every step in detail to accomplish this task is beyond the scope of today’s post, but the basic steps are as follows:

  • Configure an AMQP server
  • Enabling the “Start vApp (Deploy from api)” blocking task
  • Specify a vCenter Orchestrator workflow to subscribe to the queue

If you find this concept interesting and feel you would benefit from such a solution, please leave me feedback as a comment to the Workflow Examples document in the Orchestrator Community.

vCAT Workflow Examples – What would you like to see?

The current release of vCAT features a few different workflow examples for use with vCenter Orchestrator. Those examples were based on the needs of VMware and various client projects we had worked on.

In considering what to include as examples, we had to be sure that we could make the processes generic enough to fit into any organization’s environment. The three released examples are:

Each of the examples above may be used as they are but are commonly used as starting points to larger custom projects around vCloud Director.

We want to hear your ideas on how to make the above packages better as well as ideas for new packages. Please post your ideas as comments to the vCAT Workflow Examples document post in the communities here: http://communities.vmware.com/docs/DOC-20230