Forge Home

networker

Manages EMC Networker client

6,224 downloads

6,224 latest version

3.6 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.0 (latest)
released Dec 18th 2017

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jgazeley-networker', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jgazeley-networker
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jgazeley-networker --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

jgazeley/networker — version 0.1.0 Dec 18th 2017

networker

Table of Contents

  1. Overview
  2. Usage - Configuration options and additional functionality
  3. Limitations - OS compatibility, etc.
  4. Development - Guide for contributing to the module

Overview

This module installs the client part of EMC Networker backup software on Linux servers.

You will need to separately configure a suitable package repository to provide the lgtoclnt package.

Usage

Usage is straightforward. The only mandatory parameter is server. Only set the service and connections ports if your site is configured differently from the defaults shown below.

class { networker:
  service_ports    => '7937-7999',
  connection_ports => '10001-30000',
  server           => 'server.example.com'
  nsr_file         => 'puppet:///modules/networker/dotnsr'
}

Unless an alternative is specified, the default the dotnsr file is deployed.

Limitations

Tested on CentOS, may work on other platforms.

Development

Pull requests are gratefully received.

Testing

Beaker acceptance tests can be run using bundle exec rake beaker. You will have to set a few site specific environment variables to make the tests useful.

REPO: A URL to a yum repo where the Networker packages can be found

Example:

BEAKER_destroy=no NSRSRV=anubis.bris.ac.uk REPO='http://packages.example.com/centos/$releasever/$basearch' bundle exec rake beaker