X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/25520da76bbd3c00223cf401a4b48de4681f02e8..d9214af111bb44deed1246ec97624b6bd8d970c5:/doc/install/install-manual-prerequisites.html.textile.liquid diff --git a/doc/install/install-manual-prerequisites.html.textile.liquid b/doc/install/install-manual-prerequisites.html.textile.liquid index 58aa2bb49c..74a8647fba 100644 --- a/doc/install/install-manual-prerequisites.html.textile.liquid +++ b/doc/install/install-manual-prerequisites.html.textile.liquid @@ -11,12 +11,12 @@ This guide assumes you have seven systems available in the same network subnet:
table(table table-bordered table-condensed). |_Function_|_Number of nodes_| -|Arvados REST API, Websockets, Workbench and Crunch dispatcher|1| -|Arvados SSO server|1| +|Arvados API, Crunch dispatcher, Git, Websockets and Workbench|1| +|Arvados Compute node|1| |Arvados Keepproxy server|1| |Arvados Keepstore servers|2| -|Arvados shell server|1| -|Arvados compute node|1| +|Arvados Shell server|1| +|Arvados SSO server|1|
The number of Keepstore, shell and compute nodes listed above is a minimum. In a real production installation, you will likely run many more of each of those types of nodes. In such a scenario, you would probably also want to dedicate a node to the Workbench server and Crunch dispatcher, respectively. For performance reasons, you may want to run the database server on a separate node as well. @@ -39,10 +39,10 @@ There are six public-facing services that will require an SSL certificate. If yo
table(table table-bordered table-condensed). |_Function_|_Hostname_| -|Arvados REST API|@uuid_prefix@.your.domain| -|Arvados Websockets endpoint|ws.@uuid_prefix@.your.domain| +|Arvados API|@uuid_prefix@.your.domain| |Arvados Git server|git.@uuid_prefix@.your.domain| |Arvados Keepproxy server|keep.@uuid_prefix@.your.domain| -|Arvados Workbench|workbench.@uuid_prefix@.your.domain| |Arvados SSO Server|auth.your.domain| +|Arvados Websockets endpoint|ws.@uuid_prefix@.your.domain| +|Arvados Workbench|workbench.@uuid_prefix@.your.domain|