You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9d6a910
Browse filesBrowse the repository at this point in the historyBrowse files
Gate nodesets on their deployOnAllNodeSets service jobs
A deployOnAllNodeSets service runs as a single AnsibleEE Job for the whole
deployment.
DedupeServices kept such a service in the first nodeSet's service list
only, so every later nodeSet lost its ordering relationship to it:
dependsOn resolves against the nodeSet's own list and silently skipped the
missing entry. Those nodeSets advanced past the shared Job while it was
still mutating their hosts.
Keep the service in every listing nodeSet's plan, where it acts as a
barrier. The deployment starts its Job before the nodeSet loop, once every
service ordered before it in each listing nodeSet has completed, and a
nodeSet blocks until that Job succeeded. Readiness is read from the Job
rather than from conditions, which are rebuilt every reconcile, so a
restart mid-deployment resumes from cluster state. A nodeSet that does not
list the service neither waits for it nor delays it.
Applies to both serial and parallel execution.
Related: OSPRH-37768
Signed-off-by: Rabi Mishra <ramishra@redhat.com>
Copy file name to clipboardExpand all lines: docs/assemblies/proc_creating-a-custom-service.adoc
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,9 @@ spec:
92
92
+
93
93
A mount is created for each `ConfigMap` and `Secret` in the `OpenStackAnsibleEE` pod with a filename that matches the resource value. The mounts are created under `/var/lib/openstack/configs/<service name>`.
94
94
95
-
. Optional: It may be necessary to run some services on all nodesets at the same time. These services need to have their `deployOnAllNodeSets` field set to true. If these services are repated in multiple nodeset specs included in a deployment, they would be ignored from subsequent nodeset services and would be run only once.
95
+
. Optional: It may be necessary to run some services on all nodesets at the same time. These services need to have their `deployOnAllNodeSets` field set to true. Such a service produces a single `OpenStackAnsibleEE` job for the whole deployment, targeting the hosts of every nodeset, even nodesets that do not list the service.
96
+
+
97
+
A deployment scoped service is an execution barrier for the nodesets that list it: its job starts only once every service ordered before it in each of those nodesets has completed, and none of those nodesets starts a service ordered after it until the job completed. A nodeset that does not list the service neither waits for it nor delays it, so list the service in every nodeset whose deployment ordering depends on it.
0 commit comments