You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 8, 2022. It is now read-only.
Copy file name to clipboardexpand all lines: vagrant/README.md
+9-12
Original file line number
Diff line number
Diff line change
@@ -44,16 +44,7 @@ You will need to build [mutilate](https://github.com/leverich/mutilate) by hand
44
44
sudo ln -svf /opt/swan/bin/* /usr/bin/
45
45
```
46
46
47
-
Now you should be able to run an experiment on the Kubernetes cluster that was automatically provisioned. If you want to be able to run without Kuberenetes, then you will need to take a few more steps.
48
-
49
-
Some of the project dependencies are distributed as [Docker image](https://hub.docker.com/r/intelsdi/swan/). They need to be extracted from the container in order to be used for non-Kubernetes experiments. To do this you need to execute the following commands:
50
-
51
-
```sh
52
-
make extract_binaries
53
-
sudo chown -R $USER:$USER opt
54
-
sudo cp -fa opt/swan /opt
55
-
sudo ln -svf /opt/swan/bin/* /usr/bin/
56
-
```
47
+
Now you should be able to run an experiment on the Kubernetes cluster or your virtual machine.
57
48
58
49
If you want to be able to use [iBench](https://github.com/stanford-mast/iBench) they you will need to compile binaries and make then available in `$PATH` (see mutilate description above). Keep in mind that compiling iBench binaries may require a lot of RAM and can't be done on default Vagrant VM configuration.
59
50
@@ -65,11 +56,11 @@ Vagrant will allocate 2 CPUs and 4096 MB RAM for the VM by default. You can cons
65
56
66
57
## Deeper dive
67
58
68
-
If you want to learn more about VM configuration and installed packages refer to [provisioning script](provision.sh).
59
+
If you want to learn more about VM configuration and installed packages refer to [provisioning script](provision.sh). It calls three other scripts and their names should be self explanatory.
69
60
70
61
Note that the `~/.glide` directory from your host will be mounted on the VM to speed up Go dependency management.
71
62
72
-
The script is responsible for:
63
+
The scripts are responsible for:
73
64
* Installing all the necessary CentOS packages that are needed to build Swan, run experiments and analyse their results.
74
65
* Installing [Snap](http://snap-telemetry.io/) and its plugins that are responsible for gathering experiment results.
75
66
* Installing [Docker](https://www.docker.com/) that allows running experiment on [Kubernetes](https://kubernetes.io) cluster.
@@ -78,6 +69,12 @@ The script is responsible for:
78
69
* Setting up SSH for root.
79
70
* Installing [Go](https://golang.org/).
80
71
72
+
If you wish to setup experiment environment on another host then you should be able to run [provision_experiment_environment.sh](provision_experiment_environment.sh) on the host. You will need to provide following environmental variables when calling the script:
73
+
*`SWAN_USER` - name of the user that will run experiments.
74
+
*`HOME_DIR` - home directory of `SWAN_USER`
75
+
76
+
Example call can be found in [the provisioning script](provision.sh).
77
+
81
78
### Provisioners
82
79
83
80
There are two provisioners defined in the [Vagrantfile](Vagrantfile): `aws` and `virtualbox`. Our CI infracture uses the first of them while the second should be used for development. If you try to use `aws` provider on your own it will fail as AMI is not publicly available.
0 commit comments