VMware has launched a new site called Cloud Credibility. Its a kind of fun interactive online game where you can build up your #cloudcred. So what is CloudCred? According to the cloudcredibility.com site it is: If you know your stuff when it comes to the cloud, then you’ve got Cloud Cred. Cloud Cred is the hub for all things cloud related. The game is your gateway to building your cloud expertise, broadening your professional network and earning rewards and certifications based on your Cloud Cred score. Looks kinda fun and interesting, I have signed up and going to try to see what I can achieve. If nothing else, you can have the chance to win a trip for 2 to VMworld Barcelona. That in itself is surely worth signing up for. Im off to a good start, having completed two tasks, I now have a score of 502.
Eric Siebert over at vsphere-land has opened the 2013 voting for the top virtualization blogs. I am hoping to make it into the top 50 this year. This is the first time my blog has been listed and included for the voting, so I am excited to see what people think of my blog and its content. The top 10 sites I voted for are: Duncan Epping Kendrick Coleman Chris Colotti Eric Sloof Cormac Hogan Rawlinson Rivera William Lam Alan Renouf Frank Denneman Rick Vanover Anyone looking to vote should follow Eric’s criteria when choosing there top 10. Longevity - Anyone can start a blog but it requires dedication, time & effort to keep it going. Some bloggers start a blog only to have it fall to the wayside several months later. Things always come up in life but the good bloggers keep going regardless of what is happening in their life. Length - It’s easy to make a quick blog post without much content, nothing wrong with this as long as you have good content in the post that people will enjoy. But some bloggers post pretty long detailed posts which takes a lot of time and effort to produce. The
Working in my lab today, I was having some issues with deploying virtual machines within vCloud Director. I remember a while ago that Chris Colotti had written an article about the importance of NTP with vCloud Director. I thought I had better syncronize the vCNSM (formally vShield Manager), vCenter Appliance, and vCloud Director. Setting NTP on a vCD cell and vCNS Manager is a very simple task, but how do you do it on the vCenter Appliance? There is no option through the configuration UI. A quick google showed me this page within the vSphere 5.1 documentation center. Procedure Log into the vCenter Server Appliance as root. From a command line, enter the following commands to configure and start an NTP client. yast2 ntp-client add server=your_chosen_time_server yast2 ntp-client enable Enter the following command to request immediate synchronization with the time server. sntp -P no -r your_chosen_time_server However following this guide, I received the error: Error: Cannot update the dynamic configuration policy. Again I hit google, and found this bugzilla page by Novell. It states this issue is fixed, but doesnt show you how to fix the problem. So what do I do know? Well the vCenter Appliance is based on
I dont normally re-post video’s on my blog site without any corresponding article, but I am currently working on the VMware vCloud Networking and Security 5.1 product, and found this really helpful video on how to configure Logical networks using VXLAN. This is really useful and well worth a watch if you are configuring VXLAN. Duncan Epping over at Yellow-Bricks has also written a really helpful guide on how to configure VXLAN.
I have been re-building my lab yesterday with all the latest vCloud suite 5.1 GA bits. After deploying and configuring the vCenter Virtual Appliance, when I was trying to login to the vSphere web client, I kept receiving the error “ Failed to connect to VMware Lookup Service https://[hostname]:7444/lookupservice/sdk – SSL certificate verification failed. ” and could not login. This issue occurs if you have changed the hostname or IP address of the vCenter Virtual Appliance. The certificate that was created on initial configuration is no longer valid. To resolve this issue, follow the steps below: Login into vCenter VA Configuration https://[hostname]:5480 Select the Admin tab Click Toggle certificate setting, you will see Certificate regeneration enabled change to Yes. Re-boot the Virtual Appliance During the bootup procedure you will see Hostname or IP has changed. Regenerating self signed certificate.