682 Commits (148136ac0e140677ae9176ef1b4fbc2d15dbd72a)

Author SHA1 Message Date
zhangbailin 148136ac0e Change openstack-dev to openstack-discuss
Mailinglists have been updated. Openstack-discuss replaces

Change-Id: Ifdb408cadf02a22fb3a7c370235f28a371baaf3f
5 years ago
Zuul fef5951bad Merge "Network Segment Range Management" 5 years ago
Kailun Qin 4c8156c804 Network Segment Range Management
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
5 years ago
Zuul 5b577b5880 Merge "Update min tox version to 2.0" 5 years ago
Nguyen Hai bc7ba113ed Add placeholder for Train specs
The "T" release of OpenStack is officially "Train".


Change-Id: I8173bd1886df4d306c10d434e2ecdec095070dbd
5 years ago
Bence Romsics 2af53625e7 Adapt to changed resource class names
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
5 years ago
Vieri 5e3f3ce32a Update min tox version to 2.0
The commands used by constraints need at least tox 2.0.  Update to
reflect reality, which should help with local running of constraints

Change-Id: Ie69f0a6fa56fd1fceaa7893bece8b2735095216c
Related-Bug: 1801465
5 years ago
Zuul 3cdf4b8ae7 Merge "Always run py27 test" 5 years ago
Doug Hellmann 8857a844ba fix tox python3 overrides
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>
5 years ago
Andreas Jaeger 32a202874c Always run py27 test
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
5 years ago
Doug Hellmann cdad349eaa import zuul job settings from project-config
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project

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

See the python3-first goal document for details:

Change-Id: I482073ef15154dff754839ffd161fe08211ebc89
Story: #2002586
Task: #24314
5 years ago
Zuul b60610fcc2 Merge "Add list of all working DSCP marks" 5 years ago
Zuul 86566de1de Merge "fwaas 2.0 address groups support" 5 years ago
Nate Johnston a728b8a642 Add list of all working DSCP marks
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
5 years ago
Slawek Kaplonski c886130f15 Switch to stestr
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
5 years ago
Wang Tao 4b78201207 fwaas 2.0 address groups support
This spec provides details on a enhancement to Firewall as
a Service(FWaaS) API 2.0 for supporting address groups.

Change-Id: I7472f9611e2f5794c46f37fbbacadf38e0320a6f
5 years ago
Zuul fd44a5a96a Merge "(Operator-only) Extend logging framework for FWaaS v2" 5 years ago
Slawek Kaplonski d531e274d5 Fix py27 job in specs repo
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
5 years ago
Cao Xuan Hoang 6a1372079a (Operator-only) Extend logging framework for FWaaS v2
This spec follows up the original spec[1] to extend the
work to support for FWaaS v2.

[1] https://specs.openstack.org/openstack/neutron-specs/specs/pike/logging-API-for-security-group-rules.html

Partial-Bug: #1720727

Co-Authored-By: Yushiro FURUKAWA <y.furukawa_2@jp.fujitsu.com>
Co-Authored-By: Nguyen Phuong An <AnNP@vn.fujitsu.com>
Co-Authored-By: Cuong Nguyen <cuongnv@vn.fujitsu.com>
Change-Id: I409265229853f3d5c7e7a698c5b0787586ac1558
5 years ago
Zuul 537788b261 Merge "Trivial:Update pypi url to new url" 5 years ago
zhengwei6082 61fe7beaff Trivial:Update pypi url to new url
Pypi url changed from [1] to [2]

[1] https://pypi.python.org/pypi/<package>
[2] https://pypi.org/project/<package>

Change-Id: I10bf93ff44c88e39fbd98d0061ede2dbfcca929b
5 years ago
Thomas Morin 77f36d5f89 Minor typo corrections
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

Change-Id: I4ebb090de53370708e871c75c789b62bc5e71010
5 years ago
Zuul cf38b6af27 Merge "Neutron-Neutron Interconnections" 5 years ago
Bence Romsics dca619fd9e QoS minimum bandwidth allocation in Placement API
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
5 years ago
Thomas Morin 2a34abbd25 Neutron-Neutron Interconnections
Proposed specifications for the Neutron-Neutron Interconnections

Change-Id: I3860a62420ab4983e2b741dff04498fbb0432d00
Related-Bug: 1750368
5 years ago
Zuul ac7d3cffcc Merge "Spec for VPN service support Qos" 5 years ago
Zuul 9b7cd99a76 Merge "decouple neutron db models and ovo for neutron-lib" 5 years ago
Zuul d4aa5a56b8 Merge "rehome db api and utils into neutron-lib" 5 years ago
Nguyen Hai 877df70754 Delete redundant rst files and update README
- 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
5 years ago
ZhaoBo cc8b3ec9ee Spec for VPN service support Qos
This is the spec for the VPN Qos.

Paritial-Bug: #1727578
Change-Id: I5f94b89d2e11734385b58e5e5edf55d149b9f38a
Depends-On: If40305044c9dfe0024b64bd3921232bb0a6c9372
5 years ago
Boden R 3df6e5c811 decouple neutron db models and ovo for neutron-lib
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
5 years ago
Boden R 32c862feec rehome db api and utils into neutron-lib
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
5 years ago
Zuul 1aca235131 Merge "Move specs implemented in Queens from backlog" 5 years ago
Zuul d06a992d18 Merge "Reorganize docs to fit openstackdocstheme" 5 years ago
Akihiro Motoki 32de16ed89 Move Port Forwarding spec to Rocky
It is targetted to Rocky but it was merged accidentally before
Rocky directory is prepared.

Change-Id: Ia73a333b7544dd1bc4ab8027dd69f7dcc92c8e36
5 years ago
Zuul b877de2b3a Merge "Initiate Rocky specs" 5 years ago
Zuul 55c44fc161 Merge "Spec for Port Forwarding" 5 years ago
Akihiro Motoki e5b2487c86 Move specs implemented in Queens from backlog
Change-Id: If28b5bbb31168546a70492bb837df4f05165cc9c
5 years ago
Akihiro Motoki e910a8c84e Reorganize docs to fit openstackdocstheme
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
5 years ago
Thomas Morin eb776ef84c Initiate Rocky specs
Change-Id: I32b61bed3b18c30d3e51e5e049a3036ac7080979
5 years ago
ZhaoBo c95726bbf0 Need to follow the new PTI for document build
For compliance with the Project Testing Interface as described in:

For more detials information, please refer to:

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
5 years ago
Reedip 66eb7e1729 Spec for Port Forwarding
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
5 years ago
Cao Xuan Hoang 28f2a4357b Queens: Assessment for neutron-vpnaas
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>
6 years ago
Cao Xuan Hoang bc9e638e11 Open stadium doc structure
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>
6 years ago
Armando Migliaccio 1399546ec6 Open Queens spec directory
* Move Pike incompleted efforts to backlog
* Archive Ocata specs that were not reproposed for Pike
* Open Queens directory.

Change-Id: I80e4aefe5700f6c1dcf1037f22bf58b5d23ea95d
6 years ago
Cao Xuan Hoang f26b787aea Pike: Assessment for neutron-vpnaas
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
6 years ago
Sławek Kapłoński a40b46100f Update description of possible values in QoS rule types
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

Change-Id: I460f7b2b265115120102e575d4040c0c5f5264f8
Partial-Bug: 1686035
6 years ago
Jenkins dcc30d91b5 Merge "Fix doc generation for Python3" 6 years ago
Jenkins a307e8719d Merge "Neutron Common Classification Framework" 6 years ago
Jenkins e27012686f Merge "Add more detailed info about supported QoS rule types" 6 years ago