Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

On 10/16/2017 09:09 AM, Amrith Kumar wrote: > In a recent conversation on #openstack-tc where we bemoaned the ills > of Stackalytics and related management-by-objectives to Heisenberg's > uncertainty principle, the conversation (on 10-03, for example) veered > towards why people were interested

Re: [openstack-dev] [policy] AWS IAM session

Sending out a gentle reminder to vote for time slots that work for you [0]. We'll keep the poll open for a few more days, or until we reach quorum. Thanks! [0] https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu On 10/11/2017 01:48 PM, Lance Bragstad wrote: > Oh - one note about the doodle [0].

Re: [openstack-dev] [policy] AWS IAM session

Oh - one note about the doodle [0]. All proposed times are in UTC, so just keep that in mind when selecting your availability. Thanks! [0] https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu On 10/11/2017 01:44 PM, Lance Bragstad wrote: > In today's policy meeting we went through and started prepp

Re: [openstack-dev] [policy] AWS IAM session

for upgrading the account. [0] https://etherpad.openstack.org/p/analyzing-other-policy-systems [1] https://doodle.com/poll/ntkpzgmcv3k6v5qu On 10/09/2017 04:23 PM, Lance Bragstad wrote: > I've put a scheduling session on the books for the next policy meeting > [0][1]. Advertising it here since

Re: [openstack-dev] [keystone][middleware]: Use encrypted password in the service conf file

This sounds like something that was discussed during the PTG. The oslo team was exploring ways to implement this, which would be consumable to keystonemiddleware as a library [0]. [0] https://etherpad.openstack.org/p/oslo-ptg-queens On 10/11/2017 07:43 AM, pnkk wrote: > Hi, > > We have our API

Re: [openstack-dev] [policy] AWS IAM session

://eavesdrop.openstack.org/#Keystone_Policy_Meeting [1] https://etherpad.openstack.org/p/keystone-policy-meeting On 10/05/2017 02:24 AM, Colleen Murphy wrote: > On Tue, Oct 3, 2017 at 10:08 PM, Lance Bragstad <lbrags...@gmail.com > <mailto:lbrags...@gmail.com>> wrot

[openstack-dev] [keystone] office hours report 2017-10-03

Hey all, The following was done during office hours this week: Bug #1698455 in OpenStack Identity (keystone): "Install and configure in Installation Guide: Populate the Identity service database step fails on CentOS7" https://bugs.launchpad.net/keystone/+bug/1698455 Triaged and tagged Bug

[openstack-dev] [policy] AWS IAM session

Hey all, It was mentioned in today's keystone meeting [0] that it would be useful to go through AWS IAM (or even GKE) as a group. With all the recent policy discussions and work, it seems useful to get our eyes on another system. The idea would be to spend time using a video conference/screen

[openstack-dev] [all] policy community goal progress

Hey all, According to our burndown chart [0], just over half the projects have started implementing the goal [1]. I've been proposing patches for some of the projects in the not-started column. Most patches I've been working on would benefit from a review from someone more experienced with the

Re: [openstack-dev] [keystone][zuul] A Sad Farewell

+1,000 to all of what Steve said. It's still tough for me to wrap my head around all the client/library work you shouldered. Your experience, perspective, and insight will certainly be missed. Thanks for being an awesome member of this community and best of luck on the new gig, they're lucky to

[openstack-dev] [keystone] office hours report 2017-09-26 and plans for next week

Office hours was a little slow this week. Most people seem to be getting back in the groove from the PTG. No bugs were closed during this week's office hours. FWIW - I plan to go through and start cleaning up v2.0 bugs there are no longer relevant now that v2.0 is being removed. This will be a

Re: [openstack-dev] [Oslo][oslo.policy] Bug: Glance doesn't send correctly authorization request to Oslo policy

++ it'd be great to come up with some sort of pattern here that other projects can follow if they need to implement the same thing. Some sort of consistency would be great when/if we start seeing more http_check adoption. On 09/29/2017 07:56 AM, ruan...@orange.com wrote: > > Hi folks, > > We are

Re: [openstack-dev] [keystone] [keystoneauth] Debug data isn't sanitized - bug 1638978

