Refactor cluster bringup. #180
Conversation
Signed-off-by: Dumitru Ceara <dceara@redhat.com>
It was confusing to have both and the majority of cases used 'cluster_cfg' instead of 'cluster_config' (100 vs 10). Signed-off-by: Dumitru Ceara <dceara@redhat.com>
Storing a reference will have unexpected results as we might end up sharing it between different nodes. Signed-off-by: Dumitru Ceara <dceara@redhat.com>
The IPs were skewed by 2 for clustered DB deployments. Instead of mangling the connection string generation just allocate the correct IP. Signed-off-by: Dumitru Ceara <dceara@redhat.com>
It removes the need to artificially compute remote values. Instead just use the correct RelayNode IPs. Signed-off-by: Dumitru Ceara <dceara@redhat.com>
|
CC: @LorenzoBianconi - this probably should go in before your PR #169 as it should simplify a bit multi-AZ deployments |
It makes it easier to encapsulate things in the Cluster class. Signed-off-by: Dumitru Ceara <dceara@redhat.com>
All nodes run the same OVSDB protocol. Signed-off-by: Dumitru Ceara <dceara@redhat.com>
A cluster is a collection of central and worker nodes (+ relays). Signed-off-by: Dumitru Ceara <dceara@redhat.com>
dceara
force-pushed
the
explicit-nodes-refactor
branch
from
15ddc8b
to
1380bba
Compare
| @@ -56,7 +56,7 @@ class Node(ovn_sandbox.Sandbox): | |||
| def __init__(self, phys_node, container, mgmt_ip): | |||
| super().__init__(phys_node, container) | |||
| self.container = container | |||
| self.mgmt_ip = mgmt_ip | |||
| self.mgmt_ip = netaddr.IPAddress(mgmt_ip) | |||
There was a problem hiding this comment.
Is the concern here that other parts of the code might change mgmt_ip value? Because looking at the docs, the IPAddress object looks pretty immutable. (Just curious here)
There was a problem hiding this comment.
Yes, that's exactly it. I was doing something like that while trying out @LorenzoBianconi's ovn-ic changes, using a netaddr.IPAddress externally through iterate through node IPs and ending up changing all the ones that were already assigned.
ovn-tester/ovn_workload.py
Outdated
| @@ -147,6 +139,27 @@ def central_containers(self): | |||
| return self.db_containers | |||
|
|
|||
|
|
|||
| class RelayNode(Node): | |||
| def __init__(self, phys_node, container, mgmt_ip): | |||
There was a problem hiding this comment.
This is slightly unrelated, but I was thinking whether there's a good way to improve semantics/logic of the container argument in the Node subclasses. All three WorkerNode, CentralNode and RelayNode accept container argument but it doesn't really affect anything. When creating these classes you have to match what's pretty much hardcoded. For the relay and central, prefix for the container names is set in ovn-fake-multinode script and for the worker nodes it can be set via prefix config option.
I think it'd be better if the logic of creating instances of these classes was entirely hidden from user and they'd be created automatically based on the values from test scenario and configs. Right now these classes give illusion of control but in reality user has to match names and counts defined somewhere else.
This is of course topic for entirely separate change, just something I was thinking about.
There was a problem hiding this comment.
That's a very good point. I'll see if it's easy to handle with a new commit in this PR, otherwise I'll open an issue to follow up later, thanks!
There was a problem hiding this comment.
Sorry, I didn't get a chance to do this but I did open an issue to track it. I'll merge the PR as is to unblock other contributions. Thanks for the review, @mkalcok!
Define explicit nodes for all components (central DBs, relays, etc.), avoid IP guesswork and fix a few bugs.