700 Commits

Author SHA1 Message Date
Akihiro Motoki
635de2f087 Switch py27 job to py36
Change-Id: I1633b3cccced0b37de667ff6d440f39ebe66fccc
2019-05-04 17:38:15 +00:00
OpenDev Sysadmins
e532cd1d2e OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:34:46 +00:00
Zuul
a097bd8bce Merge "Changing segmentation ID of existing network should be allowed" 2019-03-07 08:36:32 +00:00
ythomas1
c97f096695 Update Neutron-Neutron Interconnections
- Move specification for Neutron-Neutron Interconnections RFE for
  implementation in Stein release,
- Remove redundant states from lifecycle FSM,
- Add remote_interconnection_id attribute to interconnection resource,
- Minor update in API exchange example.

Signed-off-by: Thomas Morin <thomas.morin@orange.com>
Submitted on behalf of a third-party: Orange

Change-Id: I30a886813cdca4ed47507bbff38aff2d4137b434
Related-Bug: 1750368
2019-02-22 10:36:41 +01:00
Zuul
597f767e5c Merge "Registering RouterInfo by L3 extention API" 2019-02-21 12:09:16 +00:00
Yang Youseok
bd23545778 Registering RouterInfo by L3 extention API
Currently, most plugin implementations releated L3 override the
L3NatAgent class itself for their own logic since there is no proper
interface to extend RouterInfo class. This adds unnecessary complexity
for developers who just want to extend agent mechanism instead of
whole RPC related to L3 functinalities.

This spec introduces RouterFactory class which acts on the factory for
creating RouterInfo class, and add new l3 extension API which enable to
dynamically add RouterInfo to the factory. Now plugin developers can
use new extension API for their own specific router.

Change-Id: Ic3486830e449f6ee8dbe19db614179b2077bcf7b
Related-Bug: #1804634
Implements: blueprint router-factory-with-l3-extension
2019-02-21 10:20:26 +09:00
Zuul
bb48efae10 Merge "Update links in README" 2019-02-13 10:23:27 +00:00
Rodolfo Alonso Hernandez
3f9ca0e441 Changing segmentation ID of existing network should be allowed
In the context of a live datacenter, sometimes the network teams re-organize
their VLANs by changing VLAN IDs. This is pretty straightforward in the
context of network configuration and physical servers, but when using ML2
VLAN provider networks, those IDs cannot be updated. The only possible
solution here would be to delete those networks and recreate them with a
different segmentation ID which might be a problem when you have 1000 VMs
and 2000 ports.

For this reason it would be good if we could change the segmentation ID of
an existing network.

Change-Id: I71b5b4ff2ba7ace3a8523de2ae6e4dc6a1c110c2
Related-Bug: #1806052
2019-02-11 11:50:11 -05:00
Zuul
6824b2a647 Merge "Add Support for Smart NIC in OVS ML2 mech driver" 2019-01-19 00:04:29 +00:00
Moshe Levi
33d4d845f1 Add Support for Smart NIC in OVS ML2 mech driver
This spec is the Neutron side changes to support
smart NICs with Neutron OVS ML2 mechanism driver
and Neutron OVS Agent.

Related-Bug: #1785608

Change-Id: I658754f7f8c74087b0aabfdef222a2c0b5698541
2019-01-13 10:32:53 +02:00
Zuul
70abe178b6 Merge "Change openstack-dev to openstack-discuss" 2019-01-09 22:24:07 +00:00
Zuul
c7e397a60c Merge "Fix inconsistent shared attribute default value" 2019-01-09 20:37:30 +00:00
Kailun Qin
813a5ce92d Fix key type of used dict in JSON responses
JSON regulates key type to be string.

Co-Authored-By: Matt Peters <matt.peters@windriver.com>

Partially-implements: blueprint network-segment-range-management
Change-Id: I946a6ee14cef4f6b2e7e29ac644b31e1c340e83b
2019-01-10 02:43:44 +08:00
Kailun Qin
3cc92d0cc0 Fix inconsistent shared attribute default value
The proposed `shared` attribute in the resource extension table should
have a default value `True` to align with the definition in the
RESOURCE_ATTRIBUTE_MAPS.

Co-Authored-By: Matt Peters <matt.peters@windriver.com>

Partially-implements: blueprint network-segment-range-management
Change-Id: Ic7f98a71bcfe289754438f9c3d1eed2d3ed4bfdc
2019-01-10 02:43:22 +08:00
Kailun Qin
629248149d Add default to network segment range resource
This patch is a follow-up to [1] to propose adding a new `read-only`
attribute `default` to the network segment range resource. It tracks
whether this is a range that is managed/loaded from the host ML2 config
file [2].

The attribute is proposed based on the following considerations:
1. We prefer the underlying network segment ranges to be exposed so that
   an admin can base on the info to make per-tenant range assignment;