On 09/27/2017 06:38 AM, Bhor, Dinesh wrote: > > Hi Team, > >   > > There are four solutions to fix the below bug: > > https://bugs.launchpad.net/keystoneauth/+bug/1638978 > >   > > 1) Carry a copy of mask_password() method to keystoneauth from > oslo_utils [1]: > > *Pros:* > > A. keystoneauth

[openstack-dev] [keystone] Sydney Forum Session Proposals

Hey all, In the weekly meeting on Tuesday, we talked about possible forum sessions for Sydney. I proposed the following based on the etherpad [0]. * Keystone User & Operator Feedback [1] * Application Credentials Feedback [2] * RBAC/Policy Roadmap Feedback [3] We decided to omit the last

[openstack-dev] [keystone]] Trello board update

Hey all, I went through the Trello board for all our Queens work and updated all cards that needed "fleshing out". Each should have an accurate description of the work, why it's needed, and a checklist if applicable. If a card still doesn't make sense, please ping me or add the "needs fleshing

Re: [openstack-dev] Garbage patches for simple typo fixes

On Sep 22, 2017 07:59, "Matt Riedemann" wrote: On 9/22/2017 9:50 AM, Rajath Agasthya (rajagast) wrote: > On 9/21/17, 10:19 PM, "Jeremy Freudberg" > wrote: > > 3) Delay spin-up of resource-intensive/long-running CI jobs until after > some >

[openstack-dev] [keystone] [policy] policy meeting 2017-09-20

Hey all, I won't be available to run the policy meeting tomorrow. It doesn't look like there is anything posted to the agenda yet [0]. If someone feels like hosting it, please feel free to do so. I'll catch the scroll back afterwords. Thanks, Lance [0]

Re: [openstack-dev] [all] dashboard query changes since upgrade

I should have read this thread before starting a new one [0]. The query bits sound somewhat similar to what I experienced with a script to generate a burndown chart, but querying a topic instead. [0] http://lists.openstack.org/pipermail/openstack-dev/2017-September/122315.html On 09/19/2017

[openstack-dev] [all] policy in code burndown chart

Hey all, The upgrade to Gerrit 2.13.9 affected a script I was using to generate the burndown chart by querying the REST api. I've pushed a fix [0] and it should be working again in case you weren't seeing your project being reflected in the burndown [1]. Let me know if you have any additional

[openstack-dev] [policy] [all] policy in code schedule and room

Hey all, The schedule [0] has been updated with room information for the policy-in-code effort. We'll be in Grays Peak on Level 3 on Monday and Tuesday to help projects with the Queens goal [1]. [0] https://etherpad.openstack.org/p/policy-queens-ptg [1]

Re: [openstack-dev] [keystone] Queens PTG Planning

Looks like we'll be in Telluride B, Atrium Level. I've updated the room information in the etherpad [0]. [0] https://etherpad.openstack.org/p/keystone-queens-ptg On 08/24/2017 02:25 PM, Lance Bragstad wrote: > I've worked the topics into a schedule [0]. Monday and Tuesday are > pretty g

Re: [openstack-dev] [keystone] [nova] [neutron] [cinder] [ironic] [glance] [swift] Baremetal/VM SIG PTG Schedule/Etherpad

Looks like the Baremetal/VM SIG (#compute) will meet in Ballroom B, Banquet Level. I've updated the etherpad with the room information [0]. [0] https://etherpad.openstack.org/p/queens-PTG-vmbm On 09/07/2017 10:01 AM, Lance Bragstad wrote: > I spoke with John a bit today in IRC and we h

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

around in the morning, pending the Application Credentials discussion. [0] https://etherpad.openstack.org/p/queens-PTG-vmbm On 09/05/2017 09:15 PM, Lance Bragstad wrote: > Thanks! That should work. We have a couple things set up with the > baremetal/VM SIG [0] during that time, but I don't

Re: [openstack-dev] [keystone] [nova] [neutron] [cinder] [ironic] [glance] [swift] Baremetal/VM SIG PTG Schedule/Etherpad

know it's a bit late, but I'd like to have the schedule pretty well set by the weekend. Thanks! [0] https://etherpad.openstack.org/p/queens-PTG-vmbm On 08/24/2017 03:34 PM, Lance Bragstad wrote: > Hi all, > > Keystone has a few cross-project topics we'd like to share with a wider >

[openstack-dev] [all] tracking policy community goal for queens

Hey all, I reused some of Doug's doc-migration tooling to create a burndown chart specifically for policy work in Queens [0][1]. As some of you might know, I've attempted to update projects that are not impacted by the goal [2]. Another reminder that we will be having two sessions dedicated to

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

you still have conflicts :-) > > [1] https://etherpad.openstack.org/p/oslo-ptg-queens > > 2017-09-02 6:16 GMT+08:00 Lance Bragstad <lbrags...@gmail.com>: > >> Thanks for the schedule! I should be somewhat available Monday afternoon >> for the policy deprecation discussion

