Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Cédric Jeanneret
On 05/29/2018 09:43 PM, Davanum Srinivas wrote: > Agree with Ian here. > > Also another problem that comes up is: "Why are you touching *MY* > review?" (probably coming from the view where stats - and stackalytics > leaderboard position is important). So i guess we ask permission > before editin

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Cédric Jeanneret
On 05/30/2018 01:42 AM, Zane Bitter wrote: > On 29/05/18 16:49, Slawomir Kaplonski wrote: >> Hi, >> >>> Wiadomość napisana przez Jay S Bryant w dniu >>> 29.05.2018, o godz. 22:25: >>> Maybe it would be different now that I am a Core/PTL but in the past >>> I had been warned to be careful as it c

[openstack-dev] [vitrage] No IRC meeting this week

2018-05-29 Thread Afek, Ifat (Nokia - IL/Kfar Sava)
Hi, The IRC meeting this week is canceled, since many Vitrage developers are on vacation. We will meet next Wednesday, June 6th, at 8:00 UTC. See you next week, Ifat __ OpenStack Development Mailing List (not for usage que

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Masayuki Igawa
I think this is not only for code but also for doc and reno. We should fix it basically, especially about doc/reno. But I don't think it should be in the same patch if the mistake isn't critical which means *nitpicks*. I think we can fix them with following patches if we need to fix it. Otherwise,

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Ghanshyam Mann
Thanks for making it formal process which really helps. I think most of the people usually does that but yes it is always helpful to be added as principles. I have gotten mix feedback on fixing other patches in past and when i got anger by author i try to leave comment for a day or two then fix if

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Samuel Cassiba
On Tue, May 29, 2018 at 4:26 PM, Ian Wells wrote: > On 29 May 2018 at 14:53, Jeremy Stanley wrote: > >> On 2018-05-29 15:25:01 -0500 (-0500), Jay S Bryant wrote: >> [...] >> > Maybe it would be different now that I am a Core/PTL but in the past I >> had >> > been warned to be careful as it could

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Ben Swartzlander
On 05/29/2018 03:43 PM, Davanum Srinivas wrote: Agree with Ian here. Also another problem that comes up is: "Why are you touching *MY* review?" (probably coming from the view where stats - and stackalytics leaderboard position is important). So i guess we ask permission before editing (or) file

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Zane Bitter
On 29/05/18 16:49, Slawomir Kaplonski wrote: Hi, Wiadomość napisana przez Jay S Bryant w dniu 29.05.2018, o godz. 22:25: Maybe it would be different now that I am a Core/PTL but in the past I had been warned to be careful as it could be misinterpreted if I was changing other people's patche

[openstack-dev] [Cyborg] [Nova] Cyborg traits

2018-05-29 Thread Nadathur, Sundar
Hi all,    The Cyborg/Nova scheduling spec [1] details what traits will be applied to the resource providers that represent devices like GPUs. Some of the traits referred to vendor names. I got feedback that traits must not refer to products or specific models of devices. I agree. However, we

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Ian Wells
On 29 May 2018 at 14:53, Jeremy Stanley wrote: > On 2018-05-29 15:25:01 -0500 (-0500), Jay S Bryant wrote: > [...] > > Maybe it would be different now that I am a Core/PTL but in the past I > had > > been warned to be careful as it could be misinterpreted if I was changing > > other people's patc

Re: [openstack-dev] [tc][forum] TC Retrospective for Queens/Rocky

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 17:26:16 -0400 (-0400), Doug Hellmann wrote: [...] > There was some discussion of whether the office hours themselves > are useful, based on the apparent lack of participation. We had > theories that this was a combination of bad times (meaning that TC > members haven't always attende

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 15:25:01 -0500 (-0500), Jay S Bryant wrote: [...] > Maybe it would be different now that I am a Core/PTL but in the past I had > been warned to be careful as it could be misinterpreted if I was changing > other people's patches or that it could look like I was trying to pad my > numbe

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Doug Hellmann
Excerpts from Slawomir Kaplonski's message of 2018-05-29 22:49:07 +0200: > Hi, > > > Wiadomość napisana przez Jay S Bryant w dniu > > 29.05.2018, o godz. 22:25: > > > > > > On 5/29/2018 3:19 PM, Doug Hellmann wrote: > >> Excerpts from Jonathan Proulx's message of 2018-05-29 16:05:06 -0400: > >

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 13:17:50 -0400 (-0400), Doug Hellmann wrote: [...] > We have the status:maintenance-mode tag[3] today. How would a new > "low-activity" tag be differentiated from the existing one? [...] status:maintenance-mode is (as it says on the tin) a subjective indicator that a team has entered

[openstack-dev] [nova] review runway status

2018-05-29 Thread melanie witt
Hi everybody, This is just a brief status about the blueprints currently occupying review runways [0] and an ask for the nova-core team to give these reviews priority for their code review focus. Note that these 3 blueprints were in runways during summit week with end dates of 2018-05-28 and 20

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 13:59:27 +0200 (+0200), Thierry Carrez wrote: [...] > Alternatively (if that's too much work), we could add a new team > tag (low-activity ?) that would appear for all projects where the > activity is so low that the team diversity tags no longer really > apply. As others have also s

[openstack-dev] [tc][forum] TC Retrospective for Queens/Rocky

2018-05-29 Thread Doug Hellmann
At the forum last week the TC held a retrospective to discuss how we felt things have gone for the TC over the last 6-ish months, since the previous election. I will try to summarize the feedback here based on the notes in the etherpad [1], but please reply if I misremember something, leave out det

Re: [openstack-dev] [all][tc] final stages of python 3 transition

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 15:51:31 -0400 (-0400), Doug Hellmann wrote: [...] > Could we, for example, look at the set of packages installed under > python2 and report errors if any OpenStack packages end up there? [...] This sounds like a marvellous solution. -- Jeremy Stanley signature.asc Description: PG

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Slawomir Kaplonski
Hi, > Wiadomość napisana przez Jay S Bryant w dniu > 29.05.2018, o godz. 22:25: > > > On 5/29/2018 3:19 PM, Doug Hellmann wrote: >> Excerpts from Jonathan Proulx's message of 2018-05-29 16:05:06 -0400: >>> On Tue, May 29, 2018 at 03:53:41PM -0400, Doug Hellmann wrote: >>> :> >> maybe we're all

Re: [openstack-dev] [all][tc] final stages of python 3 transition

2018-05-29 Thread Doug Hellmann
Excerpts from Matthew Treinish's message of 2018-05-29 16:16:50 -0400: > On Tue, May 29, 2018 at 03:51:31PM -0400, Doug Hellmann wrote: > > Following up on this topic, at the Forum discussion last week (see > > https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline) the > > general plan

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jay S Bryant
On 5/29/2018 3:19 PM, Doug Hellmann wrote: Excerpts from Jonathan Proulx's message of 2018-05-29 16:05:06 -0400: On Tue, May 29, 2018 at 03:53:41PM -0400, Doug Hellmann wrote: :> >> maybe we're all saying the same thing here? :> > Yeah, I feel like we're all essentially in agreement that nits (

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Doug Hellmann
Excerpts from Jonathan Proulx's message of 2018-05-29 16:05:06 -0400: > On Tue, May 29, 2018 at 03:53:41PM -0400, Doug Hellmann wrote: > :> >> maybe we're all saying the same thing here? > :> > Yeah, I feel like we're all essentially in agreement that nits (of the > :> > English mistake of typo typ

Re: [openstack-dev] [all][tc] final stages of python 3 transition

2018-05-29 Thread Matthew Treinish
On Tue, May 29, 2018 at 03:51:31PM -0400, Doug Hellmann wrote: > Following up on this topic, at the Forum discussion last week (see > https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline) the > general plan outlined below was acceptable to most of the folks in the > room with a few sm

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jonathan Proulx
On Tue, May 29, 2018 at 03:53:41PM -0400, Doug Hellmann wrote: :> >> maybe we're all saying the same thing here? :> > Yeah, I feel like we're all essentially in agreement that nits (of the :> > English mistake of typo type) do need to get fixed, but sometimes :> > (often?) putting the burden of fix

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Samuel Cassiba
On Tue, May 29, 2018 at 5:51 AM, Mohammed Naser wrote: > On Tue, May 29, 2018 at 7:59 AM, Thierry Carrez > wrote: > > Mohammed Naser wrote: > >> > >> During the TC retrospective at the OpenStack summit last week, the > >> topic of the organizational diversity tag is becoming irrelevant was > >>

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Doug Hellmann
Excerpts from Julia Kreger's message of 2018-05-29 15:41:55 -0400: > On Tue, May 29, 2018 at 3:16 PM, Jay S Bryant wrote: > > > > > > On 5/29/2018 2:06 PM, Artom Lifshitz wrote: > >> Yeah, I feel like we're all essentially in agreement that nits (of the > >> English mistake of typo type) do need t

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Doug Hellmann
Excerpts from Jay S Bryant's message of 2018-05-29 14:16:33 -0500: > > On 5/29/2018 2:06 PM, Artom Lifshitz wrote: > >> On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote: > >> > >> :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz > >> wrote: > >> :> One idea would be that, once th

Re: [openstack-dev] [all][tc] final stages of python 3 transition

2018-05-29 Thread Doug Hellmann
Following up on this topic, at the Forum discussion last week (see https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline) the general plan outlined below was acceptable to most of the folks in the room with a few small changes (included below). Excerpts from Doug Hellmann's message of

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Davanum Srinivas
Agree with Ian here. Also another problem that comes up is: "Why are you touching *MY* review?" (probably coming from the view where stats - and stackalytics leaderboard position is important). So i guess we ask permission before editing (or) file a follow up later (or) just tell folks that this i

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Julia Kreger
On Tue, May 29, 2018 at 3:16 PM, Jay S Bryant wrote: > > > On 5/29/2018 2:06 PM, Artom Lifshitz wrote: >> Yeah, I feel like we're all essentially in agreement that nits (of the >> English mistake of typo type) do need to get fixed, but sometimes >> (often?) putting the burden of fixing them on the

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Ian Wells
If your nitpick is a spelling mistake or the need for a comment where you've pretty much typed the text of the comment in the review comment itself, then I have personally found it easiest to use the Gerrit online editor to actually update the patch yourself. There's nothing magical about the orig

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jay S Bryant
On 5/29/2018 2:06 PM, Artom Lifshitz wrote: On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote: :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote: :> One idea would be that, once the meat of the patch :> has passed multiple rounds of reviews and looks good, and what remains

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Artom Lifshitz
> On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote: > > :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote: > :> One idea would be that, once the meat of the patch > :> has passed multiple rounds of reviews and looks good, and what remains > :> is only nits, the reviewer themse

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jay S Bryant
Julia, Thank you for starting this discussion. On 5/29/2018 9:43 AM, Artom Lifshitz wrote: I dunno, there's a fine line to be drawn between getting a finished product that looks unprofessional (because of typos, English mistakes, etc), and nitpicking to the point of smothering and being counte

Re: [openstack-dev] [TC] [Infra] Terms of service for hosted projects

2018-05-29 Thread Jeremy Stanley
On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote: > We allow various open source projects that are not an official > part of OpenStack or necessarily used by OpenStack to be hosted on > OpenStack infrastructure - previously under the 'StackForge' > branding, but now without separate branding

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Doug Hellmann
Excerpts from Mohammed Naser's message of 2018-05-29 08:51:16 -0400: > On Tue, May 29, 2018 at 7:59 AM, Thierry Carrez wrote: > > Mohammed Naser wrote: > >> > >> During the TC retrospective at the OpenStack summit last week, the > >> topic of the organizational diversity tag is becoming irrelevant

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Davanum Srinivas
Thanks for driving this Julia. +1. It's time to do this. -- Dims On Tue, May 29, 2018 at 6:55 AM, Julia Kreger wrote: > During the Forum, the topic of review culture came up in session after > session. During these discussions, the subject of our use of nitpicks > were often raised as a point of

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Joshua Harlow
Jonathan D. Proulx wrote: On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote: :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote: :> One idea would be that, once the meat of the patch :> has passed multiple rounds of reviews and looks good, and what remains :> is only nits,

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Mathieu Gagné
Hi Julia, Thanks for the follow up on this topic. On Tue, May 29, 2018 at 6:55 AM, Julia Kreger wrote: > > These things are not just frustrating, but also very inhibiting for > part time contributors such as students who may also be time limited. > Or an operator who noticed something that was c

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Jonathan D. Proulx
On Tue, May 29, 2018 at 10:52:04AM -0400, Mohammed Naser wrote: :On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote: :> One idea would be that, once the meat of the patch :> has passed multiple rounds of reviews and looks good, and what remains :> is only nits, the reviewer themselves take o

Re: [openstack-dev] [Release-job-failures][tripleo] Release of openstack/tripleo-validations failed

2018-05-29 Thread Alex Schultz
On Tue, May 29, 2018 at 9:31 AM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-05-29 14:28:57 +: >> Build failed. >> >> - release-openstack-python >> http://logs.openstack.org/26/26956a27b95550e2162243da79d62bb1b19d50d7/release/release-openstack-python/2bd7f7d/ >> : POST_FAILUR

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Neil Jerram
>From my point of view as someone who is still just an occasional contributor (in all OpenStack projects other than my own team's networking driver), and so I think still sensitive to the concerns being raised here: - Nits are not actually a problem, at all, if they are uncontroversial and quick t

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Amy Marrich
If I have a nit that doesn't affect things, I'll make a note of it and say if you do another patch I'd really like it fixed but also give the patch a vote. What I'll also do sometimes if I know the user or they are online I'll offer to fix things for them, that way they can see what I've done, I've

Re: [openstack-dev] [Release-job-failures][tripleo] Release of openstack/tripleo-validations failed

2018-05-29 Thread Doug Hellmann
Excerpts from zuul's message of 2018-05-29 14:28:57 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/26/26956a27b95550e2162243da79d62bb1b19d50d7/release/release-openstack-python/2bd7f7d/ > : POST_FAILURE in 6m 34s > - announce-release announce-release : SKIPPED >

[openstack-dev] [TC] Terms of service for hosted projects

2018-05-29 Thread Zane Bitter
We allow various open source projects that are not an official part of OpenStack or necessarily used by OpenStack to be hosted on OpenStack infrastructure - previously under the 'StackForge' branding, but now without separate branding. Do we document anywhere the terms of service under which we

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Mohammed Naser
On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote: > I dunno, there's a fine line to be drawn between getting a finished > product that looks unprofessional (because of typos, English mistakes, > etc), and nitpicking to the point of smothering and being > counter-productive. One idea would be

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Artom Lifshitz
I dunno, there's a fine line to be drawn between getting a finished product that looks unprofessional (because of typos, English mistakes, etc), and nitpicking to the point of smothering and being counter-productive. One idea would be that, once the meat of the patch has passed multiple rounds of r

Re: [openstack-dev] [Openstack-operators] [nova] Need some feedback on the proposed heal_allocations CLI

2018-05-29 Thread Matt Riedemann
On 5/28/2018 7:31 AM, Sylvain Bauza wrote: That said, given I'm now working on using Nested Resource Providers for VGPU inventories, I wonder about a possible upgrade problem with VGPU allocations. Given that :  - in Queens, VGPU inventories are for the root RP (ie. the compute node RP), but,

Re: [openstack-dev] [nova] nova aggregate and nova placement api aggregate

2018-05-29 Thread Matt Riedemann
On 5/25/2018 12:56 AM, Matt Riedemann wrote: On 5/24/2018 8:33 PM, Jeffrey Zhang wrote: Recently, i am trying to implement a function which aggregate nova hypervisors rather than nova compute host. But seems nova only aggregate nova-compute host. On the other hand, since Ocata, nova depends o

[openstack-dev] [tc][all] A culture change (nitpicking)

2018-05-29 Thread Julia Kreger
During the Forum, the topic of review culture came up in session after session. During these discussions, the subject of our use of nitpicks were often raised as a point of contention and frustration, especially by community members that have left the community and that were attempting to re-engage

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Sylvain Bauza
On Tue, May 29, 2018 at 2:21 PM, Balázs Gibizer wrote: > > > On Tue, May 29, 2018 at 1:47 PM, Sylvain Bauza wrote: > >> >> >> Le mar. 29 mai 2018 à 11:02, Balázs Gibizer >> a écrit : >> >>> >>> >>> On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza >>> wrote: >>> > >>> > >>> > On Tue, May 29, 2018

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Mohammed Naser
On Tue, May 29, 2018 at 7:59 AM, Thierry Carrez wrote: > Mohammed Naser wrote: >> >> During the TC retrospective at the OpenStack summit last week, the >> topic of the organizational diversity tag is becoming irrelevant was >> brought up by Thierry (ttx)[1]. It seems that for projects that are >>

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Balázs Gibizer
On Tue, May 29, 2018 at 1:47 PM, Sylvain Bauza wrote: Le mar. 29 mai 2018 à 11:02, Balázs Gibizer a écrit : On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: > > > On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA > wrote > >> > In that situation, say for example with VGPU invent

Re: [openstack-dev] [tc] Organizational diversity tag

2018-05-29 Thread Thierry Carrez
Mohammed Naser wrote: During the TC retrospective at the OpenStack summit last week, the topic of the organizational diversity tag is becoming irrelevant was brought up by Thierry (ttx)[1]. It seems that for projects that are not very active, they can easily lose this tag with a few changes by p

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Sylvain Bauza
Le mar. 29 mai 2018 à 11:02, Balázs Gibizer a écrit : > > > On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza > wrote: > > > > > > On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA > > wrote > > > >> > In that situation, say for example with VGPU inventories, that > >> would mean > >> > that the c

[openstack-dev] New OpenStack project for rolling maintenance and upgrade in interaction with application on top of it

2018-05-29 Thread Juvonen, Tomi (Nokia - FI/Espoo)
Hi, I am the PTL of the OPNFV Doctor project. I have been working for a couple of years figuring out the infrastructure maintenance in interaction with application on top of it. Looked into Nova, Craton and had several Ops sessions. Past half a year there has been couple of different POCs, the

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Balázs Gibizer
On Tue, May 29, 2018 at 11:52 AM, Sylvain Bauza wrote: 2018-05-29 11:01 GMT+02:00 Balázs Gibizer : On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA wrote > In that situation, say for example with VGPU inventories, that wou

[openstack-dev] [nova] Notification update week 22

2018-05-29 Thread Balázs Gibizer
Hi, Here is the latest notification subteam update. Bugs No new bugs, no progress on open bugs. Features Sending full traceback in versioned notifications ~ https://blueprints.launchpad.net/nova/+spec/add-full-traceback-to-error-no

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Sylvain Bauza
2018-05-29 11:01 GMT+02:00 Balázs Gibizer : > > > On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: > >> >> >> On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA < >> nakamura.tets...@lab.ntt.co.jp> wrote >> >> > In that situation, say for example with VGPU inventories, that would >>> mean >>>

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Balázs Gibizer
On Tue, May 29, 2018 at 9:38 AM, Sylvain Bauza wrote: On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA wrote > In that situation, say for example with VGPU inventories, that would mean > that the compute node would stop reporting inventories for its root RP, but > would rather repor

[openstack-dev] [kolla-ansible] dns_interface, inv

2018-05-29 Thread vladislav . belogrudov
Hi, in multinode inventory I see that both haproxy and l3 agents run on network nodes. Does it mean that network nodes need two public interfaces - one for external VIP and another (unassigned) for external bridge? Will it work without conflicts? Another question, designate-mdns runs on netw

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

2018-05-29 Thread Sylvain Bauza
On Tue, May 29, 2018 at 3:08 AM, TETSURO NAKAMURA < nakamura.tets...@lab.ntt.co.jp> wrote: > Hi, > > > Do I still understand correctly ? If yes, perfect, let's jump to my > upgrade > > concern. > > Yes, I think. The old microversions look into only root providers and give > up providing resources