Burst value for TCP traffic should be set as 80% of desired bandwidth
limit value. For example, if the bandwidth limit is set to 1000kbps
then enough burst value will be 800kbit. If the configured burst value
is too low, achieved bandwidth limit will be lower than expected.
If the configured burst value is too high, too few packets could
be limited and achieved bandwidth limit would be higher than expected.
So we should recommend a correct example in case that user ignores
the note.
Change-Id: Iefea3ce699c39e217e89dec93a8fe8ea1a90ac82
Qos policy with bandwidth limit rules can be applied on router's
gateway ports to limit only if veth are used to connect it to
namespaces.
This commit updates "ovs_use_veth" config option help message and
qos docs to add such info there.
Change-Id: I69e78bc125d430c933f7576d05308030789cee0a
Related-Bug: #1732852
OpenStack client doesn't display "Created" after
create operation.
Also this patch corrects an erroneous ingress rule update command by
changing "--max-burst-kbps" to "--max-burst-kbits".
Finally, the output of several commands is corrected.
Change-Id: I93aac4a5f293919b3fd8acf1c0310f6864004ee0
Closes-Bug: #1730896
This patch adds a note to clarify the need for nova to be installed
prior to configuring the compute service for neutron.
Change-Id: If7f16c1bd01843c244b87a48a024d17e57cb775e
Closes-Bug: #1732669
The OpenFlow spec says packets shouldn't match against multiple flows
at the same priority or the result is undefined. In ovsfw, 8 priority
levels are needed to comply with this rule.
Note: unlike overlapping TCP port ranges cases, the current version
of OVS seems to handle this case magically.
Change-Id: I6deaee8dbe81453285b1fc685282952bc9456949
Closes-bug: #1708092
The ovsfw code generated multiple flows with the same or overlapping
match fields and different actions=conjunction(nnn,2/2) flows.
Merge such flows and generate only one flow with
actions=conjunction(mmm,2/2),conjunction(nnn,2/2) so that filtering
are correctly performed.
Change-Id: I0cd325b02f35e103606595b8b124010fff8dc397
Partial-bug: #1708092
As discussed at Denver PTG, DocImpact tag will be retired.
Feature patch must now include relevant documentation changes.
Change-Id: I6aa3753772321733920481ac57549a648f92c6de
In this section there were only links to 3 stale branches.
Now it describes how link to Launchpad's page with
links to current stable branches can be build.
Change-Id: I721dfbb7e907eb1f4bac0fdb4f6fe35dc447dee1
On docs bugs policies page link to page which
describes OpenStack stable branch policy is updated to
correct page.
Change-Id: I4eb4a53c52155da4abcf724885339df2afecdfaf
In order to support LIKE statement filter in OVO objects,
StringMatchingFilterObj class is introduced. However, this class
does not provide initial attributes of "starts", "contains" and
"ends".
In real usage, if these attributes are not initialized, we will
hit failures in method apply_filters() in db/_model_query.py.
This patch adds the initialization back.
Secondly, a typo of "obj_utils.StringMatchingContains" is revised
in this patch too.
Change-Id: If828068d8d08ff09dff6c63d53320bc397d32448
Closes-Bug: #1724446
Since 1b8664f8e1213a1703304c9e4259f544d0b223e6 moves qos
constants to neutron-lib, here we updates the link.
Also this patch adds short description for
supported QoS rule types.
Change-Id: Id6ebadc1dc9f6a4ea390f8c47dcdf72992494526
The example of "detach a port from the QoS policy" is
wrong in config qos doc.
OpenStack client don't display info about "Updated" after
set or unset operation. Egg, associate the created policy
with an existing neutron port, or detach a port from the
QoS policy. It is the same as network.
Also, OpenStack client don't display info about "Updated
or Deleted" when we modify or delete rules from Qos policy.
Change-Id: Idbc1877e85a13faca150307b3e773c1ea5333b77
Closes-Bug: #1727132
As [1] shows, the controller node hosts the Neutron server but
also agents like L3 and DHCP which require also OVS or LinuxBridge
agent to be running on it.
To enable QoS is required to enable the 'service_plugins' and
the 'extension_drivers', along with the agent section in the plugin
config if the agent is running on this host.
In the network node and the compute node only the agent
'extensions' configuration is needed to enable QoS
on the agent.
[1] https://docs.openstack.org/security-guide/networking/architecture.html
Closes-Bug: #1720077
Change-Id: I14128aabe0a9209c31a1bd4c76eed1182364ccdf
Co-Authored-By: Slawek Kaplonski <slawek@kaplonski.pl>
Tweak the wording so that it's a bit more clear on how to
handle rfe-approved RFEs and why certain RFEs are marked
as 'rfe-postponed'.
Change-Id: Iad66a1322918338ab51035de8fdb6b6ca23ddd8c
This patch clarifies the routed network configuration doc with respect
to when a fixed IP is assigned to a port on a routed network. For
more details see related bug.
Change-Id: Id8e97afdfc488069ac3a910e017c34b085b4eb36
Closes-Bug: #1718320
This patch clarifies the agent file to update when configuring QoS as
the actual file name will depend which agent is being used.
Change-Id: Ie53e30c329e4b0bcaadc0b437ed783c7e0c00dbb
Closes-Bug: #1628533
With Kevin Benton leaving we need to update ownership for
all the areas he covered. Also removed some people that
have left neutron recently.
Change-Id: Ie3fb6a15996bd91e9b0c8c4573afffd58582de08
