Last night I managed to get my first vCloud .net app working. To get started I took one of the simple examples contained with the vCloud .Net SDK and copied aspects of it test what could be done. I imported the 2 DLLs (VcloudSDK_V5_1.dll, VcloudRestSchema_V5_1.dll) as needed and added the correct the using statements:
using System.Net; using com.vmware.vcloud.sdk; using com.vmware.vcloud.sdk.admin; using com.vmware.vcloud.sdk.utility; using com.vmware.vcloud.api.rest.schema; using System.Security.Cryptography.X509Certificates;
After handling the certificate issue next I initiated a connection but received a failure:
Mike Laverick recently made aware of a nice alternative to home labs. I have an extensive home lab at home so I think it’s too late for me now but I did contemplate getting a hosted lab rather than kill my electricity and upset the wife. But too late for me but not for you. Check out Mike’s article here:
“When I was in Australia recently for the Sydney/Melbourne VMUG I had the chance to meet Alastair Cooke – and sit in on his presentation on AutoLab. Alastair is a VMware Certified Instructor (VCI) based in New Zealand, and is one of the hosts of the APAC VMTN Communities Podcast. In case you don’t know AutoLab is tool that will build for you using scripts a vSphere Lab environment – and its based on the principle of “nested ESX” or “vESX” – where ESX is run in VM on a physical ESX host. It’s was updated in Dec, 2012 to support vSphere 5.1.”
So I need to 100% for sure need to bring my vCloud skills up to speed. I found out this week that latest version vCloud Connector is much more than a migration tool. With vCC 2.0 you can stretch vApps across Clouds. The feature of vCC 2.0 is called “vCloud Connector Datacenter Extension” and enables you to extend your private datacenter to a public – private 2 private etc etc.
You can shift workloads from your private datacenter to a public while maintaining the network config and whilst still being able to access the workload left over on the private cloud.
vCC stretches its vApp/VM network boundary to the public vCloud using a stretched network.
I believe this is the start of something much grander.