Openstack Tenant Deployment

OpenStack Tenant Deployment Where Operator Provides a Tenant on Their Existing OpenStack to EdgeXR

In this model, the operator supplies an OpenStack Tenant account within their existing OpenStack Infrastructure (for eg: VMware VIO, Redhat RHOSP or Cisco VIM) to EdgeXR with configured UE Wireless and External Internet Provider networks. With this model, the operator manages the OpenStack IaaS stack, flavors, and its associated external networking. EdgeXR is provided access to the OpenStack endpoint, with granted permissions to create the VMs and networks in the assigned OpenStack tenant. Once the OpenStack tenant Networking design is finalized, either EdgeXR or operator itself via EdgeXR console onboards the cloudlets. EdgeXR will maintain the cloudlets and support the rest of the Edge operations.

Scope and Constraints

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

Operator Workflow

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 EdgeXR 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.

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 (EdgeXR responsibility)

The EdgeXR DevOps 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, EdgeXR requests that the operator has a defined contact point in the event there are any issues with the deployed VMs, network, firewall, or any other issues.

Step 5: Handover testing

Following the completion of the cloudlet deployment, the EdgeXR DevOps 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 EdgeXR support team monitors the deployment and management until both EdgeXR and the operator agree that the cloudlet is working properly.