-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
5
-
False
-
-
False
-
RHOSSTRAT-100 - OVN gateway Adoption - Support for OSP 17.1 Controller Nodes on OCP Pods and Retained Networker Nodes [FR2]
-
-
Known Issue
-
-
-
Neutron Sprint 7
-
1
-
Important
In the https://issues.redhat.com/browse/OSPRH-1031 it was mentioned that while adopting OSP 17.1 environment where controller nodes are running as gateway chassis also (there are no dedicated networker nodes there) such nodes should be adopted to the RHOSO as edpm-networker nodes and still run as gateway chassis there, at least temporary. Later, after adoption is finished user can plane to e.g. scale such gateway chassis down and get rid of them.
For this spike:
*It seems that we don't have any documentation nor testing related to that. We should probably add some documentation(Draft DOC PR ) about how to adopt such controller nodes to be networkers - this should be similar to adoption of the OSP 17.1 networker nodes to be RHOSO networker nodes but may require some small changes and probably separate chapter in the docs.
- See if we can have adoption job with the dedicated networker node. If it an easy thing to do (like creating .yaml job definition) then do it. If it is more involved work, create a task for it under the parent epic.
- depends on
-
OSPRH-10714 As a cloud operator I want to adopt OSP-17.1's controller nodes, which were gateway chassis, to keep them as networker
-
- In Progress
-
- relates to
-
OSPRH-9615 Validate dataplane adoption where OSP controllers becomes networker nodes
-
- Backlog
-
-
OSPRH-11149 [adoption][NFV] no ping to FIPs of pre-created VMs after adoption
-
- Closed
-
- links to