Hey Keystoners!
I’ve written up a summary for a few of the technical aspects of the
mid-cycle [1]. Dolph has written up a mid-cycle retrospective [2]. For a
full summary see the etherpad [3].
We came out of the mid-cycle with a lot of TODOs, here is a summary of the
action items.
everyone
- Re
Yes, known bug, try with version 3.0.1
On Aug 22, 2016 3:46 PM, "Andrey Pavlov" wrote:
> I have an issue with new openstack client -
>
> openstack client is installed in new virtual env. it version is 3.0.0
> os-client-config!=1.19.0,>=1.13.1 (from osc-lib>=0.4.0->python-
> openstackclient)
>
>
The keystone team is pursuing a trigger-based approach to support rolling,
zero-downtime upgrades. The proposed operator experience is documented here:
http://docs.openstack.org/developer/keystone/upgrading.html
This differs from Nova and Neutron's approaches to solve for rolling
upgrades (whic
I want to welcome Ron De Rose (rderose) to the Keystone core team. In a
short time Ron has shown a very positive impact. Ron has contributed
feature work for shadowing LDAP and federated users, as well as enhancing
password support for SQL users. Implementing these features and picking up
various b
>
> On 09/02/2016 01:53 PM, Doug Hellmann wrote:
>
>> Excerpts from Thierry Carrez's message of 2016-09-02 12:15:33 +0200:
>
> I agree with Sean: increasing the variety of technologies used increases
>>> the system complexity, which in turn requires more skills to fully
>>> understand and maintain
There's been a bug filed against OSC to implement ospurge for cleaning up
resources in (compute, network, storage, image and identity) [1] for a
while now. As Jordan said, this is something we want to be modular, and
pluggable, so other OSC plugins could extend this clean up command.
[1] https://b
Thanks for your leadership, dedication and hard work over the last 18
months. I've always enjoyed working with you to resolve the gate failures
(despite being a cause of said failures :] )
On Fri, Sep 9, 2016 at 12:05 PM, Emilien Macchi wrote:
> Hi,
>
> I wrote a little blog post about the last
ystone to use Shibboleth (which you did, I
snipped that part of the message), then you can set it up to use these
social logins as well. See documentation here:
http://docs.openstack.org/developer/keystone/federation/federated_identity.html#id4
> Thanks.
>
> Best regards,
>
> W
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 +, Amrith Kumar wrote:
>
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, 2
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 think.
>
> It's not immediate
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 discussion
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 (option
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
>>
>>
>>
>> Thoughts?
>>
>
> This is the closest thing I can see
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 keystone's bug queue by tri
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
now, 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-guide/
> >>
>
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
IPs
see everyone next week, happy holidays!
stevemar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mai
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 forms
>
> On Tue, Jan 3, 2017 at 3:05 PM, Boris Bobrov wrote:
>
>> "What were you trying to accomplish with keystone but failed"
>> "What functionality in keystone did you try to use but it wasn't good
>> enough"
>> "In your opinion, what in
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 is
"Neil Jerram" wrote:
> Hi Steve,
>
> On Tue, Jan 10, 2017 at 7:35 AM Steve Martinelli
> wrote:
>
>> 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.
>>
>
>
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
___
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 Service
> > Catalog was
+++ 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 Hellmann
> wrote:
> > I an
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
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 in there is a new
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 insta
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
RA
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 PM,
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 to this
> resolution[1],
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.
>
> http://logs.openstack.org/48/423548/11/gate/gate-keyston
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
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
> expect to run database-re
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 use when I get them don
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
Blockin
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
wrote:
> Steve Martinelli wrote:
>
> A bug was recently filed against keystone [1]. As of the Newton releas
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
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, if
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 Mon
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/
___
.
[1] 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.openstac
On Wed, Sep 21, 2016 at 1:04 PM, Dolph Mathews
wrote:
>
> I should also express a +1 for something along the lines of your original
> proposal. I'd go so far as to suggest that `openstack show user` (without a
> user ID or name as an argument) should return "me" (the authenticated
> user), as I t
On Wed, Sep 21, 2016 at 6:34 PM, Adrian Turjak
wrote:
>
>
> What I'd like to do is one of these two options:
> - "openstack user project list", a command which will get your id from
> your authed token and used it directly with the keystoneclient as such:
> "keystoneclient.projects.list(user='')
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
py
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. There is more t
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 We
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
python
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 a committee :)
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 fi
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.
_
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 PTLs / stable CPLs think?
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 her
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_
> name/periodic-ironic-py35-with-oslo-master
But t
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
http://lists.opens
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
> > frozen until the Tuesday after summit, 1 Nov.
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 (09:00-09:40) but I'm not s
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
signif
. 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 Develo
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 A
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
selecte
n Thu, Nov 3, 2016 at 10:23 AM, Alex Schultz wrote:
> Hey Steve,
>
> On Thu, Nov 3, 2016 at 8:11 AM, Steve Martinelli
> 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
bump, still hoping to get feedback on this
On Fri, Oct 28, 2016 at 1:23 AM, Steve Martinelli
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
> agent has had *very* few commi
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 does
On Sat, Nov 5, 2016 at 6:15 PM, Jay Pipes 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 projects
>> (for now) [1].
&
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 open-sourcing it
>
>
>
> Step
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 summit, it sounds like
!
On Thu, Nov 3, 2016 at 10:11 AM, Steve Martinelli
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 you probably want to look
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 meeting agendas. I creat
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):
=
On Tue, Nov 15, 2016 at 4:08 PM, Steve Martinelli
wrote:
> $ find . -name '*.py' -exec sed -i .bak -e 's/""".*"""/_description=_("&")/g'
> {} \;
>
>
On Tue, Nov 15, 2016 at 4:53 PM, Jeremy Stanley 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 find it way easier to navigate the
On Wed, Nov 16, 2016 at 9:10 AM, Jeremy Stanley 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
>
> Oh, I see, using it
s work will already be familiar with the problem, but I
>>> want to make it easy for folks who aren't to ramp up quickly and get them
>>> into the discussion.
>>>
>>> Some have already started contributing to the etherpad! I've slowly
>>> start
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] h
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
> Guide. However, it seem
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) the
one of these days i'll learn how to spell :)
On Mon, Nov 21, 2016 at 12:52 PM, Steve Martinelli
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 with folks interested in the ro
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:
> Hi
201 - 280 of 280 matches
Mail list logo
