Deployment Automation

Contents

Debian Software Package

RPM package Manager

Chef

Puppet

Ansible

SaltStack

Heroku

AWS ElasticBeanstalk

Testing the Installation

 

This page includes instructions for advanced environments. If your environment is not included in the OverOps documentation, contact OverOps support at hello@overops.com.

 

Debian Software Package (Ubuntu/Debian)

To install OverOps on Ubuntu/Debian:

  1. Add OverOps to your deb repository:
    sudo sh -c "echo 'deb [arch=amd64] http://takipi-deb-repo.s3.amazonaws.com stable main' >> /etc/apt/sources.list.d/takipi.list"
  2. Add the OverOps gpg public key:
    wget -O - http://takipi-deb-repo.s3.amazonaws.com/hello@takipi.com.gpg.key | sudo apt-key add -
  3. Update apt-get:
    sudo apt-get update
  4. Install OverOps:
    sudo apt-get install takipi
  5. Enter your installation key as the <MyKey> argument:
    sudo /opt/takipi/etc/takipi-setup-package <MyKey>
  6. Optional: set up a proxy connection:
    /opt/takipi/etc/takipi-setup-proxy <MyProxyAddress> (e.g. http://user:pass@192.168.1.101:8080/)
  7. Add the -agentlib:TakipiAgent JVM argument to the Java processes to monitor and restart it.
     

RPM Package Manager (RedHat/Centos)

  1. Write the following into a OverOps repository file named /etc/yum.repos.d/takipi.repo[takipi]
    name=Takipi Repository
    baseurl=https://s3.amazonaws.com/takipi-rpm-repo
    gpgcheck=1
    enabled=1
  2. Add the OverOps gpg public keysudo rpm --import https://s3.amazonaws.com/takipi-rpm-repo/hello%40takipi.com.gpg.key
  3. Install OverOps:
    sudo yum install takipi
  4. Enter your installation key as the <MyKey> argument.
    sudo /opt/takipi/etc/takipi-setup-package <MyKey>
  5. Optional: set up a proxy connection 
    /opt/takipi/etc/takipi-setup-proxy <MyProxyAddress> (e.g. http://user:pass@192.168.1.101:8080/)
  6. Add the -agentlib:TakipiAgent JVM argument to the Java processes to monitor and restart it.

 

Chef

The OverOps Chef cookbook is available at https://github.com/takipi-cookbooks/takipi.

To install OverOps with Chef cookbook:

  1. Configure the name for the server, and the installation key:
    default["takipi"]["server_name"] = "YOUR SERVER NAME HERE"default["takipi"]["secret_key"] = "YOUR SECRET KEY HERE"
  2. Add the -agentlib:TakipiAgent JVM argument to the Java processes to monitor and restart it.

 

Puppet

The OverOps Puppet module is available at https://github.com/takipi/takipi-puppet. Detailed instructions are available on the Github page.

The module requires the puppetlabs-stdlib and puppetlabs-javalibraries.

Usage:
include takipi
class {'::takipi':
secret_key => <INSTALLATION_KEY>,
}

Ansible

The Ansible playbook is available at https://github.com/takipi/takipi-playbooks.

To install OverOps for Ansible:

  1. Run the playbook against your server with:
    ansible-playbook -i inventory site.yml<>/code
  2. In inventory.ini, add the hostname:
    [remote]
    example.com ansible_ssh_user=root
  3. Add your API Key in roles/common/vars/main.yml or group_vars/all.yml:
    takipi:
    SECRET_KEY: <INSTALLATION_KEY>

SaltStack

The OverOps formula for SaltStack is available at https://github.com/takipi/takipi-formula.

Make sure to include your OverOps secret key as custom the salt/minion file:
grains:
takipi:
secret_key: <INSTALLATION_KEY>
machine_name: ""

 

Heroku

Installing OverOps through Heroku requires the use of a custom buildpack. Instructions are available at: https://github.com/takipi/heroku-buildpack-takipi.

 

AWS ElasticBeanstalk

To install OverOps on AWS ElasticBeanstalk, visit https://github.com/takipi/takipi-ebextensions. The package and instructions are available on Github through the link.

Installing OverOps on AWS ElasticBeanstalk requires an eb-extensions file.

 

Testing the Installation

After following the instructions for any of the above environments, test the installation.

To test the installation:

  1. From the OverOps web application (app.overops.com) Dashboard, click Add Server and then, from the dialog box, click Next and then click Test Installation.

    When the connection is established, the JVM status is 'Monitoring'.
  2. Test that your application throws exceptions.

 

Have more questions? Submit a request