Getting started with Maestro
Maestro is an end-to-end solution for building, deploying and managing containerized applications. We build your code into Docker images and/or fetch pre-built images from your repostitories. We also take care of deploying and managing your containers and infrastructure (servers, load balancers, etc).
What you’ll need
Before you start, please check you have the following:
- A Cloud 66 Account — If you don’t already have one, sign up for a Cloud 66 account. You’ll get free unlimited access to all products for 4 weeks.
- Application code and/or pre-built images — Application code should be hosted in a (secure) publicly accessible git repository and pre-built images should be hosted in image publicly accessible repositories.
- A Cloud account linked to Cloud 66 or your own servers set up — See below.
If you don't have images or code ready, you can use this simple visit counter application we've supplied on Github. (You can also use this project with our next tutorial on Clusters.)
An account with your cloud provider of choice. Cloud 66 supports AWS, Google Cloud, Microsoft Azure, DigitalOcean, Hetzner, Maxihost, OVH, Packet, Rackspace,
Vultr, and Cloud A.
Click on any of the links above for instructions on linking your cloud provider to your Cloud 66 account.
Registered servers are a great way for operations teams to manage and allocate physical server resources for consumption by dev teams. Registered servers are a pool of your own servers (on a private or public cloud) that can be used for any application and configuration. For more information on how to add your own registered servers, we recommend this tutorial.
Step 1: Choose a source
The first thing we need is access to your code, so that we can build and deploy it for you. The easiest option is to give us (read-only) access to a Github repo. To do this:
- Click Get Started
- On the next page click Link with Github
- We’ll send you to our app on Github (you’ll need to sign in)
- Once you’re signed in, click Configure & then select the account you wish to link to Cloud 66
- Install and authorize our Github app (you can restrict our access to specific repos if needed)
- You will be redirected back to your Cloud 66 dashboard and you can move on to Step 2.
Using a non-Github host
If you’d prefer to use another git host, or your own self-hosted repository:
- Click I’d rather enter a git repo URL.
- Copy the SSH key
- Open your repo and add the key to the settings (usually found under SSH or SSH keys)
- Come back to Cloud 66 and click the green Next… button
Using a prebuilt image
If you already have your code built into images and stored in a registry:
- Click I’m deploying Docker images
- If you’re using the Docker public image repo, enter the name of the Docker image (be sure to spell it correctly)
- If you’re using a private image repo, click the Add your credentials link, choose your provider and your credentials, then click Save and enter the full image name (including the repository) in the form.
- Move to Step 3 below
Step 2: Add repo details
Now that we have access to your code, we can set up your app’s container images. These contain all the code that makes your application work. To add:
- Choose the repo you want to deploy and set the branch
- Choose an environment for your application
- Give your application a name (this will be used to label your application throughout the Cloud 66 dashboard, and will not be visible to public users.)
- Click Analyze
Step 3: Add, validate and build images
You can now validate your code repo to ensure we can access it, and that it has a valid Docker file:
- Click the Validate repo access and Dockerfile link
- Check the details in the form and update if needed (you can also inspect and update the YAML that underlies your image definition by clicking the YAML tab).
- Click the Validate button
- We will now analyze the details and report any issues. Once you have successfully validated, click Save.
Note that you can skip this step, but we will still need to validate your repo before you can deploy.
If needed, you can also add additional Docker images to your application as needed:
- Click the + Add Image
- Name the service this image will support
- Supply the details of the image (see Using a pre-built image above if you need more help)
- Click Validate. We will check the image exists and is valid.
Once all your images (services) are added - click Next → at the bottom of the main panel.
Step 4: Configure services
Next we need to configure network access and (where needed) storage for each of your app’s services. You can also specify how many instances of each service you’d like to run and a variety of other custom settings.
A. Configure ports
To configure the internal and external ports for a service:
- Click the Configure Ports link in the Network column
- Set the Container Port, HTTP Port and HTTPS port
- You can also add traffic matching arguments if needed
- Click Save Service
If you’re using our sample application you should set the HTTP port to
80 and the Container port to
💡 This settings panel is used for both networking and storage options - so you can configure them simultaneously if you'd prefer.
B. Configure storage (optional)
To configure storage volumes for a service:
- Specify the path inside the container where the storage will be mounted
- Specify the path on the host server where the data will actually be stored
- You can use the Add Volume button to specify additional storage volumes
Once all your storage volumes are configured, click Save Service.
C. Set the desired number of instances (optional)
To add instances of a service:
- Click on the number in the Desired instances column
- Change the number in the Desired Count input box
- You can also add a start command to your service if required
- Click Save Service
Once all your services are configured, click the Next → button.
Step 5: Configure servers for deployment
A. Specify servers
Now that your application is configured, we can link your cloud provider and roll it out on your servers (if you need to use your own servers follow our guide to add them). To do this:
- Choose your provider from the list
- Choose a region
- We will suggest servers for your app you can customise them by clicking the ⚙️ Configure Server link at the top of its panel
- You can add additional servers by clicking the button
- You can add a data source to a newly created server using Configure Server (Note: doing so turns a server into a standalone database server)
You can also add a data source to your cluster server, but we do not recommend you do so in a production environment.
If you’re using our sample application you will need to set up a Redis instance at this point.
B. Add deployment target
We need access to your cloud account in order to provision and manage servers on your behalf. How you configure that access differs from provider to provider. Click the link to your provider below if you need help.
Amazon Web Services
- AWS Access key ID — You get this info from your AWS account Dashboard. (more help)
- AWS Secret Access Key — You get this info from your AWS account dashboard, when you create your AWS account. (more help)
- Give this cloud key a name — This is to give you the option of deploying to multiple AWS accounts. If you are deploying to a single account only, you can leave it as default.
- Give this cloud key a name — this is to give you the option of deploying to multiple accounts with the same cloud provider. If you only have 1 account you can leave it as default.
- Click Add Cloud — this will redirect you to the DigitalOcean dashboard. You'll need to login to DigitalOcean to finish adding the key.
Google Compute Engine
- GCE Client Email — You get this info from your GCE account Dashboard. Under Service Accounts → API's → Credentials (more help)
- GCE Project Id — You get this info from your GCE Dashboard. It's located at the top of the Overview page. (more help)
- GCE Key — This is a JSON file you need to upload, you get this from your GCE Dashboard.
- Hetzner API key — You can find this under Access → API tokens → Generate API Token (more help)
- Give this cloud key a name — this is to give you the option of deploying to multiple Linode different Linode accounts. If you only have one account you can leave it as default.
- Linode API Key — You get this information from your Linode Cloud Dashboard. my profile → API Keys tab.
- Maxihost API Key — You can find this under Settings & Billing → API Keys → Create API key (more help)
- Azure Subscription ID — You get this info from your Azure cloud Dashboard. (more help)
- Client ID — You get this info from your Azure Dashboard.
- Client Secret — You get this info from your Azure Dashboard.
- Tenant ID — You get this info from your Azure Dashboard.
- API region — You need to specify which API region your project uses
- OVH Project ID — You can find this on your OVH project dashboard (more help)
- Packet API Key — You get this info from your Packet Cloud Dashboard.
- Rackspace Username — You get this info from your Rackspace Cloud Dashboard.
- Rackspace API Key — You get this info from your Rackspace Cloud Dashboard. (more help)
- Rackspace user base — Select either UK or US.
Your Own Servers
- Registered Servers — First you need to Register your server as a deployment target with Cloud 66. Click on the Add Registered Servers link. You can also navigate to the Registered Servers page under Account Settings.
- Copy & run the command — Run the provided command in the terminal on your server. Once this has successfully completed you can then approve the server and it will become available as a Cloud 66 deployment target.
To add cloud credentials, ensure you have the right provider selected (at the top of the form) and then click Start Deployment. This will open a panel that will let you configure access to your provider.
Click Add Deployment Target once complete.
Step 6: Deploy your app
When you’re satisfied with your servers, click the Start Deployment button. During the build and deployment process you can view the log to see what’s happening behind the scenes.
The full build and deployment process may take 15 minutes or more because Maestro needs to provision the new servers from the ground up. You can close the window and Cloud 66 will send you an email when the deployment is complete.
Step 7: Test your app
Once deployment is complete, you can test your application by visiting your app’s detail page and clicking on the Visit Site link in the panel at the top of the Services tab.