https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-633 Instrument control development <p>We need to agree on the exports and mountpoints for the data, product, log disks. Probably others, like <tt>home</tt>.</p> <p>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.</p> <div class='table-wrap'> <table class='confluenceTable'><tbody> <tr> <th class='confluenceTh'>server export</th> <th class='confluenceTh'>client mount</th> <th class='confluenceTh'>client write</th> </tr> <tr> <td class='confluenceTd'><tt>servername:/data/pfs</tt></td> <td class='confluenceTd'><tt>/data/pfs</tt></td> <td class='confluenceTd'><tt>/data/pfs/{r1,mcs,ag2,etc.</tt>}</td> </tr> </tbody></table> </div> <p>Adding the client or server hostname to fstab would be a significant complication. Using it in actor self-configuration is trivial.</p> <p>One question is what the <em>server</em> side looks like? Can we easily use such generic mounts? Can we have a single server name for all datasets or should we have <tt>dataserver</tt><br/> <tt>logserver</tt>, <tt>productserver</tt>, etc.</p> INSTRM-633

Define mountpoints and exports for image data disks

Task Normal Open Unresolved cloomis cloomis Wed, 26 Jul 2017 16:44:50 +0000 Thu, 22 Jul 2021 12:51:52 +0000 Wed, 26 Jul 2017 16:44:50 +0000 0 2 <ol> <li>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.</li> <li>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.</li> <li>For home and actor code, SpS and others shall be different, to deal with SpS standalone mode.</li> </ol> <p>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.</p> <p>Following discussions with <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>: this ticket is not related to the datamodel, so has been moved to INSTRM as it is ICS-specific.</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>: I think this is already implemented, correct?</p> Relates INSTRM-145 Development Rank 0|ii02kv: