custom: add ovs-manager play to configure OVSDB managers#2920
Closed
berendt wants to merge 1 commit into
Closed
Conversation
Add a custom Ansible play that configures the OVSDB managers (TCP listener on port 6640) on all Open vSwitch nodes. It sets a listener on 127.0.0.1 and on the node's own internal management address, guarded by the presence of the openvswitch_db container and made idempotent via a get-manager comparison. Run it automatically at the end of the service deployment so it executes once OVS and all other services are up. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Christian Berendt <berendt@osism.tech>
berendt
added a commit
that referenced
this pull request
Jul 1, 2026
Add a custom Ansible play that installs Northwatch (https://github.com/b42Labs/northwatch) as a .deb package on the manager and configures it to browse, debug and monitor the testbed OVN control plane. This is the config-file equivalent of Northwatch's `make testbed` target: the OVN Northbound/Southbound addresses and the OpenStack enrichment credentials are rendered into /etc/northwatch/clusters.json, and the shipped northwatch.service is driven via /etc/default/northwatch. The second play configures the OVSDB managers (TCP listener on port 6640, on 127.0.0.1 and the node's internal management address) on all Open vSwitch nodes for per-chassis OVS visibility. It supersedes the standalone ovs-manager play from #2920, so that PR can be closed. Run with: osism apply --environment custom northwatch Assisted-by: Claude:claude-opus-4-8
berendt
added a commit
that referenced
this pull request
Jul 1, 2026
Add a custom Ansible play that installs Northwatch (https://github.com/b42Labs/northwatch) as a .deb package on the manager and configures it to browse, debug and monitor the testbed OVN control plane. This is the config-file equivalent of Northwatch's `make testbed` target: the OVN Northbound/Southbound addresses and the OpenStack enrichment credentials are rendered into /etc/northwatch/clusters.json, and the shipped northwatch.service is driven via /etc/default/northwatch. The second play configures the OVSDB managers (TCP listener on port 6640, on 127.0.0.1 and the node's internal management address) on all Open vSwitch nodes for per-chassis OVS visibility. It supersedes the standalone ovs-manager play from #2920, so that PR can be closed. Run with: osism apply --environment custom northwatch Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Christian Berendt <berendt@osism.tech>
berendt
added a commit
that referenced
this pull request
Jul 1, 2026
Add a custom Ansible play that installs Northwatch (https://github.com/b42Labs/northwatch) as a .deb package on the manager and configures it to browse, debug and monitor the testbed OVN control plane. This is the config-file equivalent of Northwatch's `make testbed` target: the OVN Northbound/Southbound addresses and the OpenStack enrichment credentials are rendered into /etc/northwatch/clusters.json, and the shipped northwatch.service is driven via /etc/default/northwatch. The second play configures the OVSDB managers (TCP listener on port 6640, on 127.0.0.1 and the node's internal management address) on all Open vSwitch nodes for per-chassis OVS visibility. It supersedes the standalone ovs-manager play from #2920, so that PR can be closed. Run with: osism apply --environment custom northwatch Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Christian Berendt <berendt@osism.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ovs-managerthat configures the OVSDBmanagers (TCP listener on port 6640) on all Open vSwitch nodes — a
listener on
127.0.0.1and one on the node's own internal managementaddress (
ptcp:6640:{{ internal_address }}).openvswitch_dbcontainer and madeidempotent via a
get-managercomparison, so it only acts on nodesthat actually run Open vSwitch and only when the managers differ.
deploy-services.shso it executesonce OVS and all other services are up.
This is required in preparation for the use of b42labs/northwatch to
demonstrate the OVS feature.
Test plan
🤖 Generated with Claude Code