Fahmy Sherif Alaa Salaheldin
2017-07-18 14:18:25 UTC
In the Ryu documentation this is written
# set a queue to the switches
# POST /qos/queue/{switch-id}
#
# request body format:
# {"port_name":"<name of port>",
# "type": "<linux-htb or linux-other>",
# "max-rate": "<int>",
# "queues":[{"max_rate": "<int>", "min_rate": "<int>"},...]}
#
# Note: This operation override
# previous configurations.
# Note: Queue configurations are available for
# OpenvSwitch.
# Note: port_name is optional argument.
# If does not pass the port_name argument,
# all ports are target for configuration.
I was wondering if this meant that we cannot configure each port separately.
For instance if I want to have 2 queues x,y on port s1-eth1 and 2 queues a,b,c on port s1-eth2, is that possible? if yes then in the flow rule what should the "actions" be (since we can only give "queue" and queue_id)!
# set a queue to the switches
# POST /qos/queue/{switch-id}
#
# request body format:
# {"port_name":"<name of port>",
# "type": "<linux-htb or linux-other>",
# "max-rate": "<int>",
# "queues":[{"max_rate": "<int>", "min_rate": "<int>"},...]}
#
# Note: This operation override
# previous configurations.
# Note: Queue configurations are available for
# OpenvSwitch.
# Note: port_name is optional argument.
# If does not pass the port_name argument,
# all ports are target for configuration.
I was wondering if this meant that we cannot configure each port separately.
For instance if I want to have 2 queues x,y on port s1-eth1 and 2 queues a,b,c on port s1-eth2, is that possible? if yes then in the flow rule what should the "actions" be (since we can only give "queue" and queue_id)!