2016-11-04 12:13:42 |
Dr. Jens Harbott |
bug |
|
|
added bug |
2017-01-17 15:49:48 |
Rodolfo Alonso |
neutron: assignee |
|
Rodolfo Alonso (rodolfo-alonso-hernandez) |
|
2017-01-31 15:59:17 |
Rodolfo Alonso |
tags |
|
qos |
|
2017-01-31 15:59:26 |
Rodolfo Alonso |
tags |
qos |
qos rfe |
|
2017-01-31 16:00:08 |
Miguel Angel Ajo |
neutron: importance |
Undecided |
Low |
|
2017-02-01 12:15:54 |
Rodolfo Alonso |
summary |
[RFE] Default action for RBAC |
[RFE] Network QoS policy "default" behaviour |
|
2017-02-01 12:16:16 |
Rodolfo Alonso |
summary |
[RFE] Network QoS policy "default" behaviour |
[RFE] Introduce Network QoS policy "is_default" behaviour |
|
2017-02-01 12:28:07 |
Rodolfo Alonso |
description |
Introduce a new type of action in RBAC for use with QoS (and potentially useful for other stuff),
The action would be default:
neutron rbac-create <qos-policy-id> --type qos-policy --target-tenant <tenant-uuid> --action default
That would mean:
Any created network for that tenant would be assigned to the specific policy id by default.
Maybe "network_default" is a more appropriate name in such case. One important use case would be an operator that wants to rate-limit tenant ports by default.
This has been proposed in https://bugs.launchpad.net/bugs/1512587 , but it was decided that this should be implemented as a separate feature after the basic work is done. |
Introduce a new parameter in Network QoS policy: "is_default".
If a new Network QoS policy is created/set with the parameter "is_default" equal to True, any new network created for that project will have this default QoS policy assigned.
E.g.:
- Create a new QoS policy
openstack network qos policy create --is-default qos_1
- Create a new network
openstack network create net_1
This new network, "net_1", will have "qos_1" as QoS policy.
The parameter "is-default" can be set in the creation and the update commands.
If a new Network QoS policy is created or updated with this flag and another Network QoS policy in the same project is set as the default policy, the new one will prevail, removing the flag from the old one. |
|
2017-02-01 14:31:48 |
Rodolfo Alonso |
bug task added |
|
python-openstacksdk |
|
2017-02-01 14:32:16 |
Rodolfo Alonso |
bug task added |
|
python-openstackclient |
|
2017-02-01 14:32:23 |
Rodolfo Alonso |
python-openstackclient: assignee |
|
Rodolfo Alonso (rodolfo-alonso-hernandez) |
|
2017-02-01 14:32:27 |
Rodolfo Alonso |
python-openstacksdk: assignee |
|
Rodolfo Alonso (rodolfo-alonso-hernandez) |
|
2017-02-01 14:39:01 |
Rodolfo Alonso |
description |
Introduce a new parameter in Network QoS policy: "is_default".
If a new Network QoS policy is created/set with the parameter "is_default" equal to True, any new network created for that project will have this default QoS policy assigned.
E.g.:
- Create a new QoS policy
openstack network qos policy create --is-default qos_1
- Create a new network
openstack network create net_1
This new network, "net_1", will have "qos_1" as QoS policy.
The parameter "is-default" can be set in the creation and the update commands.
If a new Network QoS policy is created or updated with this flag and another Network QoS policy in the same project is set as the default policy, the new one will prevail, removing the flag from the old one. |
Introduce a new parameter in Network QoS policy: "is_default".
If a new Network QoS policy is created/set with the parameter "is_default" equal to True, any new network created for that project will have this default QoS policy assigned.
E.g.:
- Create a new QoS policy
openstack network qos policy create --is-default qos_1
- Create a new network
openstack network create net_1
This new network, "net_1", will have "qos_1" as QoS policy.
The parameter "is-default" can be set in the creation and the update commands.
If a new Network QoS policy is created or updated with this flag and another Network QoS policy in the same project is set as the default policy, the new one won't be created or updated (see subnet-pool behaviour). |
|
2017-02-07 16:58:28 |
OpenStack Infra |
python-openstacksdk: status |
New |
In Progress |
|
2017-02-07 17:10:47 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
2017-02-10 11:25:31 |
OpenStack Infra |
python-openstackclient: status |
New |
In Progress |
|
2017-02-14 16:25:34 |
Anindita Das |
bug |
|
|
added subscriber Anindita Das |
2017-03-26 21:09:13 |
OpenStack Infra |
neutron: assignee |
Rodolfo Alonso (rodolfo-alonso-hernandez) |
Slawek Kaplonski (slaweq) |
|
2017-03-26 22:12:56 |
OpenStack Infra |
neutron: assignee |
Slawek Kaplonski (slaweq) |
Rodolfo Alonso (rodolfo-alonso-hernandez) |
|
2017-05-26 23:31:50 |
OpenStack Infra |
neutron: assignee |
Rodolfo Alonso (rodolfo-alonso-hernandez) |
Kevin Benton (kevinbenton) |
|
2017-05-29 16:45:06 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
2017-05-30 06:58:58 |
OpenStack Infra |
python-openstacksdk: status |
In Progress |
Fix Released |
|
2017-07-05 20:58:03 |
OpenStack Infra |
python-openstackclient: status |
In Progress |
Fix Released |
|