openstack/magnum
Code Issues Proposed changes

Add use case: Permit use of native ReST APIs

Browse Source 
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
This commit is contained in:
Steven Dake 2015-01-07 09:15:23 -07:00
parent 19cd902e06
commit f4968bb277
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
specs/containers-service.rst
View File

@ -83,6 +83,12 @@ Use cases
multiple hosting environments). End-users want a single service that could multiple hosting environments). End-users want a single service that could
help them build the container network, and dynamically modify the network help them build the container network, and dynamically modify the network
topology by adding or removing containers to or from 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 Long Term Use Cases
------------------- -------------------