vCenter

OVF Deployment Issue Ubuntu Snappy 15.04-stable (5 cloud)

When you have time, you do something.

Tonight I was headed over the Ubuntu site to grab me the latest version because I was thinking of installing OpenStack when I noticed on their landing page and noticed “Get Ubuntu Core” ; yes something new.

But where is my Raspberry Pi? No worries they have OVF images I can use to deploy to my vCenter Lab here at home. So I started just this and encountered an issue I once had.

Lets walk you through my events.

Downloading the image

  1. Found myself on the Ubuntu Internet of Things landing page: http://www.ubuntu.com/internet-of-things
  2. Located the OVF section of the getting started page: http://developer.ubuntu.com/en/snappy/start/
  3. Downloaded the OVA image (x86): 15.04/stable

Deploying the OVF Template 

  1. Using the vSphere Client, connected to vCenter (or stand alone ESXi host)
  2. Select server to deploy to and choose file > Deploy OVF Template
  3. Browse to the path were you downloaded your OVF image and select it

This is when I received the following error:
The following manifest file entry (line 1) is invalid: SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c

Troubleshooting Step 1

  1. I extracted the OVA image (core-stable-amd64-cloud) with 7zip
  2. Once extracted attempted the steps detailed above “Deploying the OVF Template”

The same error was thrown once more.

Troubleshooting Step 2

Within the extracted folder exists the following file types: certificate, manifest, ovf (instruction / configuration) and disk image

  1. I remove the SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c line from the .MF (manifest)
  2. Once removed I attempted the steps detailed above “Deploying the OVF Template”

It failed also, only this time the error started the the remaining SHA256 was also invalid.

Troubleshooting Step 3 – Third time is the charm

  1. Moved into the extracted OVA folder
  2. Deleted the .mf (manifest) file
  3. Followed steps above “Deploying the OVF Template” only this time using the OVF located in the extracted folder

This go around everything worked

So why did this happen?

The template was changed after its creation which invalidated the SHA256 key.  I have made templates myself, only to have to edit something out such as removing a CD Rom reference which later caused me issues.

I hope this helps if you face this incident or something similar

 

Thanks for visiting – jermal

Also published here

VMware: vCenter Server Appliance 6.0 Update 1

That time has come, when you upgrade vCenter 6.0.  Here are some quick simple steps to see this done.

As always, its a good idea to have a backup before proceeding.  In my case I used a snapshot of my appliance. This was done by me connecting directly to the ESXi and creating a snapshot.

And here are the steps to start this process:

  1. Download the VCSA 6.0 Update 1 from  the VMware Patch Download Website. File-name: VMware-vCenter-Server-Appliance-6.0.0.10000-3018521-patch-FP.iso
  2. Mount the VCSA 6.0 Update 1 Patch ISO to your VCSA 6.x appliance. I attached the ISO by logging into the ESXi and then attaching to the guest appliance
  3. Next is to be logged into the VCSA 6.x appliance via SSH – note this must be an admin account.  I used the local root user and password
  4. Run the following command to begin the installation process: software-packages install –iso –acceptEulas

  5. When completed issue the reboot command: shutdown reboot -r “Updated, thanks to my buddy jermsmit”

     

Congrats you have upgraded.

Info sources:

VMware KB – for additional info

William Lam – who’s tweet informed me of this release, thanks dude

 

I hope you enjoyed this post, thanks for visiting – jermal

Tech Short: Change Password VMware vCenter 6

The day would come where I would need to change my password in vCenter… Today was that day; Thankfully vCenter places am informative notice of your expiring password.

Here is how you can change your password using vCenter 6:

Log into vCenter 6

  1. Click Home.
  2. Click Administration.
  3. Click Single Sign-On > Users and Groups.
  4. Click the Users tab.
  5. Right-click the affected user account, selecting edit user
  6. Enter in the current password, followed by your new (it could be the same, I don’t ever recommend this practice)
  7. Click OK to save changes.

 

I hope you enjoyed this techshort, thanks for visiting – jermal

Tech Short Q&A: What is vCenter Single Sign-On For

What is vCenter Single Sign-On?

vCenter Single Sign-On is a feature of VMware vCenter 5, 6 and future vCenter implementations that is an authentication broker which also creates security tokens providing a secure way of accessing your environments.

This token exchange mechanism is far superior than the former requirement of each component authenticating separately with a directory service such as Active Directory. Its VMware’s answer to identity management

Here are some key capabilities of SSO?

  • add multiple AD domains, OpenLDAP, and the local operating system where SSO is deployed. It also lets you create local users and groups.
  • allows VMware vSphere to connect to a non-AD Identity Source, OpenLDAP.
  • supports the SAML 2.0 standard and WS-TRUST, both of which are open industry standards.
  • lets users delegate tasks to solutions that can run as the identity of the user.
  • supports identity delegation for long-lived tasks with the ability to renew tokens.

follow this link -> VMware vCenter Single Sigion-On for more info on

 

I hope you enjoyed this techshort, thanks for visiting – jermal

Tech Short: Enable SNMP on ESXi 6

Now that you are on or you have just started using VMware ESXi 6 and would like to do some monitoring via SNMP here is a way to enable this and set the community string in the process.

By default, remote clients are prevented from accessing services on host, unless configured to start automatically.

While you can simple set SNMP to start it does not set the community name and this is where we drop into the cli to do this.

Connect to the ESXi 6 host terminal or via SSH and issue the following commands:

By doing the following you have set the community strong value and started the service.

Finished