While moving some vCO content over from one server to another via the process of creating a package on Server1, exporting the package and then importing the package into Server2, something went awry and I was no longer able to edit some of the workflows.
Specifically, the workflows in question looked like this with the pencil edit button greyed out:
A clue was given in the User permissions section with both Add to package and Edit contents unchecked:
While at VMworld Europe 2014 I noticed in some of the slides in a vCO session that the presenter was using some icons for workflows that did not appear to be standard. I was quite curious how to do this, but couldn’t find much information about it until I stumbled on the below training video.
If you don’t want to watch the video, here’s how to do it.
Get your images into vCO Supported:
When validating a vCO workflow I received the following error message:
Object referenced by this attribute using a configuration element is not found
I’ve had similar issues before and the fix was to replace the Configuration Element being selected for the attribute. Unfortunately that was not the case this time. Instead I resolved it by removing the attribute, recreating it, then replacing it in the various places in the workflow it had been in use.
Dynamic Types in vCAC enable you to extend the vCAC Inventory to include types created in vCO. For example you might be working with an F5 system and wish to make a tangible object back in vCAC that a user can view the properties of and have Actions assigned to.
Having created some Dynaimc Types in vCO for a project I was working on they were not appearing as available to add in vCAC Custom Resources - only the defaults were seen to be available.
vCenter Orchestrator has a built -in plugin for working with systems that support REST API queries. I’ve used this fairly extensively recently while working with vCNS
Out of the box the plugin will do the majority of the hard work for you, however one thing that isn’t available via the Add a REST operation dialogue is the ability to configure a custom header for the REST query. In the following example I need to add an if-match header to update the App firewall rules for a portgroup, but for a POST method I only have the option to specify the Content type:
This has happened to me twice now with vCO 5.5.1 running on Windows using the embedded database - once in a dev install in a lab and now also in my home lab. So figured it was time to write up the steps to sort it out.
Issue:
The vCO Orchestrator Server service won’t start. In the vCO log you find something similar to:
[vcoInitializerScheduler-1] ERROR {} [ServerChecker] Server integrity problem: interface com.
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 7 we look at publishing our Create-Tenant vCO workflow back into vCAC as a catalog item to make for easy consumption of it.
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 6 we look at adding Administrators to a Tenant in vCAC.
1) Add the ‘Add administrators’ workflow
Drag the Add administrators workflow from the vCloud Automation Center section of the workflow library
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 5 we look at adding an Identity Store to a Tenant in vCAC.
1) Generate the variables for adding an Identity Store
In this series we will see how to automate the creation of a tenant in vCAC using vCO. There are multiple tasks to provision a tenant in vCAC, so even though it is an automation product itself, there’s no reason why you shouldn’t look at automating parts of it too.
In part 4 we look at the first part of creating a Tenant in vCAC.
1) Create the parent workflow