The Keystone team has released python-keystoneclient 0.11.2 [1]. This version
includes a number of bug fixes.
Details of new features and bug fixes included in the 0.11.2 release of
python-keystoneclient can be found on the milestone information page [2].
[1]
I am definitely game to join for key signing. I however don't have cards for
this (come to think of it, this is an excuse to get business cards even if they
are only for my key sig). I'll probably try and get some paper slips made up
for this too.
--Morgan
Sent via mobile
On Oct 27, 2014,
11th.
You can see the meeting information and agenda for the next meeting here:
https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting
We will pick up the normal meeting schedule for Keystone on November 18th.
Cheers,
Morgan Fainberg
___
OpenStack-dev
On Nov 2, 2014, at 22:21, Dolph Mathews dolph.math...@gmail.com wrote:
On Sunday, November 2, 2014, John Dennis jden...@redhat.com wrote:
It was hoped we could simply borrow the Keystone mapping
implementation but it was found to be too limiting and not sufficiently
expressive. We could
This is just a friendly reminder that the Keystone weekly meeting on November
11 has been cancelled. This will allow everyone a little more time to unwind
from the summit and get specs proposed etc.
We will resume the normal meeting schedule next week on November 18th.
Thanks for a great
On Nov 11, 2014, at 1:45 PM, Lance Bragstad lbrags...@gmail.com wrote:
On Tue, Nov 11, 2014 at 3:30 PM, Douglas Mendizabal
douglas.mendiza...@rackspace.com mailto:douglas.mendiza...@rackspace.com
wrote:
I think it would also be interesting to hear for the Keystone folks that
are
On Nov 10, 2014, at 4:30 PM, Angus Salkeld asalk...@mirantis.com wrote:
Hi all
I just wanted to make sure we are all under the same understanding of the
outcomes and what the next steps for the versioned objects session are.
1. There is a lot of interest in other projects using oslo
I am trying to pin down a location for our mid-cycle meetup, I need to get an
idea of who will be joining us at the Keystone meetup. I’ve included a couple
questions relating to Barbican in the case we can double-up and have a day of
overlap like the Juno meetup. I apologize for the delay, this
On Nov 12, 2014, at 14:22, Doug Hellmann d...@doughellmann.com wrote:
On Nov 12, 2014, at 4:40 PM, Adam Young ayo...@redhat.com wrote:
On 11/12/2014 02:06 PM, Doug Hellmann wrote:
During our “Graduation Schedule” summit session we worked through the list
of modules remaining the in
This is just a friendly reminder that the Keystone weekly meeting will resume
this week at the normal time. I hope everyone has had a good summit (and
potentially break post summit). Welcome back and see everyone tomorrow!
Cheers,
Morgan Fainberg
I am happy to announce a bunch of the information for the Keystone mid-cycle
meetup. The selection of dates, location, etc is based upon the great feedback
I received from the earlier poll. Currently the only thing left up in the air
is the specific venue and recommended hotel(s).
Location:
On Thursday, November 20, 2014, Anita Kuno ante...@anteaya.info wrote:
On 11/20/2014 09:04 AM, Russell Bryant wrote:
On 11/20/2014 08:55 AM, Thierry Carrez wrote:
This is mostly a cosmetic change: update the messaging around that
meeting to make it more obvious that it's not purely about
The only thing I want to caution against is making a SQL-specific choice. In
the case of some other backends, it may not be possible (for an extremely large
dataset) to get a full count, where SQL does this fairly elegantly. For
example, LDAP (in some cases) may have an administrative limit
.
-Sean
On 11/20/2014 11:28 AM, Morgan Fainberg wrote:
The only thing I want to caution against is making a SQL-specific
choice. In the case of some other backends, it may not be possible (for
an extremely large dataset) to get a full count, where SQL does this
fairly elegantly
On Nov 25, 2014, at 4:25 AM, Henry Nash hen...@linux.vnet.ibm.com wrote:
Hi
As most of you know, we have approved a spec
(https://review.openstack.org/#/c/129397/) to split the assignments component
up into two pieces, and the code (divided up into a series of patches) is
currently
another approach should be taken.
If this is a legitimate issue, maybe we should look at what Neutron is
doing, as they are using alembric for migrations already.
Cheers,
Morgan Fainberg
--
Sent from my iPhone (please excuse the brevity and any typos
for my company,
but I want to move to the memcache driver soon.
Cheers,
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
in IRC I had offered to help with the effort
of moving away from SQLite migration testing; if the nova-way is the
way we want to go, I'll be happy to help contribute to that.
Cheers,
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev
of Icehouse (barring
any major issue) the point in which we move to Alembric. We can be
selective in taking extension modifications that add migration repos if it
is a major concern that moving to Alembric is going to be really painful.
Cheers,
Morgan Fainberg
On Thu, Jul 25, 2013 at 7:35 PM, Adam
=keystone.token.providers.uuid.Provider
In older versions I believe the option (still in the [token] section) is:
token_format=UUID
I hope this info helps you out some.
Cheers,
Morgan Fainberg
Sent from my iPhone (please excuse the brevity)
31/07/2013, Paul Michali :
Yeah I was playing
to review, I am going to agree with Sean here, it is a boon
on large changes. I am against lessening/removing H302; but I understand
why people desire it eased up.
Cheers,
Morgan Fainberg
IRC: morganfainberg
On Tue, Aug 6, 2013 at 1:18 PM, Christopher Armstrong
chris.armstr...@rackspace.com
. This would be a very nice level of
transparency (not that the TC hides anything) and makes it much easier to
see what is/has been going on and how we got there. It also ensures we
have the comments recorded along the way.
Cheers,
Morgan Fainberg
IRC: morganfainberg
(and similar pluggable systems) a bit
more clear.
Cheers!
--
Morgan Fainberg
Sr. Software Architect | Metacloud, Inc
Email: m...@metacloud.com
IRC: morganfainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
for. It would still require lookups
to the backend for a number of reasons (not listed, as I don't think it is
relevant for this conversation).
--
Morgan Fainberg
IRC: morganfainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
import is likely going to take a significant amount of
refactoring. My guess is that it's going to be a bit late in the cycle,
but we will see what comes up.
--Morgan Fainberg
IRC: morganfainberg
On Wed, Sep 4, 2013 at 8:21 AM, Dolph Mathews dolph.math...@gmail.comwrote:
On Wed, Sep 4, 2013
NICE!!
On Wed, Sep 4, 2013 at 11:05 AM, Dan Smith d...@danplanet.com wrote:
Because we landed a patch to tox upstream to use setup.py develop
instead of sdist+install like our run_tests.sh scripts do - this means
that with the new tox config changes, tox runs should be just as quick
as
in place because other things changed? At a certain point restore from
backup is really the only sane option. That threshold isn't exactly a long
period of time.
Cheers,
Morgan Fainberg
IRC: morganfainberg
On Wed, Sep 11, 2013 at 10:30 PM, Robert Collins
robe...@robertcollins.netwrote:
I think
for
packaging ?if it requires packaging). With that being said, I agree that
it make sense for other (non-openstack) libraries to be added carefully
late in the cycle. Perhaps the best would be to limit additions to prior
to the release Feature-Freeze.
Cheers,
Morgan Fainberg
On Sunday, September 15
there. Also is there a minimum version that you require? I think getting
the packagers involved (and know if there is a minimum version requirement)
is the best way to know if it should be accepted.
Cheers,
Morgan Fainberg
IRC: morganfainberg
On Thu, Sep 19, 2013 at 2:08 PM, Mark Washenberger
On Fri, Sep 20, 2013 at 3:20 PM, Monty Taylor mord...@inaugust.com wrote:
What if we rethought the organization just a little bit. Instead of
having oslo-incubator from which we copy code, and then oslo.* that we
consume as libraries, what if:
- we split all oslo modules into their own
usability and ease of
deployment for all of OpenStack. I would be honored to also serve as a
member of the TC, collaborating, and helping to guide the technical
direction of the project as a whole.
Cheers,
Morgan Fainberg
___
OpenStack-dev mailing list
Hi John,
Let me say first off that I 100% agree with the value of the sample config
being in-tree. Keystone has not removed it due to similar feedback I’ve
received. However, the issue is that *gating* on config changes for all
libraries that are included in the sample config is just a process
On Dec 3, 2014, at 1:18 PM, Sean Dague s...@dague.net wrote:
On 12/03/2014 03:58 PM, Morgan Fainberg wrote:
Hi John,
Let me say first off that I 100% agree with the value of the sample config
being in-tree. Keystone has not removed it due to similar feedback I’ve
received. However
As a quick note, the OpenStack Identity Program was not renamed to AAA (based
upon the discussion with the TC) but increased scope to adopt Audit on top of
the already included scope of Authorization and Authentication.
Cheers,
Morgan
--
Morgan Fainberg
On December 8, 2014 at 5:05:51 PM
: Morgan Fainberg morgan.fainb...@gmail.com
To: Adam Young ayo...@redhat.com, OpenStack Development Mailing List
(not for usage questions) openstack-dev@lists.openstack.org
Date: 12/08/2014 06:07 PM
Subject: Re: [openstack-dev] [Keystone] OSAAA-Policy
I agree
it
out of the “common” namespace.
If there are no concerns with this change of direction we will update the
spec[1] to reflect this proposal and continue with the plans to graduate as
soon as possible.
[1] https://review.openstack.org/#/c/140161/
--
Morgan Fainberg
://review.openstack.org/#/q/status:open+project:openstack/keystone-specs,n,z
[2] https://gist.github.com/dolph/651c6a1748f69637abd0
--
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
Fainberg
--
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Friday, December 12, 2014, Sean Dague s...@dague.net wrote:
On 12/12/2014 01:05 PM, Maru Newby wrote:
On Dec 11, 2014, at 2:27 PM, Sean Dague s...@dague.net javascript:;
wrote:
On 12/11/2014 04:16 PM, Jay Pipes wrote:
On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote:
On Dec 11,
On Dec 12, 2014, at 10:30, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Dec 12, 2014 at 6:50 AM, Russell Bryant rbry...@redhat.com wrote:
On 12/11/2014 12:55 PM, Andrew Laski wrote:
Cells can handle a single API on top of globally distributed DCs. I
have spoken with a group that
) it isn’t always possible to replicate the
Keystone data around.
Cheers,
Morgan
Best regards
Henry
Sent from my iPad
On 2014-12-13, at 下午3:12, Morgan Fainberg morgan.fainb...@gmail.com wrote:
On Dec 12, 2014, at 10:30, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Dec 12, 2014 at 6:50
/
Cheers,
Morgan
--
Morgan Fainberg
On December 11, 2014 at 1:05:37 PM, Morgan Fainberg (morgan.fainb...@gmail.com)
wrote:
This is a notification that at the start of next week, all projects under the
Identity Program are going to see a cleanup of old/lingering open reviews. I
will be reviewing all
The Keystone development community would like to announce the release of
python-keystoneclient 1.0.0. The move to the 1.x.x development branch was made
to match the perception that the library has long been considered stable.
Beyond the move to the stable release version, this release is no
The Keystone development community would like to announce the 1.3.0 release of
the keystone middleware package.
This release can be installed from the following locations:
* http://tarballs.openstack.org/keystonemiddleware
* https://pypi.python.org/pypi/keystonemiddleware
1.3.0
---
*
The Keystone development community would like to announce the 1.3.1 release of
the Keystone Middleware package.
This release can be installed from the following locations:
* http://tarballs.openstack.org/keystonemiddleware
http://tarballs.openstack.org/keystonemiddleware
*
Hi Raildo,
Thanks for putting this post together. I really appreciate all the work you
guys have done (and continue to do) to get the Hierarchical Mulittenancy code
into Keystone. It’s great to have the base implementation merged into Keystone
for the K1 milestone. I look forward to seeing the
On Dec 23, 2014, at 1:08 PM, Dolph Mathews dolph.math...@gmail.com wrote:
On Tue, Dec 23, 2014 at 1:33 PM, David Chadwick d.w.chadw...@kent.ac.uk
mailto:d.w.chadw...@kent.ac.uk wrote:
Hi Adam
On 23/12/2014 17:34, Adam Young wrote:
On 12/23/2014 11:34 AM, David Chadwick wrote:
Hi
The Keystone IRC meetings will be on hiatus over the holidays. They will resume
as per normal on January 6th.
Have a good end of the year!
Cheers,
Morgan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
This is just a reminder there will be no meeting this week for Keystone.
Have a great New Years!
--Morgan
Sent via mobile
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Based upon the feedback to this thread, I want to congratulate Brad Topol as
the newest member of the Keystone-Specs-Core team!
—Morgan
On Jan 18, 2015, at 11:11 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
Hello all,
I would like to nominate Brad Topol for Keystone Spec core
Thank you for the heads up.
—Morgan
--
Morgan Fainberg
On February 2, 2015 at 1:15:49 PM, Kurt Taylor (kurt.r.tay...@gmail.com) wrote:
Just FYI, in case there was any questions,
In addition to testing and reporting on Nova, the IBM PowerKVM CI system is now
also testing against Keystone
patches.
--
Morgan Fainberg
On February 2, 2015 at 1:41:08 PM, Anita Kuno (ante...@anteaya.info) wrote:
On 02/02/2015 02:16 PM, Morgan Fainberg wrote:
Thank you for the heads up.
—Morgan
--
Morgan Fainberg
On February 2, 2015 at 1:15:49 PM, Kurt Taylor (kurt.r.tay
On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com) wrote:
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
I think the simple answer is yes. We (keystone) should emit notifications.
And yes other projects should listen.
The only thing really
I think the simple answer is yes. We (keystone) should emit notifications.
And yes other projects should listen.
The only thing really in discussion should be:
1: soft delete or hard delete? Does the service mark it as orphaned, or just
delete (leave this to nova, cinder, etc to discuss)
2:
.
Cheers,
Morgan
--
Morgan Fainberg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo
On Jan 13, 2015, at 9:06 PM, Adrian Turjak adri...@catalyst.net.nz wrote:
Hello openstack-dev,
I'm wondering if there is any interest or need for an open-source user
registration and management service for people using OpenStack.
We're currently at a point where we need a way for
As discussed on IRC: Unfortunately OS X Yosemite ships with a woefully out of
date OpenSSL, LDAP Lib, etc. Some of these are not easy to replace with
homebrew (some are). These out of date libs are usually left only for
compatibility while people move to Apple’s specific alternative libs.
to as core to the Keystone Spec repo.
Voting will remain open until Friday Jan 23.
Cheers,
Morgan Fainberg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
is going in to Keystone.
Please respond with a +1 or -1 for adding Marek to the Keystone core team. This
poll will remain open until Feb 13.
--
Morgan Fainberg
__
OpenStack Development Mailing List (not for usage questions
The Keystone development team is planning to deprecate deployment of Keystone
under Eventlet during the Kilo cycle. Support for deploying under eventlet will
be dropped as of the “M”-release of OpenStack.
The reasoning behind this move is multifaceted but the core of the reasons are
as
++ absolutely!
Sent via mobile
On Jan 27, 2015, at 14:19, Jim Meyer j...@geekdaily.org wrote:
+1 all the way down.
More fun double-plus-good.
—j
On Jan 27, 2015, at 1:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right
Good question! I was planning a keystone liens release very soon, but will
hold off of it will break everything.
--Morgan
On Thursday, January 29, 2015, Thierry Carrez thie...@openstack.org wrote:
Sean Dague wrote:
On 01/27/2015 05:21 PM, Sean Dague wrote:
On 01/27/2015 03:55 PM, Douglas
On Thursday, January 29, 2015, Roman Podoliaka rpodoly...@mirantis.com
wrote:
Hi all,
Mike, thanks for summarizing this in
https://wiki.openstack.org/wiki/PyMySQL_evaluation !
On PyMySQL: this is something we need to enable testing of oslo.db on
Python 3.x and PyPy. Though, I doubt we want
As a quick preface, today there is the assumption you can upgrade and downgrade
your SQL Schema. For the most part we do our best to test all of this in our
unit tests (do upgrades and downgrades land us in the same schema). What isn’t
clearly addressed is that the concept of downgrade might be
On January 29, 2015 at 3:19:34 AM, Yuriy Taraday (yorik@gmail.com) wrote:
Hello.
On Wed Jan 28 2015 at 11:30:43 PM Morgan Fainberg morgan.fainb...@gmail.com
wrote:
LDAP is used in Keystone as a backend for both the Identity (Users and groups)
and assignments (assigning roles to users
A Huge +1 from me.
—Morgan
--
Morgan Fainberg
On January 30, 2015 at 9:20:06 AM, James E. Blair (cor...@inaugust.com) wrote:
Hi,
The Infrastructure program has a unique three-tier team structure:
contributors (that's all of us!), core members (people with +2 ability
on infra projects
As point, we are trying to move away from this model. Having to know the
dependencies is a bad experience in general. But with the move to eliminate
optional parts of the api, most of these become real dependencies for
keystone (a few things will still be optional eg memcache lib).
--Morgan
Putting on my sorry-but-it-is-my-job-to-get-in-your-way hat (aka security),
let's be careful how generous we are with the user and data we hand back. It
should give enough information to be useful but no more. I don't want to see us
opened to weird attack vectors because we're exposing internal
I am of the opinion that the +1/-1 from non tc members can be valuable, but
similarly it would be easy to get just comments. The TC is the body I
expect to help determine the direction of cross project initiatives such as
the logging guidelines. As a PTL I feel confident the TC is the right body
I just want to toss in a quick 2 cents on the topic. It is important for
everyone to feel involved in the naming of our releases. It is part of who we
are. No one (including marketing) should be excluded from the discussion. I see
a lot of good feedback here and it should be fun again! Making
On Jan 5, 2015, at 08:07, Nikhil Komawar nikhil.koma...@rackspace.com wrote:
Based on the feedback received, we would like to avoid logging on the project
channel. My take from the discussion was that it gives many a folks a feeling
of informal platform to express their ideas freely in
when
reviewing / considering the spec for inclusion in the Kilo release.
Any spec that is not approved by the deadline will need an explicit exception
granted to land in Kilo.
Cheers,
Morgan Fainberg
__
OpenStack Development
The Keystone development team is looking for deployment feedback regarding the
use of the LDAP Identity backend. The Identity backend only covers Users and
Groups.
We are looking to get an idea of types (read-only, read-write, etc) and reasons
for use of the LDAP backend. The answers to this
On Jan 8, 2015, at 3:56 PM, Sean Dague s...@dague.net wrote:
On 01/08/2015 06:29 PM, Morgan Fainberg wrote:
As of Juno all projects are using the new keystonemiddleware package for
auth_token middleware. Recently we’ve been running into issues with
maintenance of the now frozen
On Jan 8, 2015, at 16:10, Sean Dague s...@dague.net wrote:
On 01/08/2015 07:01 PM, Morgan Fainberg wrote:
On Jan 8, 2015, at 3:56 PM, Sean Dague s...@dague.net wrote:
On 01/08/2015 06:29 PM, Morgan Fainberg wrote:
As of Juno all projects are using the new keystonemiddleware package
That was a copy paste error. The response was meant to be:
Yes, that is the issue, unbounded version on the stable branches.
--Morgan
Sent via mobile
On Jan 8, 2015, at 22:57, Morgan Fainberg morgan.fainb...@gmail.com wrote:
On Jan 8, 2015, at 16:10, Sean Dague s...@dague.net wrote
On Jan 9, 2015, at 5:28 AM, Thierry Carrez thie...@openstack.org wrote:
Dean Troyer wrote:
On Fri, Jan 9, 2015 at 4:22 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
This is probably a very dumb question, but could you explain why
Assignment
backend which only contains Projects/Tenants and Roles/Grants.
Cheers,
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
+1
Flavio has always been a good gate keeper of stable across the board.
Sent via mobile
On Jan 6, 2015, at 11:32, Adam Gandelman ad...@ubuntu.com wrote:
Hiya-
Flavio has been actively involved in stable branch maintenance for as long as
I can remember, but it looks like his +2
, and experience for the
OpenStack providers, deployers, and users.
Cheers,
Morgan Fainberg
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On February 9, 2015 at 1:25:58 PM, Jay Pipes (jaypi...@gmail.com) wrote:
On 01/20/2015 10:54 AM, Brian Rosmaita wrote:
From: Kevin L. Mitchell [kevin.mitch...@rackspace.com]
Sent: Monday, January 19, 2015 4:54 PM
When we look at consistency, we look at everything else in OpenStack.
From
Based upon the feedback from this thread, I want to welcome Marek as the newest
member of keystone core.
Cheers,
Morgan
--
Morgan Fainberg
On February 10, 2015 at 9:51:16 AM, Morgan Fainberg (morgan.fainb...@gmail.com)
wrote:
Hi everyone!
I wanted to propose Marek Denis (marekd on IRC
On Feb 13, 2015, at 09:42, Jeremy Stanley fu...@yuggoth.org wrote:
For a few months, some project core teams (including Nova's) have
been running with an ACL granting access to the rebase button in
Gerrit for all the projects they manage, a permission usually only
exposed to the owner of
On February 13, 2015 at 11:51:10 AM, Lance Bragstad (lbrags...@gmail.com) wrote:
Hello all,
I'm proposing the Authenticated Encryption (AE) Token specification [1] as an
SPFE. AE tokens increases scalability of Keystone by removing token
persistence. This provider has been discussed prior to,
On February 14, 2015 at 5:59:13 PM, Clint Byrum (cl...@fewbar.com) wrote:
Excerpts from Thomas Goirand's message of 2015-02-14 16:48:01 -0800:
Hi,
I've seen messages in the logs telling that we should move to the
identity_uri.
I don't really like the identity_uri which contains
On February 14, 2015 at 9:53:14 PM, Adam Young (ayo...@redhat.com) wrote:
On 02/13/2015 04:19 PM, Morgan Fainberg wrote:
On February 13, 2015 at 11:51:10 AM, Lance Bragstad (lbrags...@gmail.com) wrote:
Hello all,
I'm proposing the Authenticated Encryption (AE) Token specification [1
On February 15, 2015 at 3:54:24 PM, Thomas Goirand (z...@debian.org) wrote:
On 02/16/2015 12:24 AM, Morgan Fainberg wrote:
So, let me just say that while I do not have a timeline on the removal
of auth fragments, since it is deprecated assume that this should no
longer be used
On February 15, 2015 at 3:16:04 PM, Thomas Goirand (z...@debian.org) wrote:
On 02/15/2015 02:56 AM, Clint Byrum wrote:
Excerpts from Thomas Goirand's message of 2015-02-14 16:48:01 -0800:
Hi,
I've seen messages in the logs telling that we should move to the
identity_uri.
I don't
As a note, since I've seen some responses about users and/or groups on this
survey, I will be sending a survey about identity out today. This survey is
strictly about projects/tenants and roles/role assignments in LDAP.
Sent via mobile
On Jan 6, 2015, at 11:21, Morgan Fainberg morgan.fainb
I think I was just piling on your patch set there. Let me 2x check but that
might just need a rebase now.
--Morgan
Sent via mobile
On Jan 7, 2015, at 12:46, dsta...@dstanek.com wrote:
Hmmm... Might want to check with Morgan to make sure we want that. I thought
he had (and probably
continue to be proposed and approved
regardless of the Feature-Freeze state.
Thanks!
--Morgan Fainberg
(If this email looks a lot like the nova email from Michael Still, It is
because I shamelessly decided to use a lot of the same concepts/verbiage...
imitation is the highest form of flattery
-minimums, instead rely on the
manager to do business logic. This is not the case for all OpenStack
projects.
Best Regards,
Dave Chen
From: Morgan Fainberg [mailto:morgan.fainb...@gmail.com javascript:;]
Sent: Monday, March 09, 2015 2:29 AM
To: David Stanek; OpenStack
:
https://launchpad.net/keystonemiddleware/+milestone/1.5.0
--
Morgan Fainberg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
On March 8, 2015 at 11:24:37 AM, David Stanek (dsta...@dstanek.com) wrote:
On Sun, Mar 8, 2015 at 1:37 PM, Mike Bayer mba...@redhat.com wrote:
can you elaborate on your reasoning that FK constraints should be used less
overall? or do you just mean that the client side should be mirroring the
In general I'd say that cascade is the right approach. There are some very
limited cases where restrict should be used. Overall, I'd like to see less
reliance on FK constraints anywhere. The reason for using Cascade is that
we should be very specific in our code to prevent deletion independent of
The summit planning etherpad for Keystone is here:
https://etherpad.openstack.org/p/Keystone-liberty-summit-brainstorm
Please brainstorm / toss ideas up / discuss the Liberty cycle goals (since
we're almost at RC for Kilo)
Cheers,
--Morgan
-keystoneclient/+milestone/1.2.0
--
Morgan Fainberg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
On Mar 27, 2015, at 09:29, Brant Knudson b...@acm.org wrote:
On Thu, Mar 26, 2015 at 7:37 PM, Anne Gentle annegen...@justwriteclick.com
wrote:
Here's the latest news installment from docsland.
Install Guides updates
-
We've got a spec ready for the
Matt,
The idea is you have a staging key (next key) and you generate that, and sync
it out. Once it is synced out you can rotate to it as needed. All keys on the
server are valid for token validation. Only the active key is used for a
given keystone to issue a token.
Lance has some ansible
success as we move into the Liberty release cycle and beyond not just for
Keystone but all of OpenStack.
Cheers,
Morgan Fainberg
[1]
http://lists.openstack.org/pipermail/openstack-dev/2014-September/046571.html
101 - 200 of 481 matches
Mail list logo
