Re: [Openstack] [Swift] [Keystone] Account migration
Keystone was just revised to separate Tenant id's from names. ID's are now backend-managed (auto-incremented SQL primary keys, for example), while names are read/writable through the admin API. The same change also applies to Users (and Roles is in the works). -Dolph On 09/14/2011 12:32 AM, gaurav gangalwar wrote: 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. Regards, Gaurav On Wed, Sep 14, 2011 at 2:44 AM, Nguyen, Liem Manh liem_m_ngu...@hp.commailto:liem_m_ngu...@hp.com wrote: 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? Liem -Original Message- From: John Dickinson [mailto:m...@not.mnmailto:m...@not.mn] Sent: Tuesday, September 13, 2011 2:01 PM To: Nguyen, Liem Manh Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] [Swift] [Keystone] Account migration 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. On Sep 13, 2011, at 3:48 PM, Nguyen, Liem Manh wrote: 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:m...@not.mnmailto:m...@not.mn] Sent: Tuesday, September 13, 2011 1:11 PM To: Nguyen, Liem Manh Cc: openstack@lists.launchpad.netmailto:openstack@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/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp This email may include confidential information. If you received it in error, please delete it. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Swift] [Keystone] Account migration
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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
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:m...@not.mn] Sent: Tuesday, September 13, 2011 1:11 PM To: Nguyen, Liem Manh Cc: openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] [Keystone] Account migration
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. On Sep 13, 2011, at 3:48 PM, Nguyen, Liem Manh wrote: 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:m...@not.mn] Sent: Tuesday, September 13, 2011 1:11 PM To: Nguyen, Liem Manh Cc: openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] [Keystone] Account migration
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@lists.launchpad.net [mailto:openstack-bounces+jason.rouault=hp@lists.launchpad.net] On Behalf Of Nguyen, Liem Manh Sent: Tuesday, September 13, 2011 2:49 PM To: John Dickinson Cc: openstack@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:m...@not.mn] Sent: Tuesday, September 13, 2011 1:11 PM To: Nguyen, Liem Manh Cc: openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] [Keystone] Account migration
Swift uses the entire account string as part of the lookup. Therefore a different account string means that everything associated with that account (account, containers, and objects) would have to be rehashed. That's basically a fancy way of saying copy the data from the old account to the new one, or, as was originally stated, migrate. There are no plans to migrate accounts in swift from one account string to another (ie account rename). --John On Sep 13, 2011, at 3:57 PM, Souza, Bob wrote: John, If you migrate a user's account ID from uuid to reseller_prefix_tenant, dhw would you find an object that was stored in the ring based on is (uuid, container, object) tuple? Or maybe you are suggesting that is bad idea? b -Original Message- From: openstack-bounces+bob.souza=hp@lists.launchpad.net [mailto:openstack-bounces+bob.souza=hp@lists.launchpad.net] On Behalf Of John Dickinson Sent: Tuesday, September 13, 2011 4:11 PM To: Nguyen, Liem Manh Cc: openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] [Keystone] Account migration
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? Liem -Original Message- From: John Dickinson [mailto:m...@not.mn] Sent: Tuesday, September 13, 2011 2:01 PM To: Nguyen, Liem Manh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [Swift] [Keystone] Account migration 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. On Sep 13, 2011, at 3:48 PM, Nguyen, Liem Manh wrote: 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:m...@not.mn] Sent: Tuesday, September 13, 2011 1:11 PM To: Nguyen, Liem Manh Cc: openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
