[INSTRM-633] Define mountpoints and exports for image data disks Created: 27/Jul/17  Updated: 22/Jul/21  Resolved: 27/Jul/17

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

Type: Task Priority: Normal
Reporter: cloomis Assignee: cloomis
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-145 New R1 writtes data in /data/pfs/ and... Done

 Description   

We need to agree on the exports and mountpoints for the data, product, log disks. Probably others, like home.

The existing client systems know their own identity, based on their DHCP-provided hostname. My inclination is for the clients to mount "generic" mountpoints, then write into host-named subdirectories. E.g.

server export client mount client write
servername:/data/pfs /data/pfs /data/pfs/{r1,mcs,ag2,etc.}

Adding the client or server hostname to fstab would be a significant complication. Using it in actor self-configuration is trivial.

One question is what the server side looks like? Can we easily use such generic mounts? Can we have a single server name for all datasets or should we have dataserver
logserver, productserver, etc.

 Comments   
Comment by shimono [ 27/Jul/17 ]
  1. NFS server and backend storage LUNs need to be configured with performance issue taken into account. Currently 4 or 8 LUNs are planned (refer SSN-00029): FITS (1 or 5 - 4 NCUs and 1 others), VM image, operational data, DB.
  2. I am not sure what logserver means, but if it is outputs from actor instance into ICS_MHS_LOGS_ROOT, I think these could be considered as one of normal output from actor to be saved into misc data storage. If it means system-wide logging service including rsyslog etc., I don't think actor need to care of its storage beyond service server.
  3. For home and actor code, SpS and others shall be different, to deal with SpS standalone mode.

For this ticket, I'd propose to have definition only for FITS liked data products, but not including others such as logs or other misc outputs.

Comment by hassan [ 19/Mar/19 ]

Following discussions with cloomis: this ticket is not related to the datamodel, so has been moved to INSTRM as it is ICS-specific.

Comment by hassan [ 22/Jul/21 ]

cloomis: I think this is already implemented, correct?

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