Currently, network segment ranges are configured as an entry in ML2
config file [1]_ that is statically defined for tenant network
allocation and therefore must be managed as part of the host deployment
and management. When a normal 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.
This spec introduces an extension which exposes the segment range
management to be administered via the Neutron API. In addition, it
introduces the ability for the administrator to control the segment
ranges globally or on a per-tenant basis.
[1] /etc/neutron/plugins/ml2/ml2_conf.ini
Co-Authored-By: Matt Peters <matt.peters@windriver.com>
Implements: blueprint network-segment-range-management
Change-Id: I2e586bb6d51d32c0ac2a28b2429512cea036f363
Before the final merge of the minimum bandwidth resource classes
they got renamed in Nova and Placement. So we have to adapt.
This change retroactively updates the spec.
Change-Id: Ia347c71381ec2fd82a1b197f5d0fbed69a70ad70
Partial-Bug: #1578989
See-Also: I996bf705b14b564106426a2e57299638fb178750
See-Also: https://review.openstack.org/616194
The commands used by constraints need at least tox 2.0. Update to
reflect reality, which should help with local running of constraints
targets.
Change-Id: Ie69f0a6fa56fd1fceaa7893bece8b2735095216c
Related-Bug: 1801465
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I6e18dd70a74694ba2e7aad535f487498a26d05bb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The py27 test ensures that all specs are following a specific format.
The default py27 tests have an irrelevant-files list that ignores
running if especially only .rst files get updated. Override the
irrelevant files list so that it runs for nearly all changes,
only skip for release-notes (even if they do not exist here).
Change-Id: Iffb6345ddf490820ca7495f0e4a0e722acfba898
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I482073ef15154dff754839ffd161fe08211ebc89
Story: #2002586
Task: #24314
The QoS DSCP spec is not terribly specific about what DSCP marks are
valid. This change makes it explicit.
This spec is quite old. But since there has been no other place in the
documentation that explicitly lists what the valid DSCP marks are,
updating this in case people use it as documentation.
Change-Id: Ieec3e238b8d404e46c49b5a1a0fdaf695fff4252
Related-Bug: #1781915
According to Openstack summit session [1] stestr is
maintained project to which all Openstack projects
should migrate.
Let's switch it then.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: Idd7629f2a051aadaf53b04a1b331b20d7fa690de
This spec provides details on a enhancement to Firewall as
a Service(FWaaS) API 2.0 for supporting address groups.
Change-Id: I7472f9611e2f5794c46f37fbbacadf38e0320a6f
In py27 job index.rst file was checked as any other file if it
contains required headers and sections.
But index.rst file has different format so this file should be
skipped in this test.
After that there was also issue with unexpected "Footnotes"
section in neutron-inter.rst specs so this was also fixed.
Change-Id: If2baf887c49025a5481e97b2fb3500736b8668b6
This change includes:
* a follow-up to [1] to fix the typos pointed out during review
* title fixes for two specs having the same title in the TOC
* two other typos
[1] https://review.openstack.org/545826
I3860a62420ab4983e2b741dff04498fbb0432d00
Change-Id: I4ebb090de53370708e871c75c789b62bc5e71010
This spec describes how to model, from Neutron, a new resource provider
in the Placement API to describe the bandwidth allocation.
Based on a Rocky PTG discussion this is a re-work of the spec.
Co-Authored-By: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Co-Authored-By: Bence Romsics <bence.romsics@ericsson.com>
Co-Authored-By: Balazs Gibizer <balazs.gibizer@ericsson.com>
Related-Bug: #1578989
Change-Id: Ib995837f6161bcceb09735a5601d8b79a25a7354
See-Also: Ie7be551f4f03957ade9beb64457736f400560486
- Update outdated links in README
- Remove skeleton.rst, this file is unnecessary.
- Add Stein Specifications dir.
- Move placeholder.rst to stein dir, because there
is a blueprint accepted in rocky dir.
Change-Id: I5fd436db02517404d3aca3114498206f164bca44
This is the spec for the VPN Qos.
Paritial-Bug: #1727578
Change-Id: I5f94b89d2e11734385b58e5e5edf55d149b9f38a
Depends-On: If40305044c9dfe0024b64bd3921232bb0a6c9372
This spec provides details on how we can break consumer dependencies
on neutron's database model as well as object imports by
exposing neutron objects as entry points that are discoverable and
loadable from neutron-lib. This spec is part of a set of specs related
to decoupling the db for neutron-lib (see patch topic).
Change-Id: I079d06502e6e7b1e20aea882979b0ecd9106eaeb
This spec provides details on how we can break consumer dependencies
on neutron's db API and utilities by rehoming respective generic
functionality into neutron-lib. It's 1 spec in a set related to
decoupling sub-projects from neutron's db logic/layer.
Change-Id: I7b04e202321e1422e53c59c2bab0c85946fcb704
After switching to openstackdocstheme, the left side menu lists
all specs and it is no longer useful as navigation.
This commit reorganizes the doc structure and toctree so that
the toctree is easy to read with openstackdocstheme.
Change-Id: I47a8c28c038bf2022855a81f6073f4b5f4b01266
For compliance with the Project Testing Interface as described in:
https://governance.openstack.org/tc/reference/project-testing-interface.html
For more detials information, please refer to:
http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html
To handle this, this commit changes:
- Introduce doc/requirements.txt
- Update tox.ini [docs] target for developer convenience
- Fixes a lot of warnings caused by a newer sphinx 1.6.5 because
sphinx specified in upper-constraints.txt is used in the new PTI.
- Drop unnecessary [pbrp] warnerrors in favor of warning-is-error.
Change-Id: If40305044c9dfe0024b64bd3921232bb0a6c9372
The following spec specifies the Port Forwarding extension
for Floating IPs. And intro a new sub resource into floatingip for port
forwarding support.
Depends-On: If40305044c9dfe0024b64bd3921232bb0a6c9372
Change-Id: Ib2c47b585538bbc067a488e34fd0fc8097314f98
Partial-Bug: #1491317
This patch is following up from Pike discussion [1]. With the remaining
main gap (N4) has been addressed to be able to jump into the stadium.
[1] Ie06395533211847d741c9c9bbd45bc8edbab6e5c
Change-Id: I6a8b19c8c53f49a95667af331e147b977a9d0d7c
Co-Authored-By: Armando Migliaccio <armamig@gmail.com>
This is following up of [1] to open stadium doc structure
for Queens.
[1] I80e4aefe5700f6c1dcf1037f22bf58b5d23ea95d
Change-Id: I2a00a7555134a5bcf42385695bd04e207eeb96fd
Co-Authored-By: Armando Migliaccio <armamig@gmail.com>
* Move Pike incompleted efforts to backlog
* Archive Ocata specs that were not reproposed for Pike
* Open Queens directory.
Change-Id: I80e4aefe5700f6c1dcf1037f22bf58b5d23ea95d
This patch is elaborating that the gaps in Ocata are going to be
addressed in Pike.
Co-Authored-By: Armando Migliaccio <armamig@gmail.com>
Change-Id: Ie06395533211847d741c9c9bbd45bc8edbab6e5c
QoS backend drivers are using validators "type:range" and "type:values" to
validate if given value is supported.
Such possible values should be represented in different way when rule_type
details are requested.
This commit changes format of values which can be returned as result of such
request.
Change-Id: I460f7b2b265115120102e575d4040c0c5f5264f8
Partial-Bug: 1686035
zhangbailin