This repository contains setup examples of openstf/stf on various hosts using Vagrant with VirtualBox provider.
- VirtualBox >= 5.0.0
- Vagrant >= 1.7.3
git clone https://github.com/openstf/setup-examples.git stf-setup-examples
cd stf-setup-examples
cd ./db
vagrant up
Above command will do
- Download ubuntu/trusty64 image if image is not present (this may take time depending on internet speed)
- Launch Ubuntu VM and set its IP to
$rethinkdb_host_ip
configured in Configuration File (Default: 198.162.50.11) - Install and run rethinkdb server
You can confirm if rethinkdb is up by visiting rethinkdb admin console (http://198.162.50.11:8080 or http://RETHINKDB_HOST_IP:8080)
- Install fleetctl client
- On OS X, you can install it using
brew install fleetctl
.
- On OS X, you can install it using
- Make sure that rethinkdb is running by following these instructions
You can configure global variable present in CoreOS Configuration File according to your Requirements.
cd coreos
vagrant up
Above command will do
- Download CoreOS image if image is not present (this may take time depending on internet speed)
- Launch
$num_instances
configured in CoreOS Configuration File instances of CoreOS VM - You can check if all the instances are running using
vagrant global-status
command
Next, we will be launching services inside CoreOS cluster using fleetctl. First we need to export a global variable FLEETCTL_ENDPOINT. This endpoint will tell fleetctl running on host os (OS X in my case) to talk with fleet daemon running inside one of the guest OS.
export FLEETCTL_ENDPOINT=http://172.17.8.101:2379
Using core-01 guest OS.
Now, run fleetctl list-machines
command, You will see something like below
MACHINE IP METADATA
6e3e7dc2... 172.17.8.101 -
9821f508... 172.17.8.102 -
ab5747a8... 172.17.8.103 -
Now, your CoreOS cluster is ready to deploy STF Components.
You need to have a single adbd.service
unit running on each host where devices are connected.Global=true
X-Fleet parameter in adbd.service will make it run on each cluster host.
Deploy using below command
fleetctl submit ./unit_files/adbd.service
fleetctl start adbd
It will take adbd.service
some time to start on each host. Once it is done, you can check by running fleetctl list-units
command. You will see
UNIT MACHINE ACTIVE SUB
adbd.service 6e3e7dc2.../172.17.8.101 active running
adbd.service 9821f508.../172.17.8.102 active running
adbd.service ab5747a8.../172.17.8.103 active running