openstack/openstack-virtual-baremetal
Code Issues Proposed changes

Make quintupleo deploy command more realistic

Browse Source 
In practice, very few users deploy an OVB environment anymore with
no additional environments.  This change adds a few common ones to
the example command.  While these environments won't all work on
older clouds and may not be necessary in some circumstances, in
most cases they won't hurt anything and make it more likely that
a user's first attempt to deploy will succeed.

In addition, by explicitly passing env.yaml in the example, if users
do add more environment files they won't have to remember to also
add env.yaml.  This would be an easy mistake to make that might
result in confusing failures.
This commit is contained in:
Ben Nemec 2018-01-24 14:32:16 -06:00
parent a0fa1b36b3
commit 9908855a08
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/deploy/quintupleo.rst
View File

@ -12,9 +12,14 @@ however.
cp environments/base.yaml env.yaml
vi env.yaml
#. Deploy a QuintupleO stack::
#. Deploy a QuintupleO stack. The example command includes a number of
environment files intended to simplify the deployment process or make
it compatible with a broader set of host clouds. However, these
environments are not necessary in every situation and may not even work
with some older clouds. See below for details on customizing an OVB
deployment for your particular situation::
bin/deploy.py --quintupleo
bin/deploy.py --quintupleo -e env.yaml -e environments/all-networks-port-security.yaml -e environments/create-private-network.yaml
.. note:: There is a quintupleo-specific option ``--id`` in deploy.py.
It appends the value passed in to the name of all resources