Document hotfix process for IDAaaS and other platforms by cmarooney-stfc · Pull Request #1296 · pace-neutrons/Horace

cmarooney-stfc · 2023-09-27T15:24:50Z

Writeup of processes for modifying IDAaaS deployment of Horace, including notes on SCARF and ISISCompute

abuts · 2023-09-27T15:56:12Z

documentation/smg/11_ISIS_release.md

+- ISISCOMPUTE: This is the base location for code deployed to IDAaaS, and can also be used directly by experienced users only. The section on this below gives reference details
+for use of this system. 


Where it have come from. ISISCOMPUTE is dead now.
All mentions to it should be removed.

One can add instrument machines if you wish to, as example of standard user enviroments. It has been and probably still is enabled there, but this is backup as theses are old weak machines. I used to support them but had not looked into it for ages

Apologies, my text appears to be based on a clone on 20 Sept, before your changes - don't know how this happened. I will update based on the more recent versions.

abuts · 2023-09-27T15:58:55Z

documentation/smg/11_ISIS_release.md


-#### Contact
+This document is primarily concerned with the process of upgrading Horace and releasing new Horace versions on IDAaaS. However, details for how we might update SCARF 
+and how experienced users would access Horace through ISISCOMPUTE are also given for completeness.


no isiscompute

abuts · 2023-09-27T15:59:31Z

documentation/smg/11_ISIS_release.md

+
+Various versions and components of Horace are deployed in a number of local repositories under the path `/usr/local/mprogs`.
+
+The physical disk location of these Horace repositories is the same as for ISISCOMPUTE system; the description for that system below gives more details.


no isiscompute

abuts · 2023-09-27T16:00:18Z

documentation/smg/11_ISIS_release.md

+Various versions and components of Horace are deployed in a number of local repositories under the path `/usr/local/mprogs`.
+
+The physical disk location of these Horace repositories is the same as for ISISCOMPUTE system; the description for that system below gives more details.
+As this may change subject to development of the underlying IDAaaS system structure, the path `usr/local/mprogs` provides symbolic links to the repositories' current locations.


/usr/local/mprogs -- first slash is important

abuts · 2023-09-27T16:01:30Z

documentation/smg/11_ISIS_release.md

+
+The principal repositories are
+- Horace (underlying name: Horace_git): this is the directory corresponding to `horace_core` in a clone of the full Horace github repository.
+- Herbert (underlying name: Herbert_git): this is the directory corresponding to `herbert_core` in a clone of the full Horace github repository.


Herbert repository. Still used but outdated for Horace 4

@abuts Not clear on this. looking again at the directories in /usr/local/mprogs, the Horace slink point to Horace_git/horace_core, while the Herbert slink points to Herbert_git/herbert_core. The Horace_git path is a clone of the current github repo for Horace, including horace_core and herbert_core, but that herbert_core is not accessed from mprogs. The herbert_core accessed from mprogs is in Herbert_git, which appears to be a cut-down version of the release 3.6.3 branched repo. So it's not clear to me what Herbert content IDAaaS users are getting.

Herbert (underlying name: Herbert_git): this is the directory corresponding to herbert_core in a clone of the full Horace github repository.

actually not -- Herbert_git is the clone of Herbert repository, used together with Horace_git repository if Horace_git repositoy contains old version of the Horace, which uses separate Herbert.

Now you probably see why I do not want to write this. I would not be able to understand this sentence.

abuts · 2023-09-27T16:03:05Z

documentation/smg/11_ISIS_release.md

+
+The following additional repositories in /usr/local/mprogs hold earlier or current release versions
+- Horace_3_6 (underlying name Horace_3.6): the current stable release version which is being upgraded to Horace-4
+- Horace 3_2 (underlying name Horace; note this is not the same as the symbolically-linked name Horace): preceding historically stable version; not expected to be used


I've just asked to remove this so, may be removed

I mean Horace_3_2, and Herbert_3_2 -- this simulinks will be removed, so should not be described

For 3.2, guessing it's fine if you remove it. I can remove references. For 3.6, i thought that was the default choice if not switched to v4 so checking you're not going to remove that

abuts · 2023-09-27T16:03:36Z

documentation/smg/11_ISIS_release.md

+
+#### General deploy comments
+
+The process is currently absolutely the same as on ISISCOMPUTE. The real ISISCOMPUTE and virtual IDAaaS machines are currently share the same OS version 


no ISISCOMPUITE

abuts · 2023-09-27T16:03:49Z

documentation/smg/11_ISIS_release.md


-hiding technical areas from inexperienced users.
+Write access to code repository on iDaaaS is granted by the IDAaaS team on request. Currently the list of people who have write access coincides with 
+the members of **mslice** group on ISISCOMPUTE. This may change in a future. 


no isiscompute

abuts · 2023-09-27T16:05:58Z

documentation/smg/11_ISIS_release.md

+For other outputs, please consult with the Horace developers.
+- Bring the changes into the IDAaaS repository with the command `git pull`.
+- If you have also made changes in the `herbert_core` directory, repeat these steps in the Herbert (Herbert_git) repository. 
+Although Horace and Herbert have been merged into a single repository on github, they are stilll represented by two separate repositories on IDAaaS.


old versions are still present on `IDAAAS until expected to be used with old versions of Horace

@abuts As noted above on my comment on line 36, the mprogs/Horace slinks to repo Horace_git (its folder horace_core) which is the latest master or branch from it, while mprogs/Herbert slinks to a different repo Herbert_git (its folder herbert_core) which is branched to the v3.6.3 release. In general I am confused about how Horace and Herbert are paired up.

abuts

Normally I hate reading and following step-by step instructions and the addition is a step-by step instruction.
It more or less clear, and the general instructions are there, so could be accepted.
Isiscompute references should be removed. ISISCOMPUTE is in the past. This is the only change which have to be done to this document

cmarooney-stfc added 6 commits September 27, 2023 10:25

begin first draft

4482ff2

first draft continue 1

7990e3c

add to draft 2

d0ee909

draft 3

6bf0f1c

draft 4

d967bd9

draft 5

69adf8d

cmarooney-stfc added the DO_NOT_CI Skip CI on this PR label Sep 27, 2023

cmarooney-stfc requested review from abuts and tgperring September 27, 2023 15:24

abuts reviewed Sep 27, 2023

View reviewed changes

abuts requested changes Sep 27, 2023

View reviewed changes

revision requests

41b4c3a

		- ISISCOMPUTE: This is the base location for code deployed to IDAaaS, and can also be used directly by experienced users only. The section on this below gives reference details
		for use of this system.


		Various versions and components of Horace are deployed in a number of local repositories under the path `/usr/local/mprogs`.

		The physical disk location of these Horace repositories is the same as for ISISCOMPUTE system; the description for that system below gives more details.


		#### General deploy comments

		The process is currently absolutely the same as on ISISCOMPUTE. The real ISISCOMPUTE and virtual IDAaaS machines are currently share the same OS version

Conversation

cmarooney-stfc commented Sep 27, 2023 • edited by oerc0122 Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

abuts Sep 27, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

abuts Sep 27, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

abuts Sep 28, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

abuts Sep 27, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

abuts left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

cmarooney-stfc commented Sep 27, 2023 •

edited by oerc0122

Loading

abuts Sep 27, 2023 •

edited

Loading

abuts Sep 27, 2023 •

edited

Loading

abuts Sep 28, 2023 •

edited

Loading

abuts Sep 27, 2023 •

edited

Loading