Create and Manage Virtual Machines, Containers, and Workloads

Overview

You can use this document to learn how to:

• Create a virtual machine-based workload
• Create a container-based workload

At a high level: 

• A container packages application code, dependencies, and configurations into a single object that can be deployed in any environment.
• A virtual machine is a full software emulation of a physical computer that can perform all tasks similar to an operating system.  
• A workload consists of a container or virtual machine image that is deployed to one or many locations. 

For additional introductory information on Edge Computing components, see Learn about Edge Computing and Serverless Scripting.

Create a container-based workload 

1. In the StackPath Control Portal, in the left-side navigation menu, click Edge Compute. 
2. In the left-side navigation menu, click Workloads. 
3. Click Create Workload. 
4. In Name, enter a descriptive name for the workload. 
5. In Workload Type, select Container. 
6. In OS Image, enter the name of the container image to  deployed when the workload is created. The image will be pulled from Docker Hub. For example, if you enter nginx:latest, the latest Nginx image will be pulled. A URL to a container image hosted somewhere else can also be specified and the workload will pull it down. The URL should be in the same format that would work with docker pull i.e. URL/IMAGE:TAG
7. Click Continue to Settings. 
8. In Environment Variables, enter one or more key/value pairs to supply as environment variables. These variables will be available to instances within the same workload. 
   • To learn more, see Learn about Environment Variables.
9. (Optional) Mark Add Anycast IP Address if you want all instances to be assigned internal and external IP addresses to allow direct access to each instance individually.
10. In Public Ports, specify which ports to open via TCP or UDP to allow traffic. By default, all traffic to the workload is denied. 
11. In Commands, specify one or many commands that will execute when each instance starts. Arguments can be passed as if they were additional commands.
12. Click Continue to Spec. 
13. Under Spec, select the instance type to deploy to the workload. All instances will be the same type. very instance has a root SSD sized depending on the instance type selected. These disks are ephemeral and will be deleted when the instance is deleted (including if the instance dies unexpectedly). Available types and pricing are listed on the StackPath website.
14. (Optional) Under Persistent Storage, configure your storage needs.  
15. Under Deployment Target, under Name, enter a name to describe the location.   
16. Under PoPs, select a location to deploy the workload.
17. Under Instances Per PoP, enter the number of instances to deploy per PoP. 
    • For example, if you selected Dallas and London, and you enter 2, then a total of 4 instances will be deployed, 2 in Dallas and 2 in London. 
    • Failed instances will automatically restart to ensure this number is always maintained.
18. (Optional) If you want to enable autoscaling, mark Enable Auto Scaling, and then in the menu that appears, enter the minimum and maximum number of instances, based on the percentage set for CPU utilization.
    • Autoscaling is horizontal, not vertical. For example, the performance of a system will not increase from 4x8 to 12x64. 
    • The autoscaling feature will deploy another virtual machine, within the same PoP and OS template. Your apps will not be installed. As a result, you should still use auto-deploy tools, such as Puppet or Ansible, to make sure the new virtual machine is set up the same as the existing virtual machine. 
19. Review the pricing information, and then click Create Workload. 

Create a virtual machine-based workload 

1. In the StackPath Control Portal, in the left-side navigation menu, click Edge Compute. 
2. Click Create Workload. 
3. In Name, enter a descriptive name for the workload. 
4. In Workload Type, select VM.
5. In OS Image, select the OS image to deploy.
   • The image is pulled from a predefined list of options. For example, if you select CentOS 7, then the latest version of CentOS will be pulled.  
6. Click Continue to Settings. 
7. (Optional) If you want your virtual machines to be assigned internal and external IP addresses that allow direct access to each virtual machine, then mark Add Anycast IP Address.
   • In other words, this option allows multiple virtual machines to share the same IP address. The location of the user request will determine which virtual machine the user is routed to. 
8. In Public Ports, specify the ports to allow traffic through TCP or UDP. 
   • By default, all traffic to the workload is denied.
9. In First Boot SSH Key(s), enter a public SSH key.
   • Since password logins are disabled and not assigned, SSH will be your access point.
   • If you need to create an SSH key, see Generating an SSH key guide.
10. Click Continue to Spec. 
11. In Spec, select the virtual machine type to deploy to the workload. 
    • Every instance has a root SSD.
    • Available types and pricing are listed on the StackPath website.
12. (Optional) Under Persistent Storage, configure your storage needs.  
13. Under Deployment Target, under Name, enter a name to describe the location.   
14. Under PoPs, select a location to deploy the workload.
15. Under Instances Per PoP, enter the number of instances to deploy per PoP. 
    • For example, if you selected Dallas and London, and you enter 2, then a total of 4 instances will be deployed, 2 in Dallas and 2 in London. 
    • Failed instances will automatically restart to ensure this number is always maintained.
16. (Optional) If you want to enable autoscaling, mark Enable Auto Scaling, and then in the menu that appears, enter the minimum and maximum number of instances, based on the percentage set for CPU utilization.
    • Autoscaling is horizontal, not vertical. For example, the performance of a system will not increase from 4x8 to 12x64. 
    • The autoscaling feature will deploy another virtual machine, within the same PoP and OS template. Your apps will not be installed. As a result, you should still use auto-deploy tools, such as Puppet or Ansible, to make sure the new virtual machine is set up the same as the existing virtual machine. 
17. Review the pricing information, and then click Create Workload. 

View an existing workload

1. In the StackPath Control Portal, in the left-side navigation menu, click Edge Compute. 
2. In the left-side navigation menu, click Workloads  
3. Click a specific workload to view additional details.
   • Monitoring of basic metrics (CPU and memory) is included for no additional cost for every workload. These metrics are collected for each instance from outside the instance itself. No monitoring processes run inside instances themselves, which are entirely under your control through the image provided. Monitoring data is kept for 24 hours. More advanced monitoring will be available in the future.
   • For a newly created workload, under Instances, the workload will contain a Starting status. After a few seconds, the workload will be fully deployed and the full instance list will be shown as Running.