neutron CLI is deprecated and will be removed in the future. Use
openstack CLI instead.
Change-Id: I00fa6ee2e2ac19627a172ff49a55fe664e4f5c43
Closes-Bug: 1749801
There is no place in the documentation that explicitly lists the valid
DSCP marks, except for an incomplete hint in the DSCP spec in
neutron-specs. This provides an explicit list.
Change-Id: Ic350c88e59c33d98b54086707c9add05cf137dc2
Closes-Bug: #1781915
It is not necessary to use 2 "central" bridges, one for "data" and
one for "external" network simulation.
Also using 2 bridge will cause problems when "external_network_bridge"
option will be removed from L3 agent and it will use integration bridge
as it should be done.
Change-Id: I68ee51cbc148b2bfce0cba8de7cf9fe08df54c96
Incorrectly named variable in the doc conf file causing errors.
Now that jobs are running under python 3, error with dict_key
sort() no longer being supported.
Change-Id: If93b61a84e6106de7f530e4fa1084a473b413629
It was decided that we should release stable branches more
frequently than we are, document for future neutronians.
Fixed other typos as noticed.
Change-Id: I4fb0ca5f41a97ae99995c485f7296b7d81c4b78e
The neutron.object.utils module was rehomed into neutron-lib with
https://review.openstack.org/#/c/557809/
This patch consumes it by removing the neutron.objects.utils module
and corresponding test module, updating the contributor internals for
objects and using lib's version of the module.
NeutronLibImpact
Change-Id: If53d0ad660851275462d2641ed1829cdb4c32d05
It allows Virtual Functions to become “trusted” by the Physical
Function and perform some privileged operations, such as enabling VF
promiscuous mode and changing VF MAC address within the guest. The
inability to modify MAC addresses in the guest prevents the users from
being able to easily set up two VFs in a fail-over bond in a
guest. This spec aims to suggest a way for users to boot instances
with trusted VFs.
https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/sriov-trusted-vfs.html
Change-Id: I58cbfd9698a6c7832abc52e0be70eab72f66e11a
Depends-On: https://review.openstack.org/#/c/458820/
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@redhat.com>
The agent extensions code is migrating to neutron-lib. This change
reflects that migration in neutron.
NeutronLibImpact
- Consumers using the agents extension should now use
the Agent extension API from neutron-lib instead of neutron.
Co-authored-by: Reedip<reedip.banerjee@gmail.com>
Change-Id: Ie8f0e70b11435d627f73e3fed45f946e863e90bc
Depends-On: I7255a5ae6b706c09acecc0dea5dbd2febae0c282
The build-openstack-sphinx-docs is currently failing with the error
"ImportError: No module named oslotest" based on an import in
neutron/tests/functional/db/test_migrations.py. Add oslotest to
the doc requirements.
Change-Id: Ibb2b8b246ad685e2e7e2bb8d3ac1d4c7c3a981b7
Current URL of network configuration guide for Red Hat Enterprise Linux
and CentOS is incorrect
Change-Id: I9098801c6e87a58ac907784c4c1f68651c5c6ae1
Closes-Bug: 1737313
To enable the possibility to migrate a non-routed network to a
routed network allow updating the segment_id of a subnet.
Only allow the operation if:
- The network only has one segment
- The network only has one subnet
- The current segment_id == None
APIImpact: The segment_id attribute of subnets now allows put operation.
Closes-Bug: #1692490
Depends-On: Iffda823a149a1143f46ee9a05e9640b34bf42c51
Change-Id: I1aee29dfb59e9769ec0f1cb1f5d2933bc5dc0dc5
Beginning with the Queens release, the keystone install guide
recommends running all interfaces on the same port. This patch
updates the install guide to reflect that change.
Change-Id: I8bf64e2c47b55512f3ce42da3849911603cbcde0
None of these should be executable, from what I can tell.
Side note: never backup a git repo to an NTFS drive or you lose all your
permissions and need hacks to restore them.
Change-Id: I34de5488129c575a66b38b400c31393fb511765f
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This change updates the auth_url value to match what has changed
in the keystone install guide:
https://review.openstack.org/#/c/541857/
Change-Id: I97356b31af35ef19d02b9f0c0a57cbde16752c65
Per my understanding, only flat or VLAN networks make sense for physical
networks, a.k.a. physnets. However, the docs specifically mentioned only
GRE and local networks as being incompatible. Add VXLAN to this list to
complete it.
Change-Id: I7915f129bfc8436b410455507ead641a64a51bc7
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This patch adds additional information on how to do advanced
debugging of failing gate jobs directly on test nodes.
Change-Id: I97c93ecfa77b13e5ebcff906219ab8002e266b13
While we added new_facade object attribute to framework and it has its
niche and used in some stadium subprojects, it's not ideal because it's
global to an object. Meaning that if you mark an object for new_facade =
True, *all* business logic using the object must also switch to new
facade in the same step, which is a pain and sometimes close to
impossible to do without changing thousands loosely related lines of
code in multiple modules. It would be nice to instead use objects as
usual in different contexts - some using engine facade and some still
using session.begin(...) - and allow the OVO framework to pick the right
way to nest subtransactions.
This patch does exactly that. We call an internal function from oslo.db
and check whether it raises an exception. If it does, it means that the
engine facade is not used; otherwise, we use the new style of nested
transactions management.
By default, if session is not active when OVO action is called, we stick
to the old facade. Once we are done with switching the rest of the
plugin code / OVO objects to the new facade, we will rip off the
transitionary logic.
Change-Id: Ia05df925eccf3c9d397748f282e995203a058de9
Partially-Implements: blueprint enginefacade-switch
Partially-Implements: blueprint adopt-oslo-versioned-objects-for-db
