WilliamLam.com

Tips and Tricks for vMA 5

by // 13 Comments

vMA 5 is just one of the latest VMware virtual appliances that have received the blessings and conversion to VMware's standard virtual appliance OS, SUSE. There have been several changes in the latest version of vMA and here are just a few tips and tricks that can help get you going with this new OS

1. The increase password complexity is something you may notice when you first configure vMA, if you are interested in changing it to make it easier or harder, you can take a look at the following knowledge base found on Novell's website:

2. You can now update vMA using a browser versus using the vma-update utility which is no longer being bundled with vMA 5. To access the management interface of vMA, go to your browser and type the following: https://[your-vma-hostname]:5480. You can configure a few things through the VAMI interface including updates for vMA in which you have a few options to choose from such as no updates, automatic check for updates or automatic check and install updates (just like Windows Update)

3. As with the previous versions of vMA, it has the OSP (Operating Specific) VMware Tools and the status will show up on the vSphere Client as "unmanaged". If you want to upgrade to the latest version of VMware Tools found on ESXi 5.0 to make sure of functionality such as the new integrated VIX API into the core vSphere API, you will need to run the latest VMware Tools. To do so, you will need to uninstall the OSP VMware Tools and then install the VMware Tools found in ESXi

First you will need to identify the package to uninstall and then uninstall, this can all be done at once using the following command:

vi-admin@primp-dhcp-235:~> sudo rpm -e $(rpm -qa | grep "open-vm-tools")
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Virtual Printing daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Guest memory manager: done
VM communication interface socket family: done
VM communication interface: done
warning: /etc/vmware-tools/tools.conf saved as /etc/vmware-tools/tools.conf.rpmsave

You will need to either copy the linux.iso containing the latest version of VMware Tools from your ESXi 5 host or use the vSphere Client to install the tools. I will demonstrate how to do so from the command line using the linux.iso. You will need to copy the linux.iso over to your vMA host using the following command:

vi-admin@primp-dhcp-235:~> scp *protected email*:/vmimages/tools-isoimages/linux.iso .

Now you will mount the linux.iso to extract the VMware Tools package

vi-admin@primp-dhcp-235:~> sudo mount -o loop linux.iso /mnt/

Next we will extract the contents to /tmp

vi-admin@primp-dhcp-235:~> tar -zxvf /mnt/VMwareTools-8.5.1-380278.tar.gz -C /tmp

Then we will umount linux.iso file

vi-admin@primp-dhcp-235:~> sudo umount /mnt

We now will change into the extracted directory under /tmp/vmware-tools-distrib and perform the installation of VMware Tools

vi-admin@primp-dhcp-235:~> cd /tmp/vmware-tools-distrib
vi-admin@primp-dhcp-235:~> sudo ./vmware-install.pl

You can accept all the defaults and when it prompts you for "gcc", you can ignore that option as gcc is not available by default on vMA and after that you will see that your VMware Tools have been updated from the vSphere Client.

4. Previous version of vMA, if you are familiar with Redhat/CentOS/Fedora, you know that you can use YUM as a way to install packages from a package repository. You can do the same on SUSE, but you will need to leverage a different tool called zypper which is a command line package manage just like YUM. You can also use another tool called YaST which also uses libzypp which is zypper package management engine. In the following example I will demonstrate how to configure a repository using zypper and search and installing a package.

To get a list of repositories based on the version of SUSE, you can take a look at the following link.

To add a repository, you will use the "ar" (Add Reposistory) option specified by the URL and alias:

vi-admin@primp-dhcp-235:~> sudo zypper --gpg-auto-import-keys ar http://download.opensuse.org/distribution/11.1/repo/oss/ 11.1
Adding repository '11.1' [done]
Repository '11.1' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/distribution/11.1/repo/oss/

You can add multiple repository and you can reference them by either the alias or the number assigned to the given repository

vi-admin@primp-dhcp-235:~> sudo zypper --gpg-auto-import-keys ar http://download.opensuse.org/update/11.1/ Update-11.1
Adding repository 'Update-11.1' [done]
Repository 'Update-11.1' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/update/11.1/

Once you have successfully added your repository, you can view them by running the "lr" (List Repository) option

vi-admin@primp-dhcp-235:~> zypper lr
# | Alias | Name | Enabled | Refresh
--+-------------+-------------+---------+--------
1 | OS-11.1 | OS-11.1 | Yes | No
2 | Update-11.1 | Update-11.1 | Yes | No

Before you search or install packages using zypper, you will need to first refresh the repository and build the cache. To so do, you will just run the "refresh" operation

vi-admin@primp-dhcp-235:~> sudo zypper refresh
Retrieving repository '11.1' metadata [|]
New repository or package signing key received:
Key ID: B88B2FD43DBDC284
Key Name: openSUSE Project Signing Key
Key Fingerprint: 22C07BA534178CD02EFE22AAB88B2FD43DBDC284
Repository: 11.1
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t
Retrieving repository '11.1' metadata [done]
Building repository '11.1' cache [done]
Retrieving repository 'Update-11.1' metadata [-]
New repository or package signing key received:
Key ID: B88B2FD43DBDC284
Key Name: openSUSE Project Signing Key
Key Fingerprint: 22C07BA534178CD02EFE22AAB88B2FD43DBDC284
Repository: Update-11.1
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t
Retrieving repository 'Update-11.1' metadata [done]
Building repository 'Update-11.1' cache [done]
All repositories have been refreshed.
@opensuse.org>@opensuse.org>

