Merge lp:~jml/udd/deployable into lp:udd
Status: | Merged |
---|---|
Approved by: | James Westby |
Approved revision: | 569 |
Merged at revision: | 565 |
Proposed branch: | lp:~jml/udd/deployable |
Merge into: | lp:udd |
Diff against target: |
351 lines (+331/-0) 4 files modified
fabfile.py (+1/-0) fabtasks/__init__.py (+1/-0) fabtasks/deploy.py (+323/-0) fabtasks/lp_creds.txt (+6/-0) |
To merge this branch: | bzr merge lp:~jml/udd/deployable |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Westby | Approve | ||
Review via email: mp+97224@code.launchpad.net |
Commit message
A fabtask to deploy udd to a new EC2 instance
Description of the change
I wanted to test out the behaviour of lp:udd with certain config changes set, but I didn't particularly want to go to the hassle of getting it running on my own machine. So, I made a script that deploys an instance to EC2.
It uses fabric to do so, and is heavily derived from the script that james_w made for lp:pkgme-service.
Some things to note:
* it uses fixed credentials to access Launchpad. I created a user, ~jml+libdep-bot, and have stored read-only credentials for accessing Launchpad in fabtasks/
* it doesn't install bzr-buildeb. Not sure if this is a problem.
* it doesn't do the Apache / cricket / website configuration, mostly because I'm not interested in that stuff
Still, I think it's useful. It also might be the only existing documentation about how to deploy this thing from scratch, so that makes it handy in its own right.
Hi,
This looks good.
The credentials being in the branch aren't great, but making them read-only is
a good compromise.
It would be good to extract out the generic ec2 stuff to somewhere else, but
we should probably just live with it and expect to use juju for that before
too long.
Thanks,
James