[Openstack] [Swift] [Keystone] Account migration

Rouault, Jason (Cloud Services) jason.rouault at hp.com
Tue Sep 13 21:14:24 UTC 2011


If there is an existing swift customer with swift account 'foo' and nova
project 'bar', there is no way to have them belong to the same Keystone
tenant.  I think that is the data migration issue.  

Jason

-----Original Message-----
From: openstack-bounces+jason.rouault=hp.com at lists.launchpad.net
[mailto:openstack-bounces+jason.rouault=hp.com at lists.launchpad.net] On
Behalf Of Nguyen, Liem Manh
Sent: Tuesday, September 13, 2011 2:49 PM
To: John Dickinson
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] [Swift] [Keystone] Account migration

Thanks, John, for pointing out the uuid thing :).  

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?

Liem

-----Original Message-----
From: John Dickinson [mailto:me at not.mn] 
Sent: Tuesday, September 13, 2011 1:11 PM
To: Nguyen, Liem Manh
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] [Swift] [Keystone] Account migration

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.

But I may be missing something.

--John


On Sep 13, 2011, at 2:55 PM, Nguyen, Liem Manh wrote:

> Hello Stackers,
>  
> 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?
>  
> Thanks,
> Liem
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4854 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110913/8328bd36/attachment.bin>


More information about the Openstack mailing list