Zenoss ZCA Utilities¶

Scripted¶

If you want to save yourself some copy/paste time, a script is available that should automatically handle most of the steps below. The following short set of commands shoulds get you up an running. If you have an issues with the script, you should be able to fall back on the manual steps, or maybe even fix the script and let me know the changes so I can incorporate them:

cd /tmp
wget https://raw.github.com/ZCA/zenoss_zca_utils/master/source/scripts/vmware_appliance_to_virtualbox/vmwware_appliance_to_virtualbox.sh
chmod +x vmwware_appliance_to_virtualbox.sh
./vmwware_appliance_to_virtualbox.sh

At this point the VM should be converted and booting up. Once it has finished booting, login to the console and run the following commands from within the virtual machine:

cd /tmp
wget https://raw.github.com/ZCA/zenoss_zca_utils/master/source/scripts/vmware_appliance_to_virtualbox/replace_tools_with_additions.sh
chmod +x replace_tools_with_additions.sh
./replace_tools_with_additions.sh

Manual¶

• Download the existing VMware Image:

  cd /tmp
  wget http://downloads.sourceforge.net/project/zenoss/zenoss-alpha/4.1.70-1427/zenoss-4.1.70-1427-x86_64.vmware.zip
  

• Unzip the downloaded zip file:

  unzip zenoss-4.1.70-1427-x86_64.vmware.zip
  

• Create a new VirtualBox VM:

  VM_NAME="Zenoss_4.1_Appliance"
  VM_BASE_PATH=/VMs
  sudo mkdir $VM_BASE_PATH
  sudo chmod 777 $VM_BASE_PATH
  VBoxManage createvm --name $VM_NAME --basefolder $VM_BASE_PATH --register
  

• Move the VMDK file over to the VM’s directory:

  mv zenoss-4.1.70-1427-x86_64.vmdk $VM_BASE_PATH/$VM_NAME/
  

• Change Settings on the newly created VM:

  VBoxManage modifyvm $VM_NAME --ostype RedHat_64 --memory 2048 --nic1 nat --nictype1 82545EM --ioapic on
  

• Attach the VMDK file to the VM:

  VBoxManage storagectl $VM_NAME --name "SCSI Controller" --add scsi --controller LsiLogic
  VBoxManage storageattach $VM_NAME --storagectl "SCSI Controller" --type hdd --port 0 --medium $VM_BASE_PATH/$VM_NAME/zenoss-4.1.70-1427-x86_64.vmdk
  

• Some Optional Port forwards I find useful:

  VBoxManage controlvm $VM_NAME natpf1 "SSH,tcp,,8022,,22"
  VBoxManage controlvm $VM_NAME natpf1 "ZOPE,tcp,,8080,,8080"
  

• Add a DVD/CD Drive (At a minimum you’ll need this for installing Guest Additions):

  VBoxManage storagectl $VM_NAME --name "IDE Controller" --add ide --controller PIIX4
  VBoxManage storageattach $VM_NAME --storagectl "IDE Controller" --type dvddrive --port 1 --device 0 --medium emptydrive
  

• Power on the new Virtual Machine:

  VBoxManage startvm $VM_NAME
  

• Once the VM has started up, log into the console and Remove VMWare Tools:

  vmware-uninstall-tools.pl
  

• Use the VirtualBox documentation to install VirtualBox Guest Additions

Scripted¶

Maybe some day

Manual¶

Lets get our powershell on...All commands are run in a power shell prompt

• Setup some Variables:

  $buildNumber = "4.1.70-1434"
  $arch = "x86_64"
  $baseFileName = "zenoss-$buildNumber-$arch"
  $zipFileName = "$baseFileName.vmware.zip"
  $zipFileDownloadUrl = "http://downloads.sourceforge.net/project/zenoss/zenoss-alpha/$buildNumber/$zipFileName"
  
  $VM_NAME="Zenoss_Appliance_$buildNumber"
  $VM_BASE_PATH="\VMs"
  

• Download the existing VMware Image:

  cd \temp
  $webclient = New-Object System.Net.WebClient
  echo "Going to Download File. This will take a long time without output. Be Patient"
  $webclient.DownloadFile($zipFileDownloadUrl,"$pwd\$zipFileName")
  

• Unzip the downloaded zip file:

  $shell_app=new-object -com shell.application
  $zip_file = $shell_app.namespace((Get-Location).Path + "\$zipFileName")
  $destination = $shell_app.namespace((Get-Location).Path)
  $destination.Copyhere($zip_file.items())
  

• Create a new VirtualBox VM:

  if ((Test-Path -path $VM_BASE_PATH) -ne $True){New-Item $VM_BASE_PATH -type directory}
  VBoxManage createvm --name $VM_NAME --basefolder $VM_BASE_PATH --register
  

• Move the VMDK file over to the VM’s directory:

  mv $baseFileName\$baseFileName.vmdk $VM_BASE_PATH\$VM_NAME\
  

