beaker & vCloud

[Brett Swift]

I've got some beaker tests working with Vagrant, and now onto the vCloud challenge. 

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. 

I'm only a mere vOrg admin,  not a vCloud admin.   So these settings are kind of strange to me, and when I asked our real admin, I got this reply: 

-          resource pool path would be: <VDC name> (no further partitioning)

-          folder: /vcd001no/<Org>/<VDC>/<vApp>/<VM>             (all include the UUIDs)

 https://github.com/puppetlabs/beaker/wiki/Creating-A-Test-Environment#hypervisor-vcloud

This documentation states:  'specifying both the target template as well as three additional parameters'

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?

And the sample doesn't use UUID's - but I assume our folder names were configured differently from our sample. 

My config consists of

 a .fog file with working credentials. 

~~~ .fog

:default:

  :vsphere_server: 'vcd011no.**********t'

  :vsphere_username: 'bswift'

  :vsphere_password: '**********'

~~~

~~~  rhel-64-x64.yml

CONFIG:

# log_level: verbose

type: foss

consoleport: 443

datastore: IDEV7129_VDC

resourcepool: IDEV7129

folder: vcd001no/IDEV7129/IDEV7129_VDC

~~~~

As far as I've gotten, is this error. 

gems/nokogiri-1.5.11/lib/nokogiri/xml/node.rb:159:in `evaluate': Undefined namespace prefix: //soapenv:Body/* (Nokogiri::XML::XPath::SyntaxError)

I realize it might be hard for someone to help me, but a bit of background on any particulars on how vCloud needs to be configured and what API this is using in the back end would be helpful for me to work through this further. 

Thanks! 

[Scott Schneider]

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

[Brett Swift]

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!