In order to create clusters of instances running CoreOS and with docker capabilities, you will need to start with a capable CLI instance. Once your CLI is setup to communicate with your Auro project, feel free to follow along to enable the creation of CoreOS clusters.
Auro has a Beta CoreOS image available, however, you can easily upload your own CoreOS image by downloading the CoreOS image here: (http://stable.release.core-os.net/amd64-usr/current/coreos_production_openstack_image.img.bz2) and uploading this via the Auro control panel or using glance. You can choose which channel of CoreOS by changing the "stable" in the URL above to either 'alpha' or 'beta'
Once complete, you simply need to setup a cloud-config file in your CLI instance, which will push CoreOS configurations to your created clusters. A basic configuration for Openstack is as follows:
# generate a new token for each unique cluster from https://discovery.etcd.$
# multi-region and multi-cloud deployments need to use $public_ipv4
- name: etcd.service
- name: fleet.service
# include one or more SSH public keys
- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0g+ZTxC7weoIJLUafOgrm+h...
The $private_ipv4 and $public_ipv4 substitution variables are fully supported in cloud-config on most OpenStack deployments.
This config can be referenced when creating the cluster using the nova command on your CLI instance.
You can now spool up a cluster using the nova boot command, the following is an example:
nova boot \
--user-data ./cloud-config.yaml \
--image 0c98d731-cb91-4bda-b489-b8b676dd9ac2 \
--key-name coreos \
--flavor standard-1 \
--num-instances 3 \
With this you reference the cloud config file, the CoreOS image you uploaded via glance, your ssh key name, instance flavor, number of instances int he cluster, and any security groups you would like these added to.
Congratulations! You have created a cluster of Core OS instances!