Jump to: navigation, search

Difference between revisions of "Packstack"

(All in One)
(Gerrit)
 
(9 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
/!\ This page is far from complete, help by adding information.
 
/!\ This page is far from complete, help by adding information.
 
== Summary ==
 
== Summary ==
'''Packstack''' is a utility that uses '''Puppet''' modules to deploy various parts of [[OpenStack]] on multiple pre-installed servers over <code><nowiki>SSH</nowiki></code> automatically. Currently only <code><nowiki>Fedora</nowiki></code>, <code><nowiki>Red Hat Enterprise Linux (RHEL)</nowiki></code> and compatible derivatives of both are supported.
+
'''Packstack''' is a utility that uses '''Puppet''' modules to deploy various parts of [[OpenStack]] on multiple pre-installed servers over <code><nowiki>SSH</nowiki></code> automatically. Currently only <code><nowiki>CentOS</nowiki></code>, <code><nowiki>Red Hat Enterprise Linux (RHEL)</nowiki></code> and compatible derivatives of both are supported.
  
 
== Example Usage ==
 
== Example Usage ==
Line 14: Line 14:
  
 
For detailed options, please refer to the Packstack documentation at https://github.com/openstack/packstack/blob/master/docs/packstack.rst
 
For detailed options, please refer to the Packstack documentation at https://github.com/openstack/packstack/blob/master/docs/packstack.rst
 
=== Controller / multiple compute nodes ===
 
 
<code><nowiki>TODO.</nowiki></code>
 
 
=== Swift Proxy / multiple storage devices ===
 
 
<code><nowiki>TODO.</nowiki></code>
 
  
 
== Development : Getting started ==
 
== 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.
  
=== Installation of 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.
 
 
<pre><nowiki>
 
$ sudo yum install git python-yaml -y
 
$ git clone https://github.com/stackforge/packstack.git
 
$ cd packstack && sudo python setup.py install
 
</nowiki></pre>
 
 
 
=== Installation of openstack-puppet-modules (Required if running packstack from source) ===
 
 
 
<pre><nowiki>
 
$ sudo python setup.py install_puppet_modules
 
</nowiki></pre>
 
  
 
=== Using an answer file ===  
 
=== Using an answer file ===  
Line 45: Line 26:
 
</nowiki></pre>
 
</nowiki></pre>
  
Then edit <code><nowiki>answers.txt</nowiki></code> as appropriate e.g.
+
Then edit <code><nowiki>answers.txt</nowiki></code> as appropriate.
 
 
* Set <code><nowiki>CONFIG_SSH_KEY</nowiki></code> to a public ssh key to be installed to remote machines
 
* Edit the IP address to anywhere you want to install a piece of opentack on another server
 
* Edit the 3 network interfaces to whatever makes sense in your setup
 
  
 
== Links ==
 
== Links ==
* [https://github.com/stackforge/packstack Primary Git Repository]
+
* [https://github.com/openstack/packstack Primary Git Repository]
* [https://review.openstack.org/#/q/status:open+project:stackforge/packstack,n,z Open reviews in Gerrit]
+
* [https://review.openstack.org/#/q/status:open+project:openstack/packstack,n,z Open reviews in Gerrit]
 
* [https://bugzilla.redhat.com/ Bug Reporting Tool] - use only to report bugs found in packages provided in Fedora or EPEL
 
* [https://bugzilla.redhat.com/ Bug Reporting Tool] - use only to report bugs found in packages provided in Fedora or EPEL
 
* [https://launchpad.net/~packstack-core Launchpad (core developers)]
 
* [https://launchpad.net/~packstack-core Launchpad (core developers)]
Line 61: Line 38:
  
 
== IRC ==
 
== IRC ==
Developers meet in [http://webchat.freenode.net?channels=packstack-dev #packstack-dev] on Freenode for discussion.
+
Developers meet in [http://webchat.freenode.net?channels=rdo #rdo] on Freenode for discussion.
  
 
End-user questions are probably best answered in [http://webchat.freenode.net?channels=openstack #openstack] or [http://webchat.freenode.net?channels=rdo #rdo]
 
End-user questions are probably best answered in [http://webchat.freenode.net?channels=openstack #openstack] or [http://webchat.freenode.net?channels=rdo #rdo]
Line 75: Line 52:
  
 
<pre><nowiki>
 
<pre><nowiki>
$ git clone https://github.com/stackforge/packstack.git  
+
$ git clone https://github.com/openstack/packstack.git  
 
$ cd packstack
 
$ cd packstack
 
</nowiki></pre>
 
</nowiki></pre>
Line 99: Line 76:
 
</nowiki></pre>
 
</nowiki></pre>
  
'''→''' Wait for people on gerrit https://review.openstack.org/#/q/status:open+project:stackforge/packstack,n,z to review your change, if it needs to be altered simply amend your commit and submit it for review again
+
'''→''' 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
  
 
<pre><nowiki>
 
<pre><nowiki>
Line 109: Line 86:
 
=== Git branches ===
 
=== 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.
 
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 <code><nowiki>juno</nowiki></code> development, master will branch off a <code><nowiki>juno</nowiki></code> branch. Then  
+
once we start <code><nowiki>Ocata</nowiki></code> development, master will branch off a <code><nowiki>stable/ocata</nowiki></code> branch. Then  
* <code><nowiki>juno</nowiki></code>    → should only accept bug fixes and exceptional approved new features, these should be merged into master first if appropriate
+
* <code><nowiki>stable/ocata</nowiki></code>    → should only accept bug fixes and exceptional approved new features, these should be merged into master first if appropriate
* <code><nowiki>master</nowiki></code> → new features for juno and bugs
+
* <code><nowiki>master</nowiki></code> → new features and bugs
  
  
Line 123: Line 100:
 
* To send review request for the stable branch
 
* To send review request for the stable branch
 
<pre><nowiki>
 
<pre><nowiki>
$ git review juno
+
$ git review stable/ocata
 
</nowiki></pre>
 
</nowiki></pre>
  
Line 136: Line 113:
  
 
=== Gerrit ===
 
=== Gerrit ===
Open review requests https://review.openstack.org/#/q/status:open+project:stackforge/packstack,n,z
+
Open review requests https://review.openstack.org/#/q/status:open+project:openstack/packstack,n,z
  
 
=== Packstack Core ===
 
=== 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 [https://review.openstack.org/#/admin/groups/124,members here]
 
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 [https://review.openstack.org/#/admin/groups/124,members here]

Latest revision as of 13:14, 31 October 2016

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 SSH automatically. Currently only CentOS, Red Hat Enterprise Linux (RHEL) and compatible derivatives of both are supported.

Example Usage

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 answers.txt as appropriate.

Links

Presentations

IRC

Developers meet in #rdo on Freenode for discussion.

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

Packstack Development

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 Ocata development, master will branch off a stable/ocata branch. Then

  • stable/ocata → should only accept bug fixes and exceptional approved new features, these should be merged into master first if appropriate
  • master → 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)

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

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