Difference between revisions of "ZenPack:Rundeck"

From Zenoss Wiki
Jump to: navigation, search
m
Line 6: Line 6:
 
|Source URI=git://github.com/dpetzel/ZenPacks.community.Rundeck.git
 
|Source URI=git://github.com/dpetzel/ZenPacks.community.Rundeck.git
 
|Releases={{Release
 
|Releases={{Release
|Version=1.0.1
+
|Version=1.0.0
 
|Tag=v1.0.0
 
|Tag=v1.0.0
 
|Release date=2013/06/10
 
|Release date=2013/06/10

Revision as of 02:32, 11 June 2013

Author(s)
David Petzel
Current Maintainer(s)
David Petzel
License
GNU General Public License, Version 2, or later
ZenPack name
ZenPacks.community.Rundeck
Git sources (for cloning)
Link


Applications Monitored: 



Rundeck ZenPack

Monitors Rundeck

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.

Releases

Version 1.0.0- Download
Summary of changes: Initial Release
Released on 2013/06/10
Compatible with Zenoss Core 3.2.x, Zenoss Core 4.2.x

Background

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.community.Rundeck-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone git://github.com/dpetzel/ZenPacks.community.Rundeck.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.community.Rundeck
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus