Re: [openstack-dev] Minimum version of shred in our supported distros?

But to do that I'd have to learn how to use git and then you wouldn't be forced to take the 17 unrelated patches! You see where I'm going with this right? An alternative would be to move it to the start of that series before the -2 of doom. Michael On 22 Aug. 2017 2:55 am, "Matt Riedemann"

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

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 is mostly an email to Sylvain for when he gets back from vacation but I wanted to dump it before moving forward. Mainly, what is the difference between

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Finishing the

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: > Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > > We realized recently that we haven't publicized some of the tools > > > in the releases repository very

Re: [openstack-dev] [ironic] PTG planning etherpad

A reminder that the PTG is coming :) We have only two Mondays left, and Sep 4th is apparently a holiday in the US. That means we have to more or less decide on the schedule next Monday, Aug 28th. Please add your ideas by that time! On 07/28/2017 12:19 PM, Dmitry Tantsur wrote: Hi all! It

Re: [openstack-dev] Minimum version of shred in our supported distros?

On 8/20/2017 1:11 AM, Michael Still wrote: Specifically we could do something like this: https://review.openstack.org/#/c/495532 Sounds like we're OK with doing this in Queens given the other discussion in this thread. However, this is part of a much larger series. It looks like it doesn't

Re: [openstack-dev] [openstack-ansible] group/host specific config file overrides: how-to?

On 21.08.2017 16:40, Andy McCrae wrote: > Hey Markus, > > >> I'm wondering which possibilities I have to do group/host specific >> config file overrides. After reading [1], I'm still a little clueless. >> To be specific, I have this setup (expressed as Ansible inventory file): >> >>

Re: [openstack-dev] [ironic] [release] [stable] pike release

On 08/21/2017 05:44 PM, Doug Hellmann wrote: Excerpts from Sam Betts (sambetts)'s message of 2017-08-21 10:01:35 +: Quick reply with my thoughts in-line. Sam On 21/08/2017, 10:13, "Dmitry Tantsur" wrote: (adding the release and stable team just for their

Re: [openstack-dev] [ironic] [release] [stable] pike release

Excerpts from Sam Betts (sambetts)'s message of 2017-08-21 10:01:35 +: > Quick reply with my thoughts in-line. > > Sam > > On 21/08/2017, 10:13, "Dmitry Tantsur" wrote: > > (adding the release and stable team just for their information) > > Thanks Julia

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On Mon, Aug 21, 2017 at 10:43:07AM +1200, Steve Baker wrote: > On Thu, Aug 17, 2017 at 4:13 PM, Steve Baker wrote: > > > > > > > On Thu, Aug 17, 2017 at 10:47 AM, Emilien Macchi > > wrote: > > > >> > >> > Problem #3: from Ocata to Pike: all container

Re: [openstack-dev] [ironic] [release] [stable] pike release

Hi, I'd like to get more information from the release folks (wrt grenade support or lack of, what might be reasonable or not to do, etc.), and how other OpenStack projects that use the same release model as ironic, do it. I think that whatever we do, it ought to be the easiest for all

Re: [openstack-dev] [release][ptl] tools for creating new releases

Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will be useful > > this week as you prepare your release

[openstack-dev] [nova] notification subteam meeting is cancelled this week

Hi, The notification subteam meeting is canceled this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [puppet neutron]

On Sat, Aug 19, 2017 at 12:37 AM, hanish gogada wrote: > Hi all, > > Currently neutron ml2 ovs agent puppet module does not support the > configuration of ovsdb_connection. Does any work on this is in progress. > We had

Re: [openstack-dev] [Nova] On idmapshift deprecation

On 8/20/2017 3:28 AM, Michael Still wrote: I'm going to take the general silence on this as permission to remove the idmapshift binary from nova. You're welcome. The reality is that no one is using the LXC code as far as I know. Rackspace was the only one ever contributing changes for LXC

[openstack-dev] [skip-level-upgrades][upgrades] Denver PTG room & etherpad

Hello all, This is a brief announcement to highlight that there will be a skip level upgrades room again at the PTG in Denver. I'll be chairing the room and have seeded the etherpad below with a few goal and topic ideas. I'd really welcome additional input from others, especially if you were

Re: [openstack-dev] [TripleO][CI] FreeIPA Deployment

On Mon, Aug 21, 2017 at 5:48 PM, Ben Nemec wrote: > > > On 08/21/2017 01:45 AM, Juan Antonio Osorio wrote: > >> The second option seems like the most viable. Not sure how the TripleO >> integration would go though. Care to elaborate on what you had in mind? >> > > I can't

Re: [openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results

Excerpts from Thierry Carrez's message of 2017-08-17 09:42:15 +0200: > Kendall Nelson wrote: > > Hello Everyone! > > > > Thank you to the electorate, to all those who voted and to all > > candidates who put their name forward for Project Team Lead (PTL) in > > this election. A healthy, open

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

Excerpts from Raildo Mascena de Sousa Filho's message of 2017-08-17 12:16:15 +: > Hi all, > > Should we reserve a room in the extra session ethercalc [0 > ] or we > already have a time slot scheduled for that discussion? > > [0]

Re: [openstack-dev] [TripleO][CI] FreeIPA Deployment

On 08/21/2017 01:45 AM, Juan Antonio Osorio wrote: The second option seems like the most viable. Not sure how the TripleO integration would go though. Care to elaborate on what you had in mind? I can't remember if we discussed this when we were first implementing the ci job, but could

Re: [openstack-dev] [openstack-ansible] group/host specific config file overrides: how-to?

Hey Markus, > I'm wondering which possibilities I have to do group/host specific > config file overrides. After reading [1], I'm still a little clueless. > To be specific, I have this setup (expressed as Ansible inventory file): > > [z_compute_nodes] > compute1 > # more nodes >

[openstack-dev] [openstack-ansible] group/host specific config file overrides: how-to?

I'm wondering which possibilities I have to do group/host specific config file overrides. After reading [1], I'm still a little clueless. To be specific, I have this setup (expressed as Ansible inventory file): [z_compute_nodes] compute1 # more nodes [x_compute_nodes]

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

> -Original Message- > From: Chris Dent [mailto:cdent...@anticdent.org] > Sent: Monday, August 21, 2017 10:44 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova] [placement] [api] cache headers

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

Thank you Sean K Mooney and Moshe Levi for your comments. I have few follow-up questions. Not looking for a detailed answer(I know you guys must be busy J). Looking for some basic info and will be obliged if you can point me to a direction(link to code or docs) where I can continue my research to

[openstack-dev] Fwd: [l2gw]

Hi, We faced an issue with l2-gw-update, which means that actually if there are connections for a gw the update will throw an exception (L2GatewayInUse), and the update is only possible after deleting first the connections, do the update and add the connections back. It is not exactly clear why

Re: [openstack-dev] [ironic] [release] [stable] pike release

Quick reply with my thoughts in-line. Sam On 21/08/2017, 10:13, "Dmitry Tantsur" wrote: (adding the release and stable team just for their information) Thanks Julia and everyone for handling this situation while I was out. More comments inline.

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

On Mon, 21 Aug 2017, Jay Pipes wrote: On 08/21/2017 04:59 AM, Chris Dent wrote: We do have cache validation on the server side for resource classes. Any time a resource class is added or deleted, we call _RC_CACHE.clear(). Couldn't we add a single attribute to the ResourceClassCache that

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

On 08/21/2017 04:59 AM, Chris Dent wrote: On Sun, 20 Aug 2017, Jay Pipes wrote: On 08/18/2017 01:23 PM, Chris Dent wrote: So my change above adds 'last-modified' and 'cache-control: no-cache' to GET of /resource_providers and /resource_providers/{uuid} and proposes we do it for everything

Re: [openstack-dev] [ironic] [release] [stable] pike release

(adding the release and stable team just for their information) Thanks Julia and everyone for handling this situation while I was out. More comments inline. On 08/17/2017 07:13 PM, Julia Kreger wrote: Greetings everyone! As some of you may have noticed, we released ironic 9.0.0 today. But

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

On Sun, 20 Aug 2017, Jay Pipes wrote: On 08/18/2017 01:23 PM, Chris Dent wrote: So my change above adds 'last-modified' and 'cache-control: no-cache' to GET of /resource_providers and /resource_providers/{uuid} and proposes we do it for everything else. Should we? No. :) Not everything. In

Re: [openstack-dev] [TripleO][CI] FreeIPA Deployment

The second option seems like the most viable. Not sure how the TripleO integration would go though. Care to elaborate on what you had in mind? On Fri, Aug 18, 2017 at 9:11 PM, Emilien Macchi wrote: > On Fri, Aug 18, 2017 at 8:34 AM, Harry Rybacki >