Deploying Cloudlets

To create and deploy cloudlets using Direct access

Step 1: From the Edge-Cloud Console, navigate to the Cloudlets submenu.

Step 2: Click the + sign on the upper top right-hand corner to open the Create Cloudlet page.

Create Cloud screen

Step 3: For Region, select a region from the drop-down list to deploy the cloudlet.

Step 4: Type in a name for your cloudlet under Cloudlet Name.

Step 5: The Operator field is required should contain the name of the organization you created.

Step 6: For Cloudlet Location, enter the cloudlet’s coordinates.

Step 7: For IP supportDynamic is currently only supported. Dynamic indicates that the cloudlet will use a DHCP server to provide the public IP addresses.

Step 8: In the Number of Dynamic IPs field, type in the number of Dynamic IP addresses that are desired.

Step 9: For Physical Name, type in the physical name of the cloudlet. The cloudlet name is an identifier used for the OpenRC credentials.

  • If MobiledgeX added the OpenRC detail on behalf of the Operator, the OpenRC field should be populated with the details provided by MobiledgeX.

  • If a new OpenRC file is required to be uploaded, you must provide the Physical Name, which will be supplied to the Operator by MobiledgeX.

Step 10: In the Platform Type field, select one of the supported platform types—OpenStack or vSphere. If you select OpenStack, additional fields associated with that platform selection appears. Refer to Step 9 and 11 to understand the conditions to either leave those fields blank or populate them.

Step 11: For OpenRC Data, leave this field blank if MobiledgeX uploaded this file on your behalf. If you need to upload a new one, here is an example of an OpenRC file.

OS_AUTH_URL=https://openstack.api.enpoint.url/v3
OS_PROJECT_ID=b6565354422a454c965078640ad4398e
OS_PROJECT_NAME=project_name
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_DOMAIN_ID=default
OS_USERNAME=osuser
OS_PASSWORD=ospassword
OS_REGION_NAME=RegionOne
OS_INTERFACE=public
OS_IDENTITY_API_VERSION=3

Step 12: For CACert Data, you must upload the CACert Data file if the OSAUTHURL is https-based. Otherwise, if you’re using http, this field is not required.


----BEGIN CERTIFICATE-----
LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0
BAYTAkRFMSswKQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBH
bWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxU
LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0
MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0
SW50ZXJuYXRpb25hbCBHbWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2Vu
dGVyMRwwGgYDVQQIDBNOb3JkcmhlaW4gV2VzdGZhbGVuMQ4wDAYDVQQRDAU1NzI1
MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0
ci4gMjAxJjAkBgNVBAMMHVRlbGVTZWMgU2VydmVyUGFzcyBDbGFzcyAyIENBMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3oxwJVY3bSb6ejJ42f9VEt1N
vW2swwllcs5ifPsHAulpSoFc2Y9gMOKQqkuyjN1foCegDDeEr6FBLD5YuROldcX8
2aDNBKDh9GpSJYZMLrYwlfR4EJUGwLidHDn93H95j1M67sNlCyCfcbso0zFBQzXK
KO06sbC1QH9M1Xdrltz8bQS+LbGRTM5JcPYhhxXcnsFstQVaGmfqFQitPXhT3g9+
AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd
Ghvzd09jjMT6f8Q8pAlyGFTGuxsEjeU/rrS/yKU8bFEEvuR5WT/I4Kme+8OlzQID
AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd
IAAwMDAuBggrBgEFBQcCARYiaHR0cDovL3BraS50ZWxlc2VjLmRlL2Nwcy9jcHMu
aHRtbDAOBgNVHQ8BAf8EBAMCAQYwge8GA1UdHwSB5zCB5DA1oDOgMYYvaHR0cDov
L3BraS50ZWxlc2VjLmRlL3JsL0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgaqggaeg
gaSGgaFsZGFwOi8vcGtpLnRlbGVzZWMuZGUvQ049VC1UZWxlU2VjJTIwR2xvYmFs
Um9vdCUyMENsYXNzJTIwMixPVT1ULVN5c3RlbXMlMjBUcnVzdCUyMENlbnRlcixP
PVQtU3lzdGVtcyUyMEVudGVycHJpc2UlMjBTZXJ2aWNlcyUyMEdtYkgsQz1ERT9B
dXRob3JpdHlSZXZvY2F0aW9uTGlzdDA4BggrBgEFBQcBAQQsMCowKAYIKwYBBQUH
MAGGHGh0dHA6Ly9vY3NwLnRlbGVzZWMuZGUvb2NzcHIwHQYDVR0OBBYEFJTIdEb1
OrRGSCb4K8o0HlYmBBIAMB8GA1UdIwQYMBaAFL9ZIDYAeaCgImuM1fJh0rgsy4JK
MA0GCSqGSIb3DQEBCwUAA4IBAQB55S9CfCkclWVtUIxl2c4aM5wqlLZRZ7zVhynK
KOhWKyTw+D2BOjc+TXIPkgRMqF3Sn8ZD4UTOARboJxswYnLZDkvBuvTbYa+N52Jy
oBP2TXIpEWEyJl7Oq8NFbERwg4X6MabLgjGvJETicPpKGfAINKDwPScQCsWHiCaX
X50cZzmWw17S0rWECOvPEt/4tXJ4Me9aAxx6WRm708n/K8O4mB3AzvA/M7VUDaP9
8LtreoTnWInjyg/8+Ahtce3foMXiIP4+9IX7fbm6yqh4u33tqMESDcRP6eGdzq4D
qnHyIvj9XNpuGgMvDgq357kZQS9e5XVH5icSvW1kr2kX2f1t
-----END CERTIFICATE-----

