Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

Doug, We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at present) and ack on 20th for retag of final rc. We expect our rc2 to be final. If there are critical bugs that make the release doa in some way (such as upgrades, reconfigure etc), we will obviously have to

Re: [openstack-dev] [Neutron] ARP spoofing in VLAN aware VMs

Hi Kuba, On Fri, Sep 30, 2016 at 3:38 PM, Jakub Libosvar wrote: > The issue was with subports having different MAC addresses > than MAC address of the parent port. Packets leaving virtual instance via > VLAN interfaces (e.g. eth0.1) have always source MAC address of VLAN

Re: [openstack-dev] [nova][placement] placement newton leftovers

On Sun, 2 Oct 2016, Chris Dent wrote: I'm posting this as it would be great to get some feedback on: * which of these things matter * what is missing from the list * how (or if) we should formalize the doing of the work * who would like to help out in the doing (getting some help is the main

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

Hi, To follow up on the complications of bringing up trunk subports [1] I have written up a small proposal for a tiny new feature affecting neutron and nova. That is how to expose trunk details over metadata API. To avoid big process overhead I have opened a newton rfe ticket [2], plus a nova

[openstack-dev] [Glance] [stable] Bug backports

Hi Glancers! After the news that we all released Newton yesterday, it's time to start thinking about backports the future of our Mitaka and Liberty branches. I expect that Mitaka will start to enter Phase II [1] and Liberty's end-of-life is right around the corner [2] (2016-11-17). If there are

[openstack-dev] [glance] priorities for the next two weeks

I'd like to reiterate what we discussed during the "Core Awareness" topic at yesterday's Glance weekly meeting for those who weren't able to attend or read through the meeting logs yet. Three Ocata priorities have already been determined: (1) image import refactor (2) community images (including

Re: [openstack-dev] [cinder] How to retrieve volume_driver

On 10/07/2016 12:10 PM, Sean McGinnis wrote: On Fri, Oct 07, 2016 at 05:04:00PM +0200, cr...@interia.pl wrote: Hi Erlon. Thank you for the reply. I need to collect this information to generate sort of overview of drivers used in given environment. Obviously, it potentially is a multiple

Re: [openstack-dev] [nova] [libvirt] Debugging blockRebase() - "active block copy not ready for pivot"

On 10/6/2016 7:58 AM, Kashyap Chamarthy wrote: On Thu, Oct 06, 2016 at 01:32:39AM +0200, Kashyap Chamarthy wrote: TL;DR - From the debug analysis of the log below, and discussion with Eric Blake of upstream QEMU / libvirt resulted in the below bug report:

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Excerpts from Thierry Carrez's message of 2016-10-07 10:20:51 +0200: > Doug Hellmann wrote: > > Excerpts from Matt Riedemann's message of 2016-10-06 13:52:09 -0500: > >> Sorry yeah I screwed that up. I re-read the PTG email and the first two > >> days are cross-project things, and Wed-Fri are

Re: [openstack-dev] [cinder] How to retrieve volume_driver

On Fri, Oct 07, 2016 at 05:04:00PM +0200, cr...@interia.pl wrote: > Hi Erlon. > > Thank you for the reply. I need to collect this information to generate sort > of overview of drivers used in given environment. Obviously, it potentially > is a multiple backed one. This information does not

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

Jay, let me correct myself. After a round of discussion with Armando I'm no longer sure exactly what nova changes would be needed. The discussion went into a direction where we started to question which part of the change should fall into neutron and which part into nova. I think joint

Re: [openstack-dev] [Congress] PTG planning

Thanks for the additional notes, Thierry! On 10/6/16, 12:53 AM, "Thierry Carrez" wrote: >Good summary. It is true that for small-to-medium sized teams (which did >not routinely organize midcycles), there is a tough choice to make. > >See a couple of remarks inline: >

Re: [openstack-dev] [OpenStack-docs] Admin guide in-tree?

I'm not necessarily just asking for it to be done -- I'm curious what the scope of work is because I'm potentially willing to help (and find folks to help) get it done sooner. If the docs team does not support the admin guide in-tree until Pike, It'll be Q or later before other projects can

