<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:20:46 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-29] Define development archive storage operation and workflow</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-29</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;note: This is epic for initiate development archive storage service. File ticket for each individual task or issue.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&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; develop possible (or desirable) way to push FITS files from LAM local storage&lt;/li&gt;
	&lt;li&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; develop possible way to push FITS files from JHU test facility&lt;/li&gt;
	&lt;li&gt;define file distribution procedure, e.g. sync all files by periodical rsync, on-demand download by URI&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="11364">INSTRM-29</key>
            <summary>Define development archive storage operation and workflow</summary>
                <type id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10507&amp;avatarType=issuetype">Epic</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</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="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Tue, 6 Dec 2016 20:40:28 +0000</created>
                <updated>Sat, 18 Mar 2023 04:53:54 +0000</updated>
                            <resolved>Sat, 18 Mar 2023 04:53:54 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="12181" author="fmadec" created="Thu, 18 May 2017 15:34:47 +0000"  >&lt;p&gt;According to the update from  Atsuhsi it seems that IPMU have some constrains on ssh access.&lt;/p&gt;

&lt;p&gt;So that LAM propose that the synchronisation comes from IPMU or PU to LAM and not from LAM to external site.&lt;br/&gt;
This access will only be using ssh and will be restricted to ideally only to the server that will pull the data.&lt;/p&gt;

&lt;p&gt;We should agree on the frequency of the sync (ideally that could be done once a week during week-end)&lt;/p&gt;

&lt;p&gt;What do you think?&lt;/p&gt;</comment>
                            <comment id="12206" author="atsushi.shimono" created="Tue, 30 May 2017 21:31:53 +0000"  >&lt;p&gt;Restriction from outside-IPMU to global network (by means which has non-RFC1918 addresses) in IPMU is somehow messy thing now and its coordination/operation could be changed in short time scale. Web access (80/443) is relatively less restricted than ssh (22), so one &quot;reliable&quot; possibility is webdav-rsync if we want to push from outside-IPMU. For getting from this archive, there would be bunch of ways from pick one file by one via web, etc.&lt;/p&gt;

&lt;p&gt;Also if instrument development sites (like LAM, PU, ASIAA) are easily accessible from outside, ssh-rsync from IPMU archive server is one possibility. This will require some configuration at development sites, that ssh gateway is possible to reach local data storage at lab (or local archive?). How difficult depends on configurations at each site, so it is required to be checked site by site.&lt;/p&gt;

&lt;p&gt;For frequency, I think once a week at weekend could work. For immediate data transfer from LAM to PU for short time analysis, we could do/plan transfer on demand as now we are doing.&lt;/p&gt;</comment>
                            <comment id="32424" author="arnaud.lefur" created="Fri, 17 Mar 2023 20:53:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=yuki.moritani&quot; class=&quot;user-hover&quot; rel=&quot;yuki.moritani&quot;&gt;yuki.moritani&lt;/a&gt; do you want to keep this open ? or shall we close it .&lt;/p&gt;</comment>
                            <comment id="32452" author="yuki.moritani" created="Sat, 18 Mar 2023 04:53:54 +0000"  >&lt;p&gt;Since LAM data have been archiving, I close this ticket. Archiving JHU (or other institute) data will be handled under a new ticket, if we decide to do so.&#160;&lt;/p&gt;</comment>
                    </comments>
                    <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_10009" key="com.pyxis.greenhopper.jira:gh-epic-color">
                        <customfieldname>Epic Color</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ghx-label-1</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10007" key="com.pyxis.greenhopper.jira:gh-epic-label">
                        <customfieldname>Epic Name</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>devarch</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10008" key="com.pyxis.greenhopper.jira:gh-epic-status">
                        <customfieldname>Epic Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10001"><![CDATA[To Do]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii015z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>