Re: [openstack-dev] [relmgt] Libraries published to pypi with YYYY.X.Z versions

On Wed, Aug 30, 2017 at 05:04:58PM +0200, Thierry Carrez wrote: > Tony Breeds wrote: > > An extension to this would be to check for other items in the same boat. > > I wrote [1] to find anything in the openstack namespace that isn't a > > service and has something that looks like a date based

Re: [openstack-dev] [infra] Request to delete some unused pages from OpenStack wiki

Thank you! 2017-08-30 16:34 GMT+08:00 Thierry Carrez : > Chen Ying wrote: > > hi Thierry Carrez, > > Could you help me to delete this wiki page[1]? This page about > > Smaug is not used any longer. Thanks. > > > > [1]

Re: [openstack-dev] [neutron-dynamic-routing] 4-byte AS Numbers Support

2017-08-30 16:37 GMT+09:00 Jens Harbott : > 2017-08-30 9:04 GMT+02:00 Hirofumi Ichihara : > > Hi team, > > > > Currently neutron-dynamic-routing supports 2 byte AS numbers only[1]. > > Does team have a plan supporting 4 byte AS numbers? > > > >

[openstack-dev] [QA] Pike retrospective

Hello, I started an etherpad [0] for a retrospective about QA in Pike. I'd like to discuss about it during the PTG, so please add your inputs in time. Everyone is welcome to contribute, even if you're not in the QA team and/or your not attending the PTG. andrea [0]

[openstack-dev] [QA][ptg] QA Team social evening

Hello, I'd like to propose a social evening for the folks who will attend QA sessions at the PTG in Denver. I prepared a doodle [0] so if you're interested please vote :) I added the link to the main QA etherpad [1] as well. If you know a good place to go for food or drinks please add it to

[openstack-dev] [keystone] Blueprints for Queens

Now that Pike is out the door (big thanks to everyone for helping!), I've create the deprecated-as-of-queen [0] and removed-as-of-queens [1] blueprints. Feel free to use them as needed now that Queens is underway. Thanks! [0]

Re: [openstack-dev] [RFC v2] [OVS/NOVA] Vhost-user backends cross-version migration support

On Wed, Aug 30, 2017 at 11:19:08PM +0300, Michael S. Tsirkin wrote: > On Wed, Aug 30, 2017 at 04:25:10PM -0300, Eduardo Habkost wrote: > > On Wed, Aug 30, 2017 at 05:23:39PM +0300, Michael S. Tsirkin wrote: > > > On Wed, Aug 30, 2017 at 10:17:27AM -0300, Eduardo Habkost wrote: > > > > I'm CCing

Re: [openstack-dev] [RFC v2] [OVS/NOVA] Vhost-user backends cross-version migration support

On Wed, Aug 30, 2017 at 05:23:39PM +0300, Michael S. Tsirkin wrote: > On Wed, Aug 30, 2017 at 10:17:27AM -0300, Eduardo Habkost wrote: > > I'm CCing libvir-list and qemu-devel because I would like to get > > feedback from libvirt and QEMU developers too. > > > > On Tue, Aug 08, 2017 at 10:49:21PM

