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
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
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
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.
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
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
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
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
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
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
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
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
>
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:
>
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
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
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
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
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:
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
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
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
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
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
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
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
> >>
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
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
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
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
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
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
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
> 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
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
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
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
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
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
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
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
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/
>> :
>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
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,
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
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
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
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
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,
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
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
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,
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
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
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
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
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,
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
Hi,
Here is the latest notification subteam update.
Bugs
No new bugs, no progress on open bugs.
Features
Sending full traceback in versioned notifications
~
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
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
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
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
62 matches
Mail list logo
