[openstack-dev] [neutron] No QoS meeting today

Hello: Due to Denver PTG, today there will be no QoS meeting today. Next one will be on September 26. Regards. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openst

[openstack-dev] [neutron] QoS meeting cancelled, next meeting 29/08/2017

Hello: Yesterday by mistake I didn't send an email saying the QoS meeting was cancelled. During this weeks, our focus are in the RC and solving possible bugs. Next meeting (no excuses) will be on 29/08/2017. Regards. __ Op

[openstack-dev] [neutron] no QoS meeting tomorrow

Hello everyone: Sorry for the late heads up. Today won't be Neutron QoS meeting because of the lack of quorum (4th of July). Regards. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-de

[openstack-dev] [neutron] [nova] [os-vif] OVS plugin assumes an incorrect datapath_type in os-vif

Hello fellows: Currently there is a bug in os-vif [1]. When os-vif tries to plug an OVS interface, the datapath type is hardcoded: - https://github.com/openstack/os-vif/blob/9fb7fe512902a37432e38d884b8be59ce91582db/vif_plug_ovs/ovs.py#L1

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1 From: Doug Wiegley [mailto:doug...@parksidesoftware.com] Sent: Saturday, October 15, 2016 1:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona +1 Doug On Oct 14, 2016, at 6:24 PM, Kevin Benton

[openstack-dev] [nova] [scheduler] New filter: AggregateInstanceTypeFilter

Hello: We have developed a new filter for Nova scheduler (SPEC). We have a POC in https://review.openstack.org/#/c/346662/. My question is how to procced with this code: 1) Merge into nova code. This solution seems not to be accepted (see spec co

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

Hello Ihar: Please, take a look to https://review.openstack.org/#/c/318531/. >> does it mean you want to set some queues on ports that have no qos policy >> attached? That’s exactly what I'm doing, because the unique way to shape traffic in OvS is at the end of the datapath. In other words, sha

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

performance could be reduced). Now I’m in a deadpoint. Regards. From: Alonso Hernandez, Rodolfo [mailto:rodolfo.alonso.hernan...@intel.com] Sent: Friday, June 24, 2016 10:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][qos] Egress

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

] Sent: Tuesday, June 21, 2016 10:27 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance On 2016/06/15 18:54, Alonso Hernandez, Rodolfo wrote: Hello: Context: try to develop a driver for this feature

[openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

Hello: Context: try to develop a driver for this feature in OVS. During the last week I’ve been testing several scenarios to make a POC of this feature. Scenario 1: 3 VM connected to br-int, sending traffic through br-physical to other host (an external physical machine). The first VM will hav

[openstack-dev] [nova] [scheduler] New filter: AggregateInstanceAffinityFilter

Hello: For the last two cycles we have tried to introduce a new filter to be able to interact better with the aggregates, using the metadata to accept or reject an instance depending on the flavor: https://review.openstack.org/#/c/189279/ This filter was reverted and we agreed to presen

Re: [openstack-dev] [Monasca] collectd-Monasca Python plugin

ve collectd-plugin for Monasca. There are some env. we cannot deploy monasca agent, but want to put data into Monasca. In addition, we wanted to use easily accepted collectd for gathering data from legacy env. It will be interesting to see more detail about your plan. Cheers, --- Jaesuk Ahn SDI Te

[openstack-dev] [Monasca] collectd-Monasca Python plugin

Hello: We are doing (or at least planning) a collectd-Monasca Python plugin. This plugin will receive the data from RPC calls form collectd and will write this data in Monasca, using statsd API. My question is: do you think this development could be useful? Does it worth? Any comment? Thank y