No network-segment-range support

Bug #1965229 reported by Nobuto Murata
8
This bug affects 1 person
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-segment-range"

From the upstream documentation, there is a limitation in terms of operations if we miss the service plugin.

https://docs.openstack.org/neutron/latest/admin/config-network-segment-ranges.html
> 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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (master)
Changed in charm-neutron-api:
status: New → In Progress
Revision history for this message
Nobuto Murata (nobuto) wrote :

Subscribing ~field-medium.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-api (master)

Reviewed: https://review.opendev.org/c/openstack/charm-neutron-api/+/834117
Committed: https://opendev.org/openstack/charm-neutron-api/commit/c411b90d2d14e7ad7678e0ce0b81ac82fdaffa3a
Submitter: "Zuul (22348)"
Branch: master

commit c411b90d2d14e7ad7678e0ce0b81ac82fdaffa3a
Author: Nobuto Murata <email address hidden>
Date: Thu Mar 17 14:58:34 2022 +0900

    Option to enable network-segment-range support

    To let operators add an additional and optional service plugin into the
    deployment configuration as "network_segment_range".
    https://docs.openstack.org/neutron/latest/admin/config-network-segment-ranges.html

    Closes-Bug: #1965229
    Change-Id: Id0ac7c397874ad2c51935e8c0eab64f1ef4f6fd3

Changed in charm-neutron-api:
status: In Progress → Fix Committed
Revision history for this message
Nobuto Murata (nobuto) wrote (last edit ):

Just for the record, here is an output after enabling the service plugin out of the box of Charmed OpenStack deployment.

$ openstack network segment range list --long
+--------------------------------------+------+---------+--------+------------+--------------+------------------+------------+------------+----------------------------------------------------------------------------------------------+-----------------------------------------+
| ID | Name | Default | Shared | Project ID | Network Type | Physical Network | Minimum ID | Maximum ID | Used | Available |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+------------+------------+----------------------------------------------------------------------------------------------+-----------------------------------------+
| 32324656-611b-4aa5-9605-55ec607e9780 | | True | True | None | vlan | physnet1 | 1000 | 2000 | {} | ['1000-2000'] |
| 5f80fc78-ebd2-4220-8381-8872ffdc4120 | | True | True | None | geneve | None | 1001 | 2000 | {'0e5cdb8a97574b6ba171767ddc750c11': ['1602'], '8f5dc07f47794ee49d2b40863dbd692c': ['1105']} | ['1001-1104', '1106-1601', '1603-2000'] |
| be52d70a-7a8f-4e99-9185-102688827c44 | | True | True | None | gre | None | 1 | 1000 | {} | ['1-1000'] |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+------------+------------+----------------------------------------------------------------------------------------------+-----------------------------------------+

$ openstack network segment range list --format yaml
- Default: true
  ID: 32324656-611b-4aa5-9605-55ec607e9780
  Maximum ID: 2000
  Minimum ID: 1000
  Name: ''
  Network Type: vlan
  Physical Network: physnet1
  Project ID: null
  Shared: true
- Default: true
  ID: 5f80fc78-ebd2-4220-8381-8872ffdc4120
  Maximum ID: 2000
  Minimum ID: 1001
  Name: ''
  Network Type: geneve
  Physical Network: null
  Project ID: null
  Shared: true
- Default: true
  ID: be52d70a-7a8f-4e99-9185-102688827c44
  Maximum ID: 1000
  Minimum ID: 1
  Name: ''
  Network Type: gre
  Physical Network: null
  Project ID: null
  Shared: true

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/xena)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834290

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834291

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/victoria)

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834292

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/ussuri)

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834293

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834294

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834295

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (stable/21.10)

Fix proposed to branch: stable/21.10
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834278

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/21.10)

Change abandoned by "Nobuto Murata <email address hidden>" on branch: stable/21.10
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834278

Revision history for this message
Nobuto Murata (nobuto) wrote :

This is not available on the charmhub still. A weird thing is that the charm build page has two built files.

https://launchpad.net/~openstack-charmers/charm-neutron-api/+charm/charm-neutron-api.master.latest/+build/1099
- neutron-api.charm does NOT have "enable-network-segment-range" option
- neutron-api_ubuntu-20.04-amd64.charm does have "enable-network-segment-range" option

However, when executing the following command, it downloads a charm WITHOUT enable-network-segment-range.

$ juju download --arch amd64 --series focal --channel yoga/edge neutron-api

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

