<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:29:00 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-823] Restructure /data at Subaru</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-823</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Currently /data is a new ZFS filesystem, with the server side named /proddata because that was the name on the old server.&lt;/p&gt;

&lt;p&gt;We probably want a slightly different structure, for clarity, efficiency, and maintainability. I suggest that we keep mounting data products under /data, but have several ZFS filesystems mounted under that. In particular:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;/data/mcs/ (in use; old data &lt;em&gt;needs&lt;/em&gt; to be copied over to the new server.)&lt;/li&gt;
	&lt;li&gt;/data/sps/ (currently named /data/pfs at LAM/JHU. Keeping that would be easier. )&lt;/li&gt;
	&lt;li&gt;/data/agcc/&lt;/li&gt;
	&lt;li&gt;/data/drp/&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The raw data filesystems (mcs,sps,agcc) should have compression turned off (we use FITS compression), but any others should have the default compression on. The server filesystem names should be the same as the exported mountpoints.&lt;/p&gt;

&lt;p&gt;All should be group pfs. /data/sps &lt;b&gt;must&lt;/b&gt; be user pfs-data and chmod 02755; the rest should be user pfs and 02775. [ /data/&lt;/p&gt;
{mcs,agcc}
&lt;p&gt; &lt;em&gt;should&lt;/em&gt; also be user=pfs-data, 02755, but that needs to be a separate ticket. ].&lt;/p&gt;

&lt;p&gt;Any other sub-directories we come up with should be their own ZFS filesystems (/data/logs, etc.)&lt;/p&gt;

&lt;p&gt;Comments? Especially: &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=arnaud.lefur&quot; class=&quot;user-hover&quot; rel=&quot;arnaud.lefur&quot;&gt;arnaud.lefur&lt;/a&gt; &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=fmadec&quot; class=&quot;user-hover&quot; rel=&quot;fmadec&quot;&gt;fmadec&lt;/a&gt; &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan&quot; class=&quot;user-hover&quot; rel=&quot;chyan&quot;&gt;chyan&lt;/a&gt; &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl&quot; class=&quot;user-hover&quot; rel=&quot;rhl&quot;&gt;rhl&lt;/a&gt; &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=philip&quot; class=&quot;user-hover&quot; rel=&quot;philip&quot;&gt;philip&lt;/a&gt; &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro&quot; class=&quot;user-hover&quot; rel=&quot;hiro&quot;&gt;Yoshida, Hiroshige&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="14011">INSTRM-823</key>
            <summary>Restructure /data at Subaru</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="hiro">Yoshida, Hiroshige</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>SM1</label>
                            <label>SPS</label>
                            <label>subaru-personnel</label>
                    </labels>
                <created>Thu, 21 Nov 2019 17:37:40 +0000</created>
                <updated>Tue, 5 May 2020 14:19:25 +0000</updated>
                            <resolved>Wed, 4 Dec 2019 21:19:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                            <comment id="16427" author="rhl" created="Thu, 21 Nov 2019 19:47:24 +0000"  >&lt;p&gt;I think I&apos;d have transposed this, to e.g. &lt;tt&gt;/data/raw/2019-11-21/sps&lt;/tt&gt;, &lt;tt&gt;/data/raw/2019-11-21/mcs&lt;/tt&gt;, etc. so that complete sets of data get kept together.&lt;/p&gt;</comment>
                            <comment id="16428" author="cloomis" created="Thu, 21 Nov 2019 21:51:13 +0000"  >&lt;p&gt;Yes. But I suggest that having the flexibility of separate filesystems outweighs that. Maybe that is too sysadmin-y a concern.&lt;/p&gt;</comment>
                            <comment id="16429" author="rhl" created="Thu, 21 Nov 2019 23:56:02 +0000"  >&lt;p&gt;I&apos;d &quot;get it right then make it fast&quot; &amp;#8211; in this context do it &quot;properly&quot; then if we get bitten move things around and create a maze of symbolic links&lt;/p&gt;</comment>
                            <comment id="16430" author="cloomis" created="Fri, 22 Nov 2019 00:03:01 +0000"  >&lt;p&gt;Fair enough. So two filesystems: /data/raw/$DATE/&lt;/p&gt;
{mcs,sps,agcc} and /data/drp, with /data/raw being pfs-data:pfs and 02755.&lt;br/&gt;
Or simply pull that up and have /data/$DATE/{mcs,sps,agcc}
&lt;p&gt; and /drp&lt;/p&gt;</comment>
                            <comment id="16500" author="hiro" created="Tue, 3 Dec 2019 19:01:58 +0000"  >&lt;p&gt;Created and exported /data/raw and /data/drp as specified. They are already mounted on VM guests that mount /proddata on /data.&lt;/p&gt;</comment>
                            <comment id="16511" author="hassan" created="Wed, 4 Dec 2019 21:59:18 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis&quot; class=&quot;user-hover&quot; rel=&quot;cloomis&quot;&gt;cloomis&lt;/a&gt; agrees that this can be closed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14205">INSTRM-895</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="14364">PIPE2D-571</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="14101">INSTRM-831</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|02qps3:3h</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="69">SM1PD-2019 C</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>