[openstack-dev] [neutron] [QoS] QoS weekly meeting

Miguel Angel Ajo Pelayo majopela at redhat.com
Tue Apr 7 14:35:01 UTC 2015

Hi Raghunath, 

feel free to look at:
https://wiki.openstack.org/wiki/Meetings <https://wiki.openstack.org/wiki/Meetings>

and suggest other timeslots with a free meeting room,
this is a very wide community, and it’s impossible to get
a timeslot in everybody working hours.

Please note that option b is out of my working hours already,
but I picked it up there because it’s right after another meeting I have
and it’s easier to organize at home with kids/wife/etc…

Best regards,
Miguel Ángel.

> On 7/4/2015, at 13:14, Raghunath D <raghunath.d at tcs.com> wrote:
> Hi  Miguel,
> I am interested to join this meeting.
> I assume that CC of this mail are from different time zones.Please provide
> time slot with common time zone.
> With Best Regards
> Raghunath Dudyala
> Tata Consultancy Services Limited
> Mailto: raghunath.d at tcs.com
> Website: http://www.tcs.com <http://www.tcs.com/>
> ____________________________________________
> Experience certainty.	IT Services
> Business Solutions
> Consulting
> ____________________________________________
> -----Miguel Ángel Ajo <majopela at redhat.com> wrote: -----
> To: openstack-dev at lists.openstack.org
> From: Miguel Ángel Ajo <majopela at redhat.com>
> Date: 04/06/2015 09:26PM
> Cc: Kyle Mestery <mestery at mestery.com>, "Sean M. Collins" <sean at coreitpro.com>, "irenab.dev at gmail.com" <irenab.dev at gmail.com>, Suresh Balineni <sbalineni at juniper.net>, Raghunath D <raghunath.d at tcs.com>, Tal Anker <Ankertal at mellanox.com>, livnat Peer <lpeer at redhat.com>, Nir Yechiel <nyechiel at redhat.com>, Vikram Choudhary <vikram.choudhary at huawei.com>, Kalyankumar Asangi <kalyana at huawei.com>, Dhruv Dhody <dhruv.dhody at huawei.com>, "Dongfeng (C)" <albert.dongfeng at huawei.com>
> Subject: [neutron] [QoS] QoS weekly meeting
> I’d like to co-organized a QoS weekly meeting with Sean M. Collins,
>     In the last few years, the interest for QoS support has increased, Sean has been leading
> this effort [1] and we believe we should get into a consensus about how to model an extension
> to let vendor plugins implement QoS capabilities on network ports and tenant networks, and
> how to extend agents, and the reference implementation & others [2]
>     As per discussion we’ve had during the last few months [3], I believe we should start simple, but
> prepare a model allowing future extendibility, to allow for example specific traffic rules (per port,
> per IP, etc..), congestion notification support [4], …
>     It’s the first time I’m trying to organize an openstack/neutron meeting, so, I don’t know what’s the
> best way to do it, or find the best timeslot. I guess interested people may have a saying, so I’ve 
> looped anybody I know is interested in the CC of this mail. 
> Miguel Ángel Ajo
> [1] https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api <https://blueprints.launchpad.net/neutron/+spec/quantum-qos-api>
> [2] https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing <https://drive.google.com/file/d/0B2XATqL7DxHFRHNjU3k1UFNYRjQ/view?usp=sharing>
> [3] https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231 <https://docs.google.com/document/d/1xUx0Oq-txz_qVA2eYE1kIAJlwxGCSqXHgQEEGylwlZE/edit#heading=h.2pdgqfl3a231>
> [4] https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification <https://blueprints.launchpad.net/neutron/+spec/explicit-congestion-notification>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you

Miguel Angel Ajo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150407/169c5aea/attachment.html>

More information about the OpenStack-dev mailing list