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
Copy file name to clipboardExpand all lines: docs/rfcs/0002/readme.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,14 +63,14 @@ The following subsections outline the proposed communication between the Rabbit
63
63
64
64
#### Rabbit-to-Rabbit Communication
65
65
66
-
Each rabbit node can be reached via `<hostname>.<subdomain>` using DNS. The hostname is a combination of the workflow name and Rabbit node name. The workflow name is used for the subdomain.
66
+
Each rabbit node can be reached via `<hostname>.<subdomain>` using DNS. The hostname is the Rabbit node name and the workflow name is used for the subdomain.
67
67
68
-
For example, a workflow name of `foo` that targets `rabbit-node2` would be `foo-rabbit-node2.foo`.
68
+
For example, a workflow name of `foo` that targets `rabbit-node2` would be `rabbit-node2.foo`.
69
69
70
70
Environment variables are provided to the container and ConfigMap for each rabbit that is targeted by the container workflow:
DNS can then be used to communicate with other Rabbit containers. The FQDN for the container running on rabbit-node2 is `foo-rabbit-node2.foo.default.svc.cluster.local`.
89
+
DNS can then be used to communicate with other Rabbit containers. The FQDN for the container running on rabbit-node2 is `rabbit-node2.foo.default.svc.cluster.local`.
90
90
91
91
#### Compute-to-Rabbit Communication
92
92
@@ -178,8 +178,8 @@ Peter submits the job to the WLM. WLM guides the job through the workflow states
0 commit comments