Difference between revisions of "HackingNovaMacOSX"
| Line 43: | Line 43: | ||
bzr push lp:~heckj/nova/cleaning | bzr push lp:~heckj/nova/cleaning | ||
</nowiki></pre> | </nowiki></pre> | ||
| + | |||
| + | |||
| + | To submit the merge/patch: | ||
| + | * navigate to https://code.launchpad.net/~heckj/nova/cleaning | ||
| + | * click on the link "Propose for merging" | ||
| + | |||
| + | Open questions | ||
| + | * Once merged in and accepted, does the proposal get closed? | ||
| + | ** Do we then delete this branch and create another with the next cleaning/merge request? | ||
| + | ** Or do we make more changes, push to this branch, and then submit another merge request? | ||
Revision as of 18:51, 8 August 2010
Describe HackingNovaMacOSX here.
My notes for hacking and cleaning on Nova on MacOS X
bzr lp-login heckj
Initial Code Setup:
bzr branch lp:nova cd nova python tools/install_venv.py source .nova_venv/bin/activate pip install pep8 # submitting patch so that Nova has pep8 and pylint in PIP requirements file pip install pylint
from http://wiki.openstack.org/InstallationNova20100729 (I do this in a separate window that I hide to let Redis be as noisy as it wants to in the background)
cd nova curl http://redis.googlecode.com/files/redis-2.0.0-rc4.tar.gz -o redis-2.0.0-rc4.tar.gz tar xvfz redis-2.0.0-rc4.tar.gz cd redis-2.0.0-rc4 # Make and start Redis server make ./redis-server &
cd nova bzr pull # get the latest stuff... source .nova_venv/bin/activate redis-2.0.0-rc4/redis-server & ./run_tests.sh #... do cleaning work ... bzr push lp:~heckj/nova/cleaning
To submit the merge/patch:
- navigate to https://code.launchpad.net/~heckj/nova/cleaning
- click on the link "Propose for merging"
Open questions
- Once merged in and accepted, does the proposal get closed?
- Do we then delete this branch and create another with the next cleaning/merge request?
- Or do we make more changes, push to this branch, and then submit another merge request?
