...
Design
API changes
Following API shall be introduced with application cluster:
- createApplicationCluster
- name: name of the application cluster
- description: description of application cluster
- type: service type - Kubernetes, CloudFoundry, Mesos etc
- zoneid: uuid of the zone in which application cluster will be provisioned
- a list of
- role: the name for this type of VM
- serviceofferingid: service offering with which cluster VMs of this role shall be provisioned
- template: the template to use for VMs of this role
- countcluster: size of the cluster or number of VMs of this role to be provisioned
- accountname: account for which application cluster shall be created
- domainid: domain of the account for which application cluster shall be created
- networkid: uuid of the network in to which application cluster VM's will be provisioned. If not specified cluster service shall provision a new isolated network with default isolated network offering with source nat service.
- deleteApplicationCluster
- id: uuid of application cluster
- startApplicationCluster
- id: uuid of application cluster
- stopApplicationCluster
- id: uuid of application cluster
- addNodeToCluster (Not planned yet)
- id: uuid of application cluster
- role: the name for the type of node to be added
- removeNodeFromCluster (not planned yet)
- id: uuid of the node
- clusterid: uuid of application cluster
- listApplicationClusters
- id: uuid of application cluster
- listClusterNodes
- id: uuid of application cluster
New reponse 'applicationclusterreponse' shall be added with below details:
- name
- description
- zoneid
- list of
- role
- serviceofferingid
- templateid
- size
- networkid
- endpoint: URL of the application cluster manger API server endpoint
...