<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:33:57 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-1301] Adjust PFI IP addresses</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-1301</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The hosts-asiaa/pfi.conf file has 10.1 addresses for the PFI hosts. The hosts which were running at ASRD actually have statically assigned Subaru 133.40 addresses, per &lt;a href=&quot;https://github.com/Subaru-PFS/ics_pebActor/blob/master/doc/pebInstrument.rst&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/ics_pebActor/blob/master/doc/pebInstrument.rst&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So the hosts-subaru/pfi.conf file needs to be updated with a merging of that info. Since the addresses are statically assigned the MAC addresses are less important.&lt;/p&gt;

&lt;p&gt;In addition, the `fpga` host is 133.40.164.110, and `pfic` is 133.40.164.101. Those should be added before the hosts are put on the network.&lt;/p&gt;

&lt;p&gt;I&apos;d be happy to do this if other people are busy.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16902">INSTRM-1301</key>
            <summary>Adjust PFI IP addresses</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="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                    </labels>
                <created>Mon, 21 Jun 2021 19:54:03 +0000</created>
                <updated>Fri, 24 Feb 2023 08:59:47 +0000</updated>
                            <resolved>Fri, 24 Feb 2023 08:59:47 +0000</resolved>
                                                                    <component>ics_dnsmasq</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="21630" author="cloomis" created="Thu, 1 Jul 2021 03:46:20 +0000"  >&lt;p&gt;As of 2021-06-30 there are a couple of significant conflicts within the PFI hosts at Subaru. Specifically between pfic and the first temperature sensor ADAM, and between the AGCC computer and the second temperature ADAM. Note that the PFI machines currently have statically assigned IP addresses.&lt;/p&gt;

&lt;p&gt;Chi-Hung and I have looked at the current situation and are suggesting that tomorrow someone:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;move pfic to 133.40.164.105,&lt;/li&gt;
	&lt;li&gt;move the &quot;agcc-optiplex-755&quot; machine to .106&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I pushed proposed versions of the dnsmasq files. I believe they incorporate the uncommitted changes on dnsmasq-ics. I&apos;d like to suggest a couple of other changes:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;get rid of the brand and model from the agcc hostname: that will not age well.&lt;/li&gt;
	&lt;li&gt;when reconfiguring any host, switch to DHCP provisioning, which usually takes care of NTP/DNS server/netmask/gateway details.&lt;/li&gt;
	&lt;li&gt;renumber the pfilamps pi from .220 to .104. I do not know how that device is actually configured. Might need to ssh to .220 and reconfigure.&lt;/li&gt;
&lt;/ul&gt;

</comment>
                            <comment id="32306" author="yuki.moritani" created="Fri, 24 Feb 2023 08:59:47 +0000"  >&lt;p&gt;As of 2023 February, PFI IP addresses are assigned as suggested here. (although host name of the desktop PC for AG was the same. Note that the small PC o AG in the new E-box is names &quot;agcc&quot;)&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_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|zzs8ds:</customfieldvalue>

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