Packstack

= Packstack = /!\ This page is far from complete, help by adding information.

Summary
Packstack is a utility that uses Puppet modules to deploy various parts of OpenStack on multiple pre-installed servers over  automatically. Currently only,   and compatible derivatives of both are supported.

All in One
$ packstack --allinone

For detailed options, please refer to the Packstack documentation at https://github.com/openstack/packstack/blob/master/docs/packstack.rst

Development : Getting started
In general, you will want to use a packaged version of Packstack. Refer to https://www.rdoproject.org/install/quickstart/ for details on how to enable the required repositories and install Packstack.

If you are a developer and want to install Packstack from source, please refer to https://github.com/openstack/packstack/blob/master/README.md#installation-of-packstack for detailed information.

Using an answer file
$ packstack --gen-answer-file=answers.txt

Then edit  as appropriate.

Links

 * Primary Git Repository
 * Open reviews in Gerrit
 * Bug Reporting Tool - use only to report bugs found in packages provided in Fedora or EPEL
 * Launchpad (core developers)

Presentations

 * Packstack Overview (30 slides, >=~10 minutes, 2013-04-24, CC0)

IRC
Developers meet in #rdo on Freenode for discussion.

End-user questions are probably best answered in #openstack or #rdo

Making your first contribution
The process you need to follow in order to contribute to packstack is the same as the openstack core projects, documented here http://wiki.openstack.org/HowToContribute the steps to follow look something like this

→ Sign the CLA

→ Get the code

$ git clone https://github.com/openstack/packstack.git $ cd packstack

→ Make a topic branch: $ git checkout -b my_topic

→ Make your change $ hack, hack, hack !! ;-)

→ Commit your change $ git commit -a

→ Submit your change for review $ git review

→ Wait for people on gerrit https://review.openstack.org/#/q/status:open+project:openstack/packstack,n,z to review your change, if it needs to be altered simply amend your commit and submit it for review again

$ git add -p $ git commit --amend $ git review

Git branches
There is a branch for each openstack major release, this branch starts off is life as master, once development of the next release starts, it will be renamed and then master will be the branch for the next openstack release e.g. once we start  development, master will branch off a   branch. Then
 * → should only accept bug fixes and exceptional approved new features, these should be merged into master first if appropriate
 * → new features and bugs

Note : (be careful to send your changes to the correct branch and also that your basing any commits on a parent from the correct branch)

$ git review
 * To send review request for the master branch

$ git review stable/ocata
 * To send review request for the stable branch

Bugs
Bugs are tracked in Launchpad (New bug)

Reviews
All commits should be reviewed and approved by at least one core packstack member (ideally 2 for any commit more then a trivial change) and author of a commit shouldn't approve their own code.

New Features
New features go into the master branch. There may be new features committed to a stable branch but these should be the exception and not the norm.

Gerrit
Open review requests https://review.openstack.org/#/q/status:open+project:openstack/packstack,n,z

Packstack Core
You do not need to be a core member to packstack in order to contribute code. Members of packstack-core can approve commits in gerrit to be merged into the code, new members to packstack-core should be actively (and reliably) reviewing commits in gerrit before being considered. New members will be invited to join. Core members can be found here