Guides - Deploying Mist.io through the Linode Marketplace
Quickly deploy a Compute Instance with many various software applications pre-installed and ready to use.
Mist.io is an open source, multi-cloud management platform. Mist supports all popular infrastructure technologies including public clouds, private clouds, hypervisors, containers, and bare metal servers. It provides a unified interface for performing common management tasks like provisioning, orchestration, monitoring, automation, and cost analysis. It also comes with a RESTful API so you can easily integrate it in your existing workflows.
Deploying a Marketplace App
The Linode Marketplace allows you to easily deploy software on a Compute Instance using the Cloud Manager. See Get Started with Marketplace Apps for complete steps.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Complete the form by following the steps and advice within the Creating a Compute Instance guide. Depending on the Marketplace App you selected, there may be additional configuration options available. See the Configuration Options section below for compatible distributions, recommended plans, and any additional configuration options available for this Marketplace App.
Click the Create Linode button. Once the Compute Instance has been provisioned and has fully powered on, wait for the software installation to complete. If the instance is powered off or restarted before this time, the software installation will likely fail.
To verify that the app has been fully installed, see Get Started with Marketplace Apps > Verify Installation. Once installed, follow the instructions within the Getting Started After Deployment section to access the application and start using it.
NoteEstimated deployment time: Mist.io should be fully installed within 5-15 minutes after the Compute Instance has finished provisioning.
Configuration Options
- Supported distributions: Debian 10
- Recommended plan: 8GB Compute Instance
Mist.io Options
- Mist admin user’s email (required): The e-mail address of the administrator. Used as a log-in credential similar to a username.
- Mist admin user’s password (required): The password of the Mist.io administrator account.
Getting Started After Deployment
Once the Mist.io server is successfully created, a few additional steps must be completed to be able to begin using the application.
Log In to Mist.io
In a web browser, enter your Linode’s IP address or the Domain associated with it to access your Mist.io App’s login screen.
Click on the Sign in button at the top right of the page.
Enter your Mist admin
Email Address
andPassword
in their respective fields to complete the log-in process.
Next Steps
After creating your account, create a name for your organization, Add Clouds to manage, as well as any separate virtual machines, containers, and more.
For more information and guidance for getting the most out of your Mist.io App, check out the following:
- Mist User Documentation for quick start and other informative articles.
- Mist API Documentation for integration with your existing workflows.
- Mist Community Edition Github Repo for additional configuration and maintenance instructions.
Software Included
The Mist.io Marketplace App installs the following software on your Linode:
Software | Description |
---|---|
Docker Compose | Tool for defining and running multi-container Docker applications. |
Mist Community Edition (installs the latest version) | An open source Mult-Cloud Management Platform. |
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on