Now we can search for a package using the "se" (Search) option

vi-admin@primp-dhcp-235:~> zypper se ruby

Let's say we have located ruby as the package to install, you can then run "in" (Install) operation

vi-admin@primp-dhcp-235:~> sudo zypper in ruby

You could have also done this using yast by running yast -i ruby which will then launch a graphical UI or just by running yast by itself and navigating through the UI for packages.

5. vi-logger in vMA 5 has been deprecated and removed, for a free syslog alternative take a look at this blog article: Free Linux & Windows Syslog Alternatives to depercated vi-logger in vMA 5

6. How to Change the Splash Screen In vMA

vi-fastpass esxcli and resxtop bug resolved in vMA 5

by // 2 Comments

Awhile back I wrote about an resxtop bug found in vMA 4.1 in which it no longer functions with vMA's vi-fastpass component and still requires you to provide the username and password even though vi-fastpass has been initialized for a given target. There was also a slight quirk when using esxcli and vi-fastpass, in which you had to specify in addition the --server of your ESX(i) host which allowed you to utilize vi-fastpass.

With the latest release of vMA 5, both of these issues have now been resolved for both ESXi 5 and ESX(i) 4.x. I would highly recommend you download the latest version if you would like to make use the vi-fastpass component in vMA.

Here is an example of using vi-fastpass with resxtop:

vi-admin@vma50-1:~> vifptarget -s himalaya.primp-industries.com
vi-admin@vma50-1:~[himalaya.primp-industries.com]> resxtop

Here is an example of using vi-fastpass with esxcli:

vi-admin@vma50-1:~> vifptarget -s himalaya.primp-industries.com
vi-admin@vma50-1:~[himalaya.primp-industries.com]> esxcli

Automating the New Integrated VIX/Guest Operations API in vSphere 5

by // 27 Comments

VMware hinted earlier this year that the future of the VIX API would eventually be integrated into the core vSphere API, it looks like the wait is finally over. With the latest release of vSphere 5, the VIX API is no longer a separate API but consolidated into the core vSphere API which allows users to perform guest level operations directly to a virtual machine that is running VMware Tools.

There is now a new managed object called GuestOperationsManager which provides functionality for Authentication (authManager), File management (fileManager) and process management (processManager). The API is actually quite easy to use as you need to first acquire a guest auth credential within the guest and then you can perform any of the various guest operations using this credential cache.

I wanted to show the power of the VIX API by creating a vSphere SDK for Perl script called guestOpsManagement.pl that implements majority of the VIX/Guest Operations for users to manage from a centralized script. You will need to have a system that has the vCLI installed or use VMware vMA and to utilize the new VIX operations, your virtual machines must have the latest VMware Tools installed.

You can download guestOpsManagement.pl script here. 

The script supports 12 different VIX Operations which are described below:

Operation Description
validate Allows a user to validate guest credentials without performing any VIX Operation
ps Performs a process listing within the guestOS
startprog Starts a program within the guestOS
kill Kills a particular process within the guestOS
ls Perorms a listing of a particular directory within the guesOS
mkdir Creates a directory within the guestOS
rmdir Removes a directory within the guestOS
rm Removes a file within the guestOS
mv Move/Rename a file within the guestOS
mvdir Move a directory within the guestOS
copyfromguest Download a file from within the guestOS to local system
copytoguest Upload a file to the guestOS from a local system
Here is an example of performing the "validate" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation validate --guestusername root

Here is an example of performing the "ps" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation ps --guestusername root

In the next example, we will kill off the "tail" process as listed above.

Here is an example of performing the "kill" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation kill --guestusername root --pid 13198

Here is an example of performing the "startprog" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation startprog --guestusername root --working_dir /root --program_path /usr/bin/touch --program_args /root/virtuallyghetto

Note: There is known vSphere SDK for Perl bug for the return value of a "long" which will be resolved in GA release of vSphere SDK for Perl 5.0. You should not see the "error" message when running this operation

Here is an example of performing the "ls" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation ls --guestusername root --filepath_src /var/log

Here is an example of performing the "mkdir" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation mkdir --guestusername root --filepath_src /tmp/virtuallyghetto

Here is an example of performing the "rmdir" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation rmdir --guestusername root --filepath_src /tmp/virtuallyghetto

Note: If you would like to perform a recursive directory delete, you will need to specify the --recursive, please use with caution

Here is an example of performing the "rm" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation rm --guestusername root --filepath_src /root/virtuallyghetto

Here is an example of performing the "mv" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation mv --guestusername root --filepath_src /root/steve_jablonsky --filepath_dst /root/hans_zimmer

Here is an example of performing the "mvdir" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation mvdir --guestusername root --filepath_src /tmp/foo --filepath_dst /tmp/bar

Here is an example of performing the "copyfromguest" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation copyfromguest --guestusername root --filepath_src /var/log/messages

Here is an example of performing the "copytoguest" operation:

./guestOpsManagement.pl --server vcenter50-1 --username root --vm vMA5 --operation copytoguest --guestusername root --filepath_src /home/vi-admin/test.pl --filepath_dst /root/test.pl

There is also complete perl docs for this script which can be called using the following command:

perldoc guestOpsManagement.pl