GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||
GeezerVison is showing github.com — feat: add network segment range extension to networking v2 by cardoe · Pull Request #3614 · gophercloud/gophercloud Conversation
Contributor
Add support for Neutron's network segment range extension to the networking/v2 module. Fixes #3613 Links to the line numbers/files in the OpenStack source code that support the https://docs.openstack.org/neutron/2025.2//admin/config-network-segment-ranges.html
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsAdd support for Neutron's network segment range extension to the networking/v2 module.
cardoe
added a commit
to cardoe/openstack-resource-controller
that referenced
this pull request
Added an implementation to manage Network Segment Ranges which is a Neutron extension. This depends on gophercloud/gophercloud#3614. For now it pulls that in with a replacement in go.mod.
|
There was an error while loading. Please reload this page.
|
The testing failure is: Not something this code changes or touches or impacts. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Yep, this is a known issue with master branch due to eventlet removal. But I now realize the patch we were waiting for merged and the job should be back to green. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
Would it be possible to add acceptance tests as well, to ensure the feature works as expected against a live environment?
We already configure devstack with the neutron-network-segment-range extension, so the environment should be able to handle it. That said, we should add a guard similar to what's done here:
gophercloud/internal/acceptance/openstack/networking/v2/extensions/mtu/mtu_test.go
Lines 25 to 26 in 01208c9
| // Skip these tests if we don't have the required extension | |
| networking.RequireNeutronExtension(t, client, "net-mtu") |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| } | ||
|
|
||
| // NetworkSegmentRange represents a network segment range. | ||
| type NetworkSegmentRange struct { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should we add all fields? We're currently missing:
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| // CreateOpts represents options for creating a network segment range. | ||
| type CreateOpts struct { | ||
| Name string `json:"name,omitempty"` |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Ideally we'd add godoc comments for all public fields.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
At least 1 approving review is required to merge this pull request.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
neutron: support network segment ranges extension
There was an error while loading. Please reload this page.