Step 13: For Infra API Access, select Direct. This infers that the API endpoint is accessible from the public network.

Step 14: Once all the required fields are populated, click Create where a Progress bar appears and provides a live status of the cloudlet deployment process.

Progress bar

Step 15: Click the Progress indicator to view the updated state as the cloudlet is being deployed. Refreshing may to 15 minutes to complete.

Step 16: Once the cloudlet is available, the state will change to init. This change may take up to 5 minutes.

You’re done! The deployed cloudlet can now be viewed from the Cloudlets page.

Cloudlets screen

To create and deploy cloudlets using Restricted access

Step 1: From the Edge-Cloud Console, navigate to the Cloudlets submenu.

Step 2: Click the + sign on the upper top right-hand corner to open the Create Cloudlet page.

Create Cloudlet-Restricted Access

Step 3: For Region, select a region from the drop-down list to deploy the cloudlet.

Step 4: Type in a name for your cloudlet under Cloudlet Name.

Step 5: The Operator field is required and should contain the name of the organization you created.

  • For Cloudlet Location, enter the cloudlet’s coordinates.

  • For IP supportDynamic is currently only supported. Dynamic indicates that the cloudlet will use a DHCP server to provide the public IP addresses.

  • In the Number of Dynamic IPs field, type in the number of Dynamic IP addresses that are desired.

  • For Physical Name, type in the physical name of the cloudlet. The cloudlet name is an identifier used for the OpenRC credentials.

    • If MobiledgeX added the OpenRC detail on behalf of the Operator, the OpenRC field should be populated with the details provided by MobiledgeX.

    • If a new OpenRC file is required to be uploaded, you must provide the Physical Name, which will be supplied to the Operator by MobiledgeX.

Step 6: In the Platform Type field, select one of the supported platform types—OpenStack or vSphere. If you select OpenStack, additional fields associated with that platform selection appears. Refer to Step 9 and 11 to understand the conditions to either leave those fields blank or populate them.

Step 7: For OpenRC Data, leave this field blank if MobiledgeX uploaded this file on your behalf. If you need to upload a new one, here is an example of an OpenRC file.

OS_AUTH_URL=https://openstack.api.enpoint.url/v3
OS_PROJECT_ID=b6565354422a454c965078640ad4398e
OS_PROJECT_NAME=project_name
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_DOMAIN_ID=default
OS_USERNAME=osuser
OS_PASSWORD=ospassword
OS_REGION_NAME=RegionOne
OS_INTERFACE=public
OS_IDENTITY_API_VERSION=3

Step 8: For CACert Data, you must upload the CACert Data file if the OSAUTHURL is https-based. Otherwise, if you’re using http, this field is not required.


