Clone the repo, doing a git pull if you already have the repo, and would like all the great changes and fixes we’ve made recently. When running ./dev setup you’ll need your github username and password, so we can make a scratch space for you. PLUS, if you git init your .crowbar_build_cache, you can go a long way to saving yourself worry. There’s plenty of information on that in the README.* files once you clone the Crowbar repo in the first step.

Run the build. Nota Bene: indicating --pfs is a bit dangerous. It indicates that the latest stable OpenStack code will be pulled from the Internet and cached in your Crowbar.ISO. With that, you’ll be installing the latest stable bits. The more conservative approach is to install from packages, omiting the --pfs

./dev build --update-cache --pfs --os ubuntu-12.04

It will take FOREVER, unless you’re on a massively powerful machine and an OC48. 🙂

In my experience, Python’s pip system failed quite regularly to get the bits it was looking for. It doesn’t have a retry mechanism as far as I can tell.

In my next blog entry I’ll discuss install of the ISO, setup of Crowbar and the deployment of OpenStack Grizzly!