[ARVADOS] updated: 1.3.0-2107-g3c8aeceba

[Git user]

Summary of changes:
 doc/install/install-dispatch-cloud.html.textile.liquid | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

       via  3c8aecebabdfeea3fd607789b48e38fba9ef5ce7 (commit)
      from  6637c4e3656d3e2334a46a7c30eaed91905a0603 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 3c8aecebabdfeea3fd607789b48e38fba9ef5ce7
Author: Peter Amstutz <peter.amstutz at curii.com>
Date:   Fri Jan 24 15:22:48 2020 -0500

    Add a bit more discussion about DNS on compute node images closes #16085
    
    Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz at curii.com>

diff --git a/doc/install/install-dispatch-cloud.html.textile.liquid b/doc/install/install-dispatch-cloud.html.textile.liquid
index c4df633a3..7bff6a4a2 100644
--- a/doc/install/install-dispatch-cloud.html.textile.liquid
+++ b/doc/install/install-dispatch-cloud.html.textile.liquid
@@ -27,15 +27,19 @@ The cloud dispatch service is for running containers on cloud VMs. It works with
 
 The cloud dispatch service can run on any node that can connect to the Arvados API service, the cloud provider's API, and the SSH service on cloud VMs.  It is not resource-intensive, so you can run it on the API server node.
 
-h2(#create-image). Create compute node VM image
+h2(#create-image). Create compute node VM image and configure resolver
 
-Create a VM image following the steps "to set up a compute node":crunch2-slurm/install-compute-node.html
+Set up a VM following the steps "to set up a compute node":crunch2-slurm/install-compute-node.html
 
-On the compute VM image, add the API server's internal IP address to @/etc/hosts@, this will ensure that it contacts the API server on the private network and not through the public interface.  For example:
+Compute nodes must be able to resolve the hostnames of the API server and any keepstore servers to your internal IP addresses.  You can do this by running an internal DNS resolver and configuring the compute VMs to use that resolver, or by hardcoding the services in the @/etc/hosts@ file.  For example:
 
 <notextile><pre><code>10.20.30.40     <span class="userinput">ClusterID.example.com</span>
+10.20.30.41     <span class="userinput">keep1.ClusterID.example.com</span>
+10.20.30.42     <span class="userinput">keep2.ClusterID.example.com</span>
 </code></pre></notextile>
 
+Once the VM is fully configured, create a reusable VM image from it and make note of the image id.
+
 h2(#update-config). Update config.yml
 
 h3. Create a private key

-----------------------------------------------------------------------


hooks/post-receive
--