Comment 6 for bug 1390246

I was able to spin up a coreos cluster consisting of two nodes on a Vagrant VM with 6GB memory. Here are the commands that I used.

These steps assume that you have a coreos image registered in glance, you have created cloud-config.yaml, and you have generated ssh keypair.

For steps 1 and 2 below, you will need admin privileges.
On devstack you can gain those by doing 'source devstack/openrc admin'.

1) Create nova key-pair
nova keypair-add --pub-key ./ssh/id_rsa.pub devstack-keypair

2) Create nova network
nova network-create --fixed-range-v4 172.16.0.0/24 coreos-network

3) Boot coreos cluster
nova boot --user-data ./cloud-config.yaml --image 279bb4b9-3c77-40f9-9a92-a083be466363 --flavor m1.small --num-instances 2 --config-drive=true --security-groups default --nic net-id=25dc2d10-d1e4-4dff-9cf7-f1e8b31ba9de --key-name devstack-keypair coreos-vms-2

(Find the ids using following commands:
glance image-list
nova network-list
nova keypair-list)

4) Find out IP addresses of the spun up coreos machines
nova list

5) SSH into a machine (the default pre-configured username is 'core')
ssh -i id_rsa core@172.16.0.2

Once logged into the machine, I am seeing "Failed Units: 2" message on the console. The trace of the login session is below:

vagrant@devstack:~/.ssh$ ssh -i id_rsa core@172.16.0.2
The authenticity of host '172.16.0.2 (172.16.0.2)' can't be established.
ED25519 key fingerprint is 2f:57:8c:16:59:5d:41:14:c9:f4:81:ad:c6:2c:fe:02.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.16.0.2' (ED25519) to the list of known hosts.
CoreOS (alpha)
Failed Units: 2
  user-configdrive.path
  oem-cloudinit.service
core@coreos-vms-2-2095cfd8-8cdf-4a8b-9c8b-73dd2de91d13 ~ $

---

Note that in above steps I am not using Solum's CoreOS patch yet. I am just doing nova-boot. But now that I know that CoreOS can be spun up on devstack, I will be going back to Solum's CoreOS patch.

---