{"id":539,"date":"2011-12-07T09:53:46","date_gmt":"2011-12-07T17:53:46","guid":{"rendered":"http:\/\/www.outflux.net\/blog\/?p=539"},"modified":"2011-12-07T11:52:31","modified_gmt":"2011-12-07T19:52:31","slug":"how-to-throw-an-ec2-party","status":"publish","type":"post","link":"https:\/\/outflux.net\/blog\/archives\/2011\/12\/07\/how-to-throw-an-ec2-party\/","title":{"rendered":"how to throw an EC2 party"},"content":{"rendered":"

Prepare a location to run juju and install it:<\/p>\n

\r\nmkdir ~\/party\r\ncd ~\/party\r\nsudo apt-get install juju\r\n<\/pre>\n
Initialize your juju environment<\/a>. Be sure to add “juju-origin: ppa<\/code>” to your environment, along with filling in your access-key<\/code> and secret-key<\/code> from your Amazon AWS account. Note that control-bucket<\/code> and admin-secret<\/code> should not be used by any other environment or juju won’t be able to distinguish them. Other variables<\/a> are good to set now too. I wanted my instances close to me, use I set “region: us-west-1<\/code>“. I also wanted a 64bit system, so using the AMI list<\/a>, I chose “default-series: oneiric<\/code>“, “default-instance-type: m1.large<\/code>” and “default-image-id: ami-7b772b3e<\/code>”<\/p>\n
\r\njuju\r\n$EDITOR ~\/.juju\/environments.yaml\r\n<\/pre>\n
Get my sbuild charm<\/a>, and configure some types of builders. The salt<\/code> should be something used only for this party; it is used to generate the random passwords for the builder accounts. The distro<\/code> and releases<\/code> can be set to whatever the mk-sbuild<\/a> tool understands.<\/p>\n
\r\nbzr co lp:~kees\/charm\/oneiric\/sbuild\/trunk sbuild-charm\r\ncat >local.yaml <<EOM\r\nbuilder-debian:\r\n    salt: some-secret-phrase-for-this-party\r\n    distro: debian\r\n    releases: unstable\r\nbuilder-ubuntu:\r\n    salt: some-secret-phrase-for-this-party\r\n    distro: ubuntu\r\n    releases: precise,oneiric\r\nEOM\r\n<\/pre>\n
Bootstrap juju and wait for ec2 instance to come up.<\/p>\n
\r\njuju bootstrap\r\n<\/pre>\n
 Before running the status, you can either accept the SSH key blindly, or use “ec2-describe-instances<\/code><\/a>” to find the instance and public host name, and use my “wait-for-ssh<\/code>” tool to inject the SSH host key into your ~\/.ssh\/known_hosts<\/code> file. This requires having set up the environment variables needed by “ec2-describe-instances<\/code>“, though.<\/p>\n
\r\nec2-describe-instances --region REGION\r\n.\/sbuild-charm\/wait-for-ssh INSTANCE HOST REGION\r\n<\/pre>\n
Get status:<\/p>\n
\r\njuju status\r\n<\/pre>\n
Deploy a builder:<\/p>\n
\r\njuju deploy --config local.yaml --repository $PWD local:sbuild-charm builder-debian\r\n<\/pre>\n
Deploy more of the same type:<\/p>\n
\r\njuju add-unit builder-debian\r\njuju add-unit builder-debian\r\njuju add-unit builder-debian\r\n<\/pre>\n
Now you have to wait for them to finish installing, which will take a while. Once they’re at least partially up (the “builder” user has been created), you can print out the slips of paper to hand out to your party attendees:<\/p>\n
\r\n.\/sbuild-charm\/slips | mpage -1 > \/tmp\/slips.ps\r\nps2pdf \/tmp\/slips.ps \/tmp\/slips.pdf\r\n<\/pre>\n
They look like this:<\/p>\n
\r\nUnit: builder-debian\/3\r\nHost: ec2-256-1-1-1.us-west-1.compute.amazonaws.com\r\nSSH key fingerprints:\r\n  1024 3e:f7:66:53:a9:e8:96:c7:27:36:71:ce:2a:cf:65:31 (DSA)\r\n  256 53:a9:e8:96:c7:20:6f:8f:4a:de:b2:a3:b7:6b:34:f7 (ECDSA)\r\n  2048 3b:29:99:20:6f:8f:4a:de:b2:a3:b7:6b:34:bc:7a:e3 (RSA)\r\nUsername: builder\r\nPassword: 68b329da9893\r\n<\/pre>\n
To admin the machines, you can use juju itself, where N is the machine number from the “juju status<\/code>” output:<\/p>\n
\r\njuju ssh N\r\n<\/pre>\n
To add additional chroots to the entire builder service, add them to the config:<\/p>\n
\r\njuju set builder-debian release=unstable,testing,stable\r\njuju set builder-ubuntu release=precise,oneiric,lucid,natty\r\n<\/pre>\n
Notes about some of the terrible security hacks this charm does:<\/p>\n