openstack/fuel-library
Code Issues Proposed changes

Corrected typo. Also changed deployment ID to 2-254, as min is 1, but should be even number.

Browse Source
This commit is contained in:
Nick Chase 2013-03-26 21:20:09 -04:00
parent 8a07ac087e
commit be1fee8eae
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/pages/installation-instructions/0062-orchestration.rst
View File

@ -1,6 +1,6 @@
.. _orchestration:
Depolying via orchestration
Deploying via orchestration
----------------------------
Manually installing a handful of servers might be managable, but repeatable installations, or those that involve a large number of servers, require automated orchestration. Now you can use orchestration with Fuel through the ``astute`` script. This script is configured using the ``astute.yaml`` file you created when you ran ``openstack_system``.

4
docs/pages/production-considerations/0020-deployment-pipeline.rst
View File

@ -1,4 +1,4 @@
Redepolying an environment
Redeploying an environment
--------------------------
Because Puppet is additive only, there is no ability to revert changes as you would in a typical application deployment.
@ -45,7 +45,7 @@ Deployment pipeline
* Deploy
In order to deploy multiple environments that don't interfere with each other, you should specify the ``$deployment_id`` option in ``/etc/puppet/manifests/site.pp``. It should be an even integer value in the range of 0-254.
In order to deploy multiple environments that don't interfere with each other, you should specify the ``$deployment_id`` option in ``/etc/puppet/manifests/site.pp``. It should be an even integer value in the range of 2-254.
This value is used in dynamic environment-based tag generation. Fuel also apply that tag globally to all resources on each node. It is also used for the keepalived daemon, which evaluates a unique ``virtual_router_id``.