r797 - in zenoss: branches/upstream/1.1.1/inst/docs
branches/upstream/current/inst/docs trunk/inst/docs
Bernd Zeimetz
bzed-guest at alioth.debian.org
Fri Apr 13 11:45:51 UTC 2007
Author: bzed-guest
Date: 2007-04-13 11:45:51 +0000 (Fri, 13 Apr 2007)
New Revision: 797
Removed:
zenoss/branches/upstream/1.1.1/inst/docs/Admin_Guide_1.0_Screens/
zenoss/branches/upstream/1.1.1/inst/docs/CompatibilityMatrix.txt
zenoss/branches/upstream/1.1.1/inst/docs/QuickStartGuide-1.0/
zenoss/branches/upstream/1.1.1/inst/docs/UPGRADE.txt
zenoss/branches/upstream/1.1.1/inst/docs/ZenossAdminGuide-1.0.0.doc
zenoss/branches/upstream/1.1.1/inst/docs/ZenossAdminGuide-1.1.doc
zenoss/branches/upstream/1.1.1/inst/docs/ZenossVirtualAppliance.txt
zenoss/branches/upstream/current/inst/docs/Admin_Guide_1.0_Screens/
zenoss/branches/upstream/current/inst/docs/CompatibilityMatrix.txt
zenoss/branches/upstream/current/inst/docs/QuickStartGuide-1.0/
zenoss/branches/upstream/current/inst/docs/UPGRADE.txt
zenoss/branches/upstream/current/inst/docs/ZenossAdminGuide-1.0.0.doc
zenoss/branches/upstream/current/inst/docs/ZenossAdminGuide-1.1.doc
zenoss/branches/upstream/current/inst/docs/ZenossVirtualAppliance.txt
zenoss/trunk/inst/docs/Admin_Guide_1.0_Screens/
zenoss/trunk/inst/docs/CompatibilityMatrix.txt
zenoss/trunk/inst/docs/QuickStartGuide-1.0/
zenoss/trunk/inst/docs/UPGRADE.txt
zenoss/trunk/inst/docs/ZenossAdminGuide-1.0.0.doc
zenoss/trunk/inst/docs/ZenossAdminGuide-1.1.doc
zenoss/trunk/inst/docs/ZenossVirtualAppliance.txt
Log:
removing a lot of not needed stuff, which will not be in the repackaged tar.gz anymore
Deleted: zenoss/branches/upstream/1.1.1/inst/docs/CompatibilityMatrix.txt
===================================================================
--- zenoss/branches/upstream/1.1.1/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/1.1.1/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,65 +0,0 @@
-Zenoss Compatibility Matrix
-===========================
-
-Installation Packages: Native and Source Based
-
-When possible, Zenoss engineers package the core product into native
-installer format (e.g. RPM, DEB). Packing into native format provides
-a familiar and straightforward installation path for most system
-administrators. Native installation packages exist for some of the
-commonly used Linux based operating systems. Native installation
-packages offer a high degree of confidence that an installation of
-Zenoss will be successful and comprehensive. When a native
-installation package is available it should be used (unless there is a
-compelling reason to avoid it).
-
-Source based installation packages are available for any system
-administrator that wishes to use them. When a native installation
-package does not exist, the source based installation package can be
-used to install Zenoss. We strive to keep the source based
-installation package as comprehensive and complete as the native
-installers, but inevitably distribution specific errors are
-discovered. The source based installation package is intended for
-experienced system administrators.
-
-
-Installation Procedure: Manual or Automated
-
-Source based installation packages are not supported by the automated
-installers. System administrators must perform the installation
-manually using the installation instructions documented on the
-website. Although manual, the source based installation procedure
-works well on a large variety of platforms. As the number of Zenoss
-users using a source based installation package on a given platform
-increases, the likelihood of a native installer package increases as
-well. If you succeed in installing a source based installation
-package on an undocumented platform please send an email to the
-zenoss-users mailing list.
-
-Native installation packages can be installed using a manual or
-automated procedure. The manual installation procedure for native
-packages typically involves a set of commands system administrators
-should run to install dependent packages, configure the operating
-system environment, create users, and set up other configurations.
-Although manual, they do offer a degree of control and customization
-over the automated installation procedure (which makes choices on
-behalf of the system administrator). The automated installation
-procedure is simply a shell script comprised of the steps identified
-in the manual installation procedure. The automated installation
-scripts can be downloaded from the Zenoss website.
-
-
-The following compatibility matrix identifies Unix based distributions
-and versions on the left hand side and Zenoss compatibility along the
-top. The existence of a native installer is identified (source based
-installation is always an option), as well as the procedures (manual
-and automated) that are compatible with the given distribution and
-version. In several cases Zenoss engineers have extrapolated
-compatibility information by inferring relative differences in
-operating systems. For example, Zenoss may not have been tested under
-FreeBSD 6.1 in the lab but end-users report success. Additionally,
-Fedora Core 5 and Fedora Core 6 are technically very similar, and
-although never officially tested Zenoss should run under Fedora Core
-5. If there are additional data compatibility points that have not
-been identified please feel free to send us an email on the
-zenoss-users mailing list.
Deleted: zenoss/branches/upstream/1.1.1/inst/docs/UPGRADE.txt
===================================================================
--- zenoss/branches/upstream/1.1.1/inst/docs/UPGRADE.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/1.1.1/inst/docs/UPGRADE.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,93 +0,0 @@
-Upgrade to new version of Zenoss
-
-There are separate sections below for:
-* Upgrading using the tar ball
-* Upgrading an rpm installation
-* Upgrading the virtual appliance image
-
-Please follow the directions appropriate for your installation.
-
-
-** Upgrade using tar ball
-
-Download and extract new tar ball, run install.sh:
- # tar zxf zenoss-1.1.0.tar.gz
- # cd zenoss-1.1.0
- # ./install.sh
-
-
-** Upgrade the RPM to a new version
-
-Download the new RPM from SourceForge and become root. Shut down the
-existing Zenoss server using this command (run as root):
- # /etc/init.d/zenoss stop
- # ps auxww | grep zenoss
-
-After running the ps command you should only see some MySQL processes. The
-RPM will kill off any zenoss processes it sees running (except for the MySQL
-ones), but it does so using the kill command. Using the above code gracefully
-shuts down zenoss, and it is highly recommended you run
-the {{{/etc/init.d/zenoss stop}}} and {{{ps auxww | grep zenoss}}} commands
-before proceeding to the next step: upgrade.
-
-First lay down the new files contained within the RPM and then start up zenoss.
-The following commands illustrate (run them as root):
- # rpm -Uvh zenoss-1.1.0-0.i386.rpm
- # service zenoss start
-
-
-** Updating the Zenoss Virtual Appliance Image
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss-var.tar.gz ./var
-
-Run appliance_update.sh
- # ./appliance_update.sh
-
-
-** Upgrade a trunk based install
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss.tar.gz .
-
-Retrieve the latest install scripts:
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-If install fails, cleanup and restore with:
- # make clean
- # tar -xzvf /tmp/zenoss.tar.gz
-
-
-** Switch from a tarball or rpm based install to a trunk based install
-
-Use zenbackup.py to create a .tgz file containing a dump of Zenoss data and configurations:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz
-
-Retrieve the latest install scripts:
- # cd $ZENHOME
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-Use zenbackup.py to restore the Zenoss data and configurations from backup.tgz:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz --restore
-
-
Deleted: zenoss/branches/upstream/1.1.1/inst/docs/ZenossAdminGuide-1.0.0.doc
===================================================================
(Binary files differ)
Deleted: zenoss/branches/upstream/1.1.1/inst/docs/ZenossAdminGuide-1.1.doc
===================================================================
(Binary files differ)
Deleted: zenoss/branches/upstream/1.1.1/inst/docs/ZenossVirtualAppliance.txt
===================================================================
--- zenoss/branches/upstream/1.1.1/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/1.1.1/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,49 +0,0 @@
-Installing and Using the Zenoss Virtual Appliance and Vmware Player
-
-1. Download the Free VMware Player
-The free VMware player is available from:
-
-http://www.vmware.com/download/player/
-
-For a typical host system for a VMware installation, you should have a 400MHz or faster processor (500MHz recommended) and 128MB RAM minimum (256MB RAM recommended). You must have enough memory to run the host operating system, plus the memory required for each guest operating system and for applications on the host and guest. Hard disk space requirements consist of at least 1GB free disk space for each guest operating system
-
-NOTE: You can also run the virtual appliance using the free VMserver or workstation. In the type of configuration, you can run the Zenoss virtual appliance and also the sever which you can then monitor in a pure virtual environment on same machine. For more information about running Zenoss under this type of configuration, see the documentation from rpath.com.
-
-
-2. Download the Zenoss Virtual Appliance from http://zenoss.com/download/
- The link you will follow is called “VMware Virtual Appliance Package” and is a .zip file.
-
-
-3. Once you have downloaded this file, unzip it into the directory where you want to work.
-
-
-4. Install and Start the VMware player.
-Use the instructions provided by the player to run the VMware player.
-
-
-5. When prompted, use the VMware player to navigate to the directory where you unzipped the Zenoss Virtual Appliance package and open the Zenoss Virtual Appliance.
-
-After loading the appliance, the URL you will use to connect to the Zenoss management console will be listed in the virtual machine window. It will appear similar to:
-Management console is available at: http://xxx.xxx.xxx.xxx:8080/zport/dmd
-
-
-6. Log in as user root.
-Local host login: root
-
-
-7. Open a new web browser (Zenoss runs most consistently using Mozilla Firefox) and enter the URL that appears in the login screen. When the login prompt appears, log in as:
- User: admin
- Password: zenoss
-
-
-8. Click OK.
- The main Zenoss Dashboard page appears.
-
-NOTE: We recommended that you changed your password to both the Zope server and the root user account. This is done by entering the following commands. Enter
-$ passwd
-and enter a new password to for the zenoss user password. Then enter:
-$ zenpass
-and enter a new password for Zope login.
-
-
-
Deleted: zenoss/branches/upstream/current/inst/docs/CompatibilityMatrix.txt
===================================================================
--- zenoss/branches/upstream/current/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/current/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,65 +0,0 @@
-Zenoss Compatibility Matrix
-===========================
-
-Installation Packages: Native and Source Based
-
-When possible, Zenoss engineers package the core product into native
-installer format (e.g. RPM, DEB). Packing into native format provides
-a familiar and straightforward installation path for most system
-administrators. Native installation packages exist for some of the
-commonly used Linux based operating systems. Native installation
-packages offer a high degree of confidence that an installation of
-Zenoss will be successful and comprehensive. When a native
-installation package is available it should be used (unless there is a
-compelling reason to avoid it).
-
-Source based installation packages are available for any system
-administrator that wishes to use them. When a native installation
-package does not exist, the source based installation package can be
-used to install Zenoss. We strive to keep the source based
-installation package as comprehensive and complete as the native
-installers, but inevitably distribution specific errors are
-discovered. The source based installation package is intended for
-experienced system administrators.
-
-
-Installation Procedure: Manual or Automated
-
-Source based installation packages are not supported by the automated
-installers. System administrators must perform the installation
-manually using the installation instructions documented on the
-website. Although manual, the source based installation procedure
-works well on a large variety of platforms. As the number of Zenoss
-users using a source based installation package on a given platform
-increases, the likelihood of a native installer package increases as
-well. If you succeed in installing a source based installation
-package on an undocumented platform please send an email to the
-zenoss-users mailing list.
-
-Native installation packages can be installed using a manual or
-automated procedure. The manual installation procedure for native
-packages typically involves a set of commands system administrators
-should run to install dependent packages, configure the operating
-system environment, create users, and set up other configurations.
-Although manual, they do offer a degree of control and customization
-over the automated installation procedure (which makes choices on
-behalf of the system administrator). The automated installation
-procedure is simply a shell script comprised of the steps identified
-in the manual installation procedure. The automated installation
-scripts can be downloaded from the Zenoss website.
-
-
-The following compatibility matrix identifies Unix based distributions
-and versions on the left hand side and Zenoss compatibility along the
-top. The existence of a native installer is identified (source based
-installation is always an option), as well as the procedures (manual
-and automated) that are compatible with the given distribution and
-version. In several cases Zenoss engineers have extrapolated
-compatibility information by inferring relative differences in
-operating systems. For example, Zenoss may not have been tested under
-FreeBSD 6.1 in the lab but end-users report success. Additionally,
-Fedora Core 5 and Fedora Core 6 are technically very similar, and
-although never officially tested Zenoss should run under Fedora Core
-5. If there are additional data compatibility points that have not
-been identified please feel free to send us an email on the
-zenoss-users mailing list.
Deleted: zenoss/branches/upstream/current/inst/docs/UPGRADE.txt
===================================================================
--- zenoss/branches/upstream/current/inst/docs/UPGRADE.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/current/inst/docs/UPGRADE.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,93 +0,0 @@
-Upgrade to new version of Zenoss
-
-There are separate sections below for:
-* Upgrading using the tar ball
-* Upgrading an rpm installation
-* Upgrading the virtual appliance image
-
-Please follow the directions appropriate for your installation.
-
-
-** Upgrade using tar ball
-
-Download and extract new tar ball, run install.sh:
- # tar zxf zenoss-1.1.0.tar.gz
- # cd zenoss-1.1.0
- # ./install.sh
-
-
-** Upgrade the RPM to a new version
-
-Download the new RPM from SourceForge and become root. Shut down the
-existing Zenoss server using this command (run as root):
- # /etc/init.d/zenoss stop
- # ps auxww | grep zenoss
-
-After running the ps command you should only see some MySQL processes. The
-RPM will kill off any zenoss processes it sees running (except for the MySQL
-ones), but it does so using the kill command. Using the above code gracefully
-shuts down zenoss, and it is highly recommended you run
-the {{{/etc/init.d/zenoss stop}}} and {{{ps auxww | grep zenoss}}} commands
-before proceeding to the next step: upgrade.
-
-First lay down the new files contained within the RPM and then start up zenoss.
-The following commands illustrate (run them as root):
- # rpm -Uvh zenoss-1.1.0-0.i386.rpm
- # service zenoss start
-
-
-** Updating the Zenoss Virtual Appliance Image
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss-var.tar.gz ./var
-
-Run appliance_update.sh
- # ./appliance_update.sh
-
-
-** Upgrade a trunk based install
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss.tar.gz .
-
-Retrieve the latest install scripts:
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-If install fails, cleanup and restore with:
- # make clean
- # tar -xzvf /tmp/zenoss.tar.gz
-
-
-** Switch from a tarball or rpm based install to a trunk based install
-
-Use zenbackup.py to create a .tgz file containing a dump of Zenoss data and configurations:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz
-
-Retrieve the latest install scripts:
- # cd $ZENHOME
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-Use zenbackup.py to restore the Zenoss data and configurations from backup.tgz:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz --restore
-
-
Deleted: zenoss/branches/upstream/current/inst/docs/ZenossAdminGuide-1.0.0.doc
===================================================================
(Binary files differ)
Deleted: zenoss/branches/upstream/current/inst/docs/ZenossAdminGuide-1.1.doc
===================================================================
(Binary files differ)
Deleted: zenoss/branches/upstream/current/inst/docs/ZenossVirtualAppliance.txt
===================================================================
--- zenoss/branches/upstream/current/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/branches/upstream/current/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,49 +0,0 @@
-Installing and Using the Zenoss Virtual Appliance and Vmware Player
-
-1. Download the Free VMware Player
-The free VMware player is available from:
-
-http://www.vmware.com/download/player/
-
-For a typical host system for a VMware installation, you should have a 400MHz or faster processor (500MHz recommended) and 128MB RAM minimum (256MB RAM recommended). You must have enough memory to run the host operating system, plus the memory required for each guest operating system and for applications on the host and guest. Hard disk space requirements consist of at least 1GB free disk space for each guest operating system
-
-NOTE: You can also run the virtual appliance using the free VMserver or workstation. In the type of configuration, you can run the Zenoss virtual appliance and also the sever which you can then monitor in a pure virtual environment on same machine. For more information about running Zenoss under this type of configuration, see the documentation from rpath.com.
-
-
-2. Download the Zenoss Virtual Appliance from http://zenoss.com/download/
- The link you will follow is called “VMware Virtual Appliance Package” and is a .zip file.
-
-
-3. Once you have downloaded this file, unzip it into the directory where you want to work.
-
-
-4. Install and Start the VMware player.
-Use the instructions provided by the player to run the VMware player.
-
-
-5. When prompted, use the VMware player to navigate to the directory where you unzipped the Zenoss Virtual Appliance package and open the Zenoss Virtual Appliance.
-
-After loading the appliance, the URL you will use to connect to the Zenoss management console will be listed in the virtual machine window. It will appear similar to:
-Management console is available at: http://xxx.xxx.xxx.xxx:8080/zport/dmd
-
-
-6. Log in as user root.
-Local host login: root
-
-
-7. Open a new web browser (Zenoss runs most consistently using Mozilla Firefox) and enter the URL that appears in the login screen. When the login prompt appears, log in as:
- User: admin
- Password: zenoss
-
-
-8. Click OK.
- The main Zenoss Dashboard page appears.
-
-NOTE: We recommended that you changed your password to both the Zope server and the root user account. This is done by entering the following commands. Enter
-$ passwd
-and enter a new password to for the zenoss user password. Then enter:
-$ zenpass
-and enter a new password for Zope login.
-
-
-
Deleted: zenoss/trunk/inst/docs/CompatibilityMatrix.txt
===================================================================
--- zenoss/trunk/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/trunk/inst/docs/CompatibilityMatrix.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,65 +0,0 @@
-Zenoss Compatibility Matrix
-===========================
-
-Installation Packages: Native and Source Based
-
-When possible, Zenoss engineers package the core product into native
-installer format (e.g. RPM, DEB). Packing into native format provides
-a familiar and straightforward installation path for most system
-administrators. Native installation packages exist for some of the
-commonly used Linux based operating systems. Native installation
-packages offer a high degree of confidence that an installation of
-Zenoss will be successful and comprehensive. When a native
-installation package is available it should be used (unless there is a
-compelling reason to avoid it).
-
-Source based installation packages are available for any system
-administrator that wishes to use them. When a native installation
-package does not exist, the source based installation package can be
-used to install Zenoss. We strive to keep the source based
-installation package as comprehensive and complete as the native
-installers, but inevitably distribution specific errors are
-discovered. The source based installation package is intended for
-experienced system administrators.
-
-
-Installation Procedure: Manual or Automated
-
-Source based installation packages are not supported by the automated
-installers. System administrators must perform the installation
-manually using the installation instructions documented on the
-website. Although manual, the source based installation procedure
-works well on a large variety of platforms. As the number of Zenoss
-users using a source based installation package on a given platform
-increases, the likelihood of a native installer package increases as
-well. If you succeed in installing a source based installation
-package on an undocumented platform please send an email to the
-zenoss-users mailing list.
-
-Native installation packages can be installed using a manual or
-automated procedure. The manual installation procedure for native
-packages typically involves a set of commands system administrators
-should run to install dependent packages, configure the operating
-system environment, create users, and set up other configurations.
-Although manual, they do offer a degree of control and customization
-over the automated installation procedure (which makes choices on
-behalf of the system administrator). The automated installation
-procedure is simply a shell script comprised of the steps identified
-in the manual installation procedure. The automated installation
-scripts can be downloaded from the Zenoss website.
-
-
-The following compatibility matrix identifies Unix based distributions
-and versions on the left hand side and Zenoss compatibility along the
-top. The existence of a native installer is identified (source based
-installation is always an option), as well as the procedures (manual
-and automated) that are compatible with the given distribution and
-version. In several cases Zenoss engineers have extrapolated
-compatibility information by inferring relative differences in
-operating systems. For example, Zenoss may not have been tested under
-FreeBSD 6.1 in the lab but end-users report success. Additionally,
-Fedora Core 5 and Fedora Core 6 are technically very similar, and
-although never officially tested Zenoss should run under Fedora Core
-5. If there are additional data compatibility points that have not
-been identified please feel free to send us an email on the
-zenoss-users mailing list.
Deleted: zenoss/trunk/inst/docs/UPGRADE.txt
===================================================================
--- zenoss/trunk/inst/docs/UPGRADE.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/trunk/inst/docs/UPGRADE.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,93 +0,0 @@
-Upgrade to new version of Zenoss
-
-There are separate sections below for:
-* Upgrading using the tar ball
-* Upgrading an rpm installation
-* Upgrading the virtual appliance image
-
-Please follow the directions appropriate for your installation.
-
-
-** Upgrade using tar ball
-
-Download and extract new tar ball, run install.sh:
- # tar zxf zenoss-1.1.0.tar.gz
- # cd zenoss-1.1.0
- # ./install.sh
-
-
-** Upgrade the RPM to a new version
-
-Download the new RPM from SourceForge and become root. Shut down the
-existing Zenoss server using this command (run as root):
- # /etc/init.d/zenoss stop
- # ps auxww | grep zenoss
-
-After running the ps command you should only see some MySQL processes. The
-RPM will kill off any zenoss processes it sees running (except for the MySQL
-ones), but it does so using the kill command. Using the above code gracefully
-shuts down zenoss, and it is highly recommended you run
-the {{{/etc/init.d/zenoss stop}}} and {{{ps auxww | grep zenoss}}} commands
-before proceeding to the next step: upgrade.
-
-First lay down the new files contained within the RPM and then start up zenoss.
-The following commands illustrate (run them as root):
- # rpm -Uvh zenoss-1.1.0-0.i386.rpm
- # service zenoss start
-
-
-** Updating the Zenoss Virtual Appliance Image
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss-var.tar.gz ./var
-
-Run appliance_update.sh
- # ./appliance_update.sh
-
-
-** Upgrade a trunk based install
-
-Login as the zenoss user. To log in as the zenoss user, when prompted for log
-in, first, log in as root, then enter the command to log in as the zenoss user:
- # su - zenoss
-
-Make a backup of your data. Use the following command to create a copy
-of ZENHOME:
- # cd $ZENHOME
- # tar -czvf /tmp/zenoss.tar.gz .
-
-Retrieve the latest install scripts:
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-If install fails, cleanup and restore with:
- # make clean
- # tar -xzvf /tmp/zenoss.tar.gz
-
-
-** Switch from a tarball or rpm based install to a trunk based install
-
-Use zenbackup.py to create a .tgz file containing a dump of Zenoss data and configurations:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz
-
-Retrieve the latest install scripts:
- # cd $ZENHOME
- # svn co http://dev.zenoss.org/svn/trunk/inst zenossinst
-
-Install zenoss from its install directory:
- # cd zenossinst
- # ./install.sh
-
-Use zenbackup.py to restore the Zenoss data and configurations from backup.tgz:
- # $ZENHOME/bin/zenbackup.py --dbname=events --dbuser=root --dbpass=None --file=backup.tgz --restore
-
-
Deleted: zenoss/trunk/inst/docs/ZenossAdminGuide-1.0.0.doc
===================================================================
(Binary files differ)
Deleted: zenoss/trunk/inst/docs/ZenossAdminGuide-1.1.doc
===================================================================
(Binary files differ)
Deleted: zenoss/trunk/inst/docs/ZenossVirtualAppliance.txt
===================================================================
--- zenoss/trunk/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:44:24 UTC (rev 796)
+++ zenoss/trunk/inst/docs/ZenossVirtualAppliance.txt 2007-04-13 11:45:51 UTC (rev 797)
@@ -1,49 +0,0 @@
-Installing and Using the Zenoss Virtual Appliance and Vmware Player
-
-1. Download the Free VMware Player
-The free VMware player is available from:
-
-http://www.vmware.com/download/player/
-
-For a typical host system for a VMware installation, you should have a 400MHz or faster processor (500MHz recommended) and 128MB RAM minimum (256MB RAM recommended). You must have enough memory to run the host operating system, plus the memory required for each guest operating system and for applications on the host and guest. Hard disk space requirements consist of at least 1GB free disk space for each guest operating system
-
-NOTE: You can also run the virtual appliance using the free VMserver or workstation. In the type of configuration, you can run the Zenoss virtual appliance and also the sever which you can then monitor in a pure virtual environment on same machine. For more information about running Zenoss under this type of configuration, see the documentation from rpath.com.
-
-
-2. Download the Zenoss Virtual Appliance from http://zenoss.com/download/
- The link you will follow is called “VMware Virtual Appliance Package” and is a .zip file.
-
-
-3. Once you have downloaded this file, unzip it into the directory where you want to work.
-
-
-4. Install and Start the VMware player.
-Use the instructions provided by the player to run the VMware player.
-
-
-5. When prompted, use the VMware player to navigate to the directory where you unzipped the Zenoss Virtual Appliance package and open the Zenoss Virtual Appliance.
-
-After loading the appliance, the URL you will use to connect to the Zenoss management console will be listed in the virtual machine window. It will appear similar to:
-Management console is available at: http://xxx.xxx.xxx.xxx:8080/zport/dmd
-
-
-6. Log in as user root.
-Local host login: root
-
-
-7. Open a new web browser (Zenoss runs most consistently using Mozilla Firefox) and enter the URL that appears in the login screen. When the login prompt appears, log in as:
- User: admin
- Password: zenoss
-
-
-8. Click OK.
- The main Zenoss Dashboard page appears.
-
-NOTE: We recommended that you changed your password to both the Zope server and the root user account. This is done by entering the following commands. Enter
-$ passwd
-and enter a new password to for the zenoss user password. Then enter:
-$ zenpass
-and enter a new password for Zope login.
-
-
-
More information about the pkg-zope-commits
mailing list