As OpenStack becomes ubiquitous, organizations have reason to deploy multiple OpenStack clouds, sites, regions, "edges," or to distribute computing, to list a few possibilities and terms. These requirements could be based on capacity, latency, geographic location, high availability, other needs, or a combination of any or all.
But how should these varied and complex OpenStack systems be designed, deployed, and managed? What should the architecture be? Or even more basic, what to these terms mean, and who uses what definition and how do they differ? As we will show, even the nomenclature is difficult, as there are several major architectures, use-cases, and groups to be considered.
We will present an overview of the various options, projects, and decision points for this topic and detail the positives and negatives of various approaches, as well as what the gaps are in terms of solutions
Attendees to this presentation should come away with a good understanding of common terminology, uses-cases, and architectures concerning organizational requirements which depend on deploying multiple OpenStack Clouds, regions, sites, edges, distributed compute, or other similar architectures. We hope attendees will be able to go back to their organizations and recognize requirements that suggest the aforementioned architectures may be needed, what the benefits and issues are, and in doing so are able to help the organization make informed decisions.
