No network-segment-range support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Neutron API Charm |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
At this point, Charmed OpenStack deployment doesn't have Network segment ranges support.
$ openstack extension list --network
-> doesn't return "network-
From the upstream documentation, there is a limitation in terms of operations if we miss the service plugin.
https:/
> Before Stein, network segment ranges were configured as an entry in ML2
> config file ml2_conf.ini that was statically defined for tenant network
> allocation and therefore had to be managed as part of the host
> deployment and management. When a regular tenant user creates a
> network, Neutron assigns the next free segmentation ID (VLAN ID, VNI
> etc.) from the configured segment ranges. Only an administrator can
> assign a specific segment ID via the provider extension.
Changed in charm-neutron-api: | |
milestone: | none → 22.04 |
Changed in charm-neutron-api: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. opendev. org/c/openstack /charm- neutron- api/+/834117
Review: https:/