Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Epic Link:
[P1] Podified Control Plane : Neutron
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Dev Approval:
?
Docs Approval:
?
Feature Link:
OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
PM Approval:
?
QE Approval:
?
Intelligence Requested:
Market:

Planning Target:

2023Q2

Workstream:

HardProv, Networking; Neutron

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

In some cases (IPv6) Ironic[1] needs to use traditional neutron-dhcp-agent so we need to add controller which will deploy it on the control plane.

One important thing to figure out is how neutron-dhcp-agent can have access to the openvswitch which is running in the ovs pod to create port in the br-int there.

[1]https://issues.redhat.com/browse/OSP-18828

depends on

OSPRH-3210 [neutron-operator] Check how sidecar containers will work on control plane

Closed

is blocked by

OSPRH-3211 Understand if we can afford replacing DHCP agent with OVN native solution for all use cases

Closed

OSPRH-644 Find way to access network stacks between pods for agents

Closed

relates to

OSPRH-1289 OSP 18.0 2023 Q1 Demonstration

Closed

Assignee:: Unassigned

Reporter:: Slawomir Kaplonski

Team:: rhos-dfg-networking-squad-neutron

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2022/11/10 3:42 PM

Updated:: 2024/02/13 3:05 PM

Resolved:: 2023/09/15 4:28 PM

Target end:: 2023/02/28

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty