Landing bot alive again

[Martin Packman]

At second attempt, the landing bot is now running again, moved over to
lcy01. Feel free to mark any branches 'Approved' to land them.

As part of the setup, several people's keys were added to the tarmac
machine, but most management should be possible remotely by setting
juju service config now.

First source the credentials of the juju-tools-project user:

  $ source .gobotcreds

Then get the juju environment details from the swift bucket (note,
this was set up with 1.16 so may need some tweaking for a trunk
client).

  $ (cd ~/.juju/environments && swift download tarmac gobotnext.jenv)

Then fetch the tarmac service config too:

  $ swift download tarmac gobotnext.yaml

If needed update the config-changed-script config key in that file.

  $ juju set  -e gobotnext --config gobotnext.yaml tarmac

This will update packages and add new go dependencies automatically.


The bot can be setup from scratch again using the custom tarmac charm
and the service config from before.

The tarmac charm changes are mostly just adding bzr 2.6 support and a
script injection mechanism, branch is at
<lp:~juju/charms/precise/tarmac/gobotnext>.

Only minimal environments.yaml needed, juju can generate most things
for the jenv.

    gobotnext:
        type: openstack
        ca-cert-path: ~/.juju/gobot-cert.pem
        ca-private-key-path: ~/.juju/gobot-private-key.pem

We could leave juju to generate the keys too, rather than using those
ones from tarmac container on swift.

Then it's just:

  $ juju bootstrap -e gobotnext

  $ juju set-constraints -e gobotnext mem=4G cpu-cores=2

  $ juju deploy -e gobotnext --config=gobotnext.yaml local:precise/tarmac


Hopefully we won't need to do much more fiddling before we're able to
move to a new setup with jenkins alongside the CI work.

Martin