From f4968bb27750ac607d4093d29a79d947951e1dd4 Mon Sep 17 00:00:00 2001 From: Steven Dake Date: Wed, 7 Jan 2015 09:15:23 -0700 Subject: [PATCH] Add use case: Permit use of native ReST APIs The ability to use native ReST APIs may be important for some users of Magnum who only want to take advantage of the bay management features. Change-Id: I33ec50418b7ebd25786a51edff912e58d6731044 --- specs/containers-service.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/specs/containers-service.rst b/specs/containers-service.rst index 8d88c90e71..34716c16a0 100644 --- a/specs/containers-service.rst +++ b/specs/containers-service.rst @@ -83,6 +83,12 @@ Use cases multiple hosting environments). End-users want a single service that could help them build the container network, and dynamically modify the network topology by adding or removing containers to or from the network. +9. Permit secure use of native ReST APIs. Provide two models of operation with + Magnum. The first model allows Magnum to manage the lifecycle of Pods, + ReplicationControllers, and Services. The second model allows end-users to + manage the lifecycle of Pods, ReplicationControllers, and Services by + providing direct secure access to the native ReST APIs in Kubernetes and + possibly Docker. Long Term Use Cases -------------------