Increasingly, interoperability is the focus of conversation as we enter the era of multi cloud. Still up for debate though, is where exactly this compatibility should be focused: at the infrastructure or orchestration level? For example, at the infrastructure layer, the ability to perform actions between clouds using Federated Keystone to operate one cloud from another was demonstrated in Vancouver at the OpenStack Summit 2015. At the orchestration layer, we can focus on the interoperability of tools like Terraform and Heat across different clouds to achieve interoperability of your workloads. We’d also like to explore some interesting workload-based scenarios for demonstrating interoperability at both the infrastructure and orchestration levels (as guided by DefCore and tested by RefStack). Which path will lead to driving different clouds to support similar features while also providing the right feedback to the ecosystem? Join us for a spirited discussion!
The goal of this panel is to challenge common misunderstandings or definitions of Interop, and facilitate a call to action within the OpenStack community to explore areas we can seek to continue improving interoperability (whether this is meaningful at either the infrastructure or orchestration level).