Let's take this one at a time. vCO is a worklow tool that has many connector to other products including VMware and non-VMware products. vCAC doesn't really have these connectors, but has a very robust workflow engine that allows you to inject your scripts or worklows into the lifecycle of the machines/services you are managing.
So say you wanted to register a machine to a load balancer once it was deployed. You could utilize a WorkFlows that executes at the "MachineProvisioned" state of the machines lifecycle to call vCO to execute it's workflow with the connector to an F5 appliance. Then in your workflow you can wait for a response from vCO to ensur eit was successful and move forward in the machine lifecycle.
Now you may also want to layer applications on that machine. Puppet intergation is the same concept only it may happen at a differnt state, most likely the 'CustomizeOS" state. You could do one of two things. You could have scripts that execute from within the provisioned machine triggered by vCAC to call puppet and install applications or you could do it from the workflow construct like explained above.
I hope that help syou understsand a little more about this.
Thank You,
Sid Smith
