openstack team mailing list archive

[Dolph Mathews <dolph.mathews@xxxxxxxxx>]

It wasn't proposed for backporting nor did jenkins link the bug to the
review:

Review: https://review.openstack.org/#/c/24965/

Bug: https://bugs.launchpad.net/keystone/+bug/1159987

Commit:
https://github.com/openstack/keystone/commit/2f0c46179ea2eb7872167941412bdbd5abca08f0

I tagged the bug as grizzly-backport-potential as it's certainly low impact
and desirable.


-Dolph


On Thu, Mar 28, 2013 at 2:40 PM, Brad Topol <btopol@xxxxxxxxxx> wrote:

> Andy,
>
> Was there a blueprint for this function?  Can I get the review ID?   I am
> very interested in the notion of  custom token creation.
>
> Thanks,
>
> Brad
>
> Brad Topol, Ph.D.
> IBM Distinguished Engineer
> OpenStack
> (919) 543-0646
> Internet:  btopol@xxxxxxxxxx
> Assistant: Cindy Willman (919) 268-5296
>
>
>
> From:        Andy Smith <andyster@xxxxxxxxx>
> To:        Thierry Carrez <thierry@xxxxxxxxxxxxx>
> Cc:        "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
> Date:        03/28/2013 03:27 PM
> Subject:        Re: [Openstack] Keystone Grizzly RC2 available
> Sent by:        openstack-bounces+btopol=us.ibm.com@xxxxxxxxxxxxxxxxxxx
> ------------------------------
>
>
>
> The change I made to build tokens from existing data (rather than
> re-querying it all from the db) didn't go in?
>
> Without it extensions are not able to build custom tokens (meaning just
> about any extension that wants to do something with auth is not possible).
>
>
> On Thu, Mar 28, 2013 at 2:34 AM, Thierry Carrez <*thierry@xxxxxxxxxxxxx*<thierry@xxxxxxxxxxxxx>>
> wrote:
> Hello everyone,
>
> Due to the renaming of the trust extension and a response backward
> compatibility issue, we created a new Grizzly release candidate for
> OpenStack identity ("Keystone").
>
> You can find the RC2 tarball and the list of fixed bugs at:*
> **https://launchpad.net/keystone/grizzly/grizzly-rc2*<https://launchpad.net/keystone/grizzly/grizzly-rc2>
>
> This is hopefully the last Grizzly release candidate for Keystone.
> Unless new release-critical regressions are found that warrant another
> release candidate respin, this RC2 will be formally included in the
> common OpenStack 2013.1 final release next week. You are therefore
> strongly encouraged to test and validate this tarball.
>
> Alternatively, you can grab the code at:*
> **https://github.com/openstack/keystone/tree/milestone-proposed*<https://github.com/openstack/keystone/tree/milestone-proposed>
>
> If you find a regression that could be considered release-critical,
> please file it at *https://bugs.launchpad.net/keystone/+filebug*<https://bugs.launchpad.net/keystone/+filebug>and tag
> it *grizzly-rc-potential* to bring it to the release crew's attention.
>
> Happy regression hunting,
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> _______________________________________________
> Mailing list: *https://launchpad.net/~openstack*<https://launchpad.net/~openstack>
> Post to     : *openstack@xxxxxxxxxxxxxxxxxxx*<openstack@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : *https://launchpad.net/~openstack*<https://launchpad.net/~openstack>
> More help   : *https://help.launchpad.net/ListHelp*<https://help.launchpad.net/ListHelp>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>