Good news! We just got the final revision for our official keystone mascot
[0]!
I have a note on my todo list to put together a basic chart deck with them.
I'll send out a link for folks to use when I get them done.
[0] https://www.dropbox.com/sh/0owldvy0u5y4yk9/AAB5Q95wYj-
oaiisneKbnEiDa?dl=0
__
Hi all,
I wanted to remind everyone that we won't have our weekly meeting next week
(2017-02-21), since most of us with either be at the PTG or in transit.
Anything we need to talk about will be done in person.
We will pick back up on the 26th.
Thanks,
Lance
In addition to what David said, have you played around with caching in
keystone [0]? After the initial implementation of fernet landed, we
attempted to make it the default token provider. We ended up reverting the
default back to uuid because we hit several issues. Around the Liberty and
Mitaka tim
Since a bunch of us are going to be at the PTG next week, we can hold
policy discussions face-to-face.
Our next policy meeting will take place on March 1st.
Safe travels!
__
OpenStack Development Mailing List (not for usage q
On Wed, Feb 15, 2017 at 1:11 PM, Matt Riedemann wrote:
> On 2/15/2017 12:07 PM, Sajeesh Cimson Sasi wrote:
>
>> Hi Matt, Andrey,
>> CERN-BARC team was working on nested quota
>> implementation in Nova some 3 years back.But at that time, it was decided
>> to fix bugs in the
Hi all,
I tried to get most of our things shuffled around into some-what of a
schedule [0]. Everything that was on the list was eventually refactored
into the agenda.
I've broken the various topics out into their own etherpads and linked them
back to the main schedule. We should have the freedom
Keep the feedback coming. Thanks!
[0] https://etherpad.openstack.org/p/pike-ptg-keystone-ocata-carry-over
On Wed, Feb 15, 2017 at 10:24 PM, Lance Bragstad
wrote:
> Hi all,
>
> I tried to get most of our things shuffled around into some-what of a
> schedule [0]. Everything that was on t
https://etherpad.openstack.org/p/keystone-pike-ptg
>
> On Wed, Feb 15, 2017 at 9:08 AM Lance Bragstad
> wrote:
>
>> In addition to what David said, have you played around with caching in
>> keystone [0]? After the initial implementation of fernet landed, we
>> att
On Fri, Feb 17, 2017 at 11:22 AM, Clint Byrum wrote:
> Excerpts from 王玺源's message of 2017-02-17 14:08:30 +:
> > Hi David:
> >
> > We have not find the perfect solution to solve the fernet performance
> > issue, we will try the different crypt strength setting with fernet in
> > future.
> >
>
with another project).
Don't hesitate to ping me if you have any questions about the schedule and
safe travels to Atlanta!
[0] https://etherpad.openstack.org/p/keystone-pike-ptg
On Thu, Feb 16, 2017 at 1:40 PM, Lance Bragstad wrote:
> Based on early feedback I've broken up our first
Also - I just got word that keystone's project room for Wednesday through
Friday will be Georgia 13 located on the first floor. I've updated the
schedule with the location for all sessions we plan to have in that room.
On Mon, Feb 20, 2017 at 8:50 AM, Lance Bragstad wrote:
> Late
As you may have noticed from other threads, we have some early feedback
available from the User Survey. It hasn't closed yet - and I'm sure we'll
get updated results once that happens, but the early feedback will be nice
to have going into project discussions at the PTG.
The question and responses
Hi all,
Keystone recently took a big step in implementing the default roles work
that's been a hot topic over the past year [0][1][2][3][4], and a big
piece in making RBAC more robust across OpenStack. We merged a patch [5]
that ensures the roles described in the specification [6] exist. This
was
Keystone is hitting this, too [0]. I attempted the same solution that
Tony posted, but no luck. I've even gone so far as removing every
comment from the module to see if that helps narrow down the problem
area, but sphinx still trips. The output from the error message isn't
very descriptive either.
[0].
[0] https://review.openstack.org/#/c/577974/
On 06/25/2018 07:27 PM, Tony Breeds wrote:
> On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote:
>> Keystone is hitting this, too [0]. I attempted the same solution that
>> Tony posted, but no luck. I've even gone so fa
our build [1].
[0] https://github.com/oauthlib/oauthlib/issues/558
[1] https://review.openstack.org/#/c/577974/
>
>> Doug
>>
>>> On 06/25/2018 07:27 PM, Tony Breeds wrote:
>>>> On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote:
>>>>> Ke
On 06/28/2018 02:09 PM, Fox, Kevin M wrote:
> I'll weigh in a bit with my operator hat on as recent experience it pertains
> to the current conversation
>
> Kubernetes has largely succeeded in common distribution tools where OpenStack
> has not been able to.
> kubeadm was created as a way t
Hi all,
Today we added Wangxiyuan to the keystone core team [0]. He's been doing
a bunch of great work over the last couple releases and has become a
valuable reviewer [1][2]. He's also been instrumental in pushing forward
the unified limits work not only in keystone, but across projects.
Thanks
It's getting to be that time of the release (and I'm seeing other
etherpads popping up on the mailing list). I've created one specifically
for keystone [0].
Same drill as the last two PTGs. We'll start by just getting topics
written down and I'll group similar topics into buckets prior to
building
Hey all,
As noted in the weekly report [0], today is feature freeze for
keystone-related specifications. I wanted to elaborate on each
specification so that our plan is clear moving forward.
*Unified Limits**
**
*I propose that we issue a feature freeze exception for this work.
Mainly because the
On 07/13/2018 03:37 PM, Johannes Grassler wrote:
> Hello,
>
> On Fri, Jul 13, 2018 at 02:19:35PM -0500, Lance Bragstad wrote:
>> *Capability Lists**
>> *
>> The capability lists involves a lot of work, not just within keystone,
>> but also keystonemiddleware, whi
On 07/13/2018 02:37 PM, Harry Rybacki wrote:
> On Fri, Jul 13, 2018 at 3:20 PM Lance Bragstad wrote:
>> Hey all,
>>
>> As noted in the weekly report [0], today is feature freeze for
>> keystone-related specifications. I wanted to elaborate on each specification
&
36 (keystone:Undecided) opened by Pawan Gupta
> https://bugs.launchpad.net/keystone/+bug/1781536
>
> Bugs closed (0)
>
> Bugs fixed (4)
> Bug #1765193 (keystone:Medium) fixed by wangxiyuan
> https://bugs.launchpad.net/keystone/+bug/1765193
> Bug #1780159 (ke
Hey everyone,
I'm writing to submit my self-nomination as keystone's PTL for the Stein
release.
We've made significant progress tackling some of the major goals we set
for keystone in Pike. Now that we're getting close to wrapping up some
of those initiatives, I'd like to continue advocating for
# Keystone Team Update - Week of 23 July 2018
## News
This week wrapped up rocky-3, but the majority of the things working
through review are refactors that aren't necessarily susceptible to the
deadline.
## Recently Merged Changes
Search query: https://bit.ly/2IACk3F
We merged 32 changes this
Hey all,
I went through all bugs opened during the Rocky release and came up with
a list of ones that might be good to fix before next week [0]. The good
news is that more than half are in progress and none of them are release
blockers, just ones that would be good to get in.
Let me know if you s
# Keystone Team Update - Week of 30 July 2018
## News
This week was relatively quiet, but we're working towards RC1 as our
next deadline.
## Recently Merged Changes
Search query: https://bit.ly/2IACk3F
We merged 20 changes this week.
Mainly changes to continue moving APIs to flask and we land
On 08/02/2018 09:36 AM, Chris Dent wrote:
> On Thu, 2 Aug 2018, Stephen Finucane wrote:
>
>> Given that multiple projects are using this, we may want to think about
>> reaching out to the author and seeing if there's anything we can do to
>> at least keep this maintained going forward. I've talke
On 08/09/2018 12:18 PM, Matt Riedemann wrote:
> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
>> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
>>> For evidence, see:
>>>
>>> http://logs.openstack.org/41/590041/1/check/tempest-full-py3/db08dec/controller/logs/screen-placement-api.tx
On 08/09/2018 12:48 PM, Doug Hellmann wrote:
> Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
>> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
>>> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
For evidence, see:
http://logs.openstack.org/41/5900
; ## Bugs
>
> This week we opened 2 new bugs and closed 3. There don't currently seem to
> be any showstopper bugs for Rocky. orange_julius has been chasing a fun,
> apparently longstanding bug in ldappool[15], our traditionally low-effort
> adopted project.
>
> Bugs opened (2)
> Bug #
On 08/22/2018 03:23 AM, Adrian Turjak wrote:
> Bah! I saw this while on holiday and didn't get a chance to respond,
> sorry for being late to the conversation.
>
> On 11/08/18 3:46 AM, Colleen Murphy wrote:
>> ### Self-Service Keystone
>>
>> At the weekly meeting Adam suggested we make self-servi
ipermail/openstack-dev/2018-August/133610.html
>
> ## Bugs
>
> This week we opened 4 new bugs and closed 1.
>
> Bugs opened (4)
> Bug #1788415 (keystone:High) opened by Lance Bragstad
> https://bugs.launchpad.net/keystone/+bug/1788415
> Bug #1788694 (ke
On 08/22/2018 07:49 AM, Lance Bragstad wrote:
>
> On 08/22/2018 03:23 AM, Adrian Turjak wrote:
>> Bah! I saw this while on holiday and didn't get a chance to respond,
>> sorry for being late to the conversation.
>>
>> On 11/08/18 3:46 AM, Colleen Murphy w
I've worked through the list of topics and organized them into a rough
schedule [0]. As it stands right now, Monday is going to be the main
cross-project day (similar to the identity-integration track in Dublin).
We don't have a room on Tuesday and Wednesday, but we will likely have
continued cross
On Mon, Aug 27, 2018 at 2:37 PM Doug Hellmann wrote:
> This is week 3 of the "Run under Python 3 by default" goal
> (https://governance.openstack.org/tc/goals/stein/python3-first.html).
>
> == What we learned last week ==
>
> We have a few enthusiastic folks who want to contribute to the goal
> w
On Wed, Aug 29, 2018 at 1:16 PM Waines, Greg
wrote:
> Makes sense.
>
>
>
> So what is the recommended upstream approach for securely storing user
> passwords in keystone ?
>
Keystone will hash passwords before persisting them in their own table.
Encrypted passwords are never stored.
>
>
> Is t
Samuel,
Thanks for all the dedication and hard work upstream. I'm relieved that you
won't be too far away and that you're still involved with the Outreachy
programs. You played an instrumental role in getting keystone involved with
that community.
As always, we'd be happy to have you back in the
Juan Antonio Osorio Robles <
jaosor...@redhat.com> wrote:
> FWIW, instead of barbican, castellan could be used as a key manager.
>
> On 08/30/2018 12:23 PM, Adrian Turjak wrote:
>
>
> On 30/08/18 6:29 AM, Lance Bragstad wrote:
>
> Is that what is being described here ?
# Keystone Team Update - Week of 27 August 2018
## News
Welcome to Stein development!
## Release Status
Well, Rocky went out the door. A friendly reminder to keep an eye out for
bugs and things we should backport.
## PTG Planning
The topics in the PTG etherpad have been worked into a schedule
Hi all,
I'd like to submit my candidacy to be a member of the OpenStack Technical
Committee.
My involvement with OpenStack began during the Diablo release. Since then
I've participated in various parts of the community, in both upstream and
downstream roles. Today I mainly focus on authorizatio
Not yet. Keystone worked through a bunch of usability improvements with the
unified limits API last release and created the oslo.limit library. We have
a patch or two left to land in oslo.limit before projects can really start
using unified limits [0].
We're hoping to get this working with at leas
only one service?
> Is there some methods to move this more fast?
> Lance Bragstad 于2018年9月5日周三 下午9:29写道：
> >
> > Not yet. Keystone worked through a bunch of usability improvements with
> the unified limits API last release and created the oslo.limit library. We
> have a patch o
I can't believe it's already time to start thinking about forum topics, but
it's upon us [0]!
I've created an etherpad for us to brainstorm ideas that we want to bring
to the forum in Germany [1]. I also linked it to the wiki [2].
Please feel free to throw out ideas. We can go through them as a g
I wanted to send out a reminder that we won't be having formal office hours
or a team meeting next week due to the PTG. Both will resume on the 18th of
September.
Thanks,
Lance
__
OpenStack Development Mailing List (not for u
I'm noticing some odd cases with respect to the python 3 community goal
[0]. So far my findings are specific to keystone repositories, but I can
imagine this affecting other projects.
Doug generated the python 3 reviews for keystone repositories, including
the ones for stable branches. We noticed
The foundation just gave me a copy of the latest feedback from our users. I
wanted to share this with the group so people have time to digest it prior
to the PTG next week [0].
Here is the total count based on each response:
Federated identity enhancements had *184* responses
Performance improve
wrote:
> On Thu, Sep 06, 2018 at 03:01:01PM -0500, Lance Bragstad wrote:
> > I'm noticing some odd cases with respect to the python 3 community goal
> > [0]. So far my findings are specific to keystone repositories, but I can
> > imagine this affecting other projects.
/y6ucarwm
[3]
http://specs.openstack.org/openstack/keystone-specs/specs/keystone/rocky/strict-two-level-enforcement-model.html
[4]
https://review.openstack.org/#/q/project:openstack/oslo.limit+status:open
[5] https://review.openstack.org/#/c/600265/
[6]
http://logs.openstack.org/65/600265/3/check/openstack-t
Bug #1790423 (python-keystoneclient:Undecided) opened by ChenWu
https://bugs.launchpad.net/python-keystoneclient/+bug/1790423
- Bug #1790931 (oslo.limit:Medium) opened by Lance Bragstad
https://bugs.launchpad.net/oslo.limit/+bug/1790931
- Bug #1790954 (oslo.limit:Medium) opened by Lance Bragstad
https:
I agree in that it's dependent on what metrics you think accurately
showcase project health. Is it the number of contributions? The number of
unique contributors? Diversity across participating organizations?
Completion ratios of blueprints or committed fixes over bugs opened? I
imagine different p
May be first we should the keystone unified limits api really ok or
> something else ?
>
> Lance Bragstad 于2018年9月8日周六 上午2:35写道：
> >
> > That would be great! I can break down the work a little bit to help
> describe where we are at with different parts of the initiative
The topic of having consistent policy names has popped up a few times this
week. Ultimately, if we are to move forward with this, we'll need a
convention. To help with that a little bit I started an etherpad [0] that
includes links to policy references, basic conventions *within* that
service, and
On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across th
load-balancer
>
> Michael
> On Wed, Sep 12, 2018 at 12:52 PM Tim Bell wrote:
> >
> > So +1
> >
> >
> >
> > Tim
> >
> >
> >
> > From: Lance Bragstad
> > Reply-To: "OpenStack Development Mailing List (not for u
n purposes.
>
> I am guilty of borrowing this from existing code examples[0].
>
> [0]
> http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/policy-in-code.html
>
> Michael
> On Fri, Sep 14, 2018 at 8:46 AM Lance Bragstad
> wrote:
> >
> >
&
ainberg
wrote:
> I am generally opposed to needlessly prefixing things with "os".
>
> I would advocate to drop it.
>
>
> On Fri, Sep 14, 2018, 20:17 Lance Bragstad wrote:
>
>> Ok - yeah, I'm not sure what the history behind that is either...
>>
>> I&#x
This is typically something we do in-person during the PTG, but due to
weather and travel approval we didn't have great representation last week.
That said, let's try to do an asynchronous retrospective to gather feedback
regarding the last cycle. Afterwords we can try and meet to go through
speci
On Mon, Sep 17, 2018 at 1:42 PM Mohammed Naser wrote:
> Hi,
>
> On that note, is there any way to get an 'invite' onto those channels?
>
> Any information about the foundation side of things about the
> 'official' channels?
>
I actually have a question about this as well. During the TC discussio
On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann
wrote:
> Excerpts from Zhipeng Huang's message of 2018-09-14 18:51:40 -0600:
> > Hi,
> >
> > Based upon the discussion we had at the TC session in the afternoon, I'm
> > starting to draft a patch to add long term goal mechanism into
> governance.
> >
On Tue, Sep 18, 2018 at 12:17 PM Doug Hellmann
wrote:
> Excerpts from Lance Bragstad's message of 2018-09-18 11:56:22 -0500:
> > On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann
> > wrote:
> >
> > > Excerpts from Zhipeng Huang's message of 2018-09-14 18:51:40 -0600:
> > > > Hi,
> > > >
> > > > Bas
patch, and delete in the naming convention?
[0] https://service-types.openstack.org/service-types.json
[1]
https://gist.github.com/lbragstad/5000b46f27342589701371c88262c35b#file-policy-names-yaml
On Sun, Sep 16, 2018 at 9:47 PM Lance Bragstad wrote:
> If we consider dropping "os",
On Thu, Sep 20, 2018 at 12:22 AM Adrian Turjak
wrote:
> For Adam's benefit continuing this a bit in email:
>
> regarding the noop role:
>
>
> http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-09-20.log.html#t2018-09-20T04:13:43
>
> The first benefit of such a
On Thu, Sep 20, 2018 at 7:19 PM Sean McGinnis wrote:
> On Thu, Sep 20, 2018 at 03:46:43PM -0600, Doug Hellmann wrote:
> > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
> > > tl;dr: The openstack, openstack-dev, openstack-sigs and
> > > openstack-operators mailing lists (to
API, not the codeIgnore the crazy names in Nova, I certainly
> hate them
>
> Big +1 on consistent naming which will help operator as well as developer
> to maintain those.
>
> >
> > Lance Bragstad wrote:
> > > I'm curious if anyone has context on the &
On Mon, Sep 24, 2018 at 7:00 AM Colleen Murphy wrote:
> This is in regard to https://launchpad.net/bugs/1641625 and the proposed
> patch https://review.openstack.org/588211 for it. Thanks Vishakha for
> getting the ball rolling.
>
> tl;dr: Keystone as an IdP should support sending
> non-strings/l
On Mon, Sep 24, 2018 at 9:31 AM Colleen Murphy wrote:
> On Mon, Sep 24, 2018, at 4:16 PM, Lance Bragstad wrote:
> > On Mon, Sep 24, 2018 at 7:00 AM Colleen Murphy
> wrote:
> >
> > > This is in regard to https://launchpad.net/bugs/1641625 and the
&
For those who may be following along and are not familiar with what we mean
by federated auto-provisioning [0].
[0]
https://docs.openstack.org/keystone/latest/advanced-topics/federation/federated_identity.html#auto-provisioning
On Wed, Sep 26, 2018 at 9:06 AM Morgan Fainberg
wrote:
> This discu
Using the domain name + group name pairing also allows for things like:
JSON:{"group_name": "C",
"domain_name": "X"}
JSON:{"group_name": "C",
"domain_name": "Y"}
To showcase how we solve the ambiguity in group names by namespacing them
with domains.
On Thu, Sep 27, 2018 at 3:11 AM Coll
On Wed, Sep 26, 2018 at 1:56 PM Tim Bell wrote:
>
> Doug,
>
> Thanks for raising this. I'd like to highlight the goal "Finish moving
> legacy python-*client CLIs to python-openstackclient" from the etherpad and
> propose this for a T/U series goal.
>
> To give it some context and the motivation:
t more of a question of which subcommands we should aim to support in OSC.
>
>
>
> The *-manage commands such as nova-manage, I would consider, out of scope
> for OSC. Only admins would be migrating between versions or DB schemas.
>
>
>
> Tim
>
>
>
> *Fr
21, 2018 at 9:13 AM Lance Bragstad wrote:
>
> On Fri, Sep 21, 2018 at 2:10 AM Ghanshyam Mann
> wrote:
>
>> On Thu, 20 Sep 2018 18:43:00 +0900 John Garbutt <
>> j...@johngarbutt.com> wrote
>> > tl;dr+1 consistent names
>> > I would make th
Adding the operator list back in.
On Fri, Sep 28, 2018 at 8:48 AM Lance Bragstad wrote:
> Bumping this thread again and proposing two conventions based on the
> discussion here. I propose we decide on one of the two following
> conventions:
>
> *::*
>
> or
>
ority
- resources are always singular
Thanks to all for sticking through this tedious discussion. I appreciate it.
>
> /R
>
> Harry
> >
> > On Fri, Sep 28, 2018 at 6:49 AM Lance Bragstad
> wrote:
> >>
> >> Bumping this thread again and proposing tw
n Fri, Sep 28, 2018 at 3:33 PM Sean McGinnis wrote:
> On Fri, Sep 28, 2018 at 01:54:01PM -0500, Lance Bragstad wrote:
> > On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki
> wrote:
> >
> > > On Fri, Sep 28, 2018 at 1:57 PM Morgan Fainberg
> > > wrote:
> > &g
On Mon, Oct 1, 2018 at 8:13 AM Ghanshyam Mann
wrote:
> On Sat, 29 Sep 2018 03:54:01 +0900 Lance Bragstad <
> lbrags...@gmail.com> wrote
> >
> > On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki
> wrote:
> > On Fri, Sep 28, 2018 at 1:5
On Mon, Oct 8, 2018 at 9:08 AM Doug Hellmann wrote:
> Based on the conversation in the other branch of this thread, I have
> filed [1] to start monthly meetings on November 1 at 1400 UTC. It may
> take a while before that actually shows up on the calendar, because it
> required adding a feature t
On Mon, Oct 8, 2018 at 9:27 AM Doug Hellmann wrote:
> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period o
Keystone is failing because it's missing a fix from oslo.messaging [0].
That said, keystone is also relying on an internal implementation detail in
oslo.messaging by mocking it in tests [1]. The notification work has been
around in keystone for a *long* time, but it's apparent that we should
revisi
On Tue, Oct 9, 2018 at 10:31 AM Ben Nemec wrote:
>
>
> On 10/9/18 9:06 AM, Lance Bragstad wrote:
> > Keystone is failing because it's missing a fix from oslo.messaging [0].
> > That said, keystone is also relying on an internal implementation detail
> > in oslo.
On Tue, Oct 9, 2018 at 10:56 AM Doug Hellmann wrote:
> Matthew Thode writes:
>
> > On 18-10-09 11:12:30, Doug Hellmann wrote:
> >> Matthew Thode writes:
> >>
> >> > several projects have had problems with the new release, some have
> ways
> >> > of working around it, and some do not. I'm sendi
https://review.openstack.org/#/c/606214/
On Mon, Oct 8, 2018 at 8:49 AM Lance Bragstad wrote:
>
> On Mon, Oct 1, 2018 at 8:13 AM Ghanshyam Mann
> wrote:
>
>> On Sat, 29 Sep 2018 03:54:01 +0900 Lance Bragstad <
>> lbrags...@gmail.com> wrote
>> >
>>
On Mon, Oct 15, 2018 at 8:52 AM Ed Leafe wrote:
> On Oct 15, 2018, at 7:40 AM, Chris Dent wrote:
> >
> > I'd like some input from the community on how we'd like this to go.
>
> I would say it depends on the long-term plans for paste. Are we planning
> on weaning ourselves off of paste, and simpl
I haven't implemented any checks, but I did take a shot at laying down the
scaffolding for implementing upgrade checks in glance [0].
Anyone who is more familiar with glance should be able to build off of that
commit by implementing specific checks in glance/cmd/status.py
[0] https://review.opens
n Sat, Oct 13, 2018 at 6:07 AM Ghanshyam Mann
wrote:
> On Sat, 13 Oct 2018 01:45:17 +0900 Lance Bragstad <
> lbrags...@gmail.com> wrote
> > Sending a follow up here quick.
> > The reviewers actively participating in [0] are nearing a conclusion.
> Ultimatel
On Wed, Oct 24, 2018 at 2:49 PM Jay Pipes wrote:
> On 10/24/2018 02:57 PM, Matt Riedemann wrote:
> > On 10/24/2018 10:10 AM, Jay Pipes wrote:
> >> I'd like to propose deprecating this API and getting rid of this
> >> functionality since it conflicts with the new Keystone /limits
> >> endpoint, is
Great work Boris. Welcome to the team!
On Mon, Oct 31, 2016 at 2:50 PM, Kristi Nikolla wrote:
> Congrats Boris! Well deserved!
>
> Kristi
>
> On 10/31/2016 03:46 PM, Steve Martinelli wrote:
> > I want to welcome Boris Bobrov (breton) to the keystone core team. Boris
> > has been a contributor fo
I totally agree with communicating this the best we can. I'm adding the
operator list to this thread to increase visibility.
If there are any other methods folks think of for getting the word out,
outside of what we've already done (release notes, email threads, etc.),
please let me know. I'd be h
penStack sore might be good. superuser? there are
> folks reading this who can help
>
> Sent from HUAWEI AnyOffice
> *From:*Lance Bragstad
> *To:*OpenStack Development Mailing List (not for usage questions),
> openstack-operat...@lists.openstack.org,
> *Date:*2016-11-03 08:11
Hi folks,
After hearing the recaps from the summit, it sounds like policy was a hot
topic (per usual). This is also reinforced by the fact every release we
have specifications proposed to re-do policy in some way.
It's no doubt policy in OpenStack needs work. Let's dedicate an hour a week
to poli
perators. Generally they'll want to publish it there first then
> you follow-up with your blog post a few days later.
>
> On Mon, Nov 7, 2016 at 8:17 AM, Lance Bragstad
> wrote:
>
>> That's a good idea. Is there a page detailing the process for
>> contributing to th
gs
> backwards compatible.
>
> On Thu, Nov 10, 2016 at 3:30 PM, Lance Bragstad
> wrote:
>
>> Hi folks,
>>
>> After hearing the recaps from the summit, it sounds like policy was a hot
>> topic (per usual). This is also reinforced by the fact every release we
Hey folks,
In today's keystone meeting, Morgan mentioned that we had the ability to go
back to using OpenStack Wikis for meeting agendas. I created a poll to get
feedback [0].
Let's keep it open for the week and look at the results as a team at our
next meeting.
Thanks!
[0] https://goo.gl/forms
e.com/call/pd36j4qv5zfbldmhxeeatq6f7ae
On Fri, Nov 11, 2016 at 8:33 AM, Lance Bragstad wrote:
> I've added some initial content to the etherpad [0], to get things
> rolling. Since this is going to be a recurring thing, I'd like our first
> meeting to level set the playing field f
ne.2016-11-16.log.html#t2016-11-16T16:01:43
[1] https://review.openstack.org/#/c/398500/
[2] https://etherpad.openstack.org/p/keystone-policy-meeting
On Wed, Nov 16, 2016 at 8:32 AM, Lance Bragstad wrote:
> Just sending out a reminder that we'll be having our first meeting in 90
> minu
to everyone who attended and I look
>> forward to next week's meeting.
>>
>>
>> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-
>> keystone/%23openstack-keystone.2016-11-16.log.html#t2016-11-16T16:01:43
>> [1] https://review.openstack.org/#/c/398500
Steve, thanks for all the hard work and dedication over the last 3 cycles.
I hope you have a nice break and I look forward to working with you on Pike!
Enjoy you're evenings :)
On Mon, Nov 21, 2016 at 1:38 PM, Steve Martinelli
wrote:
> one of these days i'll learn how to spell :)
>
> On Mon,
Thanks for all your hard work, Marek. It's been a pleasure working with
you. Best of luck and hopefully our paths cross in the future!
On Tue, Nov 22, 2016 at 7:57 PM, Steve Martinelli
wrote:
> Marek, thanks for everything you've done in Keystone. It was loads of fun
> to develop some of the ear
We had a useful discussion today [0]. I attempted to summarize the meeting
in the etherpad [1], crossed off things we accomplished, and documented our
action items to complete by next week, which I'll echo below:
*ACTION ITEM:* group to review https://review.openstack.org/#/c/391624/ and
continue
401 - 499 of 499 matches
Mail list logo
