Revision as of 16:09, 9 February 2016

Magnum's Native Container APIs

Magnum's support native API access as well as a more limited form of wrapped access to that same functionality through a /container resource in the Magnum API. This means that depending on which bay type you select: Docker Swarm, Kubernetes, or Apache Mesos, you get the API that comes with that container orchestration engine. For example, if I create a Bay in Magnum using the Docker Swarm by type, I will have an API endpoint for the Docker API that I can interact with using the native docker CLI tools.

Project Position on Native APIs

Magnum's contributors recognize the Magnum's native API is the preferred approach, as it offers users a more complete set of features and capabilities, and those can be updated without waiting for Magnum to re-implement them. It also allows for use of native tooling, which is the preferred user experience.

Use Cases for Magnum's "container" Resource

We are seeking production use cases for the /container resource offered in the Magnum API. If you have one, please identify it here:

• [use case here]