Facebook Twitter Gplus LinkedIn RSS
Home Posts tagged "performance"
formats

vCloud Director 1.5 Performance and Best practices guide

I regularly get questions from people asking where the link to this document is. I thought I would include it on my blog so that people can find it easily. Click here to open the Performance and Best Practice guide. For those of you who are unsure what this guide is about, here is an excerpt from the webpage. VMware vCloud Director gives enterprise organizations the ability to build secure private clouds that dramatically increase datacenter efficiency and business agility. Lots of new features have been added to vCloud Director 1.5 to accelerate application delivery in the cloud. In this paper, we discuss some of the features of the vCloud Director 1.5 release, performance characterizations including latency trends, resource consumptions, sizing guidelines and hardware requirements, and performance tuning tips. Some highlights of vCloud Director performance and best practices include: When using fast provisioning (linked clones) and a VMFS datastore, do not exceed eight hosts in a cluster. Be aware that there is a chance to hit the snapshot chain length limit. If the current clone has become very slow compared to the prior clone, the clone may have hit the snapshot chain length limit 30. This can be resolved by

Read More…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 
formats

vCloud Director PAY-AS-GO vCPU default setting – Gotcha

During Partner Exchange I had quite a few discussions with people about the default vCPU setting when creating an Org vDC with a Pay-As-You-Go allocation model.  Now this is nothing new however this is still causing quite a few performance issues out in the field. When creating a new Org vDC through the wizard, after selecting the allocation model Pay-As-You-Go, you are shown the configure window.  This window allows configure the compute requirements for this Org vDC.  This is where the gotcha comes in.  The default setting vCPU is configured at 0.26 Ghz.  I will repeat this as I know I have missed it in the past.  The default setting for vCPU is 0.26GHz.   You can see in the screenshot below the default setting. So how does this actually relate to the objects in vCenter?  By leaving this set to the default, this will configure every VM you create with a vCPU limit of 0.26GHz.  The screenshot below shows the vCPU limit configured in vCenter. If you experience any performance issues running VMs from vCloud Director, it is always best to check the Org vDC vCPU settings in the first instance. To read an in-depth guide about vCloud Director Allocation models

Read More…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
5 Comments  comments 
formats

vCloud Ecosystem components explained

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

Read More…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
4 Comments  comments 
formats

Cannot add groups to vCD after configuring LDAP

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.

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
1 Comment  comments 
formats

How-To: Re-install VMware vCloud Director

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

Read More…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
1 Comment  comments