----BEGIN CERTIFICATE-----
LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0
BAYTAkRFMSswKQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBH
bWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxU
LVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAyMB4XDTE0MDIxMTE0MzkxMFoXDTI0
MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0
SW50ZXJuYXRpb25hbCBHbWJIMR8wHQYDVQQLDBZULVN5c3RlbXMgVHJ1c3QgQ2Vu
dGVyMRwwGgYDVQQIDBNOb3JkcmhlaW4gV2VzdGZhbGVuMQ4wDAYDVQQRDAU1NzI1
MDEQMA4GA1UEBwwHTmV0cGhlcdefMB4GA1UECQwXVW50ZXJlIEluZHVzdHJpZXN0
ci4gMjAxJjAkBgNVBAMMHVRlbGVTZWMgU2VydmVyUGFzcyBDbGFzcyAyIENBMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3oxwJVY3bSb6ejJ42f9VEt1N
vW2swwllcs5ifPsHAulpSoFc2Y9gMOKQqkuyjN1foCegDDeEr6FBLD5YuROldcX8
2aDNBKDh9GpSJYZMLrYwlfR4EJUGwLidHDn93H95j1M67sNlCyCfcbso0zFBQzXK
KO06sbC1QH9M1Xdrltz8bQS+LbGRTM5JcPYhhxXcnsFstQVaGmfqFQitPXhT3g9+
AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd
Ghvzd09jjMT6f8Q8pAlyGFTGuxsEjeU/rrS/yKU8bFEEvuR5WT/I4Kme+8OlzQID
AQABo4IB2TCCAdUwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHSAEPDA6MDgGBFUd
IAAwMDAuBggrBgEFBQcCARYiaHR0cDovL3BraS50ZWxlc2VjLmRlL2Nwcy9jcHMu
aHRtbDAOBgNVHQ8BAf8EBAMCAQYwge8GA1UdHwSB5zCB5DA1oDOgMYYvaHR0cDov
L3BraS50ZWxlc2VjLmRlL3JsL0dsb2JhbFJvb3RfQ2xhc3NfMi5jcmwwgaqggaeg
gaSGgaFsZGFwOi8vcGtpLnRlbGVzZWMuZGUvQ049VC1UZWxlU2VjJTIwR2xvYmFs
Um9vdCUyMENsYXNzJTIwMixPVT1ULVN5c3RlbXMlMjBUcnVzdCUyMENlbnRlcixP
PVQtU3lzdGVtcyUyMEVudGVycHJpc2UlMjBTZXJ2aWNlcyUyMEdtYkgsQz1ERT9B
dXRob3JpdHlSZXZvY2F0aW9uTGlzdDA4BggrBgEFBQcBAQQsMCowKAYIKwYBBQUH
MAGGHGh0dHA6Ly9vY3NwLnRlbGVzZWMuZGUvb2NzcHIwHQYDVR0OBBYEFJTIdEb1
OrRGSCb4K8o0HlYmBBIAMB8GA1UdIwQYMBaAFL9ZIDYAeaCgImuM1fJh0rgsy4JK
MA0GCSqGSIb3DQEBCwUAA4IBAQB55S9CfCkclWVtUIxl2c4aM5wqlLZRZ7zVhynK
KOhWKyTw+D2BOjc+TXIPkgRMqF3Sn8ZD4UTOARboJxswYnLZDkvBuvTbYa+N52Jy
oBP2TXIpEWEyJl7Oq8NFbERwg4X6MabLgjGvJETicPpKGfAINKDwPScQCsWHiCaX
X50cZzmWw17S0rWECOvPEt/4tXJ4Me9aAxx6WRm708n/K8O4mB3AzvA/M7VUDaP9
8LtreoTnWInjyg/8+Ahtce3foMXiIP4+9IX7fbm6yqh4u33tqMESDcRP6eGdzq4D
qnHyIvj9XNpuGgMvDgq357kZQS9e5XVH5icSvW1kr2kX2f1t
-----END CERTIFICATE-----

Step 9: For Infra API Access, select Restricted. This infers that the API endpoint is not accessible from the public network and additional fields will appear, and require input.

Step 10: For the Infra Flavor Name, provide the name of the flavor specific to the Infra to deploy the PlatformVM. The recommended minimum hardware configuration includes: 2 vCPU, 4GB RAM, and 40G disk space.

Step 11: For the Intra External Network Name, provide the name of the external network specific to the Infra.

Step 12: Once all the required fields are populated, click Create where a Progress bar appears and provides a live status of the cloudlet deployment process.

Progress bar

Step 13: Once the progress is complete, click Get Manifest from the Actions menu to bring up the Cloudlet Manifest file. Follow the steps within the file to download the base image and upload it to Glance.

Example: Cloudlet Manifest file

Step 14: Execute the HEAT stack template and wait for the Platform VM to appear. Once created, the Platform VM will create an external IP address.

Example: Heat Stack Template

Step 15: Click the Progress indicator to view the updated state as the cloudlet is being deployed. Refreshing may to 15 minutes to complete.

Step 16: Once the cloudlet is available, the state will change to init. This change may take up to 5 minutes.

You’re done! The deployed cloudlet can now be viewed from the Cloudlets page.

Cloudlets screen