feat(docs/config): add Ironic OVN annotation examples for provisioning network and config update#1553
Closed
vish6760 wants to merge 1 commit into
Closed
feat(docs/config): add Ironic OVN annotation examples for provisioning network and config update#1553vish6760 wants to merge 1 commit into
vish6760 wants to merge 1 commit into
Conversation
169e219 to
56e9ecb
Compare
and config update Expand the OVN setup guide with Ironic-specific examples for: - multiple bridges including br-pxe - bridge-to-port mappings for provisioning VLAN interfaces - neutron physnet mappings for the provisioning network Also correct the port mapping example to use `bond0` instead of `bond1` so the examples align with the documented bond configuration. feat(ironic): bump chart version to 2025.1.4+ed289c1cd - Update the helm chart for Ironic service. refactor(ironic): Simplify db_sync job configuration - Removed the explicit ironic-db-init job dependency from the db_sync configuration. Signed-off-by: vish6760 <[email protected]>
56e9ecb to
9d934e8
Compare
rackerchris
requested changes
Apr 24, 2026
| | **ovn.openstack.org/int_bridge** | str | `br-int` | The name of the integration bridge that will be used. | | ||
| | **ovn.openstack.org/bridges** | str | `br-ex` | Comma separated list of bridges that will be created and plugged into OVS for a given node. | | ||
| | **ovn.openstack.org/ports** | str | `br-ex:bond1` | Comma separated list of bridge mappings. Maps values from the **bridges** annotation to physical devices or bonds on a given node. | | ||
| | **ovn.openstack.org/bridges** | str | `br-ex,br-pxe` | Comma separated list of bridges that will be created and plugged into OVS for a given node. | |
Contributor
There was a problem hiding this comment.
this should be moved to a "configure ovn for iconic enablement and not in the standard deployment section as this is not needed for a pure compute (non-ironic) deployment and could confuse non-ironic users when configuring ovn.
| | **ovn.openstack.org/bridges** | str | `br-ex` | Comma separated list of bridges that will be created and plugged into OVS for a given node. | | ||
| | **ovn.openstack.org/ports** | str | `br-ex:bond1` | Comma separated list of bridge mappings. Maps values from the **bridges** annotation to physical devices or bonds on a given node. | | ||
| | **ovn.openstack.org/bridges** | str | `br-ex,br-pxe` | Comma separated list of bridges that will be created and plugged into OVS for a given node. | | ||
| | **ovn.openstack.org/ports** | str | `br-ex:bond0,br-pxe:vlanXYZ` | Comma separated list of bridge mappings. Maps values from the **bridges** annotation to physical devices or bonds on a given node. | |
Contributor
There was a problem hiding this comment.
same as ^^^. It would be better to is "OVN Annotations" became a table/matrix with an ironic-enabled section but defaults to non-ironic settings
| | **ovn.openstack.org/bond-options** | str | `bond0:mii-monitor-interval=100,lacp-time=fast` | Comma separated list of additional bond options. Format: `bondname:option1=value1,option2=value2`. Supports MII monitoring, LACP timing, and other OVS bond parameters. | | ||
| | **ovn.openstack.org/vlans** | str | `bond0.126:bond0:126:1500` | Comma separated list of host VLAN interfaces that **ovn-setup** should create before attaching ports. Format: `interface_name:parent_interface:vlan_id:mtu`. | | ||
| | **ovn.openstack.org/mappings** | str | `physnet1:br-ex` | Comma separated list of neutron mappings. Maps a value that will be used in neutron to a value found in the **ports** or **bonds** annotation. Every provider network name listed in this annotation will have a unique mac address generated per-host. | | ||
| | **ovn.openstack.org/mappings** | str | `physnet1:br-ex,physnet2:br-pxe` | Comma separated list of neutron mappings. Maps a value that will be used in neutron to a value found in the **ports** or **bonds** annotation. Every provider network name listed in this annotation will have a unique mac address generated per-host. | |
Contributor
There was a problem hiding this comment.
same here. create a seperate tabbed table "if you are using ironic, you need to exapnd these to include XYZ" (see openstack-keystone-federation/?h=feder#__tabbed_1_2) for an example
Contributor
Author
|
These changes will be handled in PR-1581 |
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
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.
Expand the OVN setup guide with Ironic-specific examples for:
br-pxeAlso correct the port mapping example to use
bond0instead ofbond1sothe examples align with the documented bond configuration.
feat(ironic): bump chart version to 2025.1.4+ed289c1cd
refactor(ironic): Simplify db_sync job configuration
configuration.