OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|2 days ago|
|docs||6 months ago|
|packstack||1 month ago|
|playbooks||2 days ago|
|releasenotes||2 months ago|
|roles/packstack-integration-tempest/tasks||6 months ago|
|tests||2 months ago|
|tools||6 months ago|
|.gitignore||10 months ago|
|.gitreview||2 days ago|
|.stestr.conf||10 months ago|
|.testr.conf||2 years ago|
|.zuul.yaml||2 days ago|
|Gemfile||4 years ago|
|LICENSE||6 years ago|
|MANIFEST.in||4 years ago|
|Puppetfile||6 months ago|
|README.md||2 months ago|
|Rakefile||4 years ago|
|bindep.txt||2 years ago|
|requirements.txt||1 year ago|
|run_tests.sh||3 weeks ago|
|setup.cfg||2 years ago|
|setup.py||2 years ago|
|test-requirements.txt||10 months ago|
|tox.ini||5 months ago|
Utility to install OpenStack on Red Hat based operating system. See other branches for older OpenStack versions. Details on how to contribute to Packstack may be found in the Packstack wiki at https://wiki.openstack.org/wiki/Packstack Additional information about involvement in the community around Packstack can be found at https://openstack.redhat.com/Get_involved
This utility can be used to install OpenStack on a single or group of
This utility is still in the early stages, a lot of the configuration options have yet to be added.
$ yum install -y git $ git clone git://github.com/openstack/packstack.git $ cd packstack && sudo python setup.py install
$ export GEM_HOME=/tmp/somedir $ gem install r10k $ sudo -E /tmp/somedir/bin/r10k puppetfile install -v $ sudo cp -r packstack/puppet/modules/packstack /usr/share/openstack-puppet/modules
$ packstack --allinone
This will install all OpenStack services on a single host without
prompting for any configuration information. This will generate an
“answers” file (
packstack-answers-<date>-<time>.txt) containing all
the values used for the install.
If you need to re-run packstack, you must use the
option in order for packstack to use the correct values for passwords
and other authentication credentials:
$ packstack --answer-file packstack-answers-<date>-<time>.txt
$ packstack --gen-answer-file=ans.txt
ans.txt as appropriate e.g.
CONFIG_SSH_KEYto a public ssh key to be installed to remote machines
Edit the 3 network interfaces to whatever makes sense in your setup
$ packstack --answer-file=ans.txt
that’s it, if everything went well you can now start using OpenStack
$ cd $ . keystonerc_admin $ nova list $ swift list # if you have installed swift
220.127.116.11: create a testing loopback device and use this for storage
18.104.22.168as a storage device
The location of the log files and generated puppet manifests are in the
/var/tmp/packstack directory under a directory named by the date in which
Packstack was run and a random string (e.g.
Inside, we find a manifest directory and the
openstack-setup.log file; puppet
manifests and a log file for each one are found inside the manifest directory.
To make Packstack write more detailed information into the log file you can use the
$ packstack -d --allinone
When upgrading to a new OpenStack release and reusing old answerfile
it is useful to know if any Packstack option was removed. If answerfile is
written by hand it is possible to make a mistake. The
switch allows checking if any provided option is not recognized by Packstack.
$ packstack --validate-answer-file=ans.txt
To ease development of Packstack, it can be useful to install from git such that updates to the git repositories are immediately effective without reinstallation.
To do this, start with a minimal CentOS 7 installation. Then remove any relevant packages that might conflict:
$ yum -y erase openstack-packstack*,puppet-*
Disable SELinux by changing “
enforcing” to “
/etc/sysconfig/selinux, then reboot to allow service changes to take effect
and swap over networking. Then install packages:
$ yum -y install git python-setuptools
And install RDO:
$ yum -y install https://www.rdoproject.org/repos/rdo-release.rpm $ yum -y update
Install Puppet modules as described above.
Then we get Packstack:
$ yum install -y python-crypto python-devel libffi-devel openssl-devel gcc-c++ $ git clone https://github.com/openstack/packstack $ cd packstack $ python setup.py develop
And we’re done. Changes to the contents of Packstack source repository are picked up by the Packstack executable without further intervention, and Packstack is ready to install.
Please, respect the Puppet Style Guide as much as possible !
It assumes that both
bundler as well as
ruby) are already
installed on the system. If not, run this command:
$ sudo yum install rubygems rubygem-bundler ruby ruby-devel -y
Go into the Packstack root directory.
$ cd packstack/
Rakefile contains all you need to run puppet-lint task automatically over
all the puppet manifests included in the Packstack project.
$ ls -l packstack/puppet/templates/
$ ls -l packstack/puppet/modules/
The default puppet-lint pattern for
.pp files is
**/*.pp. So there is no
need to go inside those directories to run puppet-lint !
$ mkdir vendor $ export GEM_HOME=vendor $ bundle install $ bundle exec rake lint
Packstack is integration tested in the OpenStack gate and provides the means to reproduce these tests on your environment if you wish.
Scenario000 installs packstack allinone only and doesn’t run any tests. This is the current matrix of available tests:
To run these tests:
export SCENARIO="scenario001" ./run_tests.sh
run_tests.sh will take care of installing the required dependencies, configure packstack to run according to the above matrix and run the complete installation process. If the installation is successful, tempest will also run smoke tests.
By default, run_tests.sh will set up delorean (RDO Trunk) repositories. There are two ways of overriding default repositories:
export DELOREAN="http://someotherdomain.tld/delorean.repo" export DELOREAN_DEPS="http://someotherdomain.tld/delorean-deps.repo" ./run_tests.sh
You can also choose to disable repository management entirely:
<setup your own custom repositories here> export MANAGE_REPOS="false" ./run_tests.sh