http://swagger.mobiledgex.net/client/

Conclusion: How do we use the above API set ?

you can refer to JSON and yaml files in case you wish to integrate in your edge stack.

DeveloperAPIDocument

Incase you are using a cloud provider and would like to spin application using our code you can use the following call flow to see how this works

Image Added

We have automated the bare metal and virtualization layer open stack and kubernetes cluster with terraform script and edge stack looks as below. As you can see we have open sourced the basic CRM API set for bringing application over the above stack in 4 simple control commands.

Image Added

Example commands set:

edgectl --addr mexdemo.ctrl.mobiledgex.net:55001 --tls $TLS/mex-client.crt controller CreateApp --imagepath docker.mobiledgex.net/mobiledgex/images/mobiledgexsdkdemo --imagetype ImageTypeDocker --deployment kubernetes --key-developerkey-name MobiledgeX --key-name "Example App" --key-version 1.0 --defaultflavor-name m1.medium --accessports tcp:7777

edgectl --addr mexdemo.ctrl.mobiledgex.net:55001 --tls $TLS/mex-client.crt controller CreateClusterInst --key-cloudletkey-operatorkey-name packet --key-cloudletkey-name packet-sjc1 --key-clusterkey-name mexdemo-cluster --key-developer MobiledgeX --flavor-name m1.medium --nummasters 1 --numnodes 3

edgectl --addr mexdemo.ctrl.mobiledgex.net:55001 --tls $TLS/mex-client.crt controller CreateAppInst --key-clusterinstkey-cloudletkey-name packet-sjc1 --key-clusterinstkey-cloudletkey-operatorkey-name packet --key-clusterinstkey-clusterkey-name mexdemo-cluster --key-clusterinstkey-developer MobiledgeX --key-appkey-developerkey-name MobiledgeX --flavor-name x1.medium --key-appkey-name "Example App" --key-appkey-version 1.0