[INSTRM-867] Move JHU and LAM configurations closer to Subaru Created: 19/Dec/19  Updated: 14/Aug/20  Resolved: 14/Aug/20

Status: Done
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: cloomis
Resolution: Done Votes: 0
Labels: SM2, SPS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-995 software migration at LAM Done
relates to INSTRM-831 Re-layer /data usage for MCS and SPS. Done
Story Points: 3
Sprint: SM1PD-2020 A, SM1PD-2020 B, SM1PD-2020 C, SM1PD-2020 D, SM1PD-2020 G, SM1PD-2020 E, SM1PD-2020 F

 Description   

SM1 was the first module installed at Subaru, and forced us to configure the software for operations at the summit. We are still working on integration (INSTRM-778), but will finish soon.

I believe we should apply some of those Subaru changes to both LAM and JHU. If we do so the remaining modules should install quite smoothly. There are few, but worth stating. [ Updating the libraries and actors is a given. ]

Specifically:

  • change dnsmasq and configurations to use the Subaru hostnames (mhs-ics, actors-ics, rack5-ics, db-ics, nfs-ics, etc). JHU and LAM will need to split their configurations a bit more, to match their physical hosts. Will need to add name aliases, etc.
  • change paths to match Subaru (/data/raw/YYYMMDD/sps/, etc.)
  • switch to iicActor/"gen2Actor" for visit allocation. (as much as sensible)

We should not change the uids/gids to match Subaru. That was quick to do at Subaru, and would be horrible at JHU & LAM.

Anything else arnaud.lefur?

 Comments   
Comment by arnaud.lefur [ 22/Dec/19 ]

All good to me.
Morever, I think that we'll set up a vnc server at LAM as well, and run all the GUIs on it.

It revealed convenient.

Comment by hassan [ 13/Feb/20 ]

Work in progress.

Comment by hassan [ 26/Feb/20 ]

Arnaud reported a problem related to dnsmasq at LAM. Will be investigated.

Comment by hassan [ 14/Aug/20 ]

Majority of work done for this ticket to be closed. New tickets will be filed if required.

Generated at Sat Feb 10 16:29:28 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.