The change Ib30f681ccd9177c45d2c17d28b4a46ac5462df7c tried to remove this
file, but it only removed the content of this file.
Change-Id: I82769091947d3c593509f1d2012cd6f0bc371da5
As Paul has stepped away from VPNaaS, putting my and
John's names in as contacts so bugs have someplace to go.
Change-Id: I1ee749367e22996e7a24a06310f8559aace8a709
Signed-off-by: Ryan Moats <rmoats@us.ibm.com>
This patch set attempts to clarify how a third party vendor
can make use of the existing QoS functionality using the
notification_driver interface.
Change-Id: Ib1559c27c9405d6ec15c65ea377b162433304ff2
IPv6 issues can cover many areas from the API down to agents and
wiring. Add a couple of people to the tag to cover more things.
Change-Id: I1b9f3669f92f4590d1bf21a6d90c3b323b725c3f
Below devref documents are updated for the newly created repository.
* bugs.rst
* neutron-teams.rst
* sub_projects.rst
Change-Id: Ia210109be80a4856a7ee9138e42d05ff6bf95f8a
it would be more appropriate to update networking-fortinet
in affiliated projects list due to stadium evolution.
Change-Id: Ifd6913ca87bf994e446af3e05cc47598bacffd27
I clicked on this link while reading the plugin development section in
the effective neutron guide. I wasn't sure it linked me to the right
thing because it currently links to a blank line. I figured that it
was just a line off but I wasn't sure because the link is to the
master branch, which can change.
This patch changes master to the short commit id of the commit that
added this link in the first place. This way, it'll always link to
what it originally linked to. If contents move around on master by
adding code to the file or refactoring or whatever, it might still
cause some confusion but at least we'll know what it was originally
intended to point to without doubt.
Change-Id: I13a10e10a31b88cb6f030ca644ca20e0bf14012c
Make use of the Tempest plugin interface instead of copying Neutron
files into Tempest. This will remove the burden to port Neutron
tests onto Tempest master recurrently.
It uses neutron/tests/tempest/ as new top folder for all Tempest
tests. It follows the model of Heat [1].
[1]: https://github.com/openstack/heat/tree/master/heat_integrationtests
Partially implements bp external-plugin-interface
Change-Id: Ia233aa162746845f6ae08a8157dcd242dcd58eab
The document is hopefully a good start and will eventually collect
enough information and tips for next release managers to run the
nervous process more smoothly.
Change-Id: Iaa14d818ae13e7cfa5ad061a2ae9d87a1f0fd331
When building packages if git is absent, then we should not set
html_last_updated_fmt. It can still be set via the -D switch
when building with sphinx-build.
Change-Id: I6e6c59b101760224008fd902c8c258d6120a615d
Closes-Bug: #1552251
Instrumentation work from regxboi has stalled. For what we know this
feature may never materialize, and if it does it may end up looking
drastically different.
This reverts commit 1f329c5d012fa5d17dea5c48121c2820d70c9bb7.
Change-Id: I872c6b981d123e7f291ac950b08c3fe5ed95769c
- port masking was already implemented in 9af8f56d
- create new part about usage conntrack zones
- unused literal block removed
Change-Id: Ib458be677d5a0cbcd9fa775ef5b7cce48b3b08ec
Open vSwitch takes care of vlan tagging in case normal switching is
used. When ingress traffic packets are accepted, the
actions=output:<port_number> is used but we need to explicitly take care
of stripping out the vlan tags.
Closes-Bug: 1564947
Change-Id: If3fc44c9fd1ac0f7bc9dfe9dc48e76352e981f8e
No longer need to enable extension in service_plugins.
The feature is automatically enabled after patch [1].
[1]: https://review.openstack.org/#/c/283357/
Change-Id: Ia9a36c40e33a25335a83b96adff2d675164b5d21
During the past cycle we assumed that only RFEs with
specs were going to get a blueprint page, and hence
an approver/assignee couple. To avoid confusion and
ensure that even spec-less RFEs get enough attention
this process change proposes to treat RFEs the same
way irrespective of its design needs.
Change-Id: Idd1440267dccf84be884adbafe75461c686a8dd0
This patch makes sure that existing connection breaks once security
group rule that allowed such connection is removed. Due to correctly
track connections on the same hypervisor, zones were changed from
per-port to per-network (based on port's vlan tag). This information is
now stored in register 6. Also there was added a test for RELATED
connections to avoid marking such connection as invalid by REPLY rules.
Closes-Bug: 1549370
Change-Id: Ibb5942a980ddd8f2dd7ac328e9559a80c05789bb
Until fix [1] lands, people should learn to install
a git hook or do tox -edocs before posting a review
[1] https://review.openstack.org/#/c/229951/
Change-Id: I37e50c2d018b6ac67f2792c29eab0081afa16d75
This patch adds the front end and back end implementation of QoS DSCP.
Associated patches that are dependent on this one:
* python-neutronclient: https://review.openstack.org/#/c/254280
* openstack-manuals: https://review.openstack.org/#/c/273638
* API Guide: https://review.openstack.org/#/c/275253
* Heat:
* Spec: https://review.openstack.org/#/c/272173
* QoSDscpMarkingRule resource: https://review.openstack.org/#/c/277567
* Fullstack tests: https://review.openstack.org/#/c/288392/
APIImpact - The API now supports marking traffic egressing from a VM's
dscp field with a valid dscp value.
Co-Authored-By: Nate Johnston <nate_johnston@cable.comcast.com>
Co-Authored-By: Victor Howard <victor.r.howard@gmail.com>
Co-Authored-By: Margaret Frances <margaret_frances@cable.comcast.com>
Co-Authored-By: James Reeves <james.reeves5546@gmail.com>
Co-Authored-By: John Schwarz <jschwarz@redhat.com>
Needed-By: I25ad60c1b9a66e568276a772b8c496987d9f8299
Needed-By: I881b8f5bc9024c20275bc56062de72a1c70c8321
Needed-By: I48ead4b459183db795337ab729830a1b3c0022da
Needed-By: Ib92b172dce48276b90ec75ee5880ddd69040d7c8
Needed-By: I4eb21495e84feea46880caf3360759263e1e8f95
Needed-By: I0ab6a1a0d1430c5791fea1d5b54106c6cc93b937
Partial-Bug: #1468353
Change-Id: Ic3baefe176df05f049a2e06529c58fd65fe6b419
This patch updates the current contents of the document
after the Mitaka development cycle, but misses entries
for new features.
Change-Id: I7b1c4e6dd8210eef46c21ba0937f8c3ca56cbb4b
Document separation of configuration options between services and agents.
Configurations used in devstack and deployment documentation should also be
updated since they are referenced as examples.
Partial-Bug: #1557119
Change-Id: Ia4b2a542cded6cc56c1b3eaa9e9b9e0abff31707
These functions assume that they won't be called inside of a
transaction for two reasons. The first is an infinite loop that
will only terminate if it can actually retrieve the latest
information from the database. The second is that ML2's post-commit
operations are expected to occur after data was actually committed
so mechanism drivers that do DB lookups using a different session
may break.
This adds an explicit guard that prevents these two functions from
being called within an active DB session. The rest of the ML2
functions should eventually be converted to this style as well
(see the partial bug).
Related-Bug: #1551958
Partial-Bug: #1540844
Change-Id: I5c00b186585369ef6c8e2b9cb5a43b8bba0e5a7c
This is unsafe when calling ML2 because ML2 assumes that its
functions will not be called inside of a transaction. This is
not only an issue for drivers that try to do DB lookups using
a different session in the post commit operation, but it's a
big issue for the delete methods.
The delete subnet and network methods in ML2 have 'while True'
loops that catch concurrency errors and retry the operation after
looking up info. If these are called inside a transaction, the
lookups will contain stale information and it can lead to the
while True loop never terminating!
Closes-Bug: #1551958
Change-Id: I33dc084ed15e5491fdda19da712a746ca87fbc8c