Home > Certification, VCAP > VCAP-CIA objective 2.2 – Manage vSphere storage resources

VCAP-CIA objective 2.2 – Manage vSphere storage resources

The blueprint states the following skills needed to cover this objective.

  • Decommission storage
  • Create and manage storage profiles

The goal to decommission storage can prove to be a tricky one when done wrong, as this might get your host into an APD state. APD handling has been improved alot with ESXi 5.1 which is used in the exam but should you should still try to remove the storage correctly in order to not risk any point loss or even worse a host loss during your exam.

The following kb article shows the correct procedure to use which includes unmounting the datastore and detaching the device. If the storage device actually is an NFS share all that is needed is the unmount.

Unmounting a LUN or detaching a datastore/storage device from multiple ESXi 5.x hosts
http://kb.vmware.com/kb/2004605

unmountds

detachds

This does cover the vSphere side of things. If asked to decommission a datastore from vCloud Director you will need to disable the datastore and remove it from all Provider vDCs. This can be achieved by editing the according storage profile for the datastore to not containing it anymore. If the “* (Any)” profile is used it will be sufficient to remove the datastore on the vSphere level. In the screenshots below we are going to disable the iSCSI16GB datastore, so no new VMs can be deployed to the datastore anymore. Afterwards we are going to remove it from the Provider vDC by editing the storage capabilities of the datastore on the vSphere level so it is not contained in the according iSCSI storage profile anymore.

removestorage1

removestorage2

removestorage3

removestorage4

removestorage5

The creation and management of storage profiles is done at the vSphere level. Once you have created and enabled storage profiles they can be assigned to a Provider vDC and Organization vDCs. This process is described in the vCloud Director Administrator’s Guide on pages 49 and 63 in the English version. Additional information can be found in the following blog posts.

http://blogs.vmware.com/vsphere/2012/11/using-storage-profiles-with-vcloud-director.html
http://blogs.vmware.com/vcloud/2012/11/vcloud-director-any-storage-profile.html
http://www.yellow-bricks.com/2011/07/13/vsphere-5-0-profile-driven-storage-what-is-it-good-for/
http://cormachogan.com/2012/10/17/vcloud-director-5-1-storage-profiles/

The first step is to enable storage profiles on the clusters or hosts used for vCloud Director.

storageprofile1

storageprofile2

If your storage is not VASA (vSphere Storage APIs – Storage Awareness) capable you will need to create user defined capabilities first.

storageprofile4

storageprofile5

The third step is assigning these capabilities to your datastores.

storageprofile7

The final step is actually creating the storage profiles.

storageprofile3

storageprofile6

Your datastores are now mapped to the profiles by the assigned capabilties which covers the vSphere side of things. You are now ready to use these storage profiles in vCloud Director. You will be able to choose them during the creation of a Provider vDC. If you want to edit an already existing Provider vDC to use some newly created storage profiles you can do so in the Manage and Monitor tab.

storageprofile8

Categories: Certification, VCAP Tags:
  1. No comments yet.
  1. No trackbacks yet.