@@ -41,6 +41,7 @@ and Manila OpenStack services configured with Ceph.
41
41
| Tenant | VLAN tagged |
42
42
| StorageManagement | VLAN tagged |
43
43
| ironic | untagged |
44
+ | octavia | VLAN tagged |
44
45
45
46
### Services, enabled features and configurations
46
47
@@ -55,6 +56,7 @@ and Manila OpenStack services configured with Ceph.
55
56
| Barbican | | Must have |
56
57
| Ironic | | Must have |
57
58
| Telemetry | | Must have |
59
+ | Octavia | | Must have |
58
60
59
61
#### Support services
60
62
@@ -76,6 +78,60 @@ work properly and can be deployed with any/default configuration.
76
78
- Default settings: TLSe
77
79
- Cluster Observability Operator is installed on the platform.
78
80
81
+ ##### Octavia
82
+
83
+ Octavia is enabled with the appropriate network attachments configured to
84
+ deploy Octavia. It manages amphorae VMs through a self-service tenant network.
85
+ The Octavia Amphora controllers get access to it through a Neutron externally
86
+ routed flat provider network configured as a SNAT-less gateway for a neutron
87
+ router linked to the tenant networks. Host routes on the tenant network's
88
+ subnet and routes on the network attachment provide the required ` next hop `
89
+ routing to establish the necessary bidirectional routing.
90
+
91
+ This arrangement requires a network attachment for connecting the OVN and
92
+ Amphora Controller pods (octavia-housekeeping, octavia-healthmanager,
93
+ octavia-worker). Because Neutron ML2/OVN implements provider networks by
94
+ bridging the relevant physical interface - in this case the network-attachment,
95
+ there is an additional requirement that this attachment function when
96
+ bridged. As the default macvlan attachments do not function when bridged, a
97
+ bridge network attachment is used.
98
+
99
+ Bridge attachments do not directly provide connectivity outside of the OCP
100
+ node. To implement this, the NodeNetworkConfigurationPolicy creates an VLAN
101
+ interface as is typical for the other networks, but does not configure an IP
102
+ pool as it is not needed. It is also not configured for metallb as it is solely
103
+ as part of a way to establish a L2 network link between nodes. The
104
+ NodeNetworkConfigurationPolicy also configures an octbr linux bridge which is
105
+ configured as the bridge for the network attachment mentioned above. It is also
106
+ configured to add the VLAN interface as a port, effectively linking the nodes
107
+ and the network attachments.
108
+
109
+ ``` YAML
110
+ spec :
111
+ octavia :
112
+ enabled : true
113
+ template :
114
+ octaviaAPI :
115
+ networkAttachments :
116
+ - internalapi
117
+ octaviaHousekeeping :
118
+ networkAttachments :
119
+ - octavia
120
+ octaviaWorker :
121
+ networkAttachments :
122
+ - octavia
123
+ octaviaHealthManager :
124
+ networkAttachments :
125
+ - octavia
126
+
127
+ ovn :
128
+ template :
129
+ ovncontroller :
130
+ nicMappings :
131
+ datacentre : ospbr
132
+ octavia : octbr
133
+ ` ` `
134
+
79
135
## Considerations/Constraints
80
136
81
137
N/A
0 commit comments