OpenStack Tenant Deployment

Scope and Constraints

MobiledgeX only controls resource management within the scope of the MobiledgeX platform; VIM Operators have control over resource management beyond the platform. However, all changes must be done in coordination with MobiledgeX.

Operator Workflow

Step 1: Validate OpenStack Deployment

Step 2: Validate Network Configuration

Step 3: Provide Deployment Information to MobiledgeX

Step 4: Cloudlet Deployment (MobiledgeX Responsibility)

Step 5: Handover Testing

Operator Workflow Details

Step 1: Validate Openstack Deployment

The OpenStack environment and permissions need to be configured to meet or exceed the minimum requirements provided below.

OpenStack Version

  • Queens or Higher

OpenStack Services

  • Glance

  • Glance Image Cache (if supported)

  • Nova

  • Heat

  • Keystone

  • Neutron

  • Cinder

  • Ceilometer

OpenStack Required APIs

  • create stack (heat)

  • server list, create, delete, set properties

  • image list, save, create, delete

  • network list, create, delete

  • subnet list, create, delete

  • router create, delete, add and delete ports

  • flavor list, show, create

  • security group rule list and create

  • show limits

OpenStack Endpoint

Available to MobiledgeX Controller VM

Step 2: Validate Network Configuration

All virtual machines created as part of this deployment will require full access to the full complement of deployed virtual machines.

Additionally, the network, firewall, and security groups need to be configured to provide the detailed ingress and egress access noted in the following tables:

Egress Requirements

Service

Host/IP

Port

NTP

Any destination

UDP: 123

STUN

stun.mobiledgex.net

UDP: 19302

HTTPS Egress

0.0.0.0/0

TCP:443

EU controller

mexdemo-eu.ctrl.mobiledgex.net

TCP:37001,41001

JP controller

mexdemo-jp.ctrl.mobiledgex.net

TCP:37001,41001

US controller

mexdemo-us.ctrl.mobiledgex.net

TCP:37001,41001

Public DNS

1.1.1.1

UDP: 53

Public DNS

1.0.0.1

UDP: 53

Edge Cloud Docker Registry

registry.mobiledgex.net

TCP:5000

EdgeTurn

EU: edgeturn-eu.mobiledgex.net

JP: edgeturn-jp.mobiledgex.net

US: edgeturn-us.mobiledgex.net

TCP:6080

Log Management (Jaeger)

jaeger.mobiledgex.net

TCP:14268

Ingress Requirements

Service

Host/IP

Port

EU controller

mexdemo-eu.ctrl.mobiledgex.net

TCP:22

JP controller

mexdemo-jp.ctrl.mobiledgex.net

TCP:22

US controller

mexdemo-us.ctrl.mobiledgex.net

TCP:22

Assumptions

  • An assumption is made that both mobile and internet access are external networks, and devices have ingress access into the workloads orchestrated on the deployment.

  • By default, all ports should be opened on the mobile network side for ingress to the deployment.

  • The MobiledgeX front end load balancers will not be included in any security groups that would prevent the opening of any application-specific ports.

Step 3: Provide Deployment Information

The following should be provided for each VM that has been deployed.

  • Datacenter

  • VM Name

  • External IP

  • Internal IP

Step 4: Cloudlet Deployment (MobiledgeX Responsibility)

The MobiledgeX Dev-ops team will use the information above to deploy the cloudlet and confirm that it is communicating with all necessary services and working properly. During this process, MobiledgeX requests that the operator has a defined contact point in the event there are any issues with the deployed vm's, network, firewall, or any other issues.

Step 5: Handover Testing

Following the completion of the cloudlet deployment, the MobiledgeX Dev-ops team will run through the deployment test process to validate the configuration. Once this is complete, the customer will be able to deploy workloads to the cloudlet while the MobiledgeX support team monitors the deployment and management until both MobiledgeX and the Operator agree that the cloudlet is working properly.