<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hi,<br>
    <br>
    Completely agree with your last statement,but always good to know
    what other people are doing around identity (albiet web identity in
    this case).<br>
    I am not the best person to run with that integration, however, I
    know the guy that would be.  I will reach out to him to see if that
    would be an interesting side project.<br>
    <br>
    Cheers<br>
    James<br>
    <br>
    <br>
    On 5/26/11 4:22 PM, Ziad Sawalha wrote:
    <blockquote
cite="mid:16213_1306419758_p4QEMWWj020011_CA03CA70.45B76%25ziad.sawalha@rackspace.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>Hi James – this is interesting work. Desire to incorporate it
        into Keystone will increase when and if it gains traction.
        Either way, if this is something someone (you?) wants to
        implement as a keystone plug-in, that's why we made it
        pluggable.</div>
      <div><br>
      </div>
      <div>Reconfirming also that we're specifically not trying to solve
        identity (or web identity) with Keystone. We're focused on
        providing a framework for integrating any existing standard (or
        custom) identity solution into OpenStack.</div>
      <div><br>
      </div>
      <div>Thanks for the link.</div>
      <div><br>
      </div>
      <div>Z</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div style="font-family: Calibri; font-size: 11pt; text-align:
          left; color: black; border-width: 1pt medium medium;
          border-style: solid none none; border-color: rgb(181, 196,
          223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in
          0in;">
          <span style="font-weight: bold;">From: </span>James Weir <<a
            moz-do-not-send="true"
            href="mailto:james.weir@usharesoft.com">james.weir@usharesoft.com</a>><br>
          <span style="font-weight: bold;">Date: </span>Thu, 26 May
          2011 09:52:54 +0200<br>
          <span style="font-weight: bold;">To: </span>Ziad Sawalha <<a
            moz-do-not-send="true"
            href="mailto:ziad.sawalha@rackspace.com">ziad.sawalha@rackspace.com</a>><br>
          <span style="font-weight: bold;">Cc: </span>"<a
            moz-do-not-send="true"
            href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>"
          <<a moz-do-not-send="true"
            href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
          <span style="font-weight: bold;">Subject: </span>Re:
          [Openstack] Keystone Release #1 - seeking community input<br>
        </div>
        <div><br>
        </div>
        <div>
          <div bgcolor="#ffffff" text="#000000">Hi,<br>
            <br>
            Unsure if this is interesting also to consider under the
            keystone project:<br>
            <br>
            <a moz-do-not-send="true" class="moz-txt-link-freetext"
              href="http://www.w3.org/wiki/Foaf+ssl">http://www.w3.org/wiki/Foaf+ssl</a><br>
            <br>
            This is more for social web, but might be interesting for
            user authentication.<br>
            <br>
            Regards<br>
            James<br>
            <br>
            <br>
            On 5/26/11 9:04 AM, Ziad Sawalha wrote:
            <blockquote
cite="mid:3037_1306393496_p4Q74p5s004697_C9F4FFEB.422C8%25ziad.sawalha@rackspace.com"
              type="cite">
              <div>Hi Everyone!</div>
              <div><br>
              </div>
              <div>It's been a while since the summit in Santa Clara. It
                was great meeting with everyone who was there – looking
                forward to the next one!</div>
              <div><br>
              </div>
              <div>Since the summit, we've been working on Keystone and
                figuring out how to integrate it into OpenStack (Nova,
                Swift, Glance, and the dashboard). There has been much
                activity on the project. The code, design, and API has
                been changing daily. Anyone interested, please join us.</div>
              <div><br>
              </div>
              <div><b><u>RELEASE 1</u></b></div>
              <div>Milestone 1 for Diablo is right around the corner
                already! The goal remains to create a common auth system
                supporting existing use cases. There are a couple of
                proposals we'd like community input on before we get too
                far into the implementation:</div>
              <ol>
                <li>API spec </li>
                <li>Scope of first release </li>
              </ol>
              <div><b>API Spec</b></div>
              <div>We've published an API spec doc which we've been
                altering as requests come in for changes. The spec
                includes proposals for a core API that covers:</div>
              <ul>
                <li>tokens: for authentication </li>
                <li>tenants: for isolating and grouping resources to
                  support multi-tenancy </li>
                <li>users: because we have to! </li>
                <li>roles: to support the Nova roles (see <a
                    moz-do-not-send="true"
                    href="http://nova.openstack.org/runnova/managing.users.html">
http://nova.openstack.org/runnova/managing.users.html</a> for roles and
                  users) </li>
                <li>credentials: to address the EC2, Rackspace auth,
                  multiple-credentials question
                </li>
              </ul>
              <div>The draft spec is on github and includes both the
                core APIs and additional extensions needed to make
                Keystone function as a stand-alone system. We'd like to
                lock it down as soon as is feasible. R1 is too close
                (June 2nd) so we probably won't be done by then, but
                aiming for Friday June 10th gives us a good couple of
                weeks to get there and then a couple of weeks to firm up
                implementation and tests, so we should be able to hit R2
                with a locked down API.</div>
              <div><br>
              </div>
              <div><br>
              </div>
              <div><b>Scope of R1</b></div>
              <div>For the first Diablo milestone, we're aiming to
                support the user stories listed in <a
                  moz-do-not-send="true"
                  href="http://wiki.openstack.org/KeystoneR1">http://wiki.openstack.org/KeystoneR1</a></div>
              <div><br>
              </div>
              <div><br>
              </div>
              <div><b><u>ANNOUNCEMENTS</u></b></div>
              <div><br>
              </div>
              <div><b>Repo</b></div>
              <div>
                <div>We're moving the source to the Rackspace repo
                  (mainly because we can add multiple admins). Please
                  start using the new repo. I will keep both in sync for
                  a while.</div>
                <div><br>
                </div>
                <div><a moz-do-not-send="true"
                    href="https://github.com/rackspace/keystone">https://github.com/rackspace/keystone</a>/</div>
                <div><br>
                </div>
                <div>I was able to change my config with those commands:</div>
                <div>
                  <blockquote style="margin: 0px 0px 0px 40px;
                    border-style: none; padding: 0px;">
                    <div>git remote rm origin</div>
                    <div>git remote add origin -m master -t master <a
                        moz-do-not-send="true"
                        class="moz-txt-link-freetext" href="https://">
                        https://</a><font class="Apple-style-span"
                        color="#ff0000">your</font><i><font
                          class="Apple-style-span" color="#ff0000">-login</font></i>@github.com/rackspace/keystone.git</div>
                  </blockquote>
                </div>
                <div><br>
                </div>
                <div>As you open new issues, please use the Rackspace
                  repo.</div>
                <div><br>
                </div>
              </div>
              <div><b>Participate</b></div>
              <div>If you're interested in joining the team and working
                on Keystone, we'd love the input and help. Just let me
                know. And, of course, anyone is welcome to submit code,
                blueprints, issues, etc…</div>
              <div><br>
              </div>
              <div>Looking forward to hearing from ya'll.</div>
              <div><br>
              </div>
              <div>Ziad</div>
              <div><br>
              </div>
              <pre>Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:abuse@rackspace.com">abuse@rackspace.com</a>, and delete the original message.
Your cooperation is appreciated.
</pre>
              <pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Mailing list: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a>
Post to     : <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://launchpad.net/%7Eopenstack">https://launchpad.net/~openstack</a>
More help   : <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></pre>
            </blockquote>
            <br>
            <br>
            <pre class="moz-signature" cols="72">-- 
James Weir
Chief Technology Officer
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:james.weir@usharesoft.com">james.weir@usharesoft.com</a>
Linkedin: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/jamesweir">http://www.linkedin.com/in/jamesweir</a>
Tel: +33 (0)675 23 80 23

<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.usharesoft.com">www.usharesoft.com</a>
twitter.com/usharesoft</pre>
          </div>
        </div>
      </span>
      <pre>Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at <a class="moz-txt-link-abbreviated" href="mailto:abuse@rackspace.com">abuse@rackspace.com</a>, and delete the original message. 
Your cooperation is appreciated.
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
James Weir
Chief Technology Officer
<a class="moz-txt-link-abbreviated" href="mailto:james.weir@usharesoft.com">james.weir@usharesoft.com</a>
Linkedin: <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/jamesweir">http://www.linkedin.com/in/jamesweir</a>
Tel: +33 (0)675 23 80 23

<a class="moz-txt-link-abbreviated" href="http://www.usharesoft.com">www.usharesoft.com</a>
twitter.com/usharesoft</pre>
  </body>
</html>