• Change Settings on the newly created VM:

  VBoxManage modifyvm $VM_NAME --ostype RedHat_64 --memory 2048 --nic1 nat --nictype1 82545EM --ioapic on
  

• Attach the VMDK file to the VM:

  VBoxManage storagectl $VM_NAME --name "SCSI Controller" --add scsi --controller LsiLogic
  VBoxManage storageattach $VM_NAME --storagectl "SCSI Controller" --type hdd --port 0 --medium $VM_BASE_PATH\$VM_NAME\$baseFileName.vmdk
  

• Add a DVD/CD Drive (At a minimum you’ll need this for installing Guest Additions):

  VBoxManage storagectl $VM_NAME --name "IDE Controller" --add ide --controller PIIX4
  VBoxManage storageattach $VM_NAME --storagectl "IDE Controller" --type dvddrive --port 1 --device 0 --medium (get-command VBoxGuestAdditions.iso).Path
  

• Some Optional Port forwards I find useful:

  VBoxManage controlvm $VM_NAME natpf1 "SSH,tcp,,8022,,22"
  VBoxManage controlvm $VM_NAME natpf1 "ZOPE,tcp,,8080,,8080"
  

• Power on the new Virtual Machine:

  VBoxManage startvm $VM_NAME
  

• Once the VM has started up, log into the console (root/zenoss) and Remove VMWare Tools:

  vmware-uninstall-tools.pl
  

• While still logged into the console, install VirtualBox guest additions:

  yum -y install bzip2 make gcc
  mkdir /media/ga
  mount /dev/cdrom /media/ga
  /media/ga/VBoxLinuxAdditions.run
  

• Reboot for good measure:

  reboot
  

Automated¶

Save the egg file in /tmp/ and run the following:

wget https://raw.github.com/ZCA/zenoss_zca_utils/master/source/scripts/gitify_zenpack/gitify_zenpack.sh
sh gitify_zenpack.sh <eggfile_name>

Manual¶

The first thing we need to do is install the egg:

zenpack --install=ZenPacks.community.gitify-1.0-py2.6.egg

Now, switch the pack to development mode. This step is also discussed in the Developers guide:

cp $ZENHOME/Products/ZenModel/ZenPackTemplate/* $ZENHOME/ZenPacks/ZenPacks.community.gitify-1.0-py2.6.egg

Open a zendmd shell:

zendmd

Run the following snppet in a zendmd shell. What I found was that after doing the switch to development mode, the setup.py that gets created has an empty name field, which of course makes sense given it came from a template, however with that blank name, the relocate fails as it tries to use the setup.py with the blank name. The followig snippet, populates the setup.py based on the info that was contained in the original egg:

for pack in dmd.ZenPackManager.packs():
  if pack.id == "ZenPacks.community.gitify":
    pack.writeSetupValues()
    exit()

Next relocate the files outside of the zenoss directory:

cp -r $ZENHOME/ZenPacks/ZenPacks.community.gitify-1.0-py2.6.egg /tmp/ZenPacks.community.gitify
zenpack --link --install=/tmp/ZenPacks.community.gitify

Now lets initialize a git repo. This will be a local git repo and in no way tied to GitHub yet:

cd /tmp/ZenPacks.community.gitify
git init

You should see something that looks like:

Initialized empty Git repository in /tmp/ZenPacks.community.gitify/.git/

Now that we have an empty git repo, lets setup a few default files. Of note, we are going to pull down a standard .gitignore file supplied by Zenoss, as well as creating our base README.rst file which GitHub wants and will also serve as the file in which we will document the ZenPack:

wget https://raw.github.com/zenoss/Community-ZenPacks-SubModules/master/.gitignore
touch README.rst

Now we commit all the stuff we just did (This still won’t result in interactions with GitHub):

git add .
git commit -a -m 'Initial Commit - Post EGG Extraction'

Make your local git repo aware of the version on GitHub (no actualy interaction occurs yet):

git remote add origin git@github.com:ZCA/ZenPacks.community.gitify

Now we actually create the repo on GitHub. You can do this in the Web UI or using the API:

github_user=`git config --global github.user`
github_key=`git config --global github.token`
curl -k -F "login=$github_user" -F "token=$github_key" -i https://github.com/api/v2/json/repos/create -F 'name=ZCA/ZenPacks.community.gitify' -F 'description=Fill in a description for this ZenPack'

You will know this works based on the response. You’ll see some JSON indicating success. Now its time to push everything up to GitHub:

git push -u origin master

You can now remove the pack from your installation:

cd /tmp
zenpack --remove=ZenPacks.community.gitify

That should just above cover it. You can test by checking out the new git repo into a seperate directory and doing a development install:

mkdir /tmp/install_test
cd /tmp/install_test
git clone git://github.com/ZCA/ZenPacks.community.gitify.git
zenpack --link --install=ZenPacks.community.gitify
zenpack --list
zenpack --remove=ZenPacks.community.gitify