No description, website, or topics provided.
Python Shell Ruby PHP Perl
Latest commit ab44453 Jun 21, 2014 @jcftang Update README.md
Permalink
Failed to load latest commit information.
archive-ubuntu
files
group_vars
hacking copy up the env-setup.fish for main repo usage Mar 18, 2014
handlers
hydra-stack
library
packer
playbooks
roles
tasks
templates
.gitignore remove execute bit on all files Jan 17, 2014
Makefile update makefile with deploy-app target May 13, 2014
README.md Update README.md Jun 21, 2014
ansible.cfg
buildshim
cleanup.yml more cleaning up Apr 22, 2014
hosts.vagrant
rolling_update.yml
site-base.yml squash deprecation warning May 7, 2014
site-noproxy-vagrant.yml
site-noproxy.yml
site-prepare.yml
site-vagrant.yml
site.yml

README.md

WARNING

This repo is no longer maintained by a TCD/TCHPC/DRI employee please visit https://www.tchpc.tcd.ie/tchpcstaff/ or http://www.dri.ie/dri-team and contact an existing employee for more up to date implementations etc...

README

WARNING These playbooks are getting too big to be deployed in a vagrant VM, so they may not work in vagrant.

Playbooks for deploying DRI test and development infrastructure

In the DRI test and development infrastructure for our Hydra Head we use primarily Ubuntu 12.04, mainly due to almost everything just working and better ceph support.

The goal of this set of plays is to be able to quickly setup a base system with Ubuntu and have at least the following applications installed ready to go for use with deploying a Hydra Head.

  • Tomcat (from the base repositories)
  • Fedora-Commons (the same version as is in the hydra-jetty repo)
  • Apache SOLR (the same version as is in the hydra-jetty repo)
  • Ruby (via RVM) in a user directory
  • Passenger with the installed version of Ruby
  • MySQL (from the base repositories)
  • Redis
  • Shibboleth
  • HAProxy
  • LDAP
  • Keepalived/Corosync/Pacemaker coming soon
  • Xymon

What's missing here is the deployment of the actual Hydra-Head. This part is not automated yet as it's not clear what we want to do this is area.

Also default usernames and passwords are used (from the upstream), these scripts are not yet ready for production usage.

Requirements

  • A target machine (or VM) that you can login to with ssh keys
  • The target machine should be running a flavour of Ubuntu 12.04
    • should be a fresh/stock install (a vagrant Ubuntu based basebox is great for testing against)
  • Ansible 1.5 or newer on your own host machine

Usage

Ideally first read up on how ansible works at http://www.ansible.cc.

To deploy the scripts on to a fresh set of machines, first setup your ansible hosts file. e.g. create a file in $HOME/.ansible_hosts or look at the hosts.vagrant file as an example. You may want to override some of the group_vars/all settings via the hosts file.

The IP address will be specific to your site. Then you can run one of the playbooks from the playbooks directory.

$ pwd
/home/jtang/ansible-hydra
$ ansible-playbook -i myhosts.file site.yml
[ lots of output ]

There are a number of playbooks in the playbooks directory, so have a poke around. A large amount of the work is actually done in the roles, so they may be a better place to look at to understand how things work.

Todo

  • A scrubbed version of a our production hosts file would be of interest to other users. This should be cleaned up and shared once we are back in a steady state of changes.