Re: [openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

On 08/30/2017 10:56 AM, Matt Riedemann wrote: On 8/30/2017 11:35 AM, Chris Friesen wrote: (We might even want to fail a live migration/evacuation with a forced destination that could cause a conflict in these non-shareable resources, but that'd be a behaviour change and therefore a new

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Ifat, thanks for the reply ... just got around to trying your suggestions. This definitely helps ... I no longer get any errors on re-starting collectd or vitrage-graph. i.e. it appears to load the collectd and updated vitrage conf files correctly now. Now still don’t get any alarms in

Re: [openstack-dev] [kolla] [cinder] [ironic] PTG cross-platform meetup possibility

Hi team, I'm interested in cinder containerization too. It would be great if we can schedule our meetup after 3pm or even 4pm, It will increase my chances to attend it. Thanks in advance. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, Aug 30, 2017 at 4:23 PM, Dmitry Tantsur

[openstack-dev] [cinder][ptg] Please Put Attendance in Etherpad ... Remote People Too!

Team, We have a good number of people who have indicated they are planning to attend the PTG in our etherpad [1] .  If you have not yet recorded it, please do so. For those of you hoping to join us via hangouts, I have added a section to indicate remote attendance.  Please also add your

[openstack-dev] [cinder][ptg] Team Outing Planning ...

All, As discussed in today's team meeting I have added a section to the PTG etherpad [1] to indicate if you would like to go out for dinner and drinks as a team and what night works best for you. If you are interested please update the etherpad.  I will need a rough number so I can reserve

[openstack-dev] [searchlight] Cancelling searchlight IRC meeting 8/31

Hi, I will not be able to attend the regular searchlight IRC meeting tomorrow so I'm going to cancel it. The next scheduled one is in two weeks but obviously the regular room is always open. Thanks, and apologies for the short notice. Steve

[openstack-dev] [nova] Can we remove the monkey_patch_modules config option?

Hi Matt, Thank you for pointing this out and bringing this to my attention. We are using the monkey_patch options to add more nova capabilities. Specifically we are using it to replace Nova’s nova/network/neutronv2/api.get_port_vnic_info function for extending the vnic type + phys network

Re: [openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

On 8/30/2017 11:35 AM, Chris Friesen wrote: (We might even want to fail a live migration/evacuation with a forced destination that could cause a conflict in these non-shareable resources, but that'd be a behaviour change and therefore a new microversion.) That's

Re: [openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

On 08/30/2017 09:09 AM, Matt Riedemann wrote: Given the recent bugs [1][2] due to the force flag in the live migrate and evacuate APIs related to Placement, and some other long standing bugs about bypassing the scheduler [3], I don't think we should add the force option to the cold migrate API,

[openstack-dev] Outreachy Dec-Mar 2018: Call for funding and mentors

Hi everyone, Quick update on the Outreachy [0] program, including a request for funding and volunteer mentors. For those of you who are not aware, Outreachy helps people from groups underrepresented in free and open source software get involved by matching interns with established mentors in the

Re: [openstack-dev] [openstack-announce] OpenStack Pike is officially released!

Stackers, Today you all released Pike, the latest release of OpenStack. That’s 16 software releases, every one on time, going back nearly seven years to October 21, 2010. That’s impressive! I think it speaks to what an amazing community we have and to all of your contributions. To everyone

[openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

Given the recent bugs [1][2] due to the force flag in the live migrate and evacuate APIs related to Placement, and some other long standing bugs about bypassing the scheduler [3], I don't think we should add the force option to the cold migrate API, as (re-)proposed in Takashi's cold migrate

Re: [openstack-dev] [relmgt] Libraries published to pypi with YYYY.X.Z versions

Tony Breeds wrote: > An extension to this would be to check for other items in the same boat. > I wrote [1] to find anything in the openstack namespace that isn't a > service and has something that looks like a date based release on pypi. > [...] Thanks for computing the list. Unpublishing is a

[openstack-dev] [all] connecting nova notification users and developers

Hi, Nova emits notifications for many different event, like different instance actions[1]. Also the nova developer community is working on making nova notifications well defined and easy to consume [2]. The goal of this mail is twofold. 1) We in the nova developer community would like to

Re: [openstack-dev] [nova] RequestSpec questions about force_hosts/nodes and requested_destination

2017-08-30 15:43 GMT+02:00 Sylvain Bauza : > Still on PTO for one day, but I'll try to answer. Sorry for the delay, was > out traveling. > > > 2017-08-21 23:09 GMT+02:00 Matt Riedemann : > >> I don't dabble in the RequestSpec code much, but in trying

Re: [openstack-dev] [RFC v2] [OVS/NOVA] Vhost-user backends cross-version migration support

I'm CCing libvir-list and qemu-devel because I would like to get feedback from libvirt and QEMU developers too. On Tue, Aug 08, 2017 at 10:49:21PM +0300, Michael S. Tsirkin wrote: > On Tue, Jul 18, 2017 at 03:42:08PM +0200, Maxime Coquelin wrote: > > This is an revival from a thread I initiated

Re: [openstack-dev] [nova] RequestSpec questions about force_hosts/nodes and requested_destination

Still on PTO for one day, but I'll try to answer. Sorry for the delay, was out traveling. 2017-08-21 23:09 GMT+02:00 Matt Riedemann : > I don't dabble in the RequestSpec code much, but in trying to fix bug > 1712008 [1] I'm venturing in there and have some questions. This

[openstack-dev] OpenStack Pike is officially released!

Hello OpenStack community, I'm proud and excited to announce the final release for the components of OpenStack Pike, which concludes the 6-month Pike development cycle. You will find a complete list of all components, their latest versions, and links to individual project release notes documents

Re: [openstack-dev] [kolla] [cinder] [ironic] PTG cross-platform meetup possibility

Hi! I'm all for it. Monday sounds okay to me, though I'll have to manage some conflicts, of course. On 08/29/2017 05:56 PM, Richard Wellum wrote: Hi Folks, Would there be some interest from Cinder and Ironic (and others of course) team members to have a quick session at the PTG with the

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

On 2017-08-30 08:45 AM, Mikhail Kebich wrote: > Assume, that I made a request after events 1, 2, 3 and 4 were added to > the database. After some time events 5, 6, 7, 8 and 9 were added to > the database. I made another request to get the rest of events and > received only events 8, 9 because of

Re: [openstack-dev] [nova] Proposing Balazs Gibizer for nova-core

2017-08-29 18:02 GMT+02:00 Matt Riedemann : > On 8/22/2017 8:18 PM, Matt Riedemann wrote: > >> I'm proposing that we add gibi to the nova core team. He's been around >> for awhile now and has shown persistence and leadership in the >> multi-release versioned notifications

Re: [openstack-dev] [ptg] PTG general info & upcoming registration price hike

Thierry- > If you're still wondering what will happen at this PTG (or you went to > the first one Atlanta and wonder what changed since), I wrote a blogpost > you might be interested to read at: https://ttx.re/queens-ptg.html Thanks for this, super helpful! efried

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

On 2017-08-30 08:33:09 -0400 (-0400), Paul Belanger wrote: [...] > Regarding Bug 1713832 - Object PUT failed for > zaqar_subscription[1], which was reverted last night. That is a > great example to showcase elastic-recheck, basically if you look > back at the logstash queries, you can see the

Re: [openstack-dev] [Panko] Ways to go through events in the order they appear in database

Hello Gordon, Thank you for the feedback. > i'm having trouble understanding the issue. the marker (message_id in > this case) denotes the starting point of query. not sure why you would > expect message_id4 to show up if message_id3 is newer. In the case described above message_id3 is not

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

On Wed, Aug 30, 2017 at 11:31:14AM +0200, Bogdan Dobrelya wrote: > On 30.08.2017 6:54, Emilien Macchi wrote: > > On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi wrote: > >> We are currently dealing with 4 issues and until they are fix, please > >> do not approve any patch. We

Re: [openstack-dev] [nova] Proposing Balazs Gibizer for nova-core

On Tue, Aug 29, 2017 at 6:02 PM, Matt Riedemann wrote: On 8/22/2017 8:18 PM, Matt Riedemann wrote: > I'm proposing that we add gibi to the nova core team. He's been around > for awhile now and has shown persistence and leadership in the > multi-release versioned

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

On 30.08.2017 6:54, Emilien Macchi wrote: > On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi wrote: >> We are currently dealing with 4 issues and until they are fix, please >> do not approve any patch. We want to keep the gate clear to merge the >> fixes for the 4 problems

[openstack-dev] [ptg] PTG general info & upcoming registration price hike

Hi everyone, We are only 12 days away from the start of the PTG in Denver. If you haven't registered yet, I encourage you to do so now: early Saturday morning the registration price will increase (stragglers tax). So head now to https://www.openstack.org/ptg and hit that button before it's too

[openstack-dev] [acceleration]Cyborg Team Weekly Meeting 2017.08.30

Hi Team, As usual we will have our team meeting today UTC1500 at #openstack-cyborg, an initial agenda could be found at https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda_for_next_meeting . Specifically for PTG prep, we will focus on our TC presentation preparation -- Zhipeng

[openstack-dev] [vitrage] Vitrage Queens virtual PTG

Hi all, As Vitrage will not participate in the Denver PTG, we decided to hold a virtual PTG instead. I created an etherpad[1] with a list of topics to discuss, and a Doodle poll[2] for selecting the date. I believe that two days will be enough. If you would like to participate, please add

[openstack-dev] [watcher] blueprint discussion meeting

Watcher folks, We have decided to set or update priorities of blueprints for Queens cycle during the following meeting. I propose to take first five blueprints to update their statuses and take first five undefined blueprints to set their statuses. Here is the current list of high and medium

Re: [openstack-dev] [infra] Request to delete some unused pages from OpenStack wiki

Chen Ying wrote: > hi Thierry Carrez, > Could you help me to delete this wiki page[1]? This page about > Smaug is not used any longer. Thanks. > > [1] https://wiki.openstack.org/wiki/File:Smaug-available-protectables.svg Done! -- Thierry Carrez (ttx)

Re: [openstack-dev] [tripleo] Pacemaker + containers CI

On 29.8.2017 17:12, Emilien Macchi wrote: On Tue, Aug 29, 2017 at 2:14 AM, Jiří Stránský wrote: [...] the CI for containerized deployments with Pacemaker is close! In fact, it works [1][2] (but there are pending changes to merge). Really good news, thanks for the update!

Re: [openstack-dev] [rdo-list] [TripleO] What's the plan for shipping Pike TripleO containers ?

> snip > It's probably also worth asking if we want to be shipping stable > containers at all ? Who will be the users of those stable containers ? > snip My 2cts as a consumer of “just” RDO packages and working to move to containers: (We are currently running our own puppet infra and have

Re: [openstack-dev] [neutron-dynamic-routing] 4-byte AS Numbers Support

2017-08-30 9:04 GMT+02:00 Hirofumi Ichihara : > Hi team, > > Currently neutron-dynamic-routing supports 2 byte AS numbers only[1]. > Does team have a plan supporting 4 byte AS numbers? > > [1]: >

[openstack-dev] [neutron-dynamic-routing] 4-byte AS Numbers Support

Hi team, Currently neutron-dynamic-routing supports 2 byte AS numbers only[1]. Does team have a plan supporting 4 byte AS numbers? [1]: https://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/services/bgp/common/constants.py#L27 Thanks, Hirofumi

Re: [openstack-dev] [infra] Request to delete some unused pages from OpenStack wiki

hi Thierry Carrez, Could you help me to delete this wiki page[1]? This page about Smaug is not used any longer. Thanks. [1] https://wiki.openstack.org/wiki/File:Smaug-available-protectables.svg Best regards chen ying 2017-08-29 11:02 GMT+08:00 Chen Ying : >

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

On Wed, Aug 30, 2017 at 7:54 AM, Emilien Macchi wrote: > On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi > wrote: > > We are currently dealing with 4 issues and until they are fix, please > > do not approve any patch. We want to keep the gate clear to