Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Wednesday, October 5 • 3:30pm - 3:55pm
Service Endpoint Template Location

Sign up or log in to save this to your schedule and see who's attending!

Today, Keystone distinguishes service endpoints by Service Name/Type and Region. We would like to propose a change to the endpoint schema to allow further delineation by introducing a new complex type 'location' and attribute 'locationType'. The complex type describes the location of the endpoint and allows clients to choose services based on geography, region, and zone. This can be extremely useful when privacy laws might dictate which geography, thus service endpoint you use when storing certain types of information. Additionally, allowing a client to distinguish to the zone level can be beneficial in supporting client controlled HA within a region. Location type would be a required attribute based on an enumeration that clients could use to help them understand how, and whether, to consume the optional elements of location. For example, if the location type is 'enterprise' then clients probably do not care about zone, region, and geography. However, if the location type where cloud, then a client would want to consume the location information to help draw further distinctions on service endpoint. Concepts: - Zone: (or availability zone) a self-documenting name that represents a physically distinct install location of OpenStack services within a single region. This might be separate buildings on a campus, separate rooms in a data center, etc - Region: A collection of zones - Geo: A collection of regions Example: Zone = z1 Region = West Geography = US

Wednesday October 5, 2011 3:30pm - 3:55pm
Salon A

Attendees (18)