Bug 1042418 - [RFE][neutron]: Quantum QoS API extension and DB models
Summary: [RFE][neutron]: Quantum QoS API extension and DB models
Keywords:
Status: CLOSED DUPLICATE of bug 1042406
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL: https://blueprints.launchpad.net/neut...
Whiteboard: upstream_milestone_next upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 22:12 UTC by RHOS Integration
Modified: 2016-04-27 01:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 10:31:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 22:12:50 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api-db.

Description:

This blueprint will cover the QoS API and database models.

The "policy" column will store a JSON object that specifies the
action to be taken - it's sort of a hack - better suggestions appreciated - but the idea is that the action column could contain all the different types of QoS mechanisms that vendors use.

Possible examples for the policy column in the qos table:

{"action": {"mark": "af32"}}

{"action": {"ratelimit": "100kbps"}}

The model has many similarities with the NVP QoS DB models, so the goal will be to refactor the NVP QoS to use these models, and place the NVP QoS specific attributes inside the JSON object.

Specification URL (additional information):

https://docs.google.com/document/d/1nGUqEb4CEdabbTDyeL2ECVicnBRNrK3amJcNi-D4Ffo/edit

Comment 2 Stephen Gordon 2014-02-06 14:08:36 UTC
Updating based on BP milestone

Comment 3 Nir Yechiel 2014-03-04 10:40:46 UTC
Updating based on upsream status

Comment 4 lpeer 2015-03-19 10:31:28 UTC

*** This bug has been marked as a duplicate of bug 1042406 ***


Note You need to log in before you can comment on or make changes to this bug.