Zenoss in the cloud was installed multiple times. See below for each instantiation. See the TOC at right for an overview of the structure to this document. Later installs are latest and greatest.

1.0 Cloudbox VPC Install

Followed directions at:

Also a good beginner command-line tutorial is:

Setup and test EC2 API Tools

Create VPC instance

  • Went to UI and started to create an instance so that I could paruse the Community AMIs
  • Found suz-lab centos 5.4.5 images
  • Start instance
    • <del>ec2-run-instances ami-6b608c02 --key awsnickkey --monitor --subnet subnet-e43dfd8d --instance-type c1.medium</del>
      ec2-run-instances ami-6b608c02 --key awsnickkey --subnet subnet-e43dfd8d --monitor

First install on Public EC2

THIS IS NOW DOWN AND DEPRECATED. Please refer to VPC instructions

Used EBS image by suz lab. CentOS 2.4.5? (latest version) I put it on a Medium sized box (amazon sizing), as I figured that it may scale bigger later if we do any distributed monitoring. I turned on Elastic IP to make reaching the box over internet easier.

had to use yum install to install: wget screen locate

Installing everything you *have* to use screen. Its really neccessary. I was formerly getting issues when first installing Zenoss on earlier instances. It was at the point where you first start up the zenoss service and it goes into an initialization mode. The zope object database couldnt get created correctly. Kevin ended up noticing the symptoms and said that the machines host name needed to be correctly setup

echo "cloudbox.zenoss.com" > /proc/sys/kernel/hostname
nano /etc/hosts

/etc/hosts then had to look like

# IP            Hostname               Alias       localhost.localdomain  localhost   cloudbox.zenoss.com    cloudbox

then had to run a restart of the network service

service network restart

Error in UI

Noticed that drop down menu’s dont exist in UI. I logged in as admin and nyeates user, still no dropdowns. Weird.

2.0 Cloudbox Install of Zenoss beta

I wanted to use a rightscale AMI because this is the only CentOS image that I truly trust. Unfortunately this image does not use EBS; it used the instance-store storage method. EBS volumes are persistent and bootable, while instance-stores reset themselves to their original state when restarted.

The setup of the instance on Amazon, sizing, preping of the hosts file, opening of firewall ports, and the installing of zenoss was all done as shown in the prior install. Just now, we have to convert it to the persistant EBS volume.

The steps to convert are covered here:

technology/zenoss/cloudbox.txt · Last modified: 06.30.2010 17:23 by nyeates1
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki