Thought I would share the links to some important KB articles that have been released this week. Hope they help. Special thanks to Michael Haines for sending this to me. Enabling centralized logging of vCloud Director cell logs (2004519) Date Published: 11/14/2011 http://kb.vmware.com/kb/2004519
Thought I would share the links to some important KB articles that have been released this week. Hope they help. Installing or upgrading to vCloud Director 1.5 fails in the RHEL 5 Update 7 operating system (2007405) http://kb.vmware.com/kb/2007405 LDAP is configured, but group based authentication fails in vCloud Director 1.0.1 (2009317) http://kb.vmware.com/kb/2009317 Upgrading to vCloud Director 1.5 fails with the error: Error executing SQL statement: “INSERT INTO role_right (role_id, right_id) VALUES (102, 210)” (2008999) http://kb.vmware.com/kb/2008999
During VMworld Chris Colotti and I presented quite a few group discussions on VMware vCloud. During these discussions some people were amazed to find out how many components/products are involved in making up the vCloud environment. When planning on building a VMware vCloud, you are not just installing vCloud Director and pointing it to vSphere, you are designing/building a whole Ecosystem. The list below shows which components are used in building a full vCloud environment. They are listed in order of priority. vSphere ESXi vCenter vCloud Director vShield Manager vCenter Chargeback Vcenter Update Manager vCenter Orchestrator vCloud Service Manager vCloud Connector So why are these components important? When designing a vCloud environment, you need to take into consideration the availability of certain components, like vCenter for example. This is no longer a management tool that is used to manage your virtual infrastructure. This is a critical component of your vCloud environment passing through all the operational commands a consumer initiates using vCloud Director. How do you protect vCenter? There are 6 databases in a vCloud Ecosystem. How do you protect all the databases? Every component shown above with the exception of ESXi and vCloud Connector have a database that have
I discovered today building a new vCD 1.5 home lab, that once you configure the System LDAP, you dont have the option to add any LDAP groups. This confused me, it was possible to do this in 1.0.x. Why isn’t it available in 1.5? What I discovered is that the GUI is still configured for non LDAP authentication. Once you have configured LDAP and started the synchronization log out of the vCloud Director GUI and back in. You will then see that groups is listed under the administration tab. The GUI needs to update its configuration options. Simple solution, but still confusing until you realise.
A few of my colleagues have been working on this recently, and the process has been released on some of the communities forums. I thought I would share this process to help people re-build there dev environments and labs. This process documents how to wipe and re-install vCD, with the same version number. 1. Export vApp Templates and any other vApps that are required in the re-built environment from the existing environment. 2. Remove the VMware vCloud Director Configuration Components such as Virtual Datacenters, Organizations, vApps, VMs, Networks Pools and so on– manually. 3. Cleanup the External Networks. 4. Verify that all organization / vApp network portgroups are removed from the vSwitches/dvSwitches. You will still need the portgroups provisioned for the External Networks. 5. Cleanup all the Resource group datastores. 6. Unprepare the ESX/ESXi Hosts from the VMware vCloud Director web console. 7. Verify on the ESX/ESXi Hosts that the VMware vCloud Director agents are removed and remove the agents manually if necessary • Access tech support mode for ESXi or Service Console for ESX • if /opt/vmware/vslad is present, the host is not unprepared properly • in that case run the vslad uninstall script (/opt/vmware/uninstallers/vslad-uninstall.sh) • If running