<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:22:12 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-163] Allocation of CIDRs for subsystems on the real network</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-163</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;Not linking to &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INSTRM-70&quot; title=&quot;Define procedure of configuration and coordination on dnsmasq (ics_dnsmasq repo) for production and development&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INSTRM-70&quot;&gt;&lt;del&gt;INSTRM-70&lt;/del&gt;&lt;/a&gt;, since this is a task for real allocation of resource. &lt;br/&gt;
We need to have definition and/or registration of allocation of subnets for subsystems at somewhere, as well as DHCP definitions in dnsmasq. So, we need to agree in this ticket on:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;where (repository) and how (description file format) we will register allocations&lt;/li&gt;
	&lt;li&gt;registration management - will not change so much (it&apos;s subnet but not address)?&lt;/li&gt;
	&lt;li&gt;basic idea of allocation&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Requirements (or desires?) of allocation criteria should be:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;pack related subsystem in close subnet (e.g. xCU follows ENU), and in organized order (e.g. SM2 follows SM1)&lt;/li&gt;
	&lt;li&gt;allocate by one CIDR (to make thing simple) as much as possible, with slack in each subsystem&lt;/li&gt;
	&lt;li&gt;first address (.164.1) will be taken by default gateway (port at Subaru core switch), so we&apos;d better to assign first CIDR to network switch subsystem&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="11728">INSTRM-163</key>
            <summary>Allocation of CIDRs for subsystems on the real network</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="atsushi.shimono">shimono</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Tue, 1 Aug 2017 16:12:06 +0000</created>
                <updated>Wed, 21 Feb 2018 17:51:14 +0000</updated>
                            <resolved>Wed, 21 Feb 2018 17:51:14 +0000</resolved>
                                                                    <component>ics_dnsmasq</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="12509" author="atsushi.shimono" created="Tue, 22 Aug 2017 07:28:06 +0000"  >&lt;p&gt;repository to store this kind of definitions is better to be the same as configuration conventions, so let me propose the same directory of SSN-00028 with some reorganization (e.g. adding README.rst, have links from it).&lt;br/&gt;
&lt;a href=&quot;https://github.com/Subaru-PFS/ics_doc/tree/master/SSN-00028&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/ics_doc/tree/master/SSN-00028&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;possible Idea for allocation:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;.164.0/28 (.1-.15) network switches (core x1, CB2F x1, SpS x5+, Cs x1, PF x1, and?)&lt;/li&gt;
	&lt;li&gt;.164.16/28 (.16-.31) external services (ssh gateway etc.; has some slack for allocation)&lt;/li&gt;
	&lt;li&gt;.164.32/27 (.32-.63) infrastructure@CB2F (.32/28 for pysical, .48/28 for server)&lt;/li&gt;
	&lt;li&gt;.164.64/26 (.64-.127) SM1 (.64/28 for xCU, .96/28 for ENU+)&lt;/li&gt;
	&lt;li&gt;.164.128/26 (.128-.191) SM2 (.128/28 for xCU, .160/28 for ENU+)&lt;/li&gt;
	&lt;li&gt;.164.192/26 (.192-.255) SM3 (.192/28 for xCU, .224/28 for ENU+)&lt;/li&gt;
	&lt;li&gt;.165.0/26 (.0-.64) SM4 (.0/28 for xCU, .32/28 for ENU+)&lt;/li&gt;
	&lt;li&gt;.165.64/28 (.64-.79) PFI&lt;/li&gt;
	&lt;li&gt;.165.80/29 (.80-.87) Cs (MCS)&lt;/li&gt;
	&lt;li&gt;.165.192/27 (.192-.223) SCR control (devices, UPS)&lt;/li&gt;
	&lt;li&gt;.165.224/28 (.224-.239) SCR telemetry (temporary, development)&lt;/li&gt;
	&lt;li&gt;.165.240/28 (.240-.254) landfill&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;note:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;need to have clearer idea for required number of addresses&lt;/li&gt;
	&lt;li&gt;is it better to pack 4 SMs into .165.0/24?&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="12514" author="cloomis" created="Fri, 25 Aug 2017 19:31:33 +0000"  >&lt;p&gt;Do you forsee ever actually &lt;em&gt;using&lt;/em&gt; IP subnets, each with a gateway and broadcast address? Or are you showing CIDR ranges just for allocation? If we know we will not be using routed subnets I&apos;d prefer to allocate with decimal ranges, just for the sake of humans.&lt;/p&gt;

&lt;p&gt;[ I think you mean /27 for the xCUs and ENUs: half of a /26, and 29-32 IP addresses ] &lt;/p&gt;</comment>
                            <comment id="12515" author="atsushi.shimono" created="Fri, 25 Aug 2017 22:48:18 +0000"  >&lt;p&gt;sorry to make confusion, yes, it&apos;s CIDR, except for first and last.&lt;br/&gt;
also, half of /26 shall be /27.....&lt;/p&gt;</comment>
                            <comment id="12574" author="atsushi.shimono" created="Fri, 22 Sep 2017 12:38:46 +0000"  >&lt;p&gt;added draft and PR as&lt;br/&gt;
&lt;a href=&quot;https://github.com/Subaru-PFS/ics_doc/blob/tickets/INSTRM-163/SSN-00028/ipaddr.rst&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/ics_doc/blob/tickets/INSTRM-163/SSN-00028/ipaddr.rst&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="12592" author="atsushi.shimono" created="Thu, 28 Sep 2017 05:39:14 +0000"  >&lt;p&gt;let me rename .164.64/27 as &quot;CB2F ICS services and ICS infrastructure&quot;, to include basic services like dnsmasq or syslog etc. here.&lt;br/&gt;
I don&apos;t think we will have more than 16 hosts for ICS services, such as MHS, archive, SSC, etc, also more than 16 hosts for infrastructure, such as dnsmasq, syslog, elasticsearch, promehteus, etc.&lt;/p&gt;

&lt;p&gt;also, keep in mind to assign first /28 for infrastructure, second /28 for services, as much as possible.&lt;/p&gt;</comment>
                            <comment id="12828" author="cloomis" created="Wed, 6 Dec 2017 20:02:52 +0000"  >&lt;p&gt;[ Moving to Review Complete does not open a comment panel, unlike some of the other transitions.  ]&lt;/p&gt;

&lt;p&gt;Since there will be no real routing the allocation does not strongly matter. So this is fine.&lt;/p&gt;</comment>
                            <comment id="12839" author="atsushi.shimono" created="Sun, 10 Dec 2017 07:28:15 +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; could you change on github side also?&lt;/p&gt;</comment>
                            <comment id="13004" author="atsushi.shimono" created="Wed, 21 Feb 2018 17:51:14 +0000"  >&lt;p&gt;merged&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="12059">INSTRM-291</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|ii02nb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="24">2017-10A</customfieldvalue>

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