Thanks, So if I use generic ComputeService abstraction APIs to communicate to openstack there are APIs like listAssignableLocations() and getAvailabilityZones(). How these terms map to openstack terminologies?
On Fri, Apr 25, 2014 at 8:46 PM, Everett Toews <[email protected]>wrote: > There's a bit of a terminology disconnect in jclouds when it comes to > OpenStack regions. > > The jclouds term for an OpenStack region is zone. > > e.g. If you were working with Nova Servers, > > NovaApi.getServerApiForZone("RegionOne"); > > I've documented in the Terminology section [1] of the OpenStack guide. > > Everett > > [1] http://jclouds.apache.org/guides/openstack/#terminology > > > On Apr 25, 2014, at 5:36 AM, Shital Patil <[email protected]> wrote: > > Hi, > I am using openstack specific jclouds API for nova,neutron and glance. I > would like to know how the requests will differ for openstack deployment > over multiple regions and zones. As I know in multiple region deployment > service endpoints are different but keystone URL is same. > > > http://kimizhang.wordpress.com/2013/08/26/openstack-zoning-regionavailability-zonehost-aggregate/ > > I have seen APIs for getnoVaExtensionForzone(), getneutronExtensionForzone > but nothing for regions > > So what would we need to specify to differentiate between services from > various regions? > > Thank you > > > > > > >
