openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I739ec6a4984df396b11b29f2d55f0d24fecab6eb
The register_model_query_hook and _apply_dict_extend_functions methods
from CommonDbMixin is not being used by consumers today. This patch
removes them and updates any doc references as well.
NeutronLibImpact
Change-Id: I3e72d7f33f5a7b0c9c023295302929410f94eefb
There was missing step about adding underlying interface to the
provider bridge in ovs deployment guides.
This patch adds this missing step.
Change-Id: I2ef5f12c469647d7f197cb5db71692e68d23f718
Closes-Bug: #1801361
Now supported_vnic_types is hardcoded to the mechanism drivers, but that
can depend on several factors, like type of the NIC, admin decision,
etc.
With this patch we put the right to decide which vnic types are
supported for ovs agent into the hands of the admin, by allowing
blacklisting items from the mechanism driver specific list.
Background: http://eavesdrop.openstack.org/meetings/neutron_qos/2018/
neutron_qos.2018-07-31-15.00.log.html#l-58
Change-Id: Iad9e2e966df53b4164d2a56a93215c69825b5241
Partial-Bug: #1578989
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
The functionality allowing to disable DNS server announcement from the
DHCP agent for certain subnets was introduced in [0]. We should mention
this feature in the corresponding documentation.
[0] https://review.openstack.org/495781
Change-Id: I4adfa7ba789a59f967297ebb6c571deb0652c7ca
Related-Bug: 1311040
This adds basic framework for neutron-status upgrade check commands.
For now it has only "check_nothing" check implemented.
Real checks can be added to this tool in the future.
Depends-On: https://review.openstack.org/#/c/610061/
Change-Id: Ib08119e1bb8de80856edb6a39769d4bc9d98c587
Story: 2003657
Task: 26144
This change is adding required configuration in neutron.conf
to set the lock_path parameter, which was missing in
compute-install-ubuntu.rst
Change-Id: If090bdf060dfe21d11b1a5dfd010dc8167d9e45e
Closes-Bug: #1796976
The enable_distributed_routing option in the OVS-HA-DVR doc
is shown in the [DEFAULT] section in the openvswitch_agent.ini
file, but it is actually in the [agent] section.
Change-Id: Ic81a6da71f1935e863ec698c98441b64b41bbfa3
Now supported_vnic_types is hardcoded to the mechanism drivers, but that
can depend on several factors, like type of the NIC, admin decision,
etc.
With this patch we put the right to decide which vnic types are
supported for ovs agent into the hands of the admin, by allowing
blacklisting items from the mechanism driver specific list.
Background: http://eavesdrop.openstack.org/meetings/neutron_qos/2018/
neutron_qos.2018-07-31-15.00.log.html#l-58
Change-Id: I63e562e2eccc5b02c1c767d6a2c28cb803131e99
Partial-Bug: #1578989
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
We need to accent that only different types rules can be combined
in QoS policy Edit.
Change-Id: Ib40124127aea5d374548fb9161674975b6b906e8
Closes-Bug: 1779052
Changed QoS backend/rule support table in devref documentation to show
that Minimum Bandwidth rule can support both Egress and Ingress
directions in case of placement based enforcement.
Added a new table to show which directions are supported for Minimum
Bandwidth rule by the network backends, and how that depends on the
enforcement type (dataplane or placement).
Change-Id: I97ab4815d134d306917a84a7b308b734d6db2dd2
Depends-On: https://review.openstack.org/580387
Partial-Bug: #1578989
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
As agreed during the Stein PTG, this patch proposes an update to the
code review policies, aimed at minimizing the impact of code changes in
Neutron on the Stadium and other networking related projects.
Change-Id: I455a62daa9115962cd6347d1f3966dae533e4abb
* explain 'ingress' and 'egress'
* reword a few explanations
* provide table numbers as well as table names
* capitalize protocol names: IP, ARP, TPC, etc.
* reword explanations for tables acting as integration
points with L2 other extensions
* nits
This change also includes a newline removal in the related portion
of the code; this newline separates constants that are in fact related,
and its removal had been agreed upon to be handle as a follow-up
change to I60d299275effd9ef35c8007773d3c9fcabfa50fa.
Change-Id: Ied215b8942bfffa1f2af2f569d0e4a110a64a364
This patch updates QoS docs to remove "port show" command
before associating Floating IP to port.
It is like that to be clear that QoS policy which is attached to
the FloatingIP is NOT visible in the port's attributes.
Change-Id: I127fbd25433e39905c3b83bbe914f027ab45ef3f
Closes-Bug: #1778740
This patch combines two separate notes about burst value in
QoS bandwidth limit rules into one to make it more clear for
readers.
Change-Id: I48fa93969416db0b0049af533b6aa4021fa22616
Related-Bug: #1777866
This change is a follow-up to Ib6ced838a7ec6d5c459a8475318556001c31bdf,
reintroducing a single place for applying the NORMAL action to
egress traffic, which is necessary to fix a regression introduced
by Ib6ced838a7ec6d5c459a8475318556001c31bdf.
Change-Id: I60d299275effd9ef35c8007773d3c9fcabfa50fa
Partial-Bug: 1789878
- Add steps to ensure physnets VLAN ranges are configured, if necessary
- Add steps to ensure a network using the given physnet is configured
- Update nova scheduler options, which have been moved since Ocata
(nova 15.0.0) [1]
- Update nova PCI options, which have been moved since Ocata (nova
15.0.0) [2]
- Simply some commands
- Some typo/grammar fixes
[1] https://github.com/openstack/nova/commit/7d0381c91a6
[2] https://github.com/openstack/nova/commit/4e5ed1c4891
Change-Id: I45fdc8e40121698bf144d0e0a65537edda2c805d
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Closes-Bug: #1788900
Removes the RamFilter from the documentation as its
deprecated as of [1] and not needed when using the default
scheduler driver.
[1] https://review.openstack.org/#/c/596502/
Change-Id: I49442352d0fec2c9ff920ac1bb21fc2e5339a41e
It seems the RFC should be 1918 which defines IP addresses for private
networks.
The existing RFC 5737 actually defines private IP ranges for use in
documentation.
Change-Id: Ic794585e636bb9a9c915347a801c8a4f0baa9012
Closes-Bug: 1788936
The last two items are already done.
- fullstack tests implemented in commit ff9c6e21
- updates using bundle operation implemented in commit b3b2df14
Change-Id: I2d81fde185cee04681acb9e5f156195a035cce5c
Nova does not currently support attaching SR-IOV ports to
existing instances, you can only create a server with an
SR-IOV port at this time. This adds an item about that
limitation to the SR-IOV admin docs.
Change-Id: I0a954de724384a81cb45446da20fa6b17d4bd63a
Related-Bug: #1708433
SR-IOV has added support for enforcing egress minimum bandwidth [1]
and this commit updates the devref about that.
[1] https://review.openstack.org/#/c/347302/
Change-Id: I0e637b893e60d7fdfb1ab4cece15aad74f43d3b5
Related-Bug: #1578989
ZhongShengping