A sample VM image in QCOW2 format. Instructions to download a sample image are provided below.
Step 1: Download a sample VM image file
Create a temporary folder on your local system.
Download this image from Centos : https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2
As an alternative, you can use wget or cURL to download the image: curl -O https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2.
Step 2: Modify VM SSH Port (optional)
If you are interested in being able to SSH into your virtual machine, you will need to modify the sshd_config port for your CentOS image.
Open the VM in a Virtual Machine emulator like Virtual Box or qemu-system-x86_64
Once that image is running, open the file /etc/ssh/sshd_config
Check if a port has been specified. If so, change the port to 2222. If not, add Port 2222 to this file.
Shut down the image in order to save the changes.
Note: The default port for ssh is 22; however, port 22 is a reserved port on MobiledgeX. As a result, you need to specify an alternative port to use such as 2222.
Step 3: Upload the VM image file to the MobiledgeX Artifactory
On the command line, type ls CentOS-7-x86_64-GenericCloud.qcow2 to verify that your image is in your working directory.
Upload the image to Artifactory by typing in curl -u <username> -T ./CentOS-7-x86_64-GenericCloud.qcow2 "https://artifactory.mobiledgex.net/artifactory/repo-<orgname>/CentOS-7-x86_64-GenericCloud.qcow2".
Once prompted, type in your user password to proceed.
To observe the upload process of your file, type --progress-bar -o upload.txt.
Curl will upload the image to Artifactory. If the upload was successful, you will receive an output similar to the example below. If it was unsuccessful, you will receive an error message. For example, if you received the error "Bad Credentials", it may be that your username, password, or organization was invalid, in which case, you will need to go back and re-type them in correctly.
The proceeding steps require you to have an md5 sum. Note that the md5 is returned as shown in the example above.
Step 4: Create an application definition
You are now ready to create an application. The Apps page lets you define your backend application deploying to our registry. Performing this steps creates an 'inventory' of your applications that are part of the registry and prepares it for deployment.
From the left navigation, click Apps.
Click the + sign to add a new Application definition. The Create Apps page opens.
Select EU for Region.
For App Name, type in a name, such as vmtest.
Enter 1.0 for App Version.
For Deployment Type, select VM.
For Access Type, select Direct.
Select Qcow for Image Type.
For Image Path, enter https://artifactory.mobiledgex.net/artifactory/repo-demoorg/CentOS-7-x86_64-GenericCloud.qcow2#md5:ec8c38b1656ded3e03a6dc0938e201f1, where md5sum is in the format of $md5:sum.
Note: While optional, if you wish to ssh into your VM, make sure to add your ssh public key to the Auth Key section under Advanced Settings.
13. All other fields, leave blank.
The console will process your request and return you to the Apps screen where you should see your application.
Step 5: Create an application instance
You are ready to deploy your application. The App Instances page is where you provision your application and deploy it to a cloudlet. This step is called application provisioning. This page displays information such as the current applications running on the platform and their location.
On the left navigation, click App Instances.
For Region, select EU.
For Organization Name, type in a name, such as demoorg.
Type vmtest for App Name.
For App Version, enter 1.0.
For Operator, select TDG.
For Cloudlet, select munich-main.
Click Create. The console will process your request and bring up a progress window. Once you close out of the progress window, you will be returned to the main App Instance page where you should see your new VM Instance.
Step 6: Test your VM
You will need the following:
Information pulled from the details page for the App Instance, which can be accessed by clicking on the App Instance row on the App Instance page.
FQDN and the Port.
SSH into the system with the username and password you set in the cloud init file (manifest). You can also bring up a terminal.
To test that your VM was deployed correctly, navigate to the App Instance page and under the quick access menu, select terminal. You can see your VM running. If the VM is GUI based, such as Windows-based, you can interact with the Windows desktop.