Provisioning VMs and containers
Mist.io can simplify and decrease the time it takes to deploy and configure a new server significantly. Whether you need a new Virtual Machine, a cloud server or a new Docker container, launching it and setting it up is a matter of a few clicks.
On the Machines section, click on the + button at the bottom right to launch the machine creation wizard:
Let's go over the wizard's fields and check out our options:
Name: This is how your server will be called. You can put anything you like here, although some providers don't allow spaces or special characters. In such a case, Mist.io will let you know.
Provider: You can choose to launch your new server on any public or private cloud, KVM hypervisor or Docker engine you have already added to Mist.io.
Image: Each provider offers its' own set of images to base your new VM upon. In this example, your new VM will be launched with Ubuntu Server 14.04.2 as its' OS
Size: The size of the VM. You can choose among various options offered by your selected provider. In this example, the server will launch with 2 CPU cores and 3584MB of RAM.
Location: Some providers offer multiple locations in which you can launch your server.
Key: If you have SSH keypairs associated with Mist.io, you can choose to automatically deploy the public key once the server is launched. Highly recommended as you will be able to access your machine through the web console, enable monitoring on creation and set up automation with just a few clicks.
Script: You can choose to run a script to configure once the server once it has been created. You can write a command in the textbox (e.g. apt-get update && apt-get upgrade to update your server) or flip the switch to advanced and choose on of your scripts you have stored to Mist.io.
Enable monitoring: If you have chosen to deploy an SSH key with your new machine, you can also choose to enable monitoring once the machine has been launched.
Depending on your provider, once you press launch, it can take from a few second to several minutes for your machine to be ready (in some providers the machine appears as stopped initially while it is being deployed). In case something went wrong, Mist.io will show you an error message. For a more detailed view of the error messages, you can access them in the logs section of your home screen.
If you're launching and destroying new machines very often, you can also check the Mist.io API, CLI or Ansible modules on how to integrate Mist.io to your workflow.