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