vco licensing / home builds

[mcfadyenj]

does anyone know what the licensing modes are with vco. If you are licensed at work is it ok to build at home? (as the msdn agreements offer similar).

is there any easy way to have this fully virtualised to enable testing workflows on a home network.

[Burke- · Accepted solution]

I'm not sure on the licensing part, but for the self contained lab, see this article I wrote a while back:

http://www.vcoteam.info/learn-vco/how-to-create-an-all-in-one-vco-dev-server-on-windows-2008-64-bit....

[cdecanini_]

I am not going to handle the licensing in details since I am not sure. Likely we will not discourage you from using our products as long as they are licensed.

Technically I see Burke already addressed the vCenter / vCO / DB / AD part. You will also need at least an ESX that you can run native or in a VM. Make sure you have loads of RAM. My laptop with 8 GB running vCO / vCloud Director / vShield manager / vCenter / ESX is using all its 8GB !

Christophe.

[mcfadyenj]

thanks all, one thing I have no shortage of is hardware. I will have a go at building this up, I guess it would be useful as I can learn the vc side of things as well.

[tschoergez]

I'm not a VMware employee, so I feel free to share my opinion (it's no official statement of course):

The EULA clearly states to "install a copy of vCO...on ONE physical or virtual server..." (it was the first time I read an EULA completly, since this paragraph is at the very end ).

So if you have a vCenter license, you can install vCO anywhere (make sure to deinstall the default installation from your vCenter server 🙂 ).

One the other hand there is the 60-day trial, and since you export your work very easy it's no effort to re-install a new vCO every two month and import the stuff again.

Technical it's no problem to run it virtual, I also have a complete vSphere enviroment including vCO in several VMs on my laptop running vmware workstation.

But when you develop workflows specific to your vCenter inventory, you should have a comparable structure in your dev-environment anyway.

And if you have more than one vCenter connected to a single vCO, then there should be some "spare" licenses for the vCO from these vCenter instances.

BTW: Would you be interested in an shared "cloud-based" vCO-sandbox environment, e.g. accessible via web, maybe with some per-hour use-base?

Regards,

Joerg

[mcfadyenj]

i most certainly would be interested in access to the cloud goodies. I haven't had any exposure prior though.

I can see some interesting uses for this toolset, best of all is nobody else is doing it (at least not in this country).

[cdecanini_]

And the answer to the licensing question from the vCO product Manager is: "we're not putting any restrictions on home usage."

Christophe.