Hi Jakub, It does seem OpenFlow does not allow sending traffic back to a
previous table:
https://3vf60mmveq1g8vzn48q2o71a-wpengine.netdna-ssl.com/wp-content/uploads/2014/10/openflow-switch-v1.5.1.pdf
Page 20, middle of the 3rd paragraph.
** Changed in: neutron
Status: New => Invalid
--
Y
Public bug reported:
When moving traffic between the OpenFlow tables it can be necessary to move
traffic back to an earlier table to be reprocessed.
This action is supported when using the ofctl implementation however when the
of_interface is set to native the follow error is thrown:
RuntimeErro
Public bug reported:
The use of linux network namespaces in the l3 agent routers causes a choke
point for bandwidth on east/west and north/south traffic.
In the case of east/west traffic, the source and destination interfaces are
known to Neutron and could be routed using Open vSwitch if it is s
Public bug reported:
"The oslo.versionedobjects library can be used to define a data model
within a project independent of external APIs or database schema for the
purposes of providing upgrade compatibility across distributed
services."
However in Neutron QoS this library is used to micro versio
Public bug reported:
http://logs.openstack.org/56/425756/18/check/gate-neutron-dsvm-
fullstack-ubuntu-xenial/49cf5a9/console.html#_2017-03-01_14_32_34_632471
DeprecationWarning: Raising eventlet.TimeoutError by default has been
deprecated in version 'Ocata' and will be removed in version 'Pike':
Public bug reported:
I'm submitting this bug as it was advised in the traceback to do so and
it does not appear to have been filed yet.
2016-07-27 21:28:48.049962 | ==
2016-07-27 21:28:48.050005 | Failed 1 tests - output below:
tempest.api.compute.test_live_block_mig
Public bug reported:
I'm submitting this bug as it was advised in the traceback to do so and
it does not appear to have been filed yet.
2016-07-27 21:28:48.049962 | ==
2016-07-27 21:28:48.050005 | Failed 1 tests - output below:
tempest.api.compute.test_live_block_mig
It's in another project, I already have a bug filed for that project to mock
the call.
I just thought this seemed odd and filed this here too.
Sorry about this.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
E
Assignee: David Shaughnessy (david-shaughnessy)
Status: New
** Changed in: neutron
Assignee: (unassigned) => David Shaughnessy (david-shaughnessy)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
Public bug reported:
The l2-extensions-api that merged in Mitaka allows extensions of the
OvSNeutronAgent to use the OvS flow table.
This introduces a new challenge of interoperability between extensions creating
flows.
As the OvS flow table matches traffic to flows based on packet characteristi
Public bug reported:
This rule will create flows that will direct traffic from the assigned
port based on dscp and/or 802.1p traffic into queues with configurable
bandwidth limits.
Priority queuing can be used to manage limited resources such as
bandwidth on a transmission line from a network rou
Public bug reported:
Summary:
When calling ovsdb.db_create() it will always cause an exception.
Further info:
This is due to it's arguments being concatenated by a function that adds
'col_values:' to the start of the field=value.
This causes it to throw an exception as there is no field called 'c
Public bug reported:
The current QoS API is structured so that rules that are added to the API need
to be added to the neutron client as well.
I propose the use of proxy functions in neutron that determine which functions
to use based on the rule type retrieved using the rule_id or specified thr
13 matches
Mail list logo