Re: [openstack-dev] [oslo][oslo.db][keystone] A POC of Keystone over CockroachDB

On 09/04/2017 11:06 AM, Ronan-Alexandre Cherrueau wrote: > Hi folks, > > Recently in the Inria's Discovery initiative[1], we got in touch with > CockroachLabs guys with an idea: make Keystone supports CockorachDB. So > we give it a try and you can find a very first result on our GitHub[2]. > The

Re: [openstack-dev] [Openstack-dev][keystone][AAA] Unable to log in to DLUX UI using keystone created users

anks for your kind response!! > >   > > Can you please help me with the process to authenticate the created > users directly against keystone ?? > >   > > Best regards, > > Vamsi krishna > >   > > *From:*Lance Bragstad [mailto:lbrags...@gmail.com] > *Sent:*

Re: [openstack-dev] [all] [oslo] schedule for Denver PTG is ready !

Thanks for the schedule! I should be somewhat available Monday afternoon for the policy deprecation discussion. The only conflict that might come up for me is with the Baremetal/VM group [0]. Keystone has a few topics to iron out there, but I'm not exactly sure when that group plans to talk about

Re: [openstack-dev] [Openstack-dev][keystone][AAA] Unable to log in to DLUX UI using keystone created users

It looks like the users exist in keystone. Are you able to authenticate directly against keystone and see if that works? On 09/01/2017 06:22 AM, A Vamsikrishna wrote: > > Hi All, > > > > *Setup details: * > > > > ubuntu-16.04.2-server-amd64 > > Docker version 1.12.6 > > Installed keystone in

[openstack-dev] [keystone] Blueprints for Queens

Now that Pike is out the door (big thanks to everyone for helping!), I've create the deprecated-as-of-queen [0] and removed-as-of-queens [1] blueprints. Feel free to use them as needed now that Queens is underway. Thanks! [0]

[openstack-dev] [keystone] [nova] [neutron] [cinder] [ironic] [glance] [swift] Baremetal/VM SIG PTG Schedule/Etherpad

Hi all, Keystone has a few cross-project topics we'd like to share with a wider group, like the Baremetal/VM SIG. As a result, I attempted to dust off some of the Baremetal/VM sessions [0][1] from Boston and port the popular topics over to the etherpad for the PTG [2]. Maybe it will kick start

Re: [openstack-dev] [keystone] Queens PTG Planning

of the Etherpad as a champion, moderator, or scribe (see definitions in the main schedule). Let me know if you see any issues or conflicts. Thanks, Lance [0] https://etherpad.openstack.org/p/keystone-queens-ptg On 07/27/2017 12:21 PM, Lance Bragstad wrote: > I've added a section to the etherpad

[openstack-dev] [keystone] office hours report 2017-08-22

Today we realized we're going to need to cut a new release candidate due to some confusion around release notes. Particularly the ones for Pike. We spent the majority of office hours fixing and reviewing those patches. Full logs from office hours can be found here [0]. Thanks for all the quick

[openstack-dev] [keystone] office hours report 2017-08-15

Hey all, Office hours was pretty focused today. We spent the majority of the time discussing and merging fixes we need for RC2. In addition to that we discussed plans for the PTG as well as the schedule. Full details can be found in the logs [0]. Thanks, Lance [0]

[openstack-dev] [keystone] Adding Kristi Nikolla to keystone-core

I made the announcement in today's keystone meeting [0] that the current reviewers have decided to add Kristi Nikolla (knikolla) to the team. Kristi has been an extremely valuable asset to the team over the last couple of releases. He especially stepped up to the plate during Pike. He provides

