Wednesday, March 26, 2014

Storage Profile is gone on vCloud 5.5


You are used to configure Storage Pofiles on vCenter to make Storage Tiering available for vCloud Director, but on your recently implementation with vCloud Director 5.5 you figured out the Storage Profiles are not reflecting on vCD anymore.
no matter how many times you refresh the Storage Policies on vCloud nothing is showing up.


Don’t worry, it’s by design.

There’s a slight change on vCloud 5.5 when it’s backed up by a vCenter 5.5.
On these situations vCloud will use the Storage Policy instead.

Without further ado, lets see how to set up vCenter 5.5 to reflect the Storage Tiering on your vCloud 5.5 implementation.

First thing you need to know is that Storage Policy is based on vendor specific capabilities (which will need VASA enabled) or Tags.
Personally I think Tags are useful and enable more flexibility and mix and matches situations, so let’s see how to create those tags.

- Select your vCenter, Click on Manager and then on Tags
- Click on the small icon with a plus to create a new tag


- Give it a Name and a Category


Now we need to assign the Tag to the datastore which match it’s characteristics.
 - Select Datastores,
-  Then click on the specific datastore you want to assign the Tag
- Click Manage and Tags
- Click on the second small icon to select the Tag.

 
On the example above we can see the datastore has a tag “SAS”.

Next step is to create the Storage Policy.

- On the Home of your vCenter click on Storage Policies (see it’s not Storage Profiles anymore)



- Click on the Icon to Enable the Policy




- Select the cluster where would you like to enable Storage Policy and click on Enable


- Click on the icon to create your Storage Policy



- Give it a name and click Next



- Click Add tag-based rule



- Select the Tag you just created and click OK



- You will see the resources that matched the Tag you selected, click Next



- Click Finish to create your Storage Policy



We are done !!

Just go back to vCloud and refresh your Storage Policies and this new one will show up properly.

Review of cross functionality

vCloud 5.5 and vCenter 5.1 – Will use Storage Profiles configured on vCenter
vCloud 5.5 and vCenter 5.5 – Will use Storage Policy configured on vCenter.

Now your Storage Tiering Policy is back in place.

See you

Friday, March 14, 2014

VMware Certification now includes a recertification.


This post is intent to professionals that already have any VMware certification, and trust me, there’s a lot of certifications out there.

VMware is now changing it’s certification program for a recertification need at a maximum of every 2 years.  So no matters what level are you at right now, eventually you will need to recertify it.

But why in hell VMware is doing that ?
Well it’s nothing something new, the majority of companys and certifications programs have this concept of recertification, at least a certification of more than 2 years worth almost nothing, specially at IT Industry, think about it for a minute, how things have changed in the past 2 years…. Yeah, BIG changes, so it makes sense to recertify your knowledge.

VMware will send notification through emails about your certification expiration date, but how do you know it by yourself ?

Easy, login to the VCP portal and check your Transcription, there’s now a field that says up to when your certification is valid.


One good information: Official’s VMware training is not a requirement to take a recertification exam, but a training and hands on experience is always welcome when your are taking tests for a new product/version.

I know you have a lot of doubts…so check the FAQ page for more details.

See you in 2 years ; )
 
 

Friday, March 7, 2014

Sysprep location on VMware vCloud Director 5.5


 Missing createSysprepPackage.sh script to prepare sysprep files for VMware vCloud Director ?

With the release of vCloud Director 5.5 the sysprep preparation procedure has slightly changed, you cannot run the createSysprepPackage.sh script anymore, you would have to manually copy the files instead.

I just recently realized this change, despite the fact it’s documented on vCloud Installation guide, and because you might not got it too I’d like to share this information.

Starting with vCD 5.5, it’s just a matter of copying the binary files to: /opt/vmware/vcloud-director/guestcustomization/default/windows/sysprep

Beware that you need to create the sysprep folder first, it’s not there by default, and then create a folder for each O.S.

Another point of attention, now the folder’s name has changed to match what you would found on vCenter.


 Another thing you would notice, there’s not folder for Windows 2000, Yes, vCloud 5.5 dropped the support for it.

If you don’t know where to find the sysprep files, check KB1005593.

Good luck

Who am I

My photo
I’m and IT specialist with over 15 years of experience, working from IT infraestructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Senior Consultant, helping customers to embrace the Cloud Era and make them succefully on this journay. Despite the fact I'm a VMware employee these postings reflect my own opnion and do not represents VMware's position, strategies or opinios.

Most Viewed Posts

Blog Archive