Jump to: navigation, search

Difference between revisions of "Getting The Code"

Line 2: Line 2:
 
= Getting the source code =
 
= Getting the source code =
  
There is a page detailing full instructions on how to work with bzr and Launchpad at [[LifeWithBzrAndLaunchpad]].
+
Most of [[OpenStack]] has moved development to git and gerrit. The workflow for working with Gerrit is described at [[GerritWorkflow]].
  
You can go directly to Launchpad to look at the [https://launchpad.net/openstack OpenStack Project Group], [https://launchpad.net/swift OpenStack Object Storage (swift)], and [https://launchpad.net/nova OpenStack Compute (nova)] code or you can use bzr from the command line. Instructions on how to get the code for (swift) using bzr:
+
Nova is still managed with bzr and Launchpad. There is a page detailing full instructions on how to work with bzr and Launchpad at [[LifeWithBzrAndLaunchpad]].
  
 +
You can go directly to Launchpad to look at the [https://launchpad.net/openstack OpenStack Project Group] and [https://launchpad.net/nova OpenStack Compute (nova)] code or you can use bzr from the command line.  Instructions on how to get the code for nova using bzr:
  
<pre><nowiki>
 
bzr branch lp:swift
 
</nowiki></pre>
 
 
or
 
  
 
<pre><nowiki>
 
<pre><nowiki>
Line 27: Line 23:
  
 
<pre><nowiki>
 
<pre><nowiki>
bzr init-repo swift
+
bzr init-repo nova
cd swift
+
cd nova
bzr branch lp:swift
+
bzr branch lp:nova
 
</nowiki></pre>
 
</nowiki></pre>
  
or:
+
 
 +
To get any of the other [[OpenStack]] projects, you can look start at the [https://github.com/openstack OpenStack Organization] and browse, or you can clone a repo. For instance, for swift:
 +
 
  
 
<pre><nowiki>
 
<pre><nowiki>
bzr init-repo nova
+
git clone git://github.com/openstack/swift.git
cd nova
 
bzr branch lp:nova
 
 
</nowiki></pre>
 
</nowiki></pre>
  

Revision as of 02:55, 9 September 2011

Getting the source code

Most of OpenStack has moved development to git and gerrit. The workflow for working with Gerrit is described at GerritWorkflow.

Nova is still managed with bzr and Launchpad. There is a page detailing full instructions on how to work with bzr and Launchpad at LifeWithBzrAndLaunchpad.

You can go directly to Launchpad to look at the OpenStack Project Group and OpenStack Compute (nova) code or you can use bzr from the command line. Instructions on how to get the code for nova using bzr:


bzr branch lp:nova

You will also need to ensure you have logged in to launchpad with bzr. If you don't want to follow the full walkthrough, the quick version of of getting started is:

bzr lp-login "your-launchpad-id"
bzr whoami "Full Name <email@address.com>"

then:

bzr init-repo nova
cd nova
bzr branch lp:nova


To get any of the other OpenStack projects, you can look start at the OpenStack Organization and browse, or you can clone a repo. For instance, for swift:


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


Nova Dependencies (OSX)

Commands for installing dependencies on OSX => DependsOnOSX

Nova Dependencies (Ubuntu)

Commands for installing dependencies on Ubuntu => DependsOnUbuntu

Swift All in One (Manual Install)

Swift documentation can be found at [1]]. The [Swift All in One documentation will lead you step by step to do a development install of Swift on a VM.

Swift All In One (Chef Auto Install)

You'll want to have an Ubuntu 10.04 system/VM that you're willing to turn in to a Swift development environment. First step is to get the SSH key you are using for launchpad in your ~/.ssh directory.

Log in as your user, and do the following:


curl http://c0020195.cdn1.cloudfiles.rackspacecloud.com/install-swift.sh > install-swift.sh
bash install-swift.sh


You'll be prompted for your username, group name (which is your user group name likely identical to your username), launchpad login, and the email address you want bzr to use when sending commits. Eventually, you will also be prompted to accept the Launchpad SSH Host Key, and may be prompted for your keyphrase.

When the script completes, you'll have a functioning Swift All In One that's prepped for running the functional tests.