[ARVADOS] updated: 2.3.2-6-g14dfc5441

[Git user]

Summary of changes:
 .../crunch2-cloud/install-compute-node.html.textile.liquid | 14 +++++++++++++-
 tools/compute-images/scripts/base.sh                       |  1 -
 2 files changed, 13 insertions(+), 2 deletions(-)

       via  14dfc54412cac4cf0cb257599e19642e73f5f248 (commit)
       via  28d250e3a5ea54c3a6bcda6e5600f9fd8e3dbcf4 (commit)
       via  49d8a8f2e36d5c33577c0887d9f4482ca7b6e00d (commit)
      from  b54a01daf24713143ba7f5f85dafd1d9d0c78a0f (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 14dfc54412cac4cf0cb257599e19642e73f5f248
Author: Ward Vandewege <ward at curii.com>
Date:   Fri Jan 14 13:51:44 2022 -0500

    18624: implement review feedback.
    
    Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>

diff --git a/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid b/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
index 0db4708c0..131dde599 100644
--- a/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
+++ b/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
@@ -64,13 +64,13 @@ The desired amount of memory to make available for @mksquashfs@ can be configure
 
 h2(#requirements). Compute image requirements
 
-Arvados comes with a build script to automate the creation of a suitable compute node image (see "The build script":#building below). It is provided as a convenience. It is also possible to create a compoute node image via other means. These are the requirements:
+Arvados comes with a build script to automate the creation of a suitable compute node image (see "The build script":#building below). It is provided as a convenience. It is also possible to create a compute node image via other means. These are the requirements:
 
-* for AWS: the ssh public key for @arvados-dispatch-cloud@ (the one that corresponds with @Containers/DispatchPrivateKey@ in the Arvados config file) needs to go into ~/.ssh/authorized_keys for the ssh user you want @arvados-dispatch-cloud@ to use (cf. @CloudVMs/DriverParameters/AdminUsername@ in the Arvados config file) and that user needs to be able to sudo without password prompt, unless you use `root` in which case sudo is not used.
-* for Azure: @arvados-dispatch-cloud@ automatically extracts the ssh public key from the value of @Containers/DispatchPrivateKey@ and uses an API call to create the user specified in @CloudVMs/DriverParameters/AdminUsername@ with that ssh public key and password-less sudo enabled.
-* SSH needs to be running and reachable by @arvados-dispatch-cloud@ on port 22 (or a custom port, see @CloudVMS/SSHPort@ to in the Arvados config file)
+* for AWS: the SSH public key for @arvados-dispatch-cloud@ (the one that corresponds with @Containers.DispatchPrivateKey@ in the Arvados config file) needs to go into ~/.ssh/authorized_keys for the SSH user you want @arvados-dispatch-cloud@ to use (cf. @CloudVMs.DriverParameters.AdminUsername@ in the Arvados config file) and that user needs to be able to sudo without password prompt, unless you use `root` in which case sudo is not used.
+* for Azure: @arvados-dispatch-cloud@ automatically extracts the SSH public key from the value of @Containers.DispatchPrivateKey@ and uses an API call to create the user specified in @CloudVMs.DriverParameters.AdminUsername@ with that SSH public key and password-less sudo enabled.
+* SSH needs to be running and reachable by @arvados-dispatch-cloud@ on port 22 (or a custom port, see @CloudVMS.SSHPort@ to in the Arvados config file)
 * the @python3-arvados-fuse@ package needs to be installed
-* @Docker@ or @Singularity@ needs to be installed and running (cf. @Containers/RuntimeEngine@ in the Arvados config file).
+* @Docker@ or @Singularity@ needs to be installed (cf. @Containers.RuntimeEngine@ in the Arvados config file).
 * all available scratch space should be made available under `/tmp`.
 
 h2(#building). The build script

commit 28d250e3a5ea54c3a6bcda6e5600f9fd8e3dbcf4
Author: Ward Vandewege <ward at curii.com>
Date:   Thu Jan 13 08:39:10 2022 -0500

    18624: crunch-run no longer needs to be preinstalled on our cloud
           compute images, arvados-dispatch-cloud copies it over.
    
    Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>

diff --git a/tools/compute-images/scripts/base.sh b/tools/compute-images/scripts/base.sh
index 0ab51223b..d6887add5 100644
--- a/tools/compute-images/scripts/base.sh
+++ b/tools/compute-images/scripts/base.sh
@@ -64,7 +64,6 @@ wait_for_apt_locks && $SUDO DEBIAN_FRONTEND=noninteractive apt-get -qq --yes ins
 # Install the Arvados packages we need
 wait_for_apt_locks && $SUDO DEBIAN_FRONTEND=noninteractive apt-get -qq --yes install \
   python3-arvados-fuse \
-  crunch-run \
   arvados-docker-cleaner \
   docker.io
 

commit 49d8a8f2e36d5c33577c0887d9f4482ca7b6e00d
Author: Ward Vandewege <ward at curii.com>
Date:   Wed Jan 12 16:33:47 2022 -0500

    18624: documentation: describe the arvados-dispatch-cloud requirements
           for compute nodes.
    
    Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>

diff --git a/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid b/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
index a56519fb1..0db4708c0 100644
--- a/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
+++ b/doc/install/crunch2-cloud/install-compute-node.html.textile.liquid
@@ -15,6 +15,7 @@ SPDX-License-Identifier: CC-BY-SA-3.0
 
 # "Introduction":#introduction
 # "Create an SSH keypair":#sshkeypair
+# "Compute image requirements":#requirements
 # "The build script":#building
 # "Singularity mksquashfs configuration":#singularity_mksquashfs_configuration
 # "Build an AWS image":#aws
@@ -59,7 +60,18 @@ foktmqOY8MyctzFgXBpGTxPliGjqo8OkrOyQP2g+FL7v+Km31Xs61P8=
 
 {% include 'singularity_mksquashfs_configuration' %}
 
-The desired amount of memory to make available for @mksquashfs@ can be configured in an argument to the build script, see the next section. It defaults to @256M at .
+The desired amount of memory to make available for @mksquashfs@ can be configured in an argument to "the build script":#building. It defaults to @256M at .
+
+h2(#requirements). Compute image requirements
+
+Arvados comes with a build script to automate the creation of a suitable compute node image (see "The build script":#building below). It is provided as a convenience. It is also possible to create a compoute node image via other means. These are the requirements:
+
+* for AWS: the ssh public key for @arvados-dispatch-cloud@ (the one that corresponds with @Containers/DispatchPrivateKey@ in the Arvados config file) needs to go into ~/.ssh/authorized_keys for the ssh user you want @arvados-dispatch-cloud@ to use (cf. @CloudVMs/DriverParameters/AdminUsername@ in the Arvados config file) and that user needs to be able to sudo without password prompt, unless you use `root` in which case sudo is not used.
+* for Azure: @arvados-dispatch-cloud@ automatically extracts the ssh public key from the value of @Containers/DispatchPrivateKey@ and uses an API call to create the user specified in @CloudVMs/DriverParameters/AdminUsername@ with that ssh public key and password-less sudo enabled.
+* SSH needs to be running and reachable by @arvados-dispatch-cloud@ on port 22 (or a custom port, see @CloudVMS/SSHPort@ to in the Arvados config file)
+* the @python3-arvados-fuse@ package needs to be installed
+* @Docker@ or @Singularity@ needs to be installed and running (cf. @Containers/RuntimeEngine@ in the Arvados config file).
+* all available scratch space should be made available under `/tmp`.
 
 h2(#building). The build script
 

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


hooks/post-receive
--