[openstack-dev] [tc][election] non-candidacy for TC

Folks, due to changes in my day job I will not be running in the next TC election. I still intend to contribute to OpenStack whenever possible. I look forward to seeing how the community continues to grow, change, and approach new challenges. I'd like to encourage others to step up to the

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

It was great working with and getting to know you over the years Jamie, you did tremendous work with in keystone, particularly maintaining the libraries. I'm sure you'll succeed in your new position, I'll miss our late-night-east-coast, early-morning-aus chats. Keep in touch. On Mon, Oct 2, 2017

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

Congrats Kristi! Well deserved indeed! On Tue, Aug 15, 2017 at 3:00 PM, Lance Bragstad wrote: > 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

Re: [openstack-dev] [OpenStack-Dev][OpenStackClient] - Running functional tests

Looks like running tox will pass along any environment variables with the prefix "OS_" from the shell to tox, see https://github.com/openstack/python-openstackclient/blob/master/tox.ini#L55 So as long as you've sourced or exported a bunch of env. variables, you should be ready to run tests. You

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

++ to what colleen said. I've always preferred using the file-backed approach. I think we deprecated it for completeness and to only have a single tool for configuring LDAP-backed domains. If it's tested well enough and not much effort to support then we should keep it around as an alternative

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

Great to see this consolidation happen! On Mon, Jun 26, 2017 at 4:09 PM, Lance Bragstad wrote: > 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"

Re: [openstack-dev] [keystone] Colleen Murphy for core

Yay! Very glad to see this happen. Thanks for all your work Colleen! On Tue, May 2, 2017 at 2:15 PM, Lance Bragstad wrote: > Hey folks, > > During today's keystone meeting we added another member to keystone's core > team. For several releases, Colleen's had a profound