I think I've worked out what is going on here. The repository for neutron-api has had "neutron-api.charm" merged into it by accident, and that is (attempted) to be being uploaded: https://launchpad.net/~openstack-charmers/charm-neutron-api/+charm/charm-neutron-api.master.latest/+build/1099, in particular:

"Charmhub upload failed: Cannot insert package. An upload with that digest (SHA3-384: '3dd3d460ea5f234dfde56766b365524631b0d323c27cc0f1f177dbc3ee86617345e1a1b3635fd033bf02767a8640749d') already exists in the database."

I've raised a patch: https://review.opendev.org/c/openstack/charm-neutron-api/+/833990 to remove it from the archive. Just need it to land and hopefully that will solve this problem.

Revision history for this message
Nobuto Murata (nobuto) wrote :

Hi Alex, thank you for the detailed response. I suppose I need to be a bit more patient now to see a new job in https://launchpad.net/~openstack-charmers/charm-neutron-api/+charm/charm-neutron-api.master.latest

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-api (stable/xena)

Reviewed: https://review.opendev.org/c/openstack/charm-neutron-api/+/834290
Committed: https://opendev.org/openstack/charm-neutron-api/commit/8b5da514f69f2ea04b2ec22802f1f896613269bd
Submitter: "Zuul (22348)"
Branch: stable/xena

commit 8b5da514f69f2ea04b2ec22802f1f896613269bd
Author: Nobuto Murata <email address hidden>
Date: Thu Mar 17 14:58:34 2022 +0900

    Option to enable network-segment-range support

    To let operators add an additional and optional service plugin into the
    deployment configuration as "network_segment_range".
    https://docs.openstack.org/neutron/latest/admin/config-network-segment-ranges.html

    Closes-Bug: #1965229
    Change-Id: Id0ac7c397874ad2c51935e8c0eab64f1ef4f6fd3
    (cherry picked from commit c411b90d2d14e7ad7678e0ce0b81ac82fdaffa3a)

tags: added: in-stable-xena
Revision history for this message
Nobuto Murata (nobuto) wrote :

There are multiple issues just for the record.

latest/edge has the expected patch set which is good.

$ juju info neutron-api | grep latest/
  latest/stable: 501 2021-12-02 (501) 483kB
  latest/candidate: 498 2021-10-18 (498) 483kB
  latest/beta: ^
  latest/edge: 520 2022-03-21 (520) 795kB

However, Juju is failing to pick it (might be a charmhub issue though):
https://bugs.launchpad.net/juju/+bug/1966664

Backport to xena branch has been merged on March 25th. But somehow it doesn't show up in `juju info` while it can be seen in `charmcraft status` for the owners.

$ juju info neutron-api | grep xena/
  xena/stable: --
  xena/candidate: --
  xena/beta: --
  xena/edge: 501 2022-03-04 (501) 483kB

https://launchpad.net/~openstack-charmers/charm-neutron-api/+charm/charm-neutron-api.stable-xena.xena

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-guide (master)
Changed in charm-guide:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-guide (master)

Reviewed: https://review.opendev.org/c/openstack/charm-guide/+/837650
Committed: https://opendev.org/openstack/charm-guide/commit/d9d614de3c6e198cf04f0158e3f80dbcd6e8f281
Submitter: "Zuul (22348)"
Branch: master

commit d9d614de3c6e198cf04f0158e3f80dbcd6e8f281
Author: Nobuto Murata <email address hidden>
Date: Wed Apr 13 11:43:53 2022 +0900

    release-notes: network-segment-range

    Closes-Bug: #1965229
    Change-Id: I130e2cf11a9cf71d0ee02353d0b37810e1099c7c

Changed in charm-guide:
status: In Progress → Fix Released
Changed in charm-neutron-api:
milestone: none → 22.04
Changed in charm-neutron-api:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/wallaby)

Change abandoned by "James Page <email address hidden>" on branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834291
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/train)

Change abandoned by "James Page <email address hidden>" on branch: stable/train
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834294
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/ussuri)

Change abandoned by "James Page <email address hidden>" on branch: stable/ussuri
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834293
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/stein)

Change abandoned by "James Page <email address hidden>" on branch: stable/stein
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834295
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on charm-neutron-api (stable/victoria)

Change abandoned by "James Page <email address hidden>" on branch: stable/victoria
Review: https://review.opendev.org/c/openstack/charm-neutron-api/+/834292
Reason: This review is > 12 weeks without comment, and failed testing the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.