TABLE OF CONTENTS
...
MobiledgeX: Open Platform deployed for application Orchestration and operations:
MobiledgeX Controller today is aligned with the above strategy helps with backend application deployment and plans to build out a policy control place to specify the application needs to RIC on south bound side. Controller specifies policies at the granularity of minutes to hours (when it onboard/offboards an application backend) and the xapp does the more real time adjustments of the policy.
Markets use cases:
Edge with Mobility: Telco Edge
...
Please visit for more information:
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
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.
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
For more information on Infrastructure you can refer the following links
›https://www.terraform.io/docs/providers/packet/index.html
›https://support.packet.com/kb/articles/terraform
›https://www.packet.com/developers/guides/mesos-dcos-with-terraform/
›https://docs.ansible.com/ansible/latest/scenario_guides/guide_packet.html
›https://support.packet.com/kb/articles/ansible