[Openstack] Folsom Keystone and Grizzly Swift
Good morning, I have really simple and stupid question but I just want to confirm my assumptions Do you expect any possible problems if I will use Folsom release of Keystone with Grizzly release of Swift ? I believe that there shouldn't be any as swift in both versions using the same protocol , but I will feel much safer if you can confirm that Thank you Radek ___ 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] Folsom Keystone and Grizzly Swift
Yes it will work, but I would not recommend it for production systems. There were some changes in Keystone during the Grizzly release that are pretty much required for Keystone to be usable with Swift (specifically around Keystone's ability to support token caching). My recommendation would be to upgrade Keystone to its grizzly release or consider an alternative auth system for Swift. --John On Jun 11, 2013, at 1:23 AM, raydzu rary...@interia.pl wrote: Good morning, I have really simple and stupid question but I just want to confirm my assumptions Do you expect any possible problems if I will use Folsom release of Keystone with Grizzly release of Swift ? I believe that there shouldn't be any as swift in both versions using the same protocol , but I will feel much safer if you can confirm that Thank you Radek ___ 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] Folsom Keystone and Grizzly Swift
python-keystoneclient latest should be release independent and should be compatible with folsom and have the fix you need for caching (the cache=swift.cache parameter to have in auth_token). You will need a recent version of swift tho to get everything working well. On Tue, Jun 11, 2013 at 4:39 PM, John Dickinson m...@not.mn wrote: Yes it will work, but I would not recommend it for production systems. There were some changes in Keystone during the Grizzly release that are pretty much required for Keystone to be usable with Swift (specifically around Keystone's ability to support token caching). My recommendation would be to upgrade Keystone to its grizzly release or consider an alternative auth system for Swift. --John On Jun 11, 2013, at 1:23 AM, raydzu rary...@interia.pl wrote: Good morning, I have really simple and stupid question but I just want to confirm my assumptions Do you expect any possible problems if I will use Folsom release of Keystone with Grizzly release of Swift ? I believe that there shouldn't be any as swift in both versions using the same protocol , but I will feel much safer if you can confirm that Thank you Radek ___ 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 ___ 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] Folsom Keystone and Grizzly Swift
Ah, yes. Thanks Chmouel. My comments were specifically for the code in python-keystoneclient, not the keystone server. Sorry for the lack of clarity. --John On Jun 11, 2013, at 10:37 AM, Chmouel Boudjnah chmo...@enovance.com wrote: python-keystoneclient latest should be release independent and should be compatible with folsom and have the fix you need for caching (the cache=swift.cache parameter to have in auth_token). You will need a recent version of swift tho to get everything working well. On Tue, Jun 11, 2013 at 4:39 PM, John Dickinson m...@not.mn wrote: Yes it will work, but I would not recommend it for production systems. There were some changes in Keystone during the Grizzly release that are pretty much required for Keystone to be usable with Swift (specifically around Keystone's ability to support token caching). My recommendation would be to upgrade Keystone to its grizzly release or consider an alternative auth system for Swift. --John On Jun 11, 2013, at 1:23 AM, raydzu rary...@interia.pl wrote: Good morning, I have really simple and stupid question but I just want to confirm my assumptions Do you expect any possible problems if I will use Folsom release of Keystone with Grizzly release of Swift ? I believe that there shouldn't be any as swift in both versions using the same protocol , but I will feel much safer if you can confirm that Thank you Radek ___ 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 ___ 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] Folsom Keystone and Grizzly Swift
That's great Thank you Radek Od: John Dickinson m...@not.mn Do: Chmouel Boudjnah chmo...@enovance.com; Wysłane: 19:49 Wtorek 2013-06-11 Temat: Re: [Openstack] Folsom Keystone and Grizzly Swift Ah, yes. Thanks Chmouel. My comments were specifically for the code in python-keystoneclient, not the keystone server. Sorry for the lack of clarity. --John On Jun 11, 2013, at 10:37 AM, Chmouel Boudjnah wrote: python-keystoneclient latest should be release independent and should be compatible with folsom and have the fix you need for caching (the cache=swift.cache parameter to have in auth_token). You will need a recent version of swift tho to get everything working well. On Tue, Jun 11, 2013 at 4:39 PM, John Dickinson wrote: Yes it will work, but I would not recommend it for production systems. There were some changes in Keystone during the Grizzly release that are pretty much required for Keystone to be usable with Swift (specifically around Keystone's ability to support token caching). My recommendation would be to upgrade Keystone to its grizzly release or consider an alternative auth system for Swift. --John On Jun 11, 2013, at 1:23 AM, raydzu wrote: Good morning, I have really simple and stupid question but I just want to confirm my assumptions Do you expect any possible problems if I will use Folsom release of Keystone with Grizzly release of Swift ? I believe that there shouldn't be any as swift in both versions using the same protocol , but I will feel much safer if you can confirm that Thank you Radek ___ 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
