Agenda of Sept.21 weekly meeting, let's continue the topics:
# freeze date for Newton release
# patch planned to be merged before freeze date
# open discussion
How to join:
# IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on
every Wednesday starting from UTC 13:00.
Hello,
During the last weekly meeting, we discussed that the deadline for PTL
candidacy will be this Tuesday noon, for we are not OpenStack big-tent project
yet, so the deadline is not needed to be aligned with other official projects.
According to the election program in OpenStack community,
Hi,
The default policy.json provided by heat limits 'service-list' API to
'admin' project like below.
Is there any reason 'admin' role user in non-'admin' project cannot
see service-list?
"service:index": "rule:context_is_admin",
"context_is_admin": "role:admin and is_admin_project:True",
On 09/20/2016 05:48 PM, John Griffith wrote:
> On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas
> mailto:duncan.tho...@gmail.com>> wrote:
>
> On 20 September 2016 at 16:24, Nikita Konovalov
> mailto:nkonova...@mirantis.com>> wrote:
>
> Hi,
>
> From Sahara (and Hadoop workload
Hi,
As agreed by the manila community in IRC meeting,
we try to enable IPv6 in Ocata. Please check the brief spec[1] and code[2]).
The areas affected most are API (access rules) and in the drivers (access
rules
& export locations). This change intends to add the IPv6 format validation
for
ip acce
Hi,
As discussed in our IRC meeting today, you are welcome to suggest topics for
vitrage design sessions in Barcelona:
https://etherpad.openstack.org/p/vitrage-barcelona-design-sessions
Thanks,
Ifat.
__
OpenStack Developmen
Hi everyone,
As promised here is a link to the code PoC for the Kuryr-IPVlan proposal.
https://github.com/lmdaly/kuryr-libnetwork
Link to specific commit
https://github.com/lmdaly/kuryr-libnetwork/commit/1dc895a6d8bfaa03c0dd5cfb2d3e23e2e948a67c
>From here you can clone the repo and install Kuryr
Congratulations Ihar! You really deserved this, I am sure you'll do great.
Rossella
On 09/20/2016 10:57 AM, Miguel Angel Ajo Pelayo wrote:
Congratulations Ihar!, well deserved through hard work! :)
On Mon, Sep 19, 2016 at 8:03 PM, Brian Haley wrote:
Congrats Ihar!
-Brian
On 09/17/2016 12:
I have been working on the user-data scripts (first-boot) for updating
the kernel args on the overcloud node [1]. The pre-condition is that
the kernel args has to be applied and node has to be restarted before
os-net-config runs.
I got in to problem of provisioning network not getting ip after the
On 09/19/2016 10:49 PM, Emilien Macchi wrote:
(adding puppet tag for cross project session).
Let's continue to prepare TripleO sessions.
https://etherpad.openstack.org/p/ocata-tripleo
For reminder, we have 2 fishbowls and 4 working rooms.
I looked at the topic proposals and I started to organi
Hi everyone,
As announced previously[1][2], there were no PTL candidates within the
election deadline for a number of official OpenStack project teams:
Astara, UX, OpenStackSalt and Security.
In the Astara case, the current team working on it would like to abandon
the project (and let it be avail
On 00:48 Sep 21, joehuang wrote:
> Thank you for the message. Will the weekly IRC meeting in that week also be
> cancelled during
> the summit period according to your experience?
Likely yes.
--
Mike Perez
__
OpenStack Dev
Ilya Shakhat wrote:
> Hi,
>
> tldr; Commits stats are significantly skewed by deb-* projects
> (http://stackalytics.com/?metric=commits&module=packaging-deb-group)
>
> By default Stackalytics processes commits from project's master branch.
> For some "old core" projects there is configuration to
Of late I've been seeing a lot of rather questionable changes that appear to be
getting blasted out across multiple projects; changes that cause considerable
code churn, and don't (IMHO) materially improve the quality of OpenStack.
I'd love to provide a list of the changes that triggered this em
Thanks for your trust, much appreciated!
On 09/16/2016 10:44 PM, Emilien Macchi wrote:
Cool, sounds like great feedback here!
so I created the new gerrit groups and assign new members into it.
Congrats folks!
On Thu, Sep 15, 2016 at 12:52 PM, Ivan Berezovskiy
wrote:
+1, great job, guys! Keep
i feel like this gets brought up every year. we block these patches in
Telemetry projects unless they can be justified beyond the copy/paste
description.
in addition to this, please, PLEASE stop creating 'all project bugs'. i
don't want to get emails on updates to projects unrelated to the ones
For my part, I missed the elections, that's my bad. I normally put a
calendar item in for that issue. I don't think that my missing the election
date should result in the group being treated in this way. Members of the
TC have contacted me about unrelated things recently, I have always been
availab
If this is the bug that triggered this discussion, yes, please never do
anything like that -
https://bugs.launchpad.net/python-openstacksdk/+bug/1475722
The bug now has too many projects to take any actions on it.
I think a basic rule of thumb that before creating a bug that has > 4
projects on i
This is a topic that appears periodically; I think it's important that we
consider the patches objectively, just like any other patch.
If these patches result in substantial and unproductive load on infra that
can be deemed abusive, then that's another matter.
And as a general rule, there is zero
On Wed, Sep 21, 2016 at 8:15 AM, gordon chung wrote:
> i feel like this gets brought up every year. we block these patches in
> Telemetry projects unless they can be justified beyond the copy/paste
> description.
>
> in addition to this, please, PLEASE stop creating 'all project bugs'. i
> don't w
On Wed, Sep 21, 2016 at 12:31 AM Adrian Turjak
wrote:
> The default keystone policy up until Newton doesn't let a user get their
> own user
>
This seems to be the crutch of your issue - can you provide an example of
this specific failure and the corresponding policy? As far as I'm aware,
the def
Hello,
it's definately our bad that we missed elections in OpenStackSalt
project. Reason is similar to Rob's - we are active on different
channels (mostly IRC as we keep regular meetings) and don't used to
reading mailing lists with lots of generic topics (it would be good to
have separate mailing
-Original Message-
From: Rob C
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 21, 2016 at 07:19:40
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [security] [salt] Removal of Security and
OpenStack
I have a basic question about tempest.
When I run a tempest test/scenario-test, should I see the components (network,
subnet, router etc.) in the horizon GUI ?
If yes, for what username or what project those are created ?
Thank you,
Ofer
Hi,
So I am recent elected core to the security group, so while obviously
pro OSSG-Sec, I also have a fairly fresh perspective of the group.
I would first off all not agree on disengagement with the community.
Well at least not from my perspective.
Since I joined I have found the group welcoming
On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote:
> Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P:
>> I am currently using python-cinderclient version 1.5.0, though the code in
>> question is still in master.
>>
>> When calling client.services.list() I get this result: "At
On 14/09/16 11:44, Mike Bayer wrote:
On 09/14/2016 11:08 AM, Mike Bayer wrote:
On 09/14/2016 09:15 AM, Sean Dague wrote:
I noticed the following issues happening quite often now in the
opportunistic db tests for nova -
http://logstash.openstack.org/#dashboard/file/logstash.json?query=messag
2016-09-21 14:37 GMT+03:00 Thierry Carrez :
> Ilya Shakhat wrote:
> > Hi,
> >
> > tldr; Commits stats are significantly skewed by deb-* projects
> > (http://stackalytics.com/?metric=commits&module=packaging-deb-group)
> >
> > By default Stackalytics processes commits from project's master branch.
Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko:
> On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote:
> >
> > Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P:
> > >
> > > I am currently using python-cinderclient version 1.5.0, though the code in
> > > question
On 09/20/2016 10:30 PM, Ilya Shakhat wrote:
> Hi,
>
> tldr; Commits stats are significantly skewed by deb-* projects
> (http://stackalytics.com/?metric=commits&module=packaging-deb-group)
>
> By default Stackalytics processes commits from project's master branch.
> For some "old core" projects th
Thanks, the comment and function name led me to think it was supposed
to only return the matching group.
So I will keep current 1.3 version in the L2 agent extension then!
On 20 September 2016 at 20:48, Cathy Zhang wrote:
> Hi Bernard,
>
> Networking-sfc currently uses OF1.3. Although OF1.3 dumps
Keystoners and Keystone enthusiasts,
We're tracking ideas for design sessions on an etherpad [1] -- so please
help populate the etherpad!
The ideas will then be prioritized and grouped together into fishbowl
sessions (tokens, authorization, operators, authentication, etc) at a later
date.
[1] ht
-Original Message-
From: Thomas Goirand
Reply: OpenStack Development Mailing List (not for usage questions)
Date: September 21, 2016 at 08:40:07
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [stackalytics] [deb] [packaging] OpenStack
On 21/09/16 03:30, Akihiro Motoki wrote:
Hi,
The default policy.json provided by heat limits 'service-list' API to
'admin' project like below.
Is there any reason 'admin' role user in non-'admin' project cannot
see service-list?
https://bugs.launchpad.net/keystone/+bug/968696
"service:ind
On 09/21/2016 03:32 PM, Konstanski, Carlos P wrote:
> Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko:
>> On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote:
>>> Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P:
I am currently using python-cinderclient vers
Am Mittwoch, den 21.09.2016, 15:49 +0200 schrieb Michał Dulko:
>
> On 09/21/2016 03:32 PM, Konstanski, Carlos P wrote:
> >
> > Am Mittwoch, den 21.09.2016, 15:07 +0200 schrieb Michał Dulko:
> > >
> > > On 09/21/2016 02:32 AM, Konstanski, Carlos P wrote:
> > > >
> > > > Am Dienstag, den 20.09.20
Nope, default keystone policy has not allowed you to get your own user until this patch was merged:
https://github.com/openstack/keystone/commit/c990ec5c144d9b1408d47cb83cb0b3d6aeed0d57
Sad but true it seems. :(
On 22/09/2016 12:58 AM, Dolph Mathews wrote:
>
>
>
> On Wed, Sep 21, 2016 at 12:31 AM
Forgot to add the commit reference :)
[1] https://review.openstack.org/#/c/368244/
On Wed, Sep 21, 2016 at 10:59 AM, Rodrigo Duarte
wrote:
> After some investigation I've found the possible issue: the functional
> tests run in parallel, some of them create and delete roles and others use
> toke
On Wed, Sep 21, 2016 at 8:59 AM, Rodrigo Duarte
wrote:
> After some investigation I've found the possible issue: the functional
> tests run in parallel, some of them create and delete roles and others use
> tokens to perform the creation/update/delete of other types of fixtures.
> The problem is
On Wed, Sep 21 2016, Amrith Kumar wrote:
> Over time, the result generally is that these developers' changes get ignored.
> And that's not a good thing for the community as a whole. We want to be a
> welcoming community and one which values all contributions so I'm looking for
> some suggestions a
After some investigation I've found the possible issue: the functional
tests run in parallel, some of them create and delete roles and others use
tokens to perform the creation/update/delete of other types of fixtures.
The problem is that when we delete a role, we also revoke *all* tokens from
a us
On 9/20/16, 11:18 AM, "Haïkel" wrote:
2016-09-19 19:40 GMT+02:00 Jeffrey Zhang :
> Kolla core reviewer team,
>
> Kolla supports multiple Linux distros now, including
>
> * Ubuntu
> * CentOS
> * RHEL
> * Fedora
> * Debian
> * OracleLinux
>
> B
Hello,
in addition to this, please, PLEASE stop creating 'all project bugs'. i
don't want to get emails on updates to projects unrelated to the ones i
care about. also, it makes updating the bug impossible because it times
out. i'm too lazy to search ML but this has been raise before, please sto
The OpenStack UX team will be giving a results presentation from a series
of interviews intended to understand how operators manage quotas at scale
as well as the pain points associated with that process. The study was
conducted by Danielle (IRC: uxdanielle) and included operators from CERN,
Pacif
I have been looking at some of the stackviz output as I'm trying to improve
the run time of my thrid-party CI. As an example:
http://logs.openstack.org/36/371836/1/check/gate-tempest-dsvm-full-ubuntu-xenial/087db0f/logs/stackviz/#/stdin/timeline
What jumps out is the amount of time that each wo
I just hit that TimeoutException error in neutron functional tests:
http://logs.openstack.org/68/373868/4/check/gate-neutron-dsvm-functional-ubuntu-trusty/4de275e/testr_results.html.gz
It’s a bit weird that we hit that 180 sec timeout because in good runs, the
test takes ~5 secs.
Do we have
Nova has policy defaults in code now and we can generate the sample
using oslopolicy-sample-generator but we'd like to get the default
policy sample in the Nova developer documentation also, like we have for
nova.conf.sample.
I see we use the sphinxconfiggen extension for building the
nova.co
Excerpts from Rob C's message of 2016-09-21 13:17:07 +0100:
> For my part, I missed the elections, that's my bad. I normally put a
> calendar item in for that issue. I don't think that my missing the election
> date should result in the group being treated in this way. Members of the
> TC have cont
On 09/19/2016 01:21 PM, Steven Hardy wrote:
> Hi Alex,
>
> Firstly, thanks for this detailed feedback - it's very helpful to have
> someone with a fresh perspective look at the day-1 experience for TripleO,
> and while some of what follows are "know issues", it's great to get some
> perspective
> On Sep 21, 2016, at 8:58 AM, Filip Pytloun wrote:
>
> Hello,
>
> it's definately our bad that we missed elections in OpenStackSalt
> project. Reason is similar to Rob's - we are active on different
> channels (mostly IRC as we keep regular meetings) and don't used to
> reading mailing lists w
What if policy will be manageable using RESTful API?
I'd like to validate the idea to handle policies in keystone or
affiliated service: https://review.openstack.org/#/c/325326/
On 21.09.2016 17:49, Matt Riedemann wrote:
Nova has policy defaults in code now and we can generate the sample
using
On Wed, Sep 21, 2016 at 10:44:51AM -0400, Bob Hansen wrote:
>
>
> I have been looking at some of the stackviz output as I'm trying to improve
> the run time of my thrid-party CI. As an example:
>
> http://logs.openstack.org/36/371836/1/check/gate-tempest-dsvm-full-ubuntu-xenial/087db0f/logs/stac
On 9/21/2016 10:05 AM, Alexander Makarov wrote:
What if policy will be manageable using RESTful API?
I'd like to validate the idea to handle policies in keystone or
affiliated service: https://review.openstack.org/#/c/325326/
On 21.09.2016 17:49, Matt Riedemann wrote:
Nova has policy defaults i
Excerpts from Matt Riedemann's message of 2016-09-21 09:49:29 -0500:
> Nova has policy defaults in code now and we can generate the sample
> using oslopolicy-sample-generator but we'd like to get the default
> policy sample in the Nova developer documentation also, like we have for
> nova.conf.s
Hello everyone,
The release candidate for Ceilometer for the end of the Newton cycle
is available! You can find the RC2 source code tarball at:
https://tarballs.openstack.org/ceilometer/ceilometer-7.0.0.0rc2.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin,
On 09/21/2016 05:17 AM, Rob C wrote:
> Apart from missing elections, I think we do a huge amount for the community
> and removing us from OpenStack would in no way be beneficial to either the
> Security Project or OpenStack as a whole.
I definitely agree with Rob here and I support keeping the S
On Wed, Sep 21, 2016, at 11:05 AM, Alexander Makarov wrote:
> What if policy will be manageable using RESTful API?
> I'd like to validate the idea to handle policies in keystone or
> affiliated service: https://review.openstack.org/#/c/325326/
As Matt said, that's unrelated to what he's asking
Zane Bitter wrote:
On 14/09/16 11:44, Mike Bayer wrote:
On 09/14/2016 11:08 AM, Mike Bayer wrote:
On 09/14/2016 09:15 AM, Sean Dague wrote:
I noticed the following issues happening quite often now in the
opportunistic db tests for nova -
http://logstash.openstack.org/#dashboard/file/logsta
Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
> Hello,
>
> it's definately our bad that we missed elections in OpenStackSalt
> project. Reason is similar to Rob's - we are active on different
> channels (mostly IRC as we keep regular meetings) and don't used to
> reading mail
Thanks. After I sent the mail, we had a good conversation with Rabi and
understood the whole background.
Horizon will try to support better keystone v3 support in Ocata cycle.
2016-09-21 22:47 GMT+09:00 Zane Bitter :
> On 21/09/16 03:30, Akihiro Motoki wrote:
>
>> Hi,
>>
>> The default policy.jso
Hello,
> With 59 separate teams, even emailing the PTLs directly is becoming
> impractical. I can’t imagine trying to email all of the core members directly.
>
> A separate mailing list just for “important announcements” would need someone
> to decide what is “important”. It would also need eve
On 09/21/2016 11:41 AM, Joshua Harlow wrote:
I've seen something similar at https://review.openstack.org/#/c/316935/
Maybe its time we asked again why are we still using eventlet and do we
need to anymore. What functionality of it are people actually taking
advantage of? If it's supporting li
Andrew Laski wrote:
However, I have asked twice now on the review what the benefit of doing
this is and haven't received a response so I'll ask here. The proposal
would add additional latency to nearly every API operation in a service
and in return what do they get? Now that it's possible to regi
Mike Bayer wrote:
On 09/21/2016 11:41 AM, Joshua Harlow wrote:
I've seen something similar at https://review.openstack.org/#/c/316935/
Maybe its time we asked again why are we still using eventlet and do we
need to anymore. What functionality of it are people actually taking
advantage of? If
FWIW, there was no new failures in Nova jobs since then.
I'm confused as well why these tests would sporadically take much
longer time to execute. Perhaps we could install something like atop
on our nodes to answer that question.
On Wed, Sep 21, 2016 at 5:46 PM, Ihar Hrachyshka wrote:
> I just h
ccess API, allowing manila to support IPv6
ACL.
Hi all of the driver maintainers, could you test the IPv6 feature code[2]
to make sure whether your driver can completely support IPv6.
If there still have something else might not be IPv6-ready, please let me
known. Thanks
[1] https://review.openstack.org/#/
But something else struck me, the velocity and sheer NUMBER of emails that
must be filtered to find and extract these key announcements is tricky so I
don't fault anyone for missing the needle in the haystack. Important needle
no doubt but I wonder if there are more efficient ways to ensure importa
You know something that struck me, I noticed there were several teams last
cycle that did not elect a PTL so this round I was watching to see if any
teams did not have a PTL elected and presumed it was because of many of the
reasons surfaced in previous emails in this thread including being heads
d
On Wed, Sep 21, 2016 at 9:00 AM, John Trowbridge wrote:
>
>
>
> On 09/19/2016 01:21 PM, Steven Hardy wrote:
> > Hi Alex,
> >
> > Firstly, thanks for this detailed feedback - it's very helpful to have
> > someone with a fresh perspective look at the day-1 experience for TripleO,
> > and while some
Matthew, this helps tremendously. As you can tell the conclusion I was
heading towards was not accurate.
Now to look a bit deeper.
Thanks,
Bob Hansen
z/VM OpenStack Enablement
Matthew Treinish wrote on 09/21/2016 11:07:04 AM:
> From: Matthew Treinish
> To: "OpenStack Development Mailing List
On Wed, Sep 21, 2016 at 9:03 AM Adrian Turjak
wrote:
> Nope, default keystone policy has not allowed you to get your own user
> until this patch was merged:
>
> https://github.com/openstack/keystone/commit/c990ec5c144d9b1408d47cb83cb0b3d6aeed0d57
>
> Sad but true it seems. :(
>
Wow, you're right!
Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700:
> Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
> > Hello,
> >
> > it's definately our bad that we missed elections in OpenStackSalt
> > project. Reason is similar to Rob's - we are active on different
> > chan
xt/plain; charset="utf-8"
Hi,
As agreed by the manila community in IRC meeting,
we try to enable IPv6 in Ocata. Please check the brief spec[1] and code[2]).
The areas affected most are API (access rules) and in the drivers (access
rules
& export locations). This change intends t
Hello,
Now, when we have full list of sessions, let's prioritize them
accordingly to our preferences. Based on this we'll allocate our
summit space.
http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_8368e1e74f8a0049&akey=91bbcf4baeff0a2f
On Wed, Sep 21, 2016, at 12:02 PM, Joshua Harlow wrote:
> Andrew Laski wrote:
> > However, I have asked twice now on the review what the benefit of doing
> > this is and haven't received a response so I'll ask here. The proposal
> > would add additional latency to nearly every API operation in a
On Sep 21, 2016 09:37, "Adam Lawson" wrote:
>
> But something else struck me, the velocity and sheer NUMBER of emails
that must be filtered to find and extract these key announcements is tricky
so I don't fault anyone for missing the needle in the haystack. Important
needle no doubt but I wonder i
Excerpts from Filip Pytloun's message of 2016-09-21 17:43:46 +0200:
> Hello,
>
> > With 59 separate teams, even emailing the PTLs directly is becoming
> > impractical. I can’t imagine trying to email all of the core members
> > directly.
> >
> > A separate mailing list just for “important annou
gt; To: openstack-dev
> Subject: [openstack-dev] [manila] Enable IPv6 in Manila Ocata
> Message-ID:
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> As agreed by the manila community in IRC meeting,
> we try to enable IPv6 in Ocata. Please check
One note in this poll. Repo-split has already reached a consensus decision via
ml vote, and the activity around that will happen prior to summit, so it is
probably worth ignoring entirely.
Regards
-steve
On 9/21/16, 10:14 AM, "Michał Jastrzębski" wrote:
Hello,
Now, when we have
On Wed, Sep 21, 2016 at 11:16 PM, Steven Dake (stdake) wrote:
> One note in this poll. Repo-split has already reached a consensus decision
> via ml vote, and the activity around that will happen prior to summit, so it
> is probably worth ignoring entirely.
>
> Regards
> -steve
>
>
> On 9/21/16,
On 2016-09-21 15:41:11 +1000 (+1000), Tony Breeds wrote:
> On Tue, Sep 20, 2016 at 11:57:26AM +0100, Daniel P. Berrange wrote:
[...]
> > (3) Do nothing, leave the bug unfixed in stable/liberty
> >
> > While this is a security bug, it is one that has existed in every single
> > openstack release
On 09/21/2016 02:03 PM, Jeremy Stanley wrote:
> On 2016-09-21 15:41:11 +1000 (+1000), Tony Breeds wrote:
>> On Tue, Sep 20, 2016 at 11:57:26AM +0100, Daniel P. Berrange wrote:
> [...]
>>> (3) Do nothing, leave the bug unfixed in stable/liberty
>>>
>>> While this is a security bug, it is one that
This week at the TC meeting someone (Anne?) pointed out that the
name of the etherpad with the list of community-wide goals wasn't
ideal ("ocata-tc-goals" includes the cycle name and the "tc" component
gives the impression that these are goals of the "TC" rather than
that the pad was used by the TC
> Source code is here: https://github.com/abashmak/chrome-irc-filter
>
> Comments, suggestions are welcome.
Nice thanks!
I've always wanted a tool that could alert me of "missed mentions" when
I'm offline IRC rather than having to manually parse the IRC logs for
those times I'm offline. However
n zhong
> To: openstack-dev
> Subject: [openstack-dev] [manila] Enable IPv6 in Manila Ocata
> Message-ID:
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> As a
On Wed, Sep 21, 2016 at 1:04 PM, Dolph Mathews
wrote:
>
> I should also express a +1 for something along the lines of your original
> proposal. I'd go so far as to suggest that `openstack show user` (without a
> user ID or name as an argument) should return "me" (the authenticated
> user), as I t
On 2016/09/21 13:23, Doug Hellmann wrote:
> The idea of splitting the contributor list comes up pretty regularly
> and we rehash the same suggestions each time. Given that what we
> have now worked fine for 57 of the 59 offical teams (the Astara
> team knew in advance it would not have a PTL runni
On 21 September 2016 at 19:20, Chivers, Doug wrote:
> My concern is with the original wording “The suggested way forward there
> would be to remove the "Security project team"”.
>
> This seems like a move to instantly reduce investment in OpenStack
> security, because the majority of members of t
once again [1]. Note
> > > that was before the name "brick" was hijacked and now means something
> > > completely different.
> > >
> > > [1]: https://wiki.openstack.org/wiki/CinderBrick
> > >
> > > Thanks,
> &g
Danielle – I think this is good, but if you are not getting the level of
participation you want…or commitment to follow-on actions, I would suggest you
adopt a “go to them” strategy.
Thanks
Carol
From: Danielle Mundle [mailto:danielle.m.mun...@gmail.com]
Sent: Wednesday, September 21, 2016 7:42
"So all this said, there are individuals interested in the PTL role to
ensure project teams have someone handling the logistics and coordination.
My issue however was that I was not yet eligible to be a candidate which
I'll remedy moving forward.
I'm still interested in serving as a PTL for a proj
Excerpts from Filip Pytloun's message of 2016-09-21 20:36:42 +0200:
> On 2016/09/21 13:23, Doug Hellmann wrote:
> > The idea of splitting the contributor list comes up pretty regularly
> > and we rehash the same suggestions each time. Given that what we
> > have now worked fine for 57 of the 59 of
On 2016-09-21 14:05:51 -0400 (-0400), Sean Dague wrote:
[...]
> Well, the risk profile of what has to be changed for stable/liberty
> (given that all the actual code is buried in libraries which have tons
> of other changes). Special cherry-picked library versions would be
> needed to fix this with
Andrew Laski wrote:
On Wed, Sep 21, 2016, at 12:02 PM, Joshua Harlow wrote:
Andrew Laski wrote:
However, I have asked twice now on the review what the benefit of doing
this is and haven't received a response so I'll ask here. The proposal
would add additional latency to nearly every API operat
That's a good idea, I was just thinking along the same lines today. It's
definitely out of the scope of my tool, though. Some targeted filtering could
be implemented, but it would still be in "offline" mode. If you want it live,
then perhaps some IRC clients offer that functionality or maybe the
Hello all,
it took us 2 years of hard working to get these official. OpenStack-Salt
is now used by around 40 production deployments and it is focused very
on operation and popularity is growing. You are removing the project
week after one of top contributor announced that they will use that as
On Wed, Sep 21, 2016, at 03:18 PM, Joshua Harlow wrote:
> Andrew Laski wrote:
> >
> > On Wed, Sep 21, 2016, at 12:02 PM, Joshua Harlow wrote:
> >> Andrew Laski wrote:
> >>> However, I have asked twice now on the review what the benefit of doing
> >>> this is and haven't received a response so I'l
Travis,
My answer would be -that- is the most ideal scenario. I care about
OpenStack and ensuring quality projects have adequate representation so I
checked to see which ones didn't have anyone defined for leadership and
picked one to step in and help, assuming no one was able to fill that role
fo
On 21/09/16 01:43 AM, Zhai, Edwin wrote:
> All,
>
> I'd like make some clarification for the event-alarm timeout design as
> many of you have some misunderstanding here. Pls. correct me if any
> mistakes.
>
> I realized that there are 2 different things, but we mix them sometime:
> 1. event-timeo
Thomas Goirand wrote:
> I don't understand why Stackalytics has it wrong, when the electorate
> script for the PTL election is correct. Here's the script for getting
> commits:
> https://github.com/openstack-infra/system-config/blob/master/tools/owners.py
AFAIK that is because Stackalytics works f
1 - 100 of 147 matches
Mail list logo
