Red Hat Bugzilla – Bug 892247
Provide --all-in-one parameter to Packstack
Last modified: 2013-03-21 14:22:59 EDT
Description of problem:
Make all-in-one installs easier by providing an --all-in-one flag to the cmdline and answer file that causes packstack to assume all services enabled and ip addresses for everything to be 127.0.0.1
Just a convenience for folks doing lots of PoC setups
From an offline email thread:
> IMHO, (and following to our discussion in Bug #890841), I think that we
> should use a "real" IP Address instead of 127.0.0.1, Just in case the
> user would like to add some more nodes to his openstack system.
> This might be relevant even for PoC setup at some point.
> what do you think?
I think it should be optional but not required... you might be doing a
PoC setup on a machine w/o a real IP address at all. Or on one where
eth0 IP address is dynamic and will change from boot to boot.
So --all-in-one should default to 127.0.0.1
but maybe --all-in-one also takes an optional argument like:
to indicate that you want to use a real ip address instead of loopback
New addition submitted upstream
This commit adds an option to facilitate people trying to install openstack in
a single step without first generating an answerfile
Users can run the command
$ packstack --install-hosts=192.168.0.22,192.168.0.31
If a singe host is supplied then an all in one setup will be installed, if multiple
hosts are provided, then the first will be a controler and the others will become
nova compute nodes. For all of the other value defaults are used unless supplied in the
command line e.g.
$ packstack --install-hosts=192.168.0.22,192.168.0.31 --novacompute-privif=eth0 \
An answerfile is also generated, this should be used if packstack needs to be run again
Verified NVR: openstack-packstack-2012.2.3-0.1.dev454.el6ost.noarch
Verified 2 Setups:
packstack --install-hosts=<IP Address> --novacompute-privif=eth0 \
2. 1 Cloud Controller + 1 Compute Node
packstack --install-hosts=1<IP Address #1>,<IP Address #2> --novacompute-privif=eth0 \
Both Worked as expected, proper answers file created.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.