X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/5a33764685ef7fa9578b255e78ad2ed77abc1ded..2b2707e4acb9ee7eed53f573cf5365af9189a8e3:/doc/admin/maintenance-and-upgrading.html.textile.liquid?ds=sidebyside diff --git a/doc/admin/maintenance-and-upgrading.html.textile.liquid b/doc/admin/maintenance-and-upgrading.html.textile.liquid index ae2f8276c5..2ec1700fc9 100644 --- a/doc/admin/maintenance-and-upgrading.html.textile.liquid +++ b/doc/admin/maintenance-and-upgrading.html.textile.liquid @@ -42,9 +42,9 @@ Run @arvados-server config-check@ to make sure the configuration file has no err h3(#distribution). Distribute the configuration file -We recommend to keep the @config.yml@ file in sync between all the Arvados system nodes, to avoid issues with services running on different versions of the configuration. +It is very important to keep the @config.yml@ file in sync between all the Arvados system nodes, to avoid issues with services running on different versions of the configuration. -Distribution of the configuration file can be done in many ways, e.g. scp, configuration management software, etc. +We provide "installer.sh":../install/salt-multi-host.html#installation to distribute config changes. You may also do your own orchestration e.g. @scp@, configuration management software, etc. h3(#restart). Restart the services affected by the change @@ -62,7 +62,9 @@ Upgrading Arvados typically involves the following steps: # Wait for the cluster to be idle and stop Arvados services. # Make a backup of your database, as a precaution. # update the configuration file for the new release, if necessary (see "Maintaining Arvados":#maintaining above) -# rebuild and deploy the "compute node image":{{site.baseurl}}/install/crunch2-cloud/install-compute-node.html (cloud only) +# Update compute nodes +## (cloud) Rebuild and deploy the "compute node image":{{site.baseurl}}/install/crunch2-cloud/install-compute-node.html +## (slurm/LSF) Upgrade the @python3-arvados-fuse@ package used on your compute nodes # Install new packages using @apt-get upgrade@ or @yum upgrade@. # Wait for package installation scripts as they perform any necessary data migrations. # Run @arvados-server config-check@ to detect configuration errors or deprecated entries.