[openstack-dev] [keystone] using only sql for resource backends

During RC, Morgan's made quite a bit of progress on a bug found by the gate [0]. Part of the solution led to another patch that removes the ability to configure anything but sql for keystone's resource backend (`keystone.conf [resource] driver`). The reasoning behind this is that there were FK

Re: [openstack-dev] [keystone] rc2 updates

/1702211 [3] fail tempest run --regex tempest.api.identity.admin.v3.test_users.UsersV3TestJSON.test_password_history_not_enforced_in_admin_reset On 08/11/2017 06:26 PM, Morgan Fainberg wrote: > On Fri, Aug 11, 2017 at 11:10 AM, Lance Bragstad <lbrags...@gmail.com> wrote: >> Thanks

Re: [openstack-dev] [keystone] rc2 updates

working on a fix and we've targeted bug 1702211 to rc2. I'll keep an eye out for the translations patch and make sure that lands before we cut the next release candidate. On 08/11/2017 12:02 PM, Thierry Carrez wrote: > Lance Bragstad wrote: >> We rolled out rc1 last night [0], but missed

Re: [openstack-dev] [qa] [keystone] Random Patrole failures related to Identity v3 Extensions API

Help if you actually attach the link you want to send [0]. [0] https://bugs.launchpad.net/keystone/+bug/1702211 On 08/11/2017 11:26 AM, Morgan Fainberg wrote: > On Fri, Aug 11, 2017 at 9:25 AM, Morgan Fainberg > wrote: >> On Fri, Aug 11, 2017 at 8:44 AM, Felipe

Re: [openstack-dev] [qa] [keystone] Random Patrole failures related to Identity v3 Extensions API

More context on the patch Morgan is working on can be found in the bug report [0]. [0] On 08/11/2017 11:26 AM, Morgan Fainberg wrote: > On Fri, Aug 11, 2017 at 9:25 AM, Morgan Fainberg > wrote: >> On Fri, Aug 11, 2017 at 8:44 AM, Felipe Monteiro >>

[openstack-dev] [keystone] rc2 updates

We rolled out rc1 last night [0], but missed a couple important documentation patches and release notes [1]. I'll propose rc2 as soon as those merge. I've also created a new official bug tag, pike-backport-potential. Please feel free to use the tag if you're doing bug triage and find something you

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

I proposed a patch to remove the deprecation [0]. [0] https://review.openstack.org/492694 On 06/28/2017 09:33 PM, Lance Bragstad wrote: > Cool - I'm glad this is generating discussion. I personally don't see > a whole lot of maintenance costs with `keystone-manage > domain_config_u

[openstack-dev] [keystone] office hours report 2017-08-08

Hi all, Today we had good focus on RC1 bugs. We spent most of the keystone meeting and all of office hours discussing or reviewing fixes. Full logs can be found at the bottom of the note [0]. Here's a summary of what we accomplished: Bug #1674676 in OpenStack Identity (keystone): "The URL

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

ote: > On Fri, 4 Aug 2017, Lance Bragstad wrote: >> On 08/04/2017 03:45 PM, Kristi Nikolla wrote: >>> Therefore the call which now returns a 403 in master, returned a 2xx in >>> Ocata. So we would be fixing something which is broken on master rather >>> than

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

gt;> >> On Fri, Aug 04, 2017 at 03:35:38PM -0400, William M Edmonds wrote: >>> Lance Bragstad <lbrags...@gmail.com> wrote on 08/04/2017 02:37:40 PM: >>>> Properly fixing this would result in a 403 -> 204 status code, which >>>> requires an AP

[openstack-dev] [keystone] [keystone] [ptl] PTL candidacy for Queens

* Hi all, ** I'd like to formally communicate my desire to continue serving as the keystone PTL for the upcoming Queen’s release. Despite some turbulence throughout the Pike development cycle, keystone has managed to make progress on some long standing issues. Even though the pace of

[openstack-dev] [keystone][api] Backwards incompatible changes based on config

