Reviewed: https://review.openstack.org/430363 Committed: https://git.openstack.org/cgit/openstack/python-openstacksdk/commit/?id=7d851893951a8c0932d9e5efc179b39ee6e1b8c5 Submitter: Jenkins Branch: master
commit 7d851893951a8c0932d9e5efc179b39ee6e1b8c5 Author: Rodolfo Alonso Hernandez <[email protected]> Date: Fri Feb 3 16:51:10 2017 +0000 Add new parameter "is_default" to Network QoS policy. Closes-Bug: #1639220 Depends-On: If5ff2b00fa828f93aa089e275ddbd1ff542b79d4 Change-Id: Ibe7b7881cb190bfd5582f35b6de51a8bc21135de ** Changed in: python-openstacksdk Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1639220 Title: [RFE] Introduce Network QoS policy "is_default" behaviour Status in neutron: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: Fix Released Bug 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 won't be created or updated (see subnet-pool behaviour). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1639220/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
