Bug 1748481

Summary: [DOC] run overcloud updates across multiple compute at the same time
Product: Red Hat OpenStack Reporter: mathieu bultel <mbultel>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: dmacpher
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-12 06:03:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mathieu bultel 2019-09-03 16:47:30 UTC
Serial execution need to be documented.

Here is few words about the feature:

To run parallel Ansible update on the nodes, TripleO is using the value of the update_serial variable located in the roles_data.yaml.
This value is present on the latest roles_data.yaml that comes with tripleo-heat-templates.
The default value doesn't allow to run parallel execution on Controller nodes, which is not supported and recomanded by the Eng.

The default value for the Compute is 25.

To update the update_serial value with your own value you need to:

1/ run prepare step with the updated roles_data.yaml (if you use the default in THT, you can just edit the update_serial value)
https://github.com/openstack/tripleo-heat-templates/blob/master/roles_data.yaml#L37

If you use a custom roles_data file, you need to update the file to add the update_serial value.

2/ run the step 2: openstack overcloud update run --nodes Computes
All the compute should be updated at the same time, or according to the value of update_serial.