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 <[email protected]> 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 <[email protected]> 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 : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
