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-267 Instrument control development <p>This is my fault and shall be noted at the initial moment, but we need a fix on DHCP lease range configuration.</p> <p>For now, dhcp-range for the production is defined as:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>dhcp-range=133.40.164.1,133.40.164.239,72h dhcp-range=tag:!known,133.40.164.240,133.40.164.255,6h dhcp-range=133.40.165.0,133.40.165.254,72h </pre> </div></div> <p>and this will make</p> <ul> <li>registered hosts in hosts/macs files are assigned as defined (in two ranges w/o tag:!known)</li> <li>registered hosts only in macs files are assigned from two ranges w/o tag:!known</li> <li>unregistered hosts are assigned from any range</li> </ul> <p>So, we need to </p> <ul> <li>add tag:known for two (tag:!known could be better to be kept?)</li> <li>if we allow registered hosts in macs (e.g. temporal tool for AIT or engineering) but not in hosts, we shall have a flag to filter and guide them all in specified range</li> </ul> <p>how do you think, all? &gt; <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a>, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro" class="user-hover" rel="hiro">Yoshida, Hiroshige</a>, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kyono" class="user-hover" rel="kyono">kyono</a></p> INSTRM-267

Update document and configuration for DHCP lease range

Task Normal In Progress Unresolved shimono shimono Wed, 20 Dec 2017 02:54:42 +0000 Mon, 26 Mar 2018 12:04:19 +0000 ics_dnsmasq 0 6 <p>We have been using the following successfully:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> dhcp-range=tag:!known,10.1.255.2,10.1.255.254,5m dhcp-range=tag:known,10.1.1.1,10.1.99.254,4h </pre> </div></div> <p>so I agree with adding the <tt>known</tt> tag.</p> <p>Thank you for guideline. So,</p> <ul> <li>we shall have tag:known in configuration</li> <li>adding registered hostname without IP address shall not be an option<br/> right? I will update files and push PR following these.</li> </ul> <p>Added a branch for dnsmasq configuration.<br/> Documentation is blocked by <a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-71" title="organization of dnsmasq configuration files - both DHCP and DNS" class="issue-link" data-issue-key="INSTRM-71"><del>INSTRM-71</del></a> and should be branched/updated after that is approved and merged.</p> <p>code (dnsmasq) merged, but needs update on document (SSN-00028).</p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> considering having pairs of non-ip-address assigned hostname and MAC addresses, such as additional NICs (some are used for bonding, or V-LAN) or default network switch MAC addresses, we shall flag them not to eat non-assigned IP addresses within statically assigned to subsystem.<br/> So, I will try to add something like tag:/set:nia (no ip assigned) or something to flag them.</p> Development Rank 0|ii03pz: