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-283 Instrument control development <p>For now, we have bootstrap and installation scripts for eups/tron/actors in ics_config repository, which is defined to store all actor configurations but not any scripts without any relation to actor configurations.<br/> Not to make users confused, nor not to make repositories/files messy, it is better to move these installation scripts from ics_config repository to something other repository.</p> <p>Installation and configuration of the production is supposed to be performed using ansible with roles/tasks in ics_ansible repository, so it is possible to have misc scripts or supports scripts in there like this kind of bootstrap and helper scripts to be used during development and AIT.<br/> So, I'd propose to move ics_config/bin/* into ics_ansible/misc (some part is in INSTRM #176), with making them refactored to match with current situations and also python3 (INSTRM #280).</p> INSTRM-283

Move ics bootstrap scripts from configuration repository (ics_config)

Task Normal Open Unresolved Unassigned shimono Wed, 24 Jan 2018 09:21:19 +0000 Thu, 25 Jan 2018 07:39:42 +0000 Wed, 24 Jan 2018 09:21:19 +0000 ics_config 0 1 <p>I agree that we <em>should</em> probably not have the essential bootstrap and installation scripts be in the same product as the configurations. </p> <p>We have two scripts, as it stands: <tt>bootstrap_mhs</tt> and <tt>pfsinstall</tt>. <tt>bootstrap_mhs</tt> has been pared down to only install <tt>eups</tt> and <tt>ics_config</tt>, and (for now) all other packages are installed with <tt>pfsinstall</tt>.</p> <p>You can put those anywhere, with a couple of of caveats:</p> <ul class="alternate" type="square"> <li><tt>pfsinstall</tt> (and any others we add) <b>must</b> be in a bin/ directory on the PATH</li> <li>the product which <tt>pfsinstall</tt> is in <b>should not</b> depend on any other products. Otherwise you have to update the <tt>pfsinstall</tt> product when the dependent product(s) are updated.</li> </ul> <p>Since <tt>ics_ansible</tt> is a product composed of configuration data, just like <tt>ics_config</tt>, I do not think that is any better than <tt>ics_config</tt>.</p> <p>Also, as it stands <tt>ics_config</tt> is a slightly special product, since installing it defines the absolute base root paths for all of the MHS in the <tt>ics_config.table</tt> file: all other products must depend on <tt>ics_config</tt> because of that. If you move all scripts out of <tt>ics_config</tt> you will need to make that product depend on <tt>ics_config</tt>.</p> <p>I guess I don't see much benefit in moving the scripts.</p> Blocks INSTRM-176 Relates INSTRM-285 Development Rank 0|ii03tr: Reviewers cloomis