[ARVADOS] updated: 1.3.0-2561-gf26e4dec0

Git user git at public.arvados.org
Thu May 14 15:13:52 UTC 2020

Summary of changes:
 doc/admin/migrating-providers.html.textile.liquid  |  2 +-
 doc/install/install-components.html.textile.liquid | 27 ----------------------
 doc/install/install-ws.html.textile.liquid         | 13 ++---------
 3 files changed, 3 insertions(+), 39 deletions(-)
 delete mode 100644 doc/install/install-components.html.textile.liquid

       via  f26e4dec04ed9d68a9f826f72b4a9e627ddc4a5c (commit)
       via  3e927bdbfcb088f27f660cc0454f9be064b64004 (commit)
       via  852ab2e6837697e16b947b86a0cb9fdd93a40222 (commit)
      from  ca1eb648712232558014d648939868b2a902558a (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 f26e4dec04ed9d68a9f826f72b4a9e627ddc4a5c
Author: Tom Clegg <tom at tomclegg.ca>
Date:   Thu May 14 11:12:45 2020 -0400

    15881: Remove unreferenced doc page install/install-components.html.
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at tomclegg.ca>

diff --git a/doc/install/install-components.html.textile.liquid b/doc/install/install-components.html.textile.liquid
deleted file mode 100644
index cdaa71ce5..000000000
--- a/doc/install/install-components.html.textile.liquid
+++ /dev/null
@@ -1,27 +0,0 @@
-layout: default
-navsection: installguide
-title: Choosing which components to install
-Arvados consists of many components, some of which may be omitted (at the cost of reduced functionality.)  It may also be helpful to review the "Arvados Architecture":{{site.baseurl}}/architecture to understand how these components interact.
-table(table table-bordered table-condensed).
-|\3=. *Core*|
-|"Postgres database":install-postgresql.html |Stores data for the API server.|Required.|
-|"API server":install-api-server.html |Core Arvados logic for managing users, groups, collections, containers, and enforcing permissions.|Required.|
-|\3=. *Keep (storage)*|
-|"Keepstore":install-keepstore.html |Stores content-addressed blocks in a variety of backends (local filesystem, cloud object storage).|Required.|
-|"Keepproxy":install-keepproxy.html |Gateway service to access keep servers from external networks.|Required to be able to use arv-put, arv-get, or arv-mount outside the private Arvados network.|
-|"Keep-web":install-keep-web.html |Gateway service providing read/write HTTP and WebDAV support on top of Keep.|Required to be able to download files from Keep over plain HTTP in Workbench.|
-|"Keep-balance":install-keep-balance.html |Storage cluster maintenance daemon responsible for moving blocks to their optimal server location, adjusting block replication levels, and trashing unreferenced blocks.|Required to free deleted data from underlying storage, and to ensure proper replication and block distribution (including support for storage classes).|
-|\3=. *User interface*|
-|"Workbench":install-workbench-app.html, "Workbench2":install-workbench2-app.html |Primary graphical user interface for working with file collections and running containers.|Optional.  Depends on API server, SSO server, keep-web, websockets server.|
-|"Workflow Composer":install-composer.html |Graphical user interface for editing Common Workflow Language workflows.|Optional.  Depends on git server (arv-git-httpd).|
-|\3=. *Additional services*|
-|"Websockets server":install-ws.html |Event distribution server.|Required to view streaming container logs in Workbench.|
-|"Shell server":install-shell-server.html |Synchronize (create/delete/configure) Unix shell accounts with Arvados users.|Optional.|
-|"Git server":install-arv-git-httpd.html |Arvados-hosted git repositories, with Arvados-token based authentication.|Optional, but required by Workflow Composer.|
-|\3=. *Crunch (running containers)*|
-|"crunch-dispatch-slurm":crunch2-slurm/install-prerequisites.html |Run analysis workflows using Docker containers distributed across a SLURM cluster.|Optional if you wish to use Arvados for data management only.|
-|"Node Manager":install-nodemanager.html |Allocate and free cloud VM instances on demand based on workload.|Optional, not needed for a static SLURM cluster (such as on-premise HPC).|

commit 3e927bdbfcb088f27f660cc0454f9be064b64004
Author: Tom Clegg <tom at tomclegg.ca>
Date:   Thu May 14 11:09:03 2020 -0400

    15881: Remove duplicate section, update test URL.
    //ws/status.json has been removed.
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at tomclegg.ca>

diff --git a/doc/install/install-ws.html.textile.liquid b/doc/install/install-ws.html.textile.liquid
index e7b20f45a..11862a6ae 100644
--- a/doc/install/install-ws.html.textile.liquid
+++ b/doc/install/install-ws.html.textile.liquid
@@ -71,21 +71,12 @@ server {
 {% include 'restart_api' %}
-h2(#restart-api). Restart the API server and controller
-After adding the SSO server to the Services section, make sure the cluster config file is up to date on the API server host, and restart the API server and controller processes to ensure the changes are applied.
-<pre><code># <span class="userinput">systemctl restart nginx arvados-controller</span>
 h2(#confirm). Confirm working installation
 Confirm the service is listening on its assigned port and responding to requests.
-<pre><code>~$ <span class="userinput">curl https://<span class="userinput">ws.ClusterID.example.com</span>/status.json</span>
+<pre><code>~$ <span class="userinput">curl https://<span class="userinput">ws.ClusterID.example.com</span>/websocket</span>
+not websocket protocol

commit 852ab2e6837697e16b947b86a0cb9fdd93a40222
Author: Tom Clegg <tom at tomclegg.ca>
Date:   Thu May 14 10:56:43 2020 -0400

    15881: Fix typo.
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at tomclegg.ca>

diff --git a/doc/admin/migrating-providers.html.textile.liquid b/doc/admin/migrating-providers.html.textile.liquid
index 89a5d18a7..b684111f9 100644
--- a/doc/admin/migrating-providers.html.textile.liquid
+++ b/doc/admin/migrating-providers.html.textile.liquid
@@ -13,4 +13,4 @@ When a user logs in to Arvados, their email address (as returned by the authenti
 If you reconfigure Arvados to use a different authentication provider after some users have created accounts, you should either ensure the new provider returns the same email addresses as the old one, or update your Arvados users' @email@ attributes to match the email addresses returned by the new provider.
-Otherwise, next time users log in, they will be given new accounts intead of logging in to their existing accounts.
+Otherwise, next time users log in, they will be given new accounts instead of logging in to their existing accounts.



More information about the arvados-commits mailing list