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-335 Instrument control development <p>The MCS IP addresses are all ASIAA 10.1 &#8211; these need to be moved to Subaru's 133.40.</p> <p>From ics_doc's SSN-28 I'm going for 133.40.208.1...</p> INSTRM-335

Move MCS machines to Subaru network

Task Normal Done Done Unassigned cloomis Tue, 24 Apr 2018 19:40:25 +0000 Mon, 13 Mar 2023 01:26:38 +0000 Mon, 13 Mar 2023 01:26:38 +0000 0 1 <p>could you do PR at some point? for now, i'd post comments as:</p> <ul> <li>mac address for switch will change due to VLAN configuration</li> <li>idrac will not be on PFS-LAN</li> <li>range (in description of this ticket) shall be 133.40.164.208/28</li> <li>add component part for hostname 'mcs', but not just 'mcs'</li> <li>'mcs-eth2' violates naming convention (not yet formally defined, but i use additional charactor like rga1<span class="error">&#91;b-d&#93;</span>-vm for CB2F)</li> </ul> <p>The changes we are running with now are on the ticket branch. We should probably leave that alone until at least the May work is done and we are in a position to test with live machines.</p> <p>Some additional notes:</p> <ul> <li>I made one non-ticket change on the branch, by adding a <tt>tron</tt> alias to <tt>shell-ics</tt>.</li> <li>The MCS machines are <b>not</b> using DHCP yet: all the addresses are statically defined to match the <tt>dnsmasq</tt> assignment,</li> <li><tt>ics-eth2</tt> is gone.</li> <li>Yes, I used <tt>mcs</tt>, sorry. Should it be <tt>host-mcs</tt> or something? Can we leave an <tt>mcs</tt> alias for humans?</li> </ul> <p>ok, thank you for information. <br/> I understand that I shall try not to touch the production, since it could break something since i am not noticed enough information on changes.</p> Development Rank 0|ii04bz: