vCO 101 – Test DPM

In response to Cody Bunch‘s recent post on Testing DPM with PowerCLI, I decided to translate this into a vCO workflow.  I did this because I thought it would be fun.  The workflow is relatively simple and does the following:

    • Allows user to select the host.
    • Checks the current power state of the host.
    • Based on the above, runs through either the standby tasks or the power on tasks.
    • Logs if successful and fails with exception if not.

Instead of making this a lengthy post, I have attached the workflow for you to download if you want to see it or play with it.  Enjoy!

Test DPM vCO Workflow

 

 

Renaming a datastore through vCO

I was in need of automatically renaming a generic datastore name in one of my host deployment workflows and found that the renameDatastore() method was deprecated (Thanks Jörg!) and that we are to use rename_Task().  The rename_Task() method is one that takes any manageable object.  Here is an exert from the API reference:

Rename_Task

Renames this managed entity.

Any % (percent) character used in this name parameter must be escaped, unless it is used to start an escape sequence. Clients may also escape any other characters in this name parameter.
See name

Required Privileges
When object is VirtualMachine - VirtualMachine.Config.Rename
When object is Datacenter - Datacenter.Rename
When object is Folder - Folder.Rename
When object is VirtualApp - VApp.Rename
When object is ResourcePool - Resource.RenamePool
When object is ClusterComputeResource - Host.Inventory.RenameCluster
When object is DistributedVirtualSwitch - DVSwitch.Modify
When object is DistributedVirtualPortgroup - DVPortgroup.Modify
When object is Datastore - Datastore.Rename
When object is Network - System.Read

So I implemented the following code into a new scriptable task within my workflow:

1
2
3
4
5
6
7
8
var hostDatastoreSystem = VcPlugin.toManagedObject( host, host.configManager.datastoreSystem );

// Rename datastore on host matching Datastore
for each (var datastore in hostDatastoreSystem.datastore) {
if(datastore.name == "Datastore"){
datastore.rename_Task("newDsName");
System.log("Changing datastore name to "+newDsName);
}

Another thing I realized was that the API explorer within vCO is not always as forthcoming with information so a word to the wise, always check the API reference (http://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.apiref.doc_50/right-pane.html) for more detailed information.

vCO Webviews/Perspectives Default Values Issue

So today I was running some workflows that will be needed in the next week or so and found that they suddenly did not work in Webviews or Perspectives.  The only change recently was my upgrade of my vCO appliances.  For some odd reason the auto-generated default values I would create in the workflow would not populate.  After some soul searching and asking on VMTN, I was directed to a KB that was released recently by Christophe Decanini (@vCOTeam).

Some issues occur in vCenter Orchestrator 4.2.1 weboperator Web view. For example, when you use default values for input parameters in a workflow, run the workflow from the weboperator Web view, and then you change some of the parameters, the default values are not updated correctly. Another issue is that you cannot schedule a workflow by using the weboperator Web view.

You can get to the KB article here: http://kb.vmware.com/kb/2015178

The fix is a simple replace of a jar file and restart of the Orchestrator services.

 

VMworld 2012 Call For Papers Open

Much to my surprise, VMworld 2012 CFP is now open (http://www.vmworld.com/thread/5311).  I will be submitting a few topics with a couple of my vCO buds.  I won’t go into too much detail because I don’t want to give it away but we have some sessions that I believe people will want to attend.  There will be quite a bit of information and most of it will be useful, hahaha!  Just kidding, it will be 100% useful.  So keep an eye out for a post later in the next few weeks regarding any sessions that I will hopefully be presenting along side some other great guys involved.

2012 VMware vExpert Recognition

On Sunday, April 15, 2012, VMware released the information regarding the 2012 VMware vExpert Recipients here:  http://blogs.vmware.com/vmtn/2012/04/announcing-vexpert-2012-title-holders.html

I am honored to be a part of this list for another year.  It is great to know that what we are doing is recognized as something that helps evangelize and spread the word about VMware virtualization.  I am looking forward to another great year and providing even more content.  Thanks to VMware, John Troyer (@jtroyer), Alex Maier (@VMwareCommunity) and the rest of the VMTN group.

Also, a big congratulations to all returning vExperts and an even bigger congrats to all of the new guys!

vCO vApp Upgrade Issue

So I decided to remediate my vCO vApp to the latest version, 4.2.1.  Everything went smooth after attaching the baseline that I created to upgrade it through VUM.  Upgrade looked successful, went to login and received:

Can’t connect to host…

After re-reading the release notes, I noticed the first Known Issue for Installation was:

After you upgrade the Orchestrator appliance to version 4.2.1, the Orchestrator server might not start automatically

So following the workaround provided I proceeded to:

    • Log in to the appliance home page.
    • Click Orchestrator Configuration, and log in.
    • Click the Database tab on the left, and click Update database.
    • Click the Startup Options tab on the left.
    • Click Start service.

This didn’t seem to resolve the issue for me.  I was still unable to login.  So what to do…I decided that I may need to clear all temporary files on the server.  You can do this by:

    • Log in to the appliance home page.
    • Click Orchestrator Configuration, and log in.
    • Click the Startup Options tab on the left.
    • Click Stop service.
    • Click the Troubleshooting tab on the left.
    • Click Clean directories.
    • Click the Startup Options tab on the left again.
    • Click Start service.

Viola!  This seem to resolve the issue I was having of logging in via the Orchestrator Client.

1 2 3 … 12  Scroll to top