On Mon, Aug 04, 2014 at 10:37:08AM -0600, Chris Custine wrote: > > > HP should either have a default region for all language bindings > > > > @Chris: Would that work? If so, which region would make most sense? > > If the desire is to set a default that matches the original region-a.geo-1 > endpoint, then yes I think this would be the ONLY way to achieve it > consistently. One of the problems with using first or last is that either one > of them can change at any time depending on how keystone returns the > endpoints list (adding a new region, for instance). My preference would be to > force a caller to explicitly specify a region, but I think that will be the > case anyway when we migrate to the new swift api provider from labs. > > Should I work this in to 1.8.1-SNAPSHOT later this week?
Ideally jclouds should follow the best practice of whatever HP recommends and what other language bindings implement. We should not gratuitously change the defaults; if I understand it correctly, we will impose three transitions to users of the default region: 1.7.3 swift = default region region-a.geo-1 1.8.0 swift = default region region-b.geo-1 1.8.1 swift = default region changes back to region-a.geo-1? openstack-swift = error without default region How can we minimize this pain? -- Andrew Gaul http://gaul.org/