Keystone had a bug reported [0] recently (that we are targeting to pike-rc1) that exposes an inconsistency in the API based on configuration. The happy path is as follows: - a deployment is configured to store projects (controlled by the resource backend) and users (controlled by the identity

[openstack-dev] [all] [ptg] Policy Sessions

One of the community goals for Queens is to move all policy into code and document it [0]. I'd like to make myself available to work with projects face-to-face if they need help at the PTG. In order to successfully plan that, we need to have an estimate of how many projects are interested in

Re: [openstack-dev] [OpenStack-Ansible] Not running for Queens PTL

I couldn't agree more with what others have already said. It's been awesome to see positive things come out of close communication between deployment projects and other project teams. I look forward to seeing the pattern and precedence continue! On 07/31/2017 12:59 PM, Amy Marrich wrote: > Andy,

[openstack-dev] [keystone][policy] no policy meeting today 2017-08-02

A lot of the team is focused on getting pike-rc1 out the door and reviews. The agenda is also empty. Let's cancel today and pick up next week or shortly before the PTG to organize our policy sessions there. Thanks, Lance signature.asc Description: OpenPGP digital signature

[openstack-dev] [keystone] office hours report 2017-08-01

Hey all, Here is a condensed report of what was accomplished during office hours today. Most activity focused on reviewing fixes in flight. Full log can be found in IRC [0]. Bug #1635389 in OpenStack Identity (keystone): "keystone.contrib.ec2.controllers.Ec2Controller is untested"

[openstack-dev] [requirements][release][oslo] FFE for oslo.policy

I was cleaning up a few documentation things for keystone and noticed an issue with how the configuration reference was rendering. It turns out the oslo.policy library needed a few tweaks to the show-policy directive along with some changes to keystone that allowed us to properly render all

Re: [openstack-dev] [keystone] Queens PTG Planning

, Lance Bragstad wrote: > Hey all, > > I've started an etherpad [0] for us to collect topics and ideas for the > PTG in September. I hope to follow the same planning format as last > time. Everyone has the opportunity to add topics to the agenda and after > some time we'll gr

[openstack-dev] [keystone] canceling policy meeting 2017-07-26

Hey all, There isn't anything on the agenda for today's policy meeting [0] and I know several members of the team are wrapping things up for pike-3. As a result, I'm canceling the policy meeting today and we can reconvene next week after the dust settles. Thanks, Lance [0]

[openstack-dev] [keystone] office hours report 2017-7-25

Hey all, Nearly all of today's activity in office hours consisted of bug triage. We now have a list of target bugs for rc1 [0]. Full logs can be found below [1]. The following is a summary of what was accomplished: Bug #1669080 in OpenStack Identity (keystone): ""openstack role create" should

Re: [openstack-dev] [keystone] [all] keystoneauth version discovery is here

/openstack-dev/2017-July/120012.html [1] https://review.openstack.org/#/c/486223/ On Thu, Jul 20, 2017 at 5:41 PM, Lance Bragstad <lbrags...@gmail.com> wrote: > Happy Thursday, > > We just released keystoneauth 3.0.0 [0], which contains a bunch of > built-in functionality to handle ve

Re: [openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

rged yet > > https://review.openstack.org/#/c/486231/ > > > Thansk, > Dims > > On Fri, Jul 21, 2017 at 11:40 PM, Lance Bragstad <lbrags...@gmail.com> > wrote: > > > > > > On Fri, Jul 21, 2017 at 9:39 PM, Monty Taylor <mord...@inaugust.com> > wr

Re: [openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

On Fri, Jul 21, 2017 at 9:39 PM, Monty Taylor <mord...@inaugust.com> wrote: > On 07/22/2017 07:14 AM, Lance Bragstad wrote: > >> After a little head scratching and a Pantera playlist later, we ended up >> figuring out the main causes. The failures can be found in the gate

Re: [openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

-keystonemiddleware-python27-ubuntu-xenial/7c079da/testr_results.html.gz [1] https://github.com/openstack/keystoneauth/blob/5715035f42780d8979d458e9f7e3c625962b2749/keystoneauth1/discover.py#L947 [2] https://review.openstack.org/#/c/486231/1 On 07/21/2017 04:43 PM, Lance Bragstad wrote: > The pa

Re: [openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

The patch to blacklist version 3.0.0 is working through the moment [0]. We also have a WIP patch proposed to handled the cases exposed by keystonemiddleware [1]. [0] https://review.openstack.org/#/c/486223/ [1] https://review.openstack.org/#/c/486231/ On 07/21/2017 03:58 PM, Lance Bragstad

Re: [openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

:00 PM, Lance Bragstad wrote: > I started noticing some trivial changes failing in the > keystonemiddleware gate [0]. The failures are in tests that use the > keystoneauth1 library (8 tests are failing by my count), which we > released a new version of yesterday [1]. I've prop

[openstack-dev] [keystone] keystoneauth1 3.0.0 broken keystonemiddleware

I started noticing some trivial changes failing in the keystonemiddleware gate [0]. The failures are in tests that use the keystoneauth1 library (8 tests are failing by my count), which we released a new version of yesterday [1]. I've proposed a patch to blacklist keystoneauth1 3.0.0 from

[openstack-dev] [keystone] [all] keystoneauth version discovery is here

Happy Thursday, We just released keystoneauth 3.0.0 [0], which contains a bunch of built-in functionality to handle version discovery so that you don't have to! Check out the documentation for all the details [1]. Big thanks to Eric and Monty for tackling this work, along with all the folks who

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 07/19/2017 09:27 PM, Monty Taylor wrote: > On 07/19/2017 12:18 AM, Zane Bitter wrote: >> On 18/07/17 10:55, Lance Bragstad wrote: >>>> >>>> Would Keystone folks be happy to allow persistent credentials once >>>> we have a way to

[openstack-dev] [keystone] office hours report 2017-7-18

Hi all, This is a day late, but here is the summary for what we worked on during office hours yesterday. The full log can be found below [0]. Bug #1689888 in OpenStack Identity (keystone): "/v3/users is unproportionally slow" https://bugs.launchpad.net/keystone/+bug/1689888 participants:

Re: [openstack-dev] [keystone] office hours report 2017-7-7

68 participants: gagehugo, kaerie Reproposed patch in review For what it's worth, I also apparently thought office hours occurred on the 7th when it was actually on the 11th. On 07/11/2017 08:35 PM, Lance Bragstad wrote: > > Hey all, > > This is a summary of what was worked on today

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 07/18/2017 08:21 AM, Andy McCrae wrote: > > > > The branches have now been retired, thanks to Joshua Hesketh! > > > Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting > this out. ++ thanks all! > > Andy > > >

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 07/17/2017 10:12 PM, Lance Bragstad wrote: > > > On Mon, Jul 17, 2017 at 6:39 PM, Zane Bitter <zbit...@redhat.com > <mailto:zbit...@redhat.com>> wrote: > > So the application credentials spec has merged - huge thanks to > Monty and the Ke

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On Mon, Jul 17, 2017 at 6:39 PM, Zane Bitter wrote: > So the application credentials spec has merged - huge thanks to Monty and > the Keystone team for getting this done: > > https://review.openstack.org/#/c/450415/ > http://specs.openstack.org/openstack/keystone-specs/specs/

[openstack-dev] [keystone] feature freeze and spec status

Hi all, I wanted to send a friendly reminder that feature freeze for keystone will be in R-5 [0], which is the end of next week. That leaves just under 10 business days for feature work (8 considering the time to get through the gate). Of the specifications we've committed to for Pike, the

Re: [openstack-dev] [keystone] stable/ocata and stable/newton are broken

All the patches in the original note have merged for both stable/ocata and stable/newton. Existing patches to both branches are being recheck and rebased. On 07/13/2017 06:04 PM, Lance Bragstad wrote: > Oh - the original issues with the stable branches were reported here: > &

Re: [openstack-dev] [keystone] stable/ocata and stable/newton are broken

Oh - the original issues with the stable branches were reported here: https://bugs.launchpad.net/keystone/+bug/1704148 On 07/13/2017 06:00 PM, Lance Bragstad wrote: > Colleen found out today while doing a backport that both of our stable > branches are broken. After doing some digging, it

[openstack-dev] [keystone] stable/ocata and stable/newton are broken

Colleen found out today while doing a backport that both of our stable branches are broken. After doing some digging, it looks like bug 1687593 is the culprit [0]. The fix to that bug merged in master and the author added some nicely written functional tests using the keystone-tempest-plugin. The

Re: [openstack-dev] [keystone] office hours report 2017-7-7

On 07/12/2017 09:17 AM, Akihiro Motoki wrote: > 2017-07-12 10:35 GMT+09:00 Lance Bragstad <lbrags...@gmail.com>: >> Hey all, >> >> This is a summary of what was worked on today during office hours. Full logs >> of the meeting can be found below: >> >

[openstack-dev] [all] Queens Goal for policy-in-code

Hi all, I'd like to reach out and get ahead of the curve now that we established the community goals for Queens. If you have any questions about the policy-in-code work [0] and how it pertains to your project, please don't hesitate to ping me in #openstack-dev. Once pike starts winding down, I'll

Re: [openstack-dev] [keystone] office hours report 2017-7-7

On 07/11/2017 09:28 PM, Mathieu Gagné wrote: > Hi, > > So this email is relevant to my interests as an operator. =) Glad to hear it! > > On Tue, Jul 11, 2017 at 9:35 PM, Lance Bragstad <lbrags...@gmail.com > <mailto:lbrags...@gmail.com>> wrote: > >

[openstack-dev] [keystone] office hours report 2017-7-7

Hey all, This is a summary of what was worked on today during office hours. Full logs of the meeting can be found below: http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-07-11-19.00.log.html *The future of the templated catalog backend * Some issues were uncovered,

Re: [openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

#L331 On 07/05/2017 04:28 PM, Colleen Murphy wrote: > On Wed, Jul 5, 2017 at 9:36 PM, Lance Bragstad <lbrags...@gmail.com > <mailto:lbrags...@gmail.com>> wrote: > > Hi all, > > Keystone has a script to perform some bootstrapping operations > [0]. It'

[openstack-dev] [keystone] office hours reminder

Hey all, Just a quick reminder that today we will be holding office hours after the keystone meeting [0]. See you there! Thanks, Lance [0] http://eavesdrop.openstack.org/#Keystone_Team_Meeting signature.asc Description: OpenPGP digital signature

Re: [openstack-dev] [keystone] We still have a not identical HEAD response

Based on the comments and opinions in the original thread, I think a fix for this is justified. I wouldn't mind running this by the TC to double check that nothing has changed from the first time we had to fix this issue though. On 07/11/2017 06:03 AM, Attila Fazekas wrote: > Hi all, > > Long

[openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

Hi all, Keystone has a script to perform some bootstrapping operations [0]. It's not really tested and its purpose has been superseded by using the `keystone-manage bootstrap` command. Based on codesearch, only openstack/rpm-packaging references the script [1]. Is anyone opposed to the

[openstack-dev] [keystone] Queens PTG Planning

Hey all, I've started an etherpad [0] for us to collect topics and ideas for the PTG in September. I hope to follow the same planning format as last time. Everyone has the opportunity to add topics to the agenda and after some time we'll group related topics and start building a formal schedule.

Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion

On 06/30/2017 04:38 AM, Thierry Carrez wrote: > Mike Perez wrote: >> [...] >> What do people think before we bikeshed on the name? Would having a >> champion volunteer to each goal to help? > It feels like most agree that having champions would help. Do we have > any volunteer for the

[openstack-dev] [keystone] no policy meeting today

Hey all, Given the empty agenda [0] and the holiday, we will cancel the policy meeting this week. We'll pick up again next week. Thanks [0] https://etherpad.openstack.org/p/keystone-policy-meeting signature.asc Description: OpenPGP digital signature

[openstack-dev] [keystone] stable/newton is broken

Keystone's stable/newton gate is broken [0] [1]. The TL;DR is that our keystone_tempest_plugin is validating federated mappings before updating the protocol [2]. The lack of validation was a bug [3] that was fixed in Ocata, but the fix [4] was never backported. Since stable/newton is in Phase II,

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

t; >> On Wed, Jun 28, 2017 at 2:00 AM, Lance Bragstad >> <lbrags...@gmail.com <mailto:lbrags...@gmail.com>> wrote: >> >> Hi all, >> >> Keystone has deprecated the domain configuration upload >>

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 03:20 PM, Ben Nemec wrote: > > > On 06/28/2017 02:47 PM, Lance Bragstad wrote: >> >> >> On 06/28/2017 02:29 PM, Fox, Kevin M wrote: >>> I think everyone would benefit from a read-only role for keystone >>> out of the box. Can we get this

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 02:29 PM, Fox, Kevin M wrote: > I think everyone would benefit from a read-only role for keystone out of the > box. Can we get this into keystone rather then in the various distro's? Yeah - I think that would be an awesome idea. John Garbutt had some good work on this earlier in

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

d, Jun 28, 2017 at 2:00 AM, Lance Bragstad <lbrags...@gmail.com > <mailto:lbrags...@gmail.com>> wrote: > > Hi all, > > Keystone has deprecated the domain configuration upload capability > provided through `keystone-manage`. We discussed it's removal in

[openstack-dev] [keystone] office-hours tag

Hey all, I've created a new official tag, 'office-hours' [0]. If you're reviewing or triaging bugs and come across one that would be a good fit for us to tackle during office hours, please feel free to tag it. I was maintaining lists locally, and I'm sure you were, too. This should help reduce

[openstack-dev] [keystone] removing domain configuration upload via keystone-manage

Hi all, Keystone has deprecated the domain configuration upload capability provided through `keystone-manage`. We discussed it's removal in today's meeting [0] and wanted to send a quick note to the operator list. The ability to upload a domain config into keystone was done as a stop-gap until

[openstack-dev] [keystone] documentation migration and consolidation

Hey all, We recently merged the openstack-manuals admin-guide into keystone [0] and there is a lot of duplication between the admin-guide and keystone's "internal" operator-guide [1]. I've started proposing small patches to consolidate the documentation from the operator-guide to the official

Re: [openstack-dev] [keystone] New Office Hours Proposal

According to the poll results, office hours will be moved to Tuesday 19:00 - 22:00 UTC. We'll officially start tomorrow after the keystone meeting. Thanks for putting together and advertising the poll, Harry! On 06/20/2017 02:30 PM, Harry Rybacki wrote: > Greetings All, > > We would like to

Re: [openstack-dev] [tc][all] Move away from meeting channels

On 06/26/2017 08:58 AM, Chris Dent wrote: > On Mon, 26 Jun 2017, Flavio Percoco wrote: > >> So, should we let teams to host IRC meetings in their own channels? > > Yes. +1 > >> Thoughts? > > I think the silo-ing concern is, at least recently, not relevant on > two fronts: IRC was never a good

Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion

On 06/22/2017 12:57 PM, Mike Perez wrote: > Hey all, > > In the community wide goals, we started as a group discussing goals at > the OpenStack Forum. Then we brought those ideas to the mailing list > to continue the discussion and include those that were not able to be > at the forum. The

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 06/21/2017 11:55 AM, Matt Riedemann wrote: > On 6/21/2017 11:17 AM, Shamail Tahir wrote: >> >> >> On Wed, Jun 21, 2017 at 12:02 PM, Thierry Carrez >> > wrote: >> >> Shamail Tahir wrote: >> > In the past, governance has helped (on

Re: [openstack-dev] [all] Policy rules for APIs based on "domain_id"

Domain support hasn't really been adopted across various OpenStack projects, yet. Ocata was the first release where we had a v3-only jenkins job set up for projects to run against (domains are a v3-only concept in keystone and don't really exist in v2.0). I think it would be great to push on some

Re: [openstack-dev] [rally][no-admin] Finally Rally can be run without admin user

On Tue, Jun 13, 2017 at 3:51 PM, Morgan Fainberg wrote: > On Tue, Jun 13, 2017 at 1:04 PM, Boris Pavlovic wrote: > > Hi stackers, > > > > Intro > > > > Initially Rally was targeted for developers which means running it from > > admin was OK. > >

Re: [openstack-dev] [all] etcd3 as base service - update

On Fri, Jun 9, 2017 at 11:17 AM, Clint Byrum <cl...@fewbar.com> wrote: > Excerpts from Lance Bragstad's message of 2017-06-08 16:10:00 -0500: > > On Thu, Jun 8, 2017 at 3:21 PM, Emilien Macchi <emil...@redhat.com> > wrote: > > > > > On Thu, Jun 8,

<    1   2   3   4   5   >