Re: [openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

Hi - Great suggestions, Dan. To recap, we followed that up with a few other ideas on irc and we eventually came to a point to test some of this, with slight modification. UI also ships with a configuration file that can override the endpoint information received from Keystone. The file is

Re: [openstack-dev] [cinder] How to retrieve volume_driver

Hi Erlon. Thank you for the reply. I need to collect this information to generate sort of overview of drivers used in given environment. Obviously, it potentially is a multiple backed one. This information does not need to be pulled from the cinder API - I can assume I work under root on host

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On Fri, Oct 7, 2016 at 9:03 AM, Paul Belanger wrote: > Greetings, > > I wanted to propose a work item, that I am happy to spearhead, about setting > up > a 3rd party CI system for tripleo project. The work I am proposing, wouldn't > actually affect anything today about

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

On 7 October 2016 at 06:43, Bence Romsics wrote: > Hi, > > To follow up on the complications of bringing up trunk subports [1] I > have written up a small proposal for a tiny new feature affecting > neutron and nova. That is how to expose trunk details over metadata >

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

On 10/07/2016 09:43 AM, Bence Romsics wrote: Hi, To follow up on the complications of bringing up trunk subports [1] I have written up a small proposal for a tiny new feature affecting neutron and nova. That is how to expose trunk details over metadata API. To avoid big process overhead I have

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

Hi, Armando: Replied in the RFE comments. Let's continue there. Jay: Yes, plus the corresponding changes in the API validator. Practically this: https://review.openstack.org/383801 Cheers, Bence On Fri, Oct 7, 2016 at 5:30 PM, Jay Pipes wrote: > On 10/07/2016 09:43 AM,

Re: [openstack-dev] [tripleo] TripleO RC3

Please read Doug's email: http://lists.openstack.org/pipermail/openstack-dev/2016-October/105266.html I think it makes sense for us to relax a bit on the RC3 and continue to work on blockers we wanted fixed in stable/newton. We already did amazing work to solve most of them, my hope is that we

[openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

This week we tagged the final releases for projects using the cycle-with-milestones release model. Projects using the cycle-trailing model have two more weeks before their final release tags are due. In the time between now and then, we expect those projects to be preparing and tagging release

[openstack-dev] [Fuel][Plugins] Contributing a new fuel-plugin

Please, could someone help me find the correct process on how to contribute fuel plugins upstream? I had followed these instructions but when I opened bug it was declared invalid - has the process changed perhaps? [1] I cannot find relevant documentation for how to go about creating the

[openstack-dev] [nova][scheduler] Next Scheduler subteam meeting

The next meeting of the Nova Scheduler subteam will be on Monday, October 10 at 1400 UTC in #openstack-meeting-alt http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161010-T14 As always, the agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaScheduler Please add any

Re: [openstack-dev] [tripleo] Getting the UI to talk with Undercloud API service endpoints

Do you know how awesome it would be if you put this idea into a Blueprint at http://blueprints.launchpad.net? That would be super-awesome. File it under tripleo-ui project here if you have a few minutes: https://blueprints.launchpad.net/specs/+new - Original Message - > Hi - > > Great

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

On Fri, Oct 7, 2016 at 3:16 PM, Doug Hellmann wrote: > This week we tagged the final releases for projects using the > cycle-with-milestones release model. Projects using the cycle-trailing > model have two more weeks before their final release tags are due. In > the time

Re: [openstack-dev] [QA] The end-user test suite for OpenStack clusters

Hi Timur, 2016-10-06 4:08 GMT-07:00 Timur Nurlygayanov : > Ken, it is a good idea! > > The plan is to develop os-faults as a library which will be able > to manage cluster nodes and OpenStack services on these nodes. > It is a good idea to add some Tempest tests which

Re: [openstack-dev] [Architecture] APAC friendly meeting time for Architecture Working Group proposed

Great time slot. Unfortunately not able to attend the first meeting for Oct. 1 to Oct.7 is public holiday in China. Best Regards Chaoyi Huang (joehuang) From: Clint Byrum [cl...@fewbar.com] Sent: 05 October 2016 3:04 To: openstack-dev Subject:

Re: [openstack-dev] [murano] IRC Meeting time suggestion

Good news! Thanks very much. Best Regards, xiangxinyong On Mon, Sep 26, 2016 at 11:01 PM, Omar Shykhkerimov < oshykhkeri...@mirantis.com> wrote: > Hello team! > > As every big project Murano is getting more contributors working on it. > Our current IRC-meetings are held from 5pm till 6pm

[openstack-dev] [all][tc] Cross Project workshops in Barcelona including "Re-inventing the TC"

Folks, Please see the cross project schedule over at: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Cross%20Project%20workshops%3A For those of you who are very interested in how TC works and what it can/should do. Please mark on your calendar:

Re: [openstack-dev] [Congress] PTG planning

Thanks summarizing it, Eric. Combination of 1. and 2. looks good. Basically, we'll have work sessions in PTG for next release. Other teams and operator could come, so it's easy for Congress team to discuss anything with them. Then if needed, we can have unofficial work session of Congress

[openstack-dev] [cinder] How to retrieve volume_driver

Dear all. I'm a PHD student from Poland and have found out about this list from Openstack wiki. Could you kindly tell me, if there is a way to retrieve, from outside of OpenStack code, volume_driver for given backend? Preferably - without a need to parse the cinder.conf file? It is fairly

Re: [openstack-dev] [mistral] Who's interested in attending PTG?

Yes, thanks for clarification Clint. Renat Akhmerov @Nokia > On 6 Oct 2016, at 20:02, Clint Byrum wrote: > > Excerpts from Renat Akhmerov's message of 2016-10-06 19:21:40 +0700: >> Hi, >> >> As you likely know, the summit format will change after Barcelona. There >> will be

[openstack-dev] [kolla] ~root and /etc of osic testing

Hey folks, Several people have asked for archives of the OSIC work we did. Those files can be found here: https://drive.google.com/drive/folders/0B8q6xDPETSkHc05fR21qeElpc2M?usp=sharing Regards, -steve __ OpenStack

Re: [openstack-dev] [heat] Presence at PTG, Atlanta

Rabi, thank you for the information. I think, that we need to attend as a team. So I agree with you opinion about option 1. Also I have a question: When do we need prepare new list of topics for design sessions for this event ? On 7 October 2016 at 08:48, Rabi Mishra wrote:

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Doug Hellmann wrote: > Excerpts from Matt Riedemann's message of 2016-10-06 13:52:09 -0500: >> Sorry yeah I screwed that up. I re-read the PTG email and the first two >> days are cross-project things, and Wed-Fri are meetup style at the PTG, >> it's not time-boxed sessions like the design

[openstack-dev] [keystone] design session schedule and etherpads

Hey Keystoners, I've created an initial draft of the keystone design session schedule. A live view is at [1]. I'm attaching the times, etherpads, and descriptions for each fishbowl / work session. So please start priming the etherpads with content. Also bookmark them! You'll notice we have one

Re: [openstack-dev] [all][API WG] How does one best express a time interval as an API filtering query?

Guys, thanks for the suggestions! I like the coma separation as well, it's the closest to the ISO style. Let me propose the update. Cheers, milan čt 6. 10. 2016 v 19:28 odesílatel Jay Pipes napsal: > On 10/06/2016 11:43 AM, Jeremy Stanley wrote: > > On 2016-10-06 10:30:30

Re: [openstack-dev] [heat] Presence at PTG, Atlanta

Sergey Kraynev wrote: > Rabi, thank you for the information. > > I think, that we need to attend as a team. So I agree with you opinion > about option 1. > Also I have a question: When do we need prepare new list of topics for > design sessions for this event ? Note that the PTG will not be

Re: [openstack-dev] [nova] FYI, nova plans to have a room at the PTG in February

Clint Byrum wrote: > Excerpts from Matt Riedemann's message of 2016-10-06 11:33:35 -0500: >> Remember at a high level that the PTG is the replacement for the >> midcycle meetups, except it's centrally located and organized by the >> foundation, and it's at the release boundaries rather than the

Re: [openstack-dev] [heat] Presence at PTG, Atlanta

Thierry, Thank you for the clarification :) On 7 October 2016 at 11:35, Thierry Carrez wrote: > Sergey Kraynev wrote: > > Rabi, thank you for the information. > > > > I think, that we need to attend as a team. So I agree with you opinion > > about option 1. > > Also I

[openstack-dev] [neutron] proper cleanup of l3 resources (neutron-netns-cleanup)

Hello everyone. I’m very interesting in this one https://bugs.launchpad.net/neutron/+bug/1403455 Can anybody tell me, what is the current status of this bug? Is anybody working on it now? And as I can see, there are some options, that was discussed in comments to this bug and… did anybody

Re: [openstack-dev] [cinder] How to retrieve volume_driver

Hi Luzasz, This information (volume_driver) is only used on driver loading so, its not available outside Cinder context. Can you tell how and why you need that? And why parsing the conf file is not enough for you? Erlon On Fri, Oct 7, 2016 at 9:05 AM, wrote: > Dear all. > >

[openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

Greetings, I wanted to propose a work item, that I am happy to spearhead, about setting up a 3rd party CI system for tripleo project. The work I am proposing, wouldn't actually affect anything today about tripleo-ci but provider a working example of how 3rd party CI will work and potential

Re: [openstack-dev] [neutron] proper cleanup of l3 resources (neutron-netns-cleanup)

Hi Sergey!, This was my point of view on a possible solution: https://bugs.launchpad.net/neutron/+bug/1403455/comments/12 """ After much thinking (and quite little doing) I believe the option "2" I proposed is a rather reasonable one: 2) Before cleaning a namespace blindly in the end, identify

[openstack-dev] Affinity instance slot reservation

Nova scheduler don't reserve any slots for new instances with affinity policy. I've created a bug on Launchpad (https://bugs.launchpad.net/nova/+bug/1630929) which describes the problem and my solution. Please let me know what you think about it. Regards

[openstack-dev] [Neutron] Stadium evolution - final stage

Neutrinos, As some of you may have noticed, there has been a fresh batch of patches on topic [1]. After having worked on [2][3] during the span of Newton, we are approaching now the final stage of this consolidation effort, where I attempt to define a procedure for transparently letting the

[openstack-dev] [nova] Getting DetachedInstanceError from sqlalchemy on instance.get_by_uuid()

Hi all, In kilo (yeah I know it's an old release, but still :)), I was getting a nova errors for DetachedInstanceError on instance.get_by_uuid(). 2016-10-05 18:30:53.791 103618 ERROR nova.api.metadata.handler [req-5aa7b422-d6c0-424e-b40f-cea79d3a3963 - - - - -] Failed to get metadata for

Re: [openstack-dev] [murano] IRC Meeting time suggestion

+1 [openstack-dev] [murano] IRC Meeting time suggestion *Omar Shykhkerimov* oshykhkerimov at mirantis.com

Re: [openstack-dev] [telemetry] Deprecating the Ceilometer API

I know customers are using the 'pushing sample API', but don’t know whether they're applying transformer to those data or not. -Lianhao Lu > -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Wednesday, October 05, 2016 12:35 AM > To: gordon chung > Cc:

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

So do we like the idea of "volume based scheduling?" On Tue, Sep 27, 2016 at 11:39 AM, Joshua Harlow wrote: > Huang Zhiteng wrote: > >> >> >> On Tue, Sep 27, 2016 at 12:00 AM, Joshua Harlow > > wrote: >> >> Huang

[openstack-dev] [Trove] trove core team

Whats up yall. So I've changed my focus over the last couple months to working on some new technology and do not have time to fulfill my duties as Trove Core any longer. I think its time to move on and step down from trove core. I have been around for a while and seen the Trove community grow

Re: [openstack-dev] [murano] IRC Meeting time suggestion

The time is better than before for me and i will attend the meeting. thanks， Nanke __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all] Ocata Design Summit: Couple of empty slots up for grabs

Zhipeng Huang wrote: > Nomad team would also like to see if one of the slots would be available > :) either one would work fine for us 3 requests for 2 slots... We gave preference to existing teams (or teams already proposed for becoming an official project, so Fuel got the additional fishbowl