Deployment

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2012-12-05 14:45:34 →
Size: 3661
Editor: pitti
Comment: fix deployment branch and deploy command
← Revision 3 as of 2012-12-05 14:55:15 → ⇥
Size: 3449
Editor: pitti
Comment: simplify with run-juju-daisy script
Deletions are marked like this. Additions are marked like this.
Line 57: Line 57:
Once all the nodes and relations are out of the pending state, you should be able to start throwing crashes at it. You'll probably want to use tmux or some other terminal multiplexer for this. Once all the nodes and relations are out of the pending state, you should be able to start throwing crashes at it. The following command sets up various SSH tunnels to the Juju instances of daisy and errors, redirects the local whoopsie daemon to report crashes against the Juju daisy instance instead of errors.ubuntu.com, and shows the local whoopsie and remote daisy-retracer logs until you press Control-C:
Line 59: Line 59:
Shell #1:
Line 61: Line 60:
DAISY_ADDRESS="$(juju status daisy/0 | grep public-address | sed 's,.*public-address: \(.*\)$,\1,')"
ssh -N -L 8080:$DAISY_ADDRESS:80 $DAISY_ADDRESS		 ~/bzr/error-tracker-deployment/run-juju-daisy
Line 65: Line 63:
Shell #2: This script has a commented out alternative of the ssh command to daisy which shows the Apache logs. Enable this, and disable the default one below if you want to debug problems with uploading the .crash files.

Now generate a crash report with e. g.
Line 67: Line 67:
ERRORS_ADDRESS="$(juju status errors/0 | grep public-address | sed 's,.*public-address: \(.*\)$,\1,')"
ssh -N -L 8081:$ERRORS_ADDRESS:80 $ERRORS_ADDRESS		 bash -c 'kill -SEGV $$'
Line 71: Line 70:
and elect to report the crash in the popping up Apport window.

Now open a browser to http://localhost:8081. You should have one problem in the most common problems table.

You might also want to watch out for (TODO: what's this for?)
Line 72: Line 77:
{{{
sudo stop whoopsie
bzr branch lp:whoopsie ~/bzr/whoopsie
cd ~/bzr/whoopsie
make
sudo LD_LIBRARY_PATH=src CRASH_DB_URL=http://localhost:8080 ./src/whoopsie -f
}}}

Shell #4:
{{{
JUJU_ENV=canonistackone juju ssh daisy/0
tail -f /var/log/apache2/error.log -f /var/log/apache2/access.log
}}}

Shell #5:
Line 91: Line 81:

Shell #6:
{{{
JUJU_ENV=canonistackone juju ssh daisy-retracer/0
tail -f /var/log/retracer.log
}}}

Shell #7:
{{{
gedit &; PID="$\!"; sleep 3; kill -SEGV $PID
# Elect to submit the error report when the apport dialog appears.
}}}

Now open a browser to http://localhost:8081. You should have one problem in the most common problems table.

This document will help you create instances of http://daisy.ubuntu.com and http://errors.ubuntu.com deployed in the cloud.

First you'll need to create an environment for Juju to bootstrap to. Follow the directions here to get a basic environment going. I'd suggest doing something akin to the following to bootstrap the initial node: 

source ~/.canonistack/novarc
export AWS_SECRET_ACCESS_KEY=$EC2_SECRET_KEY
export AWS_ACCESS_KEY_ID=$EC2_ACCESS_KEY
juju bootstrap -e canonistackone --constraints "instance-type=m1.medium"

This will ensure that the juju bootstrap node doesn't take ages to perform basic tasks because it's constantly going into swap.

You should end up with something similar to the following in your ~/.juju/environments.yaml: 

environments:
  canonistacktwo:
    type: openstack_s3
    default-instance-type: m1.medium
    control-bucket: juju-replace-me-with-your-bucket
    admin-secret: <secret>
    auth-url: https://keystone.canonistack.canonical.com:443/v2.0/
    access-key: <access key>
    secret-key: <secret key>
    default-series: precise
    juju-origin: ppa
    ssl-hostname-verification: True
    default-image-id: bb636e4f-79d7-4d6b-b13b-c7d53419fd5a
  canonistackone:
  type: ec2
    control-bucket: juju-replace-me-with-your-bucket
    admin-secret: <secret>
    ec2-uri: http://91.189.93.65:8773/services/Cloud
    s3-uri: http://91.189.93.65:3333
    default-image-id: ami-00000097
    access-key: <access key>
    secret-key: <secret key>
    default-series: precise
    ssl-hostname-verification: false
    origin: ppa
    authorized-keys-path: ~/.ssh/authorized_keys

Now you're ready to deploy the individual charms that make up daisy.ubuntu.com and errors.ubuntu.com: 

mkdir -p ~/bzr/precise
bzr branch lp:~ev/charms/precise/daisy/trunk ~/bzr/precise/daisy
bzr branch lp:~ev/charms/precise/daisy-retracer/trunk ~/bzr/precise/daisy-retracer
bzr branch lp:~ev/charms/precise/errors/trunk ~/bzr/precise/errors
bzr branch lp:error-tracker-deployment ~/bzr/error-tracker-deployment

source ~/.canonistack/novarc
JUJU_ENV=canonistackone ~/bzr/error-tracker-deployment/deploy

Follow along with JUJU_ENV=canonistackone juju status.

Once all the nodes and relations are out of the pending state, you should be able to start throwing crashes at it. The following command sets up various SSH tunnels to the Juju instances of daisy and errors, redirects the local whoopsie daemon to report crashes against the Juju daisy instance instead of errors.ubuntu.com, and shows the local whoopsie and remote daisy-retracer logs until you press Control-C: 

~/bzr/error-tracker-deployment/run-juju-daisy

This script has a commented out alternative of the ssh command to daisy which shows the Apache logs. Enable this, and disable the default one below if you want to debug problems with uploading the .crash files.

Now generate a crash report with e. g. 

bash -c 'kill -SEGV $$'

and elect to report the crash in the popping up Apport window.

Now open a browser to http://localhost:8081. You should have one problem in the most common problems table.

You might also want to watch out for (TODO: what's this for?)

Shell #3: 

JUJU_ENV=canonistackone juju ssh daisy/0
watch ls /srv/local-oopses-whoopsie

ErrorTracker/Deployment (last edited 2014-05-26 11:54:50 by brian-murray)