Re: [openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

Cool, thanks for sharing Adrian. On Tue, May 2, 2017 at 12:11 AM, Adrian Turjak wrote: > Hello OpenStack folks, > > As part of my dev work I recently put together a cool little tool which > lets me have much easier access to the various OpenStack python clients > in the

Re: [openstack-dev] [keystone][horizon] weekly meeting

As someone who helped orchestrate the weekly sync-ups, I'll chime in. I always intended for these meetings to end once we accomplished most of the goals [1] we identified last summit. With most of the goals accomplished, scaling back or ending them entirely seems appropriate. We can always start

Re: [openstack-dev] Arrivederci

You'll be missed! Best of luck in your next adventure, they are very lucky to have you. On Wed, Mar 22, 2017 at 8:06 AM, Ian Cordasco wrote: > Hi everyone, > > Friday 24 March 2017 will be my last day working on OpenStack. I'll remove > myself from teams (glance, craton,

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 8, 2017 at 2:04 PM, Andreas Jaeger wrote: > > Very few people know about these URLs at all and there are only a few > places that use it in openstack (I just send a few patches for those). > ++ I had no idea they existed...

Re: [openstack-dev] [keystone] mascot

this looks great! On Mon, Feb 13, 2017 at 9:28 PM, Lance Bragstad wrote: > 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

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On Thu, Feb 2, 2017 at 10:33 AM, Mike Bayer wrote: > > > well, let me blow your mind and agree, but noting that this means, *we > drop SQLite also*. IMO every openstack developer should have > MySQL/MariaDB running on their machine and that is part of what runs if you >

[openstack-dev] [keystone] removing Guang Yee (gyee) from keystone-core

Due to inactivity and a change in his day job, Guang was informed that he would be removed from keystone-core, a change he understands and supports. I'd like to publicly thank Guang for his years of service as a core member. He juggled upstream and downstream responsibilities at HP while bringing

Re: [openstack-dev] gate jobs - papercuts

On Tue, Jan 31, 2017 at 12:49 PM, Davanum Srinivas wrote: > Folks, > > Here's the list of job failures that failed in the gate queue. > captured with my script[1][2] since around 10:00 AM today. All jobs > failed with just one bad test. > >

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Sun, Jan 29, 2017 at 8:05 PM, Kendall Nelson wrote: > PTL Nomination is now over. The official candidate list is available on > the election website[0]. > It's great to see only 1 project was without a PTL! > There is only 1 project without candidates, so according

Re: [Openstack] keystone-manage error - Devstack Mitaka

12). > Thanks again > > Silvia > > 2017-01-25 14:37 GMT+01:00 Steve Martinelli <s.martine...@gmail.com>: > >> sounds like you're using the master branch of devstack to install the >> mitaka version of openstack, it is advised that you use the mitaka branch &

Re: [Openstack] keystone-manage error - Devstack Mitaka

sounds like you're using the master branch of devstack to install the mitaka version of openstack, it is advised that you use the mitaka branch of devstack to do that. $ https://github.com/openstack-dev/devstack.git -b stable/mitaka $ cd devstack $ $ ./stack.sh On Wed, Jan 25, 2017 at 8:20 AM,

Re: [openstack-dev] [Requirements] Freeze

Hey Matthew, The OpenStackClient team will be posting patches to bump the minimum level of python-openstacksdk to the latest release 0.9.13 (out today). We'll also be releasing a new python-openstackclient version (3.8.0), which should also be the minimum version. On Tue, Jan 24, 2017 at 3:22

Re: [openstack-dev] [keystone]Error while setting up a keystone development environment

why not use devstack [1] with a minimal local.conf (used to specify which components to install) ? [1] http://docs.openstack.org/developer/devstack/ minimal local.conf: [[local|localrc]] RECLONE=yes # Credentials DATABASE_PASSWORD=openstack ADMIN_PASSWORD=openstack SERVICE_PASSWORD=openstack

Re: [openstack-dev] [ python-novaclient][ python-glanceclient][ python-cinderclient][ python-neutronclient] Remove x-openstack-request-id logging code as it is logged twice

On Fri, Jan 20, 2017 at 10:53 PM, Kekane, Abhishek < abhishek.kek...@nttdata.com> wrote: > Hi Dims, > > Thank you for reply. I will propose a patch soon. Just for curiosity, > keystoneauth1 >= 2.17.0 will not install 2.18.0? > It will, but if we make 2.18.0 the minimum then it will for sure

Re: [openstack-dev] [all] new os-api-ref warning, changes may be needed

Thanks for addressing this in the keystone project Sean! On Fri, Jan 20, 2017 at 12:41 PM, Sean Dague wrote: > We released a new os-api-ref yesterday which includes a few > enhancements, including the anchor links on the website working as > expected now. > > One of the things

[openstack-dev] [osc][openstackclient][glance] broken image functional test

hey glancerinos, it seems the OSC gate is broken, several patches are failing the same way: testtools.matchers._impl.MismatchError: !=: reference = '''\ qcow2 True 4 5 d35ba06a07654721bb730ea154b9c6e7 ''' actual= u'''\ qcow2 False 4 5 d35ba06a07654721bb730ea154b9c6e7 ''' In short, the test

Re: [Openstack] [OpenStack] [Swift] Bug: Swift doesn't save last "end of file" characters

| ++---+--+ | my.cnf | new_con | 458ebc5af3d43bc7bf31498942d3cfc0 | ++---+--+ # rm my.cnf # openstack object save new_con my.cnf # cat -A my.cnf [client-server]$ !includedir /etc/my.cnf.d$ $ On Tue, Jan 17, 2017 at 3:32 PM, Steve

Re: [Openstack] [OpenStack] [Swift] Bug: Swift doesn't save last "end of file" characters

feel free to file a bug with https://bugs.launchpad.net/python-openstackclient and we can investigate it there, which version of OSC are you using? On Tue, Jan 17, 2017 at 3:08 PM, Alexandr Porunov < alexandr.poru...@gmail.com> wrote: > Hello, > > I am using Openstack Newton. > I found a small

Re: [openstack-dev] [release][ptl] not planning to serve as release PTL for Pike

+++ Thanks for making it 100x easier to release new libraries, it's now something I look forward to. On Fri, Jan 13, 2017 at 3:11 PM, Davanum Srinivas wrote: > Many thanks for all the automation and all other initiatives Doug! > > On Fri, Jan 13, 2017 at 3:00 PM, Doug

Re: [openstack-dev] Consistent Versioned Endpoints

On Fri, Jan 13, 2017 at 7:39 AM, Sean Dague wrote: > On 01/12/2017 01:35 PM, Scott D'Angelo wrote: > > TL;DR: Let's discuss Version Discovery and Endpoints in the Service > > Catalog at the PTG in Atlanta. > > > > The topic of Versioning and the Endpoints discovered in the

[openstack-dev] [keystone] etherpad for ptg

keystoners, here is the link to the etherpad for the ptg: https://etherpad.openstack.org/p/keystone-pike-ptg here is a link to other project etherpads: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads I'll announce this in our meeting today also. - steve

Re: [openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

Neil Jerram" <n...@tigera.io> wrote: > Hi Steve, > > On Tue, Jan 10, 2017 at 7:35 AM Steve Martinelli <s.martine...@gmail.com> > wrote: > >> In preparation for the next TC meeting, a survey was sent out to driver >> maintainers, here is a summary of the feedba

[openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

In preparation for the next TC meeting, a survey was sent out to driver maintainers, here is a summary of the feedback that was gathered. Major observations == * Are drivers an important part of OpenStack? YES! * Discoverability of drivers needs to be fixed immediately. * It

Re: [Openstack] Download file from swift extremely slow

Thanks for the hint Clay, we merged https://review.openstack.org/#/c/417892/ - expect this issue to be fixed in OpenStackClient 3.7.0. On Fri, Jan 6, 2017 at 2:03 PM, Clay Gerrard wrote: > Is this *really* the default chunk_size? > >

Re: [Openstack] FW: Stable Mitaka Devstack Installation Failing with 'deprecated_reason'

that sounds about right, thanks for confirming with the solution! On Thu, Jan 5, 2017 at 11:42 AM, Harsh Kumar B wrote: > Hello, > > Thanks for replying. I had a working VM which I was trying to replicate on > a bare metal so I was building in offline mode. Once I

Re: [Openstack] FW: Stable Mitaka Devstack Installation Failing with 'deprecated_reason'

what version of oslo.config was laid down? it should be at least 3.2.0 to support "deprecated_reason" -- https://github.com/openstack/oslo.config/blob/stable/mitaka/oslo_config/cfg.py#L719-L720 using the mitaka branch of devstack should lay down version 3.7.0. can you include the local.conf and

Re: [Openstack] Download file from swift extremely slow

ller:8776/v1/ > 6fc70c831270448296c9c25361769cf5", "interface": "public", " > region": "RegionOne", "region_id": "RegionOne", "id": " > 9679385e8bf646c195b4387d07e39813"}, {"url": "http://contr

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

your opinion, what in keystone requires most attention" >> with choices "federation", "performance", "policy", "backend support" >> and some other options. >> >> On 12/30/2016 11:54 PM, Steve Martinelli wrote: >> > We

Re: [Openstack] Download file from swift extremely slow

Does doing ``openstack object save container1 cirros-0.3.4-x86_64-disk.img --debug`` give any additional information? What about using the swift CLI? any difference in speed? ``swift download container1 cirros-0.3.4-x86_64-disk.img`` ? On Wed, Jan 4, 2017 at 7:19 AM, wawayu

[openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

We have the opportunity to ask one question on the upcoming user survey and we get to decide the audience to which we serve the question. Our audience options are: USING, TESTING, or INTERESTED in Keystone (I think we should aim for USING or TESTING) The question can take one of several

[openstack-dev] [keystone] reminder: no meeting today

see everyone next week, happy holidays! stevemar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Those look like they were introduced in the latest release, and related to the OpenStackSDK refactoring that hit openstackclient networking commands. We actually released the new version because folks were hitting similar errors, but for more often used commands (like listing security groups or

Re: [openstack-dev] Proposing Steve Martinelli for project-team-guide core

you probably know, the OpenStack Project Team Guide is a piece of > >> documentation geared towards project teams, to help them navigate the > >> troubled and complex waters of being an official OpenStack team: > >> > >> http://docs.openstack.org/project-team

Re: [openstack-dev] [docs] Stepping down from core

Sorry to see you go Matt. Thanks for everything you've done with in the docs project, and thank you for always taking the time to field all the setup questions in #openstack and #openstack-dev from the newcomers, it was invaluable. Hoping your new opportunity brings you much success. On Wed, Dec

Re: [openstack-dev] [keystone] office hours starting January 6th

Thanks for setting this up Lance! You can count on me to join and smash some bugs. On Wed, Dec 21, 2016 at 1:06 PM, Lance Bragstad wrote: > Hi folks! > > If you remember, last year we started a weekly bug day [0]. The idea was > to dedicate one day a week to managing

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

On Tue, Dec 20, 2016 at 4:39 PM, Clay Gerrard wrote: > > On Tue, Dec 20, 2016 at 1:00 PM, Hongbin Lu wrote: > >> >> >> $ openstack objectstore container >> >> $ openstack container container >> >> $ openstack secret container >> >> >> >>

Re: [Openstack] Keystone apis: public vs. admin

gt; On 12/15/16 12:50 PM, Andrew Bogott wrote: > > I'm trying to set up an unprivileged keystone account that can query (but > not modify) various openstack services. > > Many thanks to Steve Martinelli who helped me sort this out on IRC > today. As I understand it, with the v3 key

Re: [Openstack] [OpenStack] [Keystone] Performance difference between ferret and uuid tokens

On Sat, Dec 10, 2016 at 10:59 AM, Alexandr Porunov < alexandr.poru...@gmail.com> wrote: > Hello, > > I read a blog about performance comparison between fernet and uuid tokens. > They said that fernet tokens is 30% faster for creation but 400% slower for > validation. Is it true? > > I assume you

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

At the last TC meeting [1] we discussed this topic and the various options that were presented, here's a quick recap: Options that will be removed, the patches for these options will be abandoned: - Red (option 6), it had the least support - Hard black (option 1) in favor of soft black

Re: [Openstack] Difference between image listings...

Ah, you're the second person to run into this problem this week, and I think it's because we (OSC) now default the image API to v2. v1 image listing worked well, we used the markers that glance returned back correctly. Turns out for v2 we weren't doing this, and only the first 20-30 images get

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

I'm OK with the agreed approach in the patch, we restrict the ID being specified to 32 character UUID4 string. And it only works on project create, not update. On Mon, Dec 5, 2016 at 1:20 PM, Andrey Grebennikov < agrebenni...@mirantis.com> wrote: > Hi keystoners, > I'd like to open the

Re: [Openstack] Creating regions...

"Regions" is definitely an overloaded term and I'm not surprised by your remarks at all. Hopefully I can help out with the openstack CLI bits at least. To create regions in keystone you need to use v3 of the API, this may involve changing up the bits of info you use to authenticate (Like adding

Re: [openstack-dev] [release] Release management team draft logo

A bit of colour should will go a long way here, black and brown would help make it more obvious (IMO). On Fri, Dec 2, 2016 at 4:05 AM, Thierry Carrez wrote: > Doug Hellmann wrote: > > Release team, please take a look at the attached logo and let me know > > what you

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

This happened to us for keystone-specs [1]. I settled on removing the reference to the README.rst from the doc folder. You can do the same by removing [2]. [1] https://review.openstack.org/#/c/402878/ [2] https://github.com/openstack/neutron-lib/blob/master/doc/source/readme.rst On Wed, Nov 30,

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Refresh (not from cache)? On Wed, Nov 30, 2016 at 11:23 AM, Ben Nemec wrote: > > > On 11/30/2016 10:19 AM, Jason Rist wrote: > >> On 11/30/2016 11:18 AM, Ben Nemec wrote: >> >>> >>> >>> On 11/30/2016 03:34 AM, Flavio Percoco wrote: >>> On 25/11/16 13:46 +,

Re: [openstack-dev] [keystone] Stepping down from keystone core

Marek, thanks for everything you've done in Keystone. It was loads of fun to develop some of the early federation work with you back in the Icehouse release! Good luck in whatever the future holds for you! On Tue, Nov 22, 2016 at 5:18 PM, Marek Denis < marek.denis+openst...@gmail.com> wrote: >

Re: [Openstack] [keystone] keystone high availability document is out-of-date and doesn't work on newton

On Tue, Nov 22, 2016 at 3:28 AM, Hong Gang Liu wrote: > Hi folks, > > > > I'm working on setting up keystone(identity API) high available function > with Newton release on CentOS 7.2 . According to document > http://docs.openstack.org/ha-guide/controller-ha-identity.html , I

Re: [openstack-dev] [keystone] Pike PTL

one of these days i'll learn how to spell :) On Mon, Nov 21, 2016 at 12:52 PM, Steve Martinelli <s.martine...@gmail.com> wrote: > Keystoners, > > I do not intend to run for the PTL position of the Pike development cycle. > I'm sending this out early so I can work wit

[openstack-dev] [keytone] Pike PTL

Keystoners, I do not intend to run for the PTL position of the Pike development cycle. I'm sending this out early so I can work with folks interested in the role, If you intend to run for PTL in Pike and are interested in learning the ropes (or just want to hear more about what the role means)

Re: [Openstack-operators] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

On Thu, Nov 17, 2016 at 11:04 PM, darren chan wrote: > Good timing, I was about to send a follow-up email about this spec. > > I agree, this content needs to be more visible, which is why the spec > proposed to move upgrade notes to the Upgrades chapter in the Operations

Re: [openstack-dev] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

On Thu, Nov 17, 2016 at 11:04 PM, darren chan wrote: > Good timing, I was about to send a follow-up email about this spec. > > I agree, this content needs to be more visible, which is why the spec > proposed to move upgrade notes to the Upgrades chapter in the Operations

[openstack-dev] [docs][upgrades] time to add official docs for upgrading services?

In the keystone docs we have notes about how to upgrade between releases [1], so does the nova team [2]. Is it time we create an official guides to [3] for this subject? [1] http://docs.openstack.org/developer/keystone/upgrading.html [2] http://docs.openstack.org/developer/nova/upgrade.html [3]

Re: [openstack-dev] [keystone] Weekly Policy Meeting

slowly >>> started massaging that information into our first agenda. I'll continue to >>> do so and send out another email on Tuesday as a reminder to familiarize >>> yourselves with the etherpad before the meeting. >>> >>> >>> Thanks! >>

Re: [openstack-dev] [keystone] meeting format poll

On Wed, Nov 16, 2016 at 9:10 AM, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2016-11-15 17:23:49 -0500 (-0500), Steve Martinelli wrote: > > I don't bother with the time slider, the meeting agenda is never deleted > > from the etherpad, we just keep tacking on

Re: [openstack-dev] [keystone] meeting format poll

On Tue, Nov 15, 2016 at 4:53 PM, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2016-11-15 15:31:40 -0500 (-0500), Steve Martinelli wrote: > > I really like the etherpad approach, its nice to see the history from > > previous meetings > > Strange, I personally fin

Re: [openstack-dev] [osc][openstackclient][cliff] translation the command description in help

On Tue, Nov 15, 2016 at 4:08 PM, Steve Martinelli <s.martine...@gmail.com> wrote: > $ find . -name '*.py' -exec sed -i .bak -e 's/""".*"""/_description=_("&")/g' > {} \; > > pep8 just bu

[openstack-dev] [osc][openstackclient][cliff] translation the command description in help

The following is a PSA for all OpenStackClient plugins. Matt Edmonds filed bug 1636209 [1] against OpenStackClient because the main help message was not getting translated. In the example below, the "Create new user" string was not translated (some of the help text was removed for readability):

Re: [openstack-dev] [keystone] meeting format poll

I really like the etherpad approach, its nice to see the history from previous meetings On Tue, Nov 15, 2016 at 2:39 PM, Lance Bragstad wrote: > Hey folks, > > In today's keystone meeting, Morgan mentioned that we had the ability to > go back to using OpenStack Wikis for

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

on this! On Thu, Nov 3, 2016 at 10:11 AM, Steve Martinelli <s.martine...@gmail.com> wrote: > As a heads up to some of keystone's consuming projects, we will be > changing the default token format from UUID to Fernet. Many patches have > merged to make this possible [1]. The last 2 that yo

Re: [openstack-dev] [keystone] Weekly Policy Meeting

Thanks for taking the initiative Lance! It'll be great to hear some ideas that are capable of making policy more fine grained, and keeping things backwards compatible. On Thu, Nov 10, 2016 at 3:30 PM, Lance Bragstad wrote: > Hi folks, > > After hearing the recaps from the

Re: [openstack-dev] Anyone want to meetup at KubeCon?

You can try finding Brad Topol, he's presently at Kubecon and familiar with all things Keystone. On Tue, Nov 8, 2016 at 4:49 PM, Stephen McQuaid wrote: > We have been developing a keystone authz webhook for easy integration. If > anyone is interested we can look at

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On Sat, Nov 5, 2016 at 6:15 PM, Jay Pipes <jaypi...@gmail.com> wrote: > On 11/05/2016 01:15 AM, Steve Martinelli wrote: > >> The keystone team has a new spec being proposed for the Ocata release, >> it essentially boils down to adding properties / metadata for

[openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

The keystone team has a new spec being proposed for the Ocata release, it essentially boils down to adding properties / metadata for projects (for now) [1]. We have somewhat had support for this, we have an "extras" column defined in our database schema, whatever a user puts in a request that

Re: [openstack-dev] [tc][solum] is solum-infra-guestagent an unmaintained project?

bump, still hoping to get feedback on this On Fri, Oct 28, 2016 at 1:23 AM, Steve Martinelli <s.martine...@gmail.com> wrote: > When reviewing the projects necessary for the ocata community-wide goal, > (to remove old oslo-incubator code [1]) I noticed that solum-infra-guest > agen

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

, Nov 3, 2016 at 10:23 AM, Alex Schultz <aschu...@redhat.com> wrote: > Hey Steve, > > On Thu, Nov 3, 2016 at 8:11 AM, Steve Martinelli <s.martine...@gmail.com> > wrote: > > As a heads up to some of keystone's consuming projects, we will be > changing > > the d

[openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

As a heads up to some of keystone's consuming projects, we will be changing the default token format from UUID to Fernet. Many patches have merged to make this possible [1]. The last 2 that you probably want to look at are [2] and [3]. The first flips a switch in devstack to make fernet the

Re: [openstack-dev] [keystone] Keystone multinode grenade job

Testing upgrades without downtime is definitely something we need to improve. At the summit Dolph Mathews (dolphm on irc) was also looking at testing out the new upgrade flow. I'm not sure what his plans are, but getting in contact with him would be a good first step. On Wed, Nov 2, 2016 at 3:44

[openstack-dev] [keystone] new keystone core (breton)

. Upon interacting with Boris, you quickly realize he has a high standard for quality and keeps us honest. Thanks for all your hard work Boris, I'm happy to have you on the team. Steve Martinelli stevemar __ OpenStack Development

[openstack-dev] [tc][solum] is solum-infra-guestagent an unmaintained project?

When reviewing the projects necessary for the ocata community-wide goal, (to remove old oslo-incubator code [1]) I noticed that solum-infra-guest agent has had *very* few commits, 13 in total [2]. Almost half of which were project cleanup type changes that all projects did. The last patch of

Re: [openstack-dev] [Keystone][Design Session] Where to propose extensions to trusts?

On Fri, Oct 21, 2016 at 5:01 AM, Johannes Grassler wrote: > Hello, > > I've got a last minute proposal, or rather two of them for the Keystone > side of > the design sessions in Barcelona. I guess it's something that would fit the > Authorization work session on Friday

Re: [openstack-dev] [release][ptl] pausing releases until 1 Nov

On Oct 20, 2016 5:15 PM, "Emilien Macchi" wrote: > > On Thu, Oct 20, 2016 at 9:27 PM, Doug Hellmann wrote: > > It's late in the week and the release and infra teams need to see > > to our travel preparations. I am declaring the releases repository > >

[openstack-dev] [keystone] meeting canceled next week (oct 25 2016)

due to the summit we'll be canceling the meeting next week. stevemar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [all] running non-devstack jobs in Python projects aka "it works outside devstack"

On Thu, Oct 13, 2016 at 10:30 PM, Davanum Srinivas wrote: > > Matt, Emilien, > > there's one more option, run jobs daily and add the output to the > openstack health dashboard. > example - http://status.openstack.org/openstack-health/#/g/build_ >

[openstack-dev] [keystone][horizon] keystone/horizon integration session in barcelona

The keystone team had a spare fishbowl session, and we decided to use it to collaborate with the horizon team on a few long standing issues we've had between the two projects. You can view the session online: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16907 Details

Re: [openstack-dev] [all][stable] Moving stable/mitaka to Phase-II and liberty to Phase-III

On Mon, Oct 10, 2016 at 5:34 PM, Tony Breeds wrote: > On Mon, Oct 10, 2016 at 08:42:48AM +0200, Ihar Hrachyshka wrote: > > > I think it would also make sense to *release* on the boundary of the > switch; > > so that it’s clear which phase a release followed. > > What do

Re: [openstack-dev] [OpenStack-docs] Admin guide in-tree?

On Oct 9, 2016 6:57 PM, "Lana Brindley" wrote: > > Why the rush? I think its more eagerness than rush. Project teams made a lot of head way with the API ref and install guides being in-tree that they want to keep the momentum with the admin guide.

Re: [Openstack-operators] [EXTERNAL] Re: Tenant/Project naming restrictions

ation Analyst Sr/SAIC Lead 09321 > Common Engineering Environment > dgv...@sandia.gov > > -Original Message- > From: Saverio Proto [mailto:ziopr...@gmail.com] > Sent: Thursday, October 6, 2016 1:21 AM > To: Steve Martinelli <s.martine...@gmail.com> >

[openstack-dev] [keystone] design session schedule and etherpads

Hey Keystoners, I've created an initial draft of the keystone design session schedule. A live view is at [1]. I'm attaching the times, etherpads, and descriptions for each fishbowl / work session. So please start priming the etherpads with content. Also bookmark them! You'll notice we have one

Re: [Openstack-operators] Tenant/Project naming restrictions

There are some restrictions. 1. The project name cannot be longer than 64 characters. 2. Within a domain, the project name is unique. So you can have project "foo" in the "default" domain, and in any other domain. On Wed, Oct 5, 2016 at 5:16 PM, Vigil, David Gabriel wrote: >

Re: [openstack-dev] [Keystone] Project name DB length

On Mon, Oct 3, 2016 at 10:52 AM, gordon chung wrote: > > > the original thread died pretty quickly; it didn't seem like an issue to > anyone or needed fixing... if only there was a global council that > worked on such technical things :P > > ah great idea, perhaps we should call it

[openstack-dev] TC candidacy

I’d like to also toss my name into the ring. I’m announcing my candidacy for a position on the OpenStack Technical Committee. -- About me I have served as the Keystone PTL for the Mitaka and Newton cycles, and will again serve as the PTL for the Ocata cycle. I’ve also contributed heavily to

Re: [openstack-dev] [Keystone] Project name DB length

We may have to ask Adam or Dolph, or pull out the history textbook for this one. I imagine that trying to not bloat the token was definitely a concern. IIRC User name was 64 also, but we had to increase to 255 because we're not in control of name that comes from external sources (like LDAP). On

Re: [openstack-dev] TC candidacy

On Wed, Sep 28, 2016 at 2:49 PM, gordon chung wrote: > > > On 28/09/2016 12:41 PM, Chris Dent wrote: > > > > * Information is not always clear nor clearly available, despite > > valiant efforts to maintain a transparent environment for the > > discussion of policy and process.

[openstack-dev] [horizon][keystone] retiring python-keystoneclient-kerberos

Hi there, I would like to retire the python-keystoneclient-kerberos repo [1]. The repo was pretty basic, it had a single auth plugin. The logic has since been copied over to keystoneauth1 and provided you have kerberos libraries installed the plugin will be available to you. The last release of

Re: [openstack-dev] [osc][keystone] User Project List

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: >

Re: [openstack-dev] [osc][keystone] User Project List

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

[openstack-dev] [keystone] Design session ideas for Barcelona

] https://etherpad.openstack.org/p/keystone-ocata-summit-brainstorm Thanks, Steve Martinelli __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [keystone] gate-keystoneclient-dsvm-functional-ubuntu-xenial is broken

Since September 14th the keystoneclient functional test job has been broken. Let's be mindful of infra resources and stop rechecking the patches there. Anyone have time to investigate this? See patches https://review.openstack.org/#/c/369469/ or https://review.openstack.org/#/c/371324/

Re: [openstack-dev] Too many mails on announce list again :)

I think bundling the puppet, ansible and oslo releases together would cut down on a considerable amount of traffic. Bundling or grouping new releases may not be the most accurate, but if it encourages the right folks to read the content instead of brushing it off, I think thats worth while. On

[openstack-dev] [keystone][ptl][election] PTL candidacy

Hey everyone, I'd like to continue to serve as the PTL of the keystone project for the Ocata release. I served as PTL of the keystone project for the Mitaka and Newton development cycles. I find the role to be extremely rewarding, and would be honoured to continue to serve in the same capacity,

[openstack-dev] [keystone] Retrospective for Newton

I like what Matt [1] and Armando [2] have done for post-mortems / retrospectives, so I'm borrowing both. Rather than use our specs repo I think we should just use an etherpad [3] for now. Please help fill it in and give feedback on how the release went. I'll start priming the content now but would

Re: [openstack-dev] [requirements][FFE][keystone][release] block keystonemiddleware 4.0.0

We're more than happy with that outcome, and may have already started the patch ;) https://review.openstack.org/#/c/370011/ On Wed, Sep 14, 2016 at 5:10 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Steve Martinelli <s.martine...@gmail.com> wrote: > > A bug was r

[openstack-dev] [requirements][FFE][keystone][release] block keystonemiddleware 4.0.0

A bug was recently filed against keystone [1]. As of the Newton release we depend on a class being public -- BaseAuthProtocol instead of _BaseAuthProtocol [2]. Which was introduced in 4.1.0 [3]. The current requirement for keystonemiddleware is: keystonemiddleware>=4.0.0,!=4.1.0,!=4.5.0

  1   2   3   4   >