Hey Cole, Some more notes on this before I forget the details ...
On Mon, 2011-11-28 at 11:34 -0500, Cole Robinson wrote: > # Checkout horizon (aka dashboard) > git clone git://github.com/openstack/horizon.git horizon.git > cd horizon.git Any reason for the '.git' suffix? e.g. I just did: $> git clone git://github.com/openstack/horizon.git $> cd horizon > git branch --track diablo remotes/origin/stable/diablo > git checkout diablo This works too: $> git checkout --track -b diablo origin/stable/diablo > # Now we set up a local environment with all the required dashboard > # dependencies, without polluting our system configuration. dashboard > # supplies tools for this but some tweaks are needed. > sudo yum install -y bzr python-coverage Can you remember what these are for? > cd openstack-dashboard > edit tools/pip-requires, comment out the quantum git URL > (reason: https://bugs.launchpad.net/horizon/+bug/888385) > python tools/install_venv.py > > # Manually install quantum into the virtual environment > git clone https://github.com/openstack/quantum.git quantum.git > cd quantum.git/common > ../../tools/with_venv.sh python setup.py install > cd ../client > ../../tools/with_venv.sh python setup.py install > cd ../.. Interestingly, on horizon master they've changed pip-requires to use stable/diablo quantum ... so: $> git clone https://github.com/openstack/quantum $> cd quantum $> git checkout --track -b diablo origin/stable/diablo $> ../tools/with_venv.sh python setup.py install > # Run unit tests. Currently looks like 2 tests are failing with a glance > # import issue: 'module' object has no attribute 'Error' > ./run_tests.sh > > # No unexpected failures, great! Let's configure the dashboard > cd openstack-dashboard > > # needed by glance imports but wasn't installed automatically > ./tools/with_venv.sh pip --verbose install --environment .dashboard-venv/ > pycrypto Can be simplified to $> ./tools/with_venv.sh pip install pycrypto > # Actually run the dashboard > ./tools/with_venv.sh python dashboard/manage.py runserver syncdb Should be just: $> ./tools/with_venv.sh python dashboard/manage.py syncdb > ./tools/with_venv.sh python dashboard/manage.py runserver 127.0.0.1:9000 > firefox 127.0.0.1:9000 I'm running my browser on a different machine, so had to supply the public IP address in the runserver command and open the port up: $> sudo lokkit -p 9000:tcp $> ./tools/with_venv.sh python dashboard/manage.py runserver 172.31.0.107:9000 > # should see a login page, accounts are demo:demo or admin:admin > log in with admin:admin, it should work! Worked, w00t! Cheers, Mark. _______________________________________________ cloud mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/cloud
