[arvados] updated: 2.1.0-2951-gfeb45077e
git repository hosting
git at public.arvados.org
Mon Oct 17 20:12:28 UTC 2022
Summary of changes:
doc/install/salt-multi-host.html.textile.liquid | 8 ++++----
doc/install/salt-single-host.html.textile.liquid | 18 +++++++++---------
2 files changed, 13 insertions(+), 13 deletions(-)
via feb45077eb3b766df63d048d492aaf7aca3d2be2 (commit)
via c25c56f88c4aad0c37c860ddae34ebcfc7c57b8b (commit)
from 9d862fee9a5a3e75b7abf1815390392128062cdc (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 feb45077eb3b766df63d048d492aaf7aca3d2be2
Author: Peter Amstutz <peter.amstutz at curii.com>
Date: Mon Oct 17 16:12:15 2022 -0400
19215: Formatting fixes
Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz at curii.com>
diff --git a/doc/install/salt-multi-host.html.textile.liquid b/doc/install/salt-multi-host.html.textile.liquid
index d4c33434e..ab101e768 100644
--- a/doc/install/salt-multi-host.html.textile.liquid
+++ b/doc/install/salt-multi-host.html.textile.liquid
@@ -37,11 +37,11 @@ h2(#prerequisites). Prerequisites and planning
h3. Cluster ID and base domain
-Choose a 5-character cluster identifier that will represent the cluster. Here are "guidelines on choosing a cluster identifier":../architecture/federation.html#cluster_id . Only lowercase letters and digits 0-9 are allowed. Examples will use @xarv1@ or ${CLUSTER}, you should substitute the cluster id you have selected.
+Choose a 5-character cluster identifier that will represent the cluster. Here are "guidelines on choosing a cluster identifier":../architecture/federation.html#cluster_id . Only lowercase letters and digits 0-9 are allowed. Examples will use @xarv1@ or @${CLUSTER}@, you should substitute the cluster id you have selected.
-Determine the base domain for the cluster. This will be referred to as ${DOMAIN}
+Determine the base domain for the cluster. This will be referred to as @${DOMAIN}@.
-For example, if CLUSTER is "xarv1" and DOMAIN is "example.com", then "controller.${CLUSTER}.${DOMAIN}" means "controller.xargv1.example.com".
+For example, if CLUSTER is @xarv1@ and DOMAIN is @example.com@, then @controller.${CLUSTER}.${DOMAIN}@" means @controller.xargv1.example.com at .
h3. Virtual Private Cloud (AWS specific)
@@ -308,7 +308,7 @@ h2(#initial_user). Initial user and login
At this point you should be able to log into the Arvados cluster. The initial URL will be
-https://workbench.${CLUSTER}.${DOMAIN}
+https://workbench.@${CLUSTER}.${DOMAIN}@
If you did *not* "configure a different authentication provider":#authentication you will be using the "Test" provider, and the provision script creates an initial user for testing purposes. This user is configured as administrator of the newly created cluster. It uses the values of @INITIAL_USER@ and @INITIAL_USER_PASSWORD@ the @local.params@ file.
diff --git a/doc/install/salt-single-host.html.textile.liquid b/doc/install/salt-single-host.html.textile.liquid
index d9afc53c1..646b7536b 100644
--- a/doc/install/salt-single-host.html.textile.liquid
+++ b/doc/install/salt-single-host.html.textile.liquid
@@ -39,16 +39,16 @@ h2(#prerequisites). Prerequisites and planning
h3. Cluster ID and base domain
-Choose a 5-character cluster identifier that will represent the cluster. Here are "guidelines on choosing a cluster identifier":../architecture/federation.html#cluster_id . Only lowercase letters and digits 0-9 are allowed. Examples will use @xarv1@ or ${CLUSTER}, you should substitute the cluster id you have selected.
+Choose a 5-character cluster identifier that will represent the cluster. Here are "guidelines on choosing a cluster identifier":../architecture/federation.html#cluster_id . Only lowercase letters and digits 0-9 are allowed. Examples will use @xarv1@ or @${CLUSTER}@, you should substitute the cluster id you have selected.
Determine if you will use a single hostname, or multiple hostnames.
* Single hostname is simpler to set up and can even be used without a hostname at all, just a bare IP address.
* Multiple hostnames is more similar to the recommended production configuration may make it easier to migrate to a multi-host production configuration in the future, but is more complicated as it requires adding a number of DNS entries.
-If you are using multiple hostnames, determine the base domain for the cluster. This will be referred to as ${DOMAIN}
+If you are using multiple hostnames, determine the base domain for the cluster. This will be referred to as @${DOMAIN}@.
-For example, if CLUSTER is "xarv1" and DOMAIN is "example.com", then "controller.${CLUSTER}.${DOMAIN}" means "controller.xargv1.example.com".
+For example, if CLUSTER is @xarv1@ and DOMAIN is @example.com@, then @controller.${CLUSTER}.${DOMAIN}@" means @controller.xargv1.example.com at .
h3. Machine specification
@@ -223,7 +223,7 @@ https://${HOSTNAME_EXT}
For the multi-hostname install, it will be:
-https://workbench.${CLUSTER}.${DOMAIN}
+https://workbench.@${CLUSTER}.${DOMAIN}@
If you did *not* "configure a different authentication provider":#authentication you will be using the "Test" provider, and the provision script creates an initial user for testing purposes. This user is configured as administrator of the newly created cluster. It uses the values of @INITIAL_USER@ and @INITIAL_USER_PASSWORD@ the @local.params@ file.
commit c25c56f88c4aad0c37c860ddae34ebcfc7c57b8b
Author: Peter Amstutz <peter.amstutz at curii.com>
Date: Mon Oct 17 15:58:18 2022 -0400
19215: Fix note about location of keep blocks.
Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <peter.amstutz at curii.com>
diff --git a/doc/install/salt-single-host.html.textile.liquid b/doc/install/salt-single-host.html.textile.liquid
index 47208de6d..d9afc53c1 100644
--- a/doc/install/salt-single-host.html.textile.liquid
+++ b/doc/install/salt-single-host.html.textile.liquid
@@ -29,11 +29,11 @@ h2(#limitations). Limitations of the single host install
*NOTE: The single host installation is a good choice for evaluating Arvados, but it is not recommended for production use.*
-Using the default configuration, has a number of limitations:
+Using the default configuration, the single host install has scaling limitations compared to a production multi-host install:
-* All services run on the same machine, and they will compete for resources. This includes any compute jobs.
-* It uses the local machine disk for Keep storage (under the @/tmp@ directory). There may not be a lot of space available.
-* It installs the @crunch-dispatch-local@ dispatcher, which has a limit of eight concurrent jobs. These jobs will be executed on the same machine that runs all the Arvados services may compete for resources.
+* It uses the local disk for Keep storage (under the @/var/lib/arvados@ directory).
+* It uses the @crunch-dispatch-local@ dispatcher, which has a limit of eight concurrent jobs.
+* Because jobs and Arvados services all run on the same machine, they will compete for CPU/RAM resources.
h2(#prerequisites). Prerequisites and planning
@@ -59,7 +59,7 @@ You will need a dedicated (virtual) machine for your Arvados server with at leas
Note: if you want to try out Arvados inside a Docker container, use "Arvbox":arvbox.html. The package-based install method uses @systemd@ to manage services; lightweight container images generally lack an init system and other tools that the installer requires.
The single host install stores user data in a PostgreSQL database (usually found under @/var/lib/postgresql@) and as Keep blocks that are stored as files under @/var/lib/arvados/@.
-Arvados logs are also kept in @/var/log@ and @/var/www/arvados-api/shared/log at . Accordingly, you should ensure that the disk partition containing @/var@ has adequate storage for your planned usage. We suggest starting with 50GiB of free space.
+Arvados logs are also kept in @/var/log@ and @/var/www/arvados-api/shared/log at . Accordingly, you should ensure that the disk partition containing @/var@ has adequate storage for your planned usage. We suggest starting with at least 50GiB of free space.
h3(#DNS). DNS hostnames for each service (multi-hostname only)
-----------------------------------------------------------------------
hooks/post-receive
--
More information about the arvados-commits
mailing list