Open Stack

Hello,

I have just tried the new "specs" proposal. Hope it is not too bad (maybe the text could be better but
english is not my language) :)


I have also included some of you involved with federations as reviewers.

Cheers,
Marco



On Tue, May 27, 2014 at 09:15:31AM -0500, Dolph Mathews wrote:
> On Tue, May 27, 2014 at 8:12 AM, Marco Fargetta
> <Marco.Fargetta at ct.infn.it>wrote:
> 
> > On Tue, May 27, 2014 at 07:39:01AM -0500, Dolph Mathews wrote:
> > > On Tue, May 27, 2014 at 6:30 AM, Marco Fargetta
> > > <Marco.Fargetta at ct.infn.it>wrote:
> > >
> > > > Hi All,
> > > >
> > > >
> > > > >   • Federated Keystone and Horizon
> > > > >       □ Completely open-ended, there isn't much an expectation that
> > we
> > > > deliver
> > > > >         this in Juno, but it's something we should start thinking
> > about.
> > > > >       □
> > > >
> > > > I have just registered a new blueprint for this point:
> > > >
> > > > https://blueprints.launchpad.net/keystone/+spec/saml-web-authn
> > > >
> > > > Could you have a look and let me know if it make sense for the
> > integration
> > > > with keystone
> > > > before I start with the code?
> > > >
> > >
> > > That's a comparable blueprint to how we've written them historically, but
> > > you're about to be bitten by a change in process (sorry!).
> > >
> > > Starting with work landing in Juno milestone 2, we're going to start
> > > requiring that design work be done using the following template:
> > >
> > >
> > https://github.com/openstack/keystone-specs/blob/master/specs/template.rst
> > >
> > > And proposed against the release during which the work is intended to
> > ship,
> > > for example:
> > >
> > >   https://github.com/openstack/keystone-specs/tree/master/specs/juno
> > >
> >
> > Therefore, this means that I have to write the specs using the template
> > you sent and submit for review, correct?
> >
> 
> Yes - the impact of your proposal (un?)fortunately happens to be a great
> use case for the design detail required by the new template. Poke us in
> #openstack-keystone if you need any help getting a formal spec up!
> 
> 
> >
> >
> >
> > > Since we're new to this as well, I'd also suggest referencing nova's
> > -specs
> > > repo which has a head start on keystone's (and is where we're copying the
> > > overall process from):
> > >
> > >   https://github.com/openstack/nova-specs
> > >
> > >
> > > >
> > > > Cheers,
> > > > Marco
> > > >
> > > > (NOTE: this is my first bp here so let me know if I miss something in
> > the
> > > > process)
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > OpenStack-dev mailing list
> > > > OpenStack-dev at lists.openstack.org
> > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > >
> > > >
> >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >

> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-- 
====================================================
Eng. Marco Fargetta, PhD
 
Istituto Nazionale di Fisica Nucleare (INFN)
Catania, Italy

EMail: Marco.Fargetta at ct.infn.it
====================================================

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5483 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140530/932bc6da/attachment.bin>