From fede795cb7c615aaa1338b9cdcb62dfc6becc6d0 Mon Sep 17 00:00:00 2001 From: dmadmin <dmadmin@data-storage> Date: Thu, 21 Nov 2019 16:18:22 -0500 Subject: [PATCH] Pull together a new version to print. --- Installation/DataManagementSplitSystemSetup.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Installation/DataManagementSplitSystemSetup.md b/Installation/DataManagementSplitSystemSetup.md index edb812d8..9e0c75df 100644 --- a/Installation/DataManagementSplitSystemSetup.md +++ b/Installation/DataManagementSplitSystemSetup.md @@ -53,9 +53,11 @@ Once again, we are installing two different systems, each with different parts o [https://git.aps.anl.gov/DM/dm.git](https://git.aps.anl.gov/DM/dm.git) -The installation scripts for the DM System assume a particular directory structure. The contents of this repository should be cloned in the DM\_INSTALL\_DIR into a directory corresponding to a version tag. This allows the system to be updated in a way that allows updating the system in operation with a new versioned directory. Initially, and as the system is updated, a symbolic link called _production_, in DM\_INSTALL\_DIR, should be directed to the version tagged directory of _dm_. Similarly, if it is discovered that fallback is necessary, then the link will be moved back to an older version. An example of this, is shown in the image below. A stepped instruction for this, assuming as with the support module a fork of the _dm_ repository has been forked by a user, follows. These steps should be followed on both _data-storage_ and _exp-station_ nodes. +The installation scripts for the DM System assume a particular directory structure. The contents of this repository should be cloned in the DM\_INSTALL\_DIR into a directory corresponding to a version tag. This allows the system to be updated in a way that allows updating the system in operation with a new versioned directory. Initially, and as the system is updated, a symbolic link called _production_, in DM\_INSTALL\_DIR, should be directed to the version tagged directory of _dm_. Similarly, if it is discovered that fallback is necessary, then the link will be moved back to an older version. An example of this, is shown in the image below. - + + +A stepped instruction for this, assuming as with the support module a fork of the _dm_ repository has been forked by a user, follows. These steps should be followed on both _data-storage_ and _exp-station_ nodes. * Change directory to DM\_INSTALL\_DIR * clone the forked repository into a version_tagged directory -- GitLab