Jump to: navigation, search

Difference between revisions of "HackingNovaMacOSX"

 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
__NOTOC__
 
= How to Set up a Development Environment on MacOS X =
 
  
Notes for hacking and cleaning on Nova on MacOS X
+
= How to Set up a Development Environment on Mac OS X =
  
== Bazaar and Launchpad ==
+
Notes for hacking and cleaning on Nova on Mac OS X
  
[[OpenStack]] uses Launchpad, so you need to install the Bazaar client tools.
+
== Git and Github ==
See also [[[LifeWithBzrAndLaunchpad|| learning BZR and Launchpad]]])
 
  
 
+
OpenStack code is hosted on Github and uses git, which should already be
<pre><nowiki>
+
installed on Mac OS X. To grab the latest code:
brew install bzr
 
</nowiki></pre>
 
 
 
 
 
Register your username (your username substitues for heckj):
 
  
  
 
<pre><nowiki>
 
<pre><nowiki>
bzr lp-login heckj
+
git clone git://github.com/openstack/nova.git
 
</nowiki></pre>
 
</nowiki></pre>
 
  
Checkout the Nova trunk.
 
  
 +
== Install Python Dependencies ==
  
<pre><nowiki>
+
Use Python's easy_install to install virtualenv
bzr branch lp:nova
 
</nowiki></pre>
 
 
 
 
 
The project is transition to hosting code on [[GitHub]], so there is a copy of trunk on [[GitHub]] now too.
 
You can get the trunk from Git too:
 
  
  
 
<pre><nowiki>
 
<pre><nowiki>
git clone git://github.com/openstack/nova.git
+
sudo easy_install virtualenv
 
</nowiki></pre>
 
</nowiki></pre>
  
  
== Install Python Dependencies ==
+
You'll also need swig (install any way you want, but brew is nice http://mxcl.github.com/homebrew/):
 
 
Use Python's easy_install to install virtualenv
 
  
  
 
<pre><nowiki>
 
<pre><nowiki>
sudo easy_install virtualenv
+
brew install swig
 
</nowiki></pre>
 
</nowiki></pre>
  
Line 57: Line 40:
 
cd nova
 
cd nova
 
python tools/install_venv.py
 
python tools/install_venv.py
source .nova_venv/bin/activate
+
source .venv/bin/activate
pip install pep8 # submitting patch so that Nova has pep8 and pylint in PIP requirements file
 
pip install pylint
 
 
</nowiki></pre>
 
</nowiki></pre>
  
Line 65: Line 46:
 
== OpenSSL Dependency ==
 
== OpenSSL Dependency ==
  
If you have installed OpenSSL 1.0.0a on MacOS, which can happen when installing a [[MacPorts]] package for OpenSSL, you will see an error when running nova.tests.auth_unittest.[[AuthTestCase]].test_209_can_generate_x509. The version that functions correctly is OpenSSL 0.9.8l 5, installed with MacOS 10.6 as a base element.   
+
If you have installed OpenSSL 1.0.0a on Mac OS X, which can happen when installing a [[MacPorts]] package for OpenSSL, you will see an error when running nova.tests.auth_unittest.[[AuthTestCase]].test_209_can_generate_x509. The version that functions correctly is OpenSSL 0.9.8l 5, installed with MacOS 10.6 as a base element.   
  
 
There is no easy way to install an older package version using macports, but if it had been installed you can reactivate it.
 
There is no easy way to install an older package version using macports, but if it had been installed you can reactivate it.
Line 86: Line 67:
 
<pre><nowiki>
 
<pre><nowiki>
 
cd nova
 
cd nova
bzr pull # get the latest stuff...
+
git pull # get the latest stuff...
source .nova_venv/bin/activate
 
 
./run_tests.sh
 
./run_tests.sh
 
 
#... do cleaning work ...
 
#... do cleaning work ...
 
bzr push lp:~heckj/nova/cleaning
 
 
</nowiki></pre>
 
</nowiki></pre>
  
  
To submit the merge/patch:
+
To submit the merge/patch, see [http://docs.openstack.org/infra/manual/developers.html#development-workflow development workflow]
* 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?
 
  Once a proposal is reviewed, merged, and accepted, Launchpad sets the branch status to "Merged" which effectively closes the proposal.
 
* Do we then delete this branch and create another with the next cleaning/merge request?
 
    Yes, a branch can be deleted locally and you just create another branch next time you want to modify code to be merged into another branch.
 
* Or do we make more changes, push to this branch, and then submit another merge request?
 
    You can do either though the merging is more complicated the further from trunk that your branch gets, I believe.
 

Latest revision as of 17:47, 5 December 2014

How to Set up a Development Environment on Mac OS X

Notes for hacking and cleaning on Nova on Mac OS X

Git and Github

OpenStack code is hosted on Github and uses git, which should already be installed on Mac OS X. To grab the latest code:


git clone git://github.com/openstack/nova.git


Install Python Dependencies

Use Python's easy_install to install virtualenv


sudo easy_install virtualenv


You'll also need swig (install any way you want, but brew is nice http://mxcl.github.com/homebrew/):


brew install swig


Initial code setup

Initial Code Setup:

cd nova
python tools/install_venv.py
source .venv/bin/activate


OpenSSL Dependency

If you have installed OpenSSL 1.0.0a on Mac OS X, which can happen when installing a MacPorts package for OpenSSL, you will see an error when running nova.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509. The version that functions correctly is OpenSSL 0.9.8l 5, installed with MacOS 10.6 as a base element.

There is no easy way to install an older package version using macports, but if it had been installed you can reactivate it.

sudo port activate openssl @0.9.8n_0+darwin


The alternative is to remove it and use the default OSX openssl. This will give you dependency errors on the port command, so you need to force it.

sudo - f port uninstall openssl


Run the Tests

cd nova
git pull # get the latest stuff...
./run_tests.sh
#... do cleaning work ...


To submit the merge/patch, see development workflow