These features are not yet designed in OpenStack API, for Liberty (the next release) its going to be only bandwidth limit, but they certainly will be added to the next release as there is a high demand for them. I can start trying to propose them, but i think at this point its a waste of time if they aren't supported by the CMS.
However, as you can see i did this as generic as i could, this schema doesnt have to change any more when we will support all the other rule types, it will just be QoS_Rule entry with a different 'type' field and a different set of 'other_config' dictionary. The aggregator of these various rules is the QoS_Profile, which is what attached to the Logical Port. If i understand your concern right, you worry that the NB schema is getting too big. I can't think of a better way to do this both use full and smaller, if you feel that we don't want to support QoS at this point, thats fine. but this is another limit for API which will be supported by OpenStack reference implementation and not by OVN, and if we aim for high adoption of OVN, we need to make sure this gap is as small as possible (at least thats how i see it) Gal. On Thu, Jul 16, 2015 at 8:22 PM, Ben Pfaff <b...@nicira.com> wrote: > Could you extend the proposal to include those features then? At the > moment it is a skeleton. > > On Thu, Jul 16, 2015 at 02:11:12AM +0300, Gal Sagie wrote: > > Yes, there are currently plans for marking (DSCP) and flow classification > > profiles. > > And other ideas like connections limiting. > > > > On Wed, Jul 15, 2015 at 8:38 PM, Ben Pfaff <b...@nicira.com> wrote: > > > > > On Sun, Jul 12, 2015 at 09:21:41AM +0300, Gal Sagie wrote: > > > > Add QoS profile and QoS rule tables and explanations > > > > to the NB schema. > > > > Add specific bandwidth limit rule configurations > > > > in the document > > > > > > > > Signed-off-by: Gal Sagie <gal.sa...@huawei.com> > > > > > > This is a lot of schema to support just a little bit of functionality! > > > I guess that must be because you foresee support for much more > > > sophisticated QoS profiles in the future. Can you tell us a little > > > about those? Otherwise it would make more sense to me to do this in a > > > simpler way. > > > > > > > > > > > -- > > Best Regards , > > > > The G. > -- Best Regards , The G. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
