Forge Home

ovhipfailover

Network interface and OVH IP failover Puppet module

9,952 downloads

9,553 latest version

0.7 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.3.2 (latest)
  • 0.3.1 (deleted)
  • 0.3.0 (deleted)
  • 0.2.0 (deleted)
  • 0.1.1 (deleted)
released Jun 23rd 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'tuxomatic-ovhipfailover', '0.3.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add tuxomatic-ovhipfailover
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install tuxomatic-ovhipfailover --version 0.3.2

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

tuxomatic/ovhipfailover — version 0.3.2 Jun 23rd 2014

OVH IP failover

This Puppet module is meant to ease the implementation of multiple network interfaces on a server and leverage special network solutions offered by the hosting company OVH.

Network interface via RedHat type network script

  • General network interface, private/public.
  • Virtual interfaces, included the ones offered by OVH as part of their vRack solution.

Manage a failover IP from OVH via an init script

  • Wraps underlying calls to the OVH API to control the routing destination of the IP (works between different data centers).
  • Can control virtual interface state regardless of subnet which isn't possible with OCF scripts such as RedHat's rgmanager.

Example

You can manage in a single definition a virtual interface with failover capability provided by OVH. Apply the definition on serverB by just changing the destination_fqdn to "serverA" and device name if differently mapped.

 class { 'ovhipfailover':
       ipaddress => "x.x.x.x",
       device => "ethX:X",
       destination_fqdn => "serverB.domain.com",
       application_key => "",
       application_secret => "",
       consumer_key => "",
 }

To obtain a consumer key to use on the OVH API after creating an application key and secret, use the embedded Python script. Calling the script will return a consumer key and a link to the validation url, you should choose an "illimited" time validity for your consumer key.

./ovh_ip_failover.py POST /auth/credential <APPLICATION_KEY> <APPLICATION_SECRET>

By using the failover init script in a cluster resource manager such as rgmanager or Pacemaker, a true HA solution can be implemented across multiple OVH datacenters. No extra parameter is needed to call the script as a standard init script resource.