docs(provision): add salt usage with roles in multi-host

[arvados.git] / doc / install / salt-single-host.html.textile.liquid

diff --git a/doc/install/salt-single-host.html.textile.liquid b/doc/install/salt-single-host.html.textile.liquid
index f8e1310e7b3b7d34c0291d5929bf1602fa0c966f..e0c8682c9fdda4276fff8e71508affe436e233e0 100644 (file)
--- a/doc/install/salt-single-host.html.textile.liquid
+++ b/doc/install/salt-single-host.html.textile.liquid
@@ -37,7 +37,7 @@ For documentation's sake, we will use the cluster name <i>arva2</i> and the doma
 
 Arvados' single host installation can be done in two fashions:
 
-* Using a single hostname, asigning <i>a different port (other than 443) for each user-facing service</i>: This choice is easier to setup, but the user will need to know the port/s for the different services she wants to connect to.
+* Using a single hostname, assigning <i>a different port (other than 443) for each user-facing service</i>: This choice is easier to setup, but the user will need to know the port/s for the different services she wants to connect to.
 * Using multiple hostnames on the same IP: this setup involves a few extra steps but each service will have a meaningful hostname so it will make easier to access them later.
 
 Once you decide which of these choices you prefer, copy one the two example configuration files and directory, and edit them to suit your needs.
@@ -74,6 +74,14 @@ ssh user@host sudo provision.sh
 </code></pre>
 </notextile>
 
+or, if you saved the @local.params@ in another directory or with some other name
+
+<notextile>
+<pre><code>scp -r provision.sh local* user@host:
+ssh user@host sudo provision.sh -c /path/to/your/local.params.file
+</code></pre>
+</notextile>
+
 and wait for it to finish.
 
 If everything goes OK, you'll get some final lines stating something like: