Excerpts from Matt Riedemann's message of 2016-09-21 18:43:06 -0500:
> The s3 image configuration options were deprecated for removal in newton
> [1].
>
> Clint has a patch up to remove the boto dependency from nova [2] which
> is only used in the nova.image.s3 module.
>
> Rather than remove th
Gordon,
Thanks for your comments.
Pls. check my answer and flow chart below.
On Wed, 21 Sep 2016, gordon chung wrote:
=== event-alarm timeout implementation =
As it's for event-alarm, we need keep it as event-driven. Furthermore,
for quick response, we need use event for ti
Folks,
We want to be inviting to new contributors even if they are green. New
contributors reflect on OpenStack’s growth in a positive way. The fact that a
new-to-openstack contributor would make such and error doesn’t warrant such a
negative response even if it a hassle for the various PTLs
On Wed, Sep 21, 2016 at 02:05:51PM -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 witho
Hi Ofer,
Tempest tests try to cleanup after themselves, so in theory after a Tempest
run you shouldn't see any test resource left around.
If you run your tests using dynamic credentials, test accounts are created
on the fly, and deleted after they're used. If you use preprovisioned
credentials, y
Hi Ofer,
The scenario test of Horizon has been removed from Tempest since
https://review.openstack.org/#/c/313713/
And now the test[1] exists in openstack/tempest-horizon.
The test is very simple like
* checks that the login page is available
* logs in as a regular user
* checks that the user h
Hi,
As previous mail, Marc has resigned from tempest-cores.
In addition, David also has done from tempest-cores to concentrate on new work.
Thank you two for many contributions to the project and I wish your
continuous successes.
Thanks
Ken Ohmichi
___
Hi Marc,
Thanks for hosting a QA/Infra code sprint.
All attendees have been satisfied with rooms, coffee, food and weather.
And thanks for your work on QA project in long term.
You have brought a lot of value to us.
Thanks
Ken Ohmichi
2016-09-19 11:51 GMT+02:00 Koderer, Marc :
> Hi folks,
Michal,
Thanks for setting this up. For future votes using civs, I’d recommend keeping
polling results hidden until the poll is completed as to not unduly influence
voters by the current incomplete polling results.
If folks would like to use civs in favor of our current mailing list voting
us
Doug,
Apologies for top post – email client upgrade broke my ability to post inline
(working on getting a revert or further instructions on how to re-enable proper
function).
Based upon your guidance, I wanted to inform you a decision has been made on
our RC2 deadline – which is October 10th-O
Join us tomorrow (Thursday) for our weekly meeting, scheduled for
September 22nd at 17:00UTC in #openstack-meeting-3
The agenda can be found here, and please add to if you want to discuss
something with the Community App Catalog team:
https://wiki.openstack.org/wiki/Meetings/app-catalog
As has be
On 09/21/2016 07:43 PM, Matt Riedemann wrote:
The s3 image configuration options were deprecated for removal in newton
[1].
Clint has a patch up to remove the boto dependency from nova [2] which
is only used in the nova.image.s3 module.
Rather than remove the boto dependency, I think we should
Hello,
During yesterday's weekly meeting, patches were identified for these must be
merged before freeze date for Newton release:
Freeze date: Sept.30, 2016
Must to have: must be merged before Sept.30, basic feature for Tricircle Newton
release
https://review.openstack.org/#/c/356187/ framewor
Hi,
On Wed, Sep 21, 2016 at 10:49 AM, Matt Riedemann
wrote:
> 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
The s3 image configuration options were deprecated for removal in newton
[1].
Clint has a patch up to remove the boto dependency from nova [2] which
is only used in the nova.image.s3 module.
Rather than remove the boto dependency, I think we should just remove
this code. Is there any reason
"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
for that s
On 22/09/16 10:45, Steve Martinelli wrote:
> On Wed, Sep 21, 2016 at 6:34 PM, Adrian Turjak
> mailto:adri...@catalyst.net.nz>> wrote:
>
> - or update "openstack project list" with a "--auth-user" flag
> that ignores all other options and directly filters the project
> list by your token
Hi folks,
Not long to go before the Ocata summit. We'll devote next week's team
meeting[1] to discussing the design sessions. If you haven't done so
already, please add your thoughts to the planning etherpad[2].
Thanks,
Richard
[1] https://wiki.openstack.org/wiki/Meetings/Horizon
[2] http
On Wed, Sep 21, 2016 at 6:34 PM, Adrian Turjak
wrote:
>
>
> What I'd like to do is one of these two options:
> - "openstack user project list", a command which will get your id from
> your authed token and used it directly with the keystoneclient as such:
> "keystoneclient.projects.list(user='')
Worth noting, I have been playing with 3.2.0 and the same problem
persists in our deployment which is running a variant of the old default
keystone policy.
On 22/09/16 10:34, Adrian Turjak wrote:
> That commit doesn't really address the problem in question though.
>
> The problem is that the Open
That commit doesn't really address the problem in question though.
The problem is that the OpenStack client assumes the "get user" policy
in Keystone allows you to get your own user, which it didn't until
Newton, and thus a lot of deployments probably are using the default
policy or some variant t
On 2016-09-21 22:53:10 +0100 (+0100), Dave Walker wrote:
> On 21 September 2016 at 22:41, Kyle Mestery wrote:
> > On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> > wrote:
> > > I privately received information that explains why the PTL was
> > > not on top of things during election weeks. With
Excerpts from Dave Walker's message of 2016-09-21 22:53:10 +0100:
> On 21 September 2016 at 22:41, Kyle Mestery wrote:
>
> > On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> > wrote:
> > > Chivers, Doug wrote:
> > >> My concern is with the original wording “The suggested way forward
> > there w
Jeremy hit all the major points there.
What we do is basically model things based on a best-practice use case, we
rely on the project to make good choices in this regard with a view to
configurations, protocols etc.
Then we conduct an asset-oriented threat review, during which we create
documenta
On 21 September 2016 at 22:41, Kyle Mestery wrote:
> On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez
> wrote:
> > 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
On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez wrote:
> 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,
>> beca
On 2016-09-21 10:18:58 -0700 (-0700), Morgan Fainberg wrote:
[...]
> For what it is worth the VMT had some discussion about this and in the case
> the security team was/is dissolved/moved to a WG we will take some action
> and make some proposals to handle the situation so we have a nice place to
>
On 22 September 2016 at 00:23, John Griffith
wrote:
>
> Yes, that is a sizeable chunk of the solution. The remaining components
> are how to coordinate with Nova (compute nodes) and figuring out if we just
> use c-vol as is, or if we come up with some form of a paired down agent.
> Just using c-
On Wed, Sep 21, 2016 at 12:57 AM, Michał Dulko
wrote:
> 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>>
On 21/09/16 11:41, Joshua Harlow wrote:
tl;dr this appears to have been around forever (at least since we
switched to using a pure-Python MySQL client) and is almost certainly
completely unrelated to any particular release of oslo.db.
Update: Mike was kind enough to run this one to ground and i
So this is happening:
https://review.openstack.org/#/c/374395/
Any feedback in the review is welcome!
On Thu, Aug 11, 2016 at 3:24 PM, Emilien Macchi wrote:
> On Tue, Aug 9, 2016 at 1:39 PM, Emilien Macchi wrote:
>> Hi,
>>
>> Today Puppet OpenStack CI is running unit and functional test jobs
>>
On Wed, Sep 21, 2016 at 6:49 AM, Giulio Fidente wrote:
> 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
On Wed, Sep 21, 2016 at 5:13 PM, Cody Herriges wrote:
>
> On September 21, 2016 at 03:49:58, Giulio Fidente (gfide...@redhat.com)
> wrote:
>>
>> On 09/19/2016 10:49 PM, Emilien Macchi wrote:
>>
>> (adding puppet tag for cross project session).
>>
>> Let's continue to prepare TripleO sessions.
>>
>
On 2016-09-21 22:04:46 +0200 (+0200), Thierry Carrez wrote:
> 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/b
Jakub,
Please see below.
On Wed, Sep 21, 2016 at 3:46 PM, Jakub Pavlik wrote:
> 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 remov
Sean Dague wrote:
> On 09/15/2016 09:20 AM, Roman Podoliaka wrote:
>> Sean,
>>
>> So currently we have a default timeout of 160s in Nova. And
>> specifically for migration tests we set a scaling factor of 2. Let's
>> maybe give 2.5 or 3 a try ( https://review.openstack.org/#/c/370805/ )
>> and mak
On Wed, Sep 21, 2016, at 04:18 PM, Joshua Harlow wrote:
> Andrew Laski wrote:
> >
> > 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 o
Please see below.
On Wed, Sep 21, 2016 at 4:35 PM, Thierry Carrez wrote:
> 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
Hello all,
We have our weekly OSSP IRC meeting tomorrow at 1700UTC (1200 Central) in
#openstack-meeting-alt. This thread has raised some important issues, and
we will devote a significant portion of our meeting to discussing them. My
IRC handle is "ccneill" on freenode if you'd like to get in touc
On Wed, 21 Sep 2016, Boden Russell wrote:
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 I'm guessing that falls outside the
scope of this tool or could be done with so
Sure, I simply pasted what was in the etherpad. I didn't want to cut
anything out as some things might be seemingly closed but people in
fact would like to talk more about them. Let see how priorities will
look like after couple days:)
Also, please vote!
On 21 September 2016 at 12:54, Swapnil Kul
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 the Security Project are corpo
Hi all,
I ran into this issue when Congress or Horizon attempts to get information
from Nova. Same thing happened on multiple devstack attempts. But I want to
make sure it's not something specific to my environment. Could someone try
to reproduce it? Thanks!
Nova client version: 6.0.0
Here¹s a bug
On 9/21/2016 6:56 AM, Amrith Kumar wrote:
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
Jakub Pavlik wrote:
> 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
Hello,
I'd like to turn attention to the broken port rule masking problem [1],
which affects 2 projects so far:
neutron (mitaka+ with ovs firewall driver configuration) and
networking-ovs-dpdk [2].
To keep it short: the existing port masking implementation is broken and in
several cases it will e
Andrew Laski wrote:
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'll
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
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
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 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
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
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
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
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
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
"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
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
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
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
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 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
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
> 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
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
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
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 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,
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
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
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
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
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
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
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
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
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!
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: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
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
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
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/#/
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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 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
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
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
1 - 100 of 147 matches
Mail list logo