2. We want the backward compatibility to be maintained, i.e. no work
   flow change with and without the extension is loaded;
3. We need to handle the range DB refresh/config repopulation when a
   Neutron server starts/restarts.

[1] https://review.openstack.org/599980
[2] /etc/neutron/plugins/ml2/ml2_conf.ini

Co-Authored-By: Matt Peters <matt.peters@windriver.com>

Partially-implements: blueprint network-segment-range-management
Change-Id: I8cc0ed77603a5d430c6d7b2b503c7b5a80ed0051
2019-01-09 06:41:02 +08:00
Zuul
a038872273 Merge "Introduce port mirroring for sriov-vf" 2018-12-21 18:18:59 +00:00
zhangbailin
148136ac0e Change openstack-dev to openstack-discuss
Mailinglists have been updated. Openstack-discuss replaces
openstack-dev.

Change-Id: Ifdb408cadf02a22fb3a7c370235f28a371baaf3f
2018-12-03 21:38:47 -05:00
Zuul
fef5951bad Merge "Network Segment Range Management" 2018-11-28 20:57:51 +00:00
Munish Mehan
f4591c55de Introduce port mirroring for sriov-vf
Add SRIOV mirroring support to Tap as a Service.
   Allows Vlans to VF mirror.
   Allows VF to VF mirror.

 Spec for new tap agent for sriov and driver for Intel i40e nic.
 Added the two implementation approaches to API.

Change-Id: If2e4e2bf70f11ab0136482cb86acad3a3eded649
2018-11-28 08:07:15 -05:00
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
2018-11-28 10:10:00 +08:00
Zuul
5b577b5880 Merge "Update min tox version to 2.0" 2018-11-21 00:17:58 +00:00
Nguyen Hai
bc7ba113ed Add placeholder for Train specs
The "T" release of OpenStack is officially "Train".

http://lists.openstack.org/pipermail/openstack-dev/2018-November/136464.html

Change-Id: I8173bd1886df4d306c10d434e2ecdec095070dbd
2018-11-14 14:09:19 +09:00
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
2018-11-13 16:48:02 +01:00
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
targets.

Change-Id: Ie69f0a6fa56fd1fceaa7893bece8b2735095216c
Related-Bug: 1801465
2018-11-10 02:20:56 +00:00
Zuul
3cdf4b8ae7 Merge "Always run py27 test" 2018-10-29 15:14:22 +00:00
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>
2018-10-17 00:16:11 -04:00
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
2018-10-03 17:38:20 +02:00
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
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
2018-08-29 17:37:38 -04:00
Zuul
b60610fcc2 Merge "Add list of all working DSCP marks" 2018-07-19 18:49:42 +00:00
Zuul
86566de1de Merge "fwaas 2.0 address groups support" 2018-07-19 17:03:05 +00:00
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
2018-07-16 11:35:49 -04:00
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
2018-06-22 12:50:11 +02:00
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
2018-06-21 23:00:18 +08:00
XiaojueGuan
952de11031 Update links in README
Change the outdated links to the latest links in README

Change-Id: I38ca6433f132d57d3fce5c14abfb5dd104af7e38
2018-06-12 16:25:02 +08:00
Zuul
fd44a5a96a Merge "(Operator-only) Extend logging framework for FWaaS v2" 2018-05-30 17:43:18 +00:00
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
2018-05-30 10:28:57 +02:00
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
2018-05-28 15:23:01 +07:00
Zuul
537788b261 Merge "Trivial:Update pypi url to new url" 2018-05-24 00:03:53 +00:00
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
2018-05-23 11:19:16 +08:00
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
    I3860a62420ab4983e2b741dff04498fbb0432d00

Change-Id: I4ebb090de53370708e871c75c789b62bc5e71010
2018-05-17 10:22:08 +02:00
Zuul
cf38b6af27 Merge "Neutron-Neutron Interconnections" 2018-05-16 20:42:06 +00:00
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
2018-05-15 21:09:50 +00:00
Thomas Morin
2a34abbd25 Neutron-Neutron Interconnections
Proposed specifications for the Neutron-Neutron Interconnections
RFE.

Change-Id: I3860a62420ab4983e2b741dff04498fbb0432d00
Related-Bug: 1750368
2018-05-07 10:39:13 +02:00
Zuul
ac7d3cffcc Merge "Spec for VPN service support Qos" 2018-04-27 22:45:02 +00:00
Zuul
9b7cd99a76 Merge "decouple neutron db models and ovo for neutron-lib" 2018-04-16 03:24:21 +00:00
Zuul
d4aa5a56b8 Merge "rehome db api and utils into neutron-lib" 2018-04-16 03:24:20 +00:00
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
2018-04-11 15:24:45 +09:00
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
2018-03-27 16:31:34 +08:00
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
2018-03-19 06:31:20 -06:00
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
2018-03-15 13:26:04 -06:00