Thanks Scott, Yes very helpful. Unfortunately I'm not sure if I'll be able to get the right access to our vSphere. I only have a vOrg in vCloud to play with.
I saw a video from Hunter (hunner), where there's a video (http://club.black.co.at/log/posts/2014-05-24-beaker/) and at the 39th minute it shows your 'vcloud.delivery.puppetlabs.net' dashboard.. so I presume from your reply that this also isn't vcloud. Are there any plans to have vCloud integration? Or products like vCAC which may be more strategic? That might be our best bet right now as the Big Enterprise is probably going to take a while figuring out legality for us to use AWS and the like. Your post helps, and if I can get access to our vSphere layer, I'll give it a shot. Thanks! On Thursday, 4 September 2014 14:34:52 UTC-6, Scott Schneider wrote: > > Hi Brett, > > The vCloud settings seem a bit confusing to me. I've integrated only >> briefly against the http API for vCloud, and these settings of "datastore" >> "resourcepool" and "folder" seem to be vSphere specific. > > > First of all, I'm obliged to point out that "vCloud" is a misnomer here -- > it was a name chosen in beaker before VMware introduced their "vCloud" > product. It interacts with VMware's vSphere API, but is in no way actually > related to their "vCloud" product. We'll be renaming things shortly. > > - resource pool path would be: <VDC name> (no further partitioning) >> - folder: /vcd001no/<Org>/<VDC>/<vApp>/<VM> (all include the UUIDs) > > > These refer to where cloned VMs will be provisioned. More details in my > response below. > > By "Target Template" I assumed "Catalog Template"... or does this have >> some convention around a bootable VM with a snapshot that it can restore >> that puts the VM in a ready state for testing and provisioning? > > > This refers to the template you're be cloning from. This can be either a > "template" in VMware terms, or simple a powered-down VM. We use > powered-down VMs rather than "templates" (you can convert them back and > forth) because "templates" don't support linked-cloning. > > datastore: IDEV7129_VDC >> resourcepool: IDEV7129 >> folder: vcd001no/IDEV7129/IDEV7129_VDC > > > These look wrong to me; the values should be something closer to your > examples above, or the example shown at > https://github.com/puppetlabs/beaker/wiki/Creating-A-Test-Environment#hypervisor-vcloud. > > In your vSphere views, "datastore" should correspond to the name of one of > your datastores shown in "Storage". "resourcepool" should correspond to > the "Hosts and Clusters" vSphere view, in the form of > "<cluster>/<resourcepool>". Similarily, "folder" corresponds to "VMs and > Folders" in vSphere, in the format of "<folder>". The template target uses > the "VMs and Folders" view as well, in the form of "<folder>/<vmname>". > > Hopefully this helps point you in the right direction! > > --scott > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d3d584f3-8ec5-4ab6-a79f-fa3f76c69152%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
