<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Keystone was just revised to separate Tenant "id's" from "names".<br>
<br>
ID's are now backend-managed (auto-incremented SQL primary keys, for example), while names are read/writable through the admin API.<br>
<br>
The same change also applies to Users (and Roles is in the works).
<pre class="moz-signature" cols="72">-Dolph</pre>
<br>
On 09/14/2011 12:32 AM, gaurav gangalwar wrote:
<blockquote cite="mid:CAJiE4OmgHWeXBj9R+YfFf2i=XbWddF3fumm9YRf3VcLj=TW7_w@mail.gmail.com" type="cite">
For swauth there is provision to change account_id using swauth-set-account-service, it could be changed to the tenant_id, but since account_id is part of the hashing, old data in that account won't be accessible, i am not familiar with keystone, is there any
such service in keystone to change tenant_id, then we can change tenant_id to the account_id, and old account will be accessible.<br>
<br>
Regards,<br>
Gaurav<br>
<br>
<div class="gmail_quote">On Wed, Sep 14, 2011 at 2:44 AM, Nguyen, Liem Manh <span dir="ltr">
<<a moz-do-not-send="true" href="mailto:liem_m_nguyen@hp.com">liem_m_nguyen@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Without changing the account id, how do I map the uuid of the old account to a Keystone tenant Id? For a given tenantId, I would like to be able to reference both the corresponding Swift account and Nova project, right?<br>
<div class="im"><br>
Liem<br>
<br>
-----Original Message-----<br>
From: John Dickinson [mailto:<a moz-do-not-send="true" href="mailto:me@not.mn">me@not.mn</a>]<br>
</div>
<div>
<div class="h5">Sent: Tuesday, September 13, 2011 2:01 PM<br>
To: Nguyen, Liem Manh<br>
Cc: <a moz-do-not-send="true" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Subject: Re: [Openstack] [Swift] [Keystone] Account migration<br>
<br>
Why would the account need to change? Can the swift account reference in keystone be set to the old value? If not, then yes you will have 2 swift accounts.<br>
<br>
<br>
On Sep 13, 2011, at 3:48 PM, Nguyen, Liem Manh wrote:<br>
<br>
> Thanks, John, for pointing out the uuid thing :).<br>
><br>
> So, let's say I have stored data into a Swift account with a UUID. When I switch to using Keystone, I would like to continue using my "old" account, since I have a bunch of data in it. However, the account format has changed (under Keystone). So, if I
have lazy provisioning on (account_autocreate), would I *accidentally* have 2 Swift accounts instead of one? Ideally, if I can "migrate" all the old account Ids to use the new format, that would guarantee consistency between the old accounts and any newly-created
accounts. Am I missing something here?<br>
><br>
> Liem<br>
><br>
> -----Original Message-----<br>
> From: John Dickinson [mailto:<a moz-do-not-send="true" href="mailto:me@not.mn">me@not.mn</a>]<br>
> Sent: Tuesday, September 13, 2011 1:11 PM<br>
> To: Nguyen, Liem Manh<br>
> Cc: <a moz-do-not-send="true" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Subject: Re: [Openstack] [Swift] [Keystone] Account migration<br>
><br>
> Swift treats the <hash> or <tenantid> part of the account as an opaque string. (Technically, the first one isn't a hash but a uuid.) I don't think there is any migration path because there is nothing to migrate.<br>
><br>
> But I may be missing something.<br>
><br>
> --John<br>
><br>
><br>
> On Sep 13, 2011, at 2:55 PM, Nguyen, Liem Manh wrote:<br>
><br>
>> Hello Stackers,<br>
>><br>
>> With swauth, Swift accounts are identified by <reseller_prefix>_<hash>. Under Keystone (with swift_auth and Swift's lazy provisioning), I see the Swift account now has the format <reseller_prefix>_<tenantId>. So, if we have existing Swift account data
with the old format, how would one go about migrating from the old format to the Keystone format? Is there a plan to do so within the Diablo time-frame?<br>
>><br>
>> Thanks,<br>
>> Liem<br>
>> _______________________________________________<br>
>> Mailing list: <a moz-do-not-send="true" href="https://launchpad.net/%7Eopenstack" target="_blank">
https://launchpad.net/~openstack</a><br>
>> Post to : <a moz-do-not-send="true" href="mailto:openstack@lists.launchpad.net">
openstack@lists.launchpad.net</a><br>
>> Unsubscribe : <a moz-do-not-send="true" href="https://launchpad.net/%7Eopenstack" target="_blank">
https://launchpad.net/~openstack</a><br>
>> More help : <a moz-do-not-send="true" href="https://help.launchpad.net/ListHelp" target="_blank">
https://help.launchpad.net/ListHelp</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true" href="https://launchpad.net/%7Eopenstack" target="_blank">
https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true" href="mailto:openstack@lists.launchpad.net">
openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true" href="https://launchpad.net/%7Eopenstack" target="_blank">
https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true" href="https://help.launchpad.net/ListHelp" target="_blank">
https://help.launchpad.net/ListHelp</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
<font face="monospace">This email may include confidential information. If you received it in error, please delete it.</font></body>
</html>