OpenStack Mitaka Design Summit

By definition, DefCore picks what is required for vendors to use the OpenStack trademark. Ideally, that allows workloads to interoperate between vendors.  A common baseline may help users but can impact vendor differentiation.

So does that mean we are picking winners?  Join us at this session and we'll give you the background and review the critical issues to answer that question.

What is DefCore?  With a growing number of OpenStack projects, we define what is the minimum set of OpenStack capabilities and components that must be enabled.  We go further and define the actual tests (from Tempest) that vendor clouds must pass.  

Why? DefCore is trying to define the minimum set of capabilities for INTEROPERABLE CLOUDS; it is not about an OpenStack distribution or release but trying to create a multi-vendor ecosystem.

After attending this session, you will know what DefCore is, how capabilities get defined, and how it is decided what is and what is not part of DefCore.

After we cover the basics, we'll bring you up to speed on the hard questions that DefCore is trying to address.