Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: Debian packages for debian 9 (stretch) ?
From: Ralph Lange <ralph.lange@gmx.de>
To: EPICS Tech Talk <tech-talk@aps.anl.gov>
Date: Thu, 27 Jul 2017 13:57:27 +0200
In the context of ITER's CODAC Core System (RHEL+EPICS+ITER-tools), all support modules (e.g. Base, Asyn, Stream, locally developed drivers) are packaged; in this case as RPMs, naturally, containing shared libraries.

Any application module will also generate RPMs: one RPM per IOC. Such an IOC package contains the IOC binary as well as the st.cmd and all DBD and DB files it uses, including the snippets necessary to start the IOC as a system service. The RPM has proper dependency settings to the exact versions of the driver and support packages it needs, as well as to the services that have to run locally (logging server, CA Repeater etc.).

Installing an IOC package on a host pulls all other packages the IOC needs to run, and adds the IOC to the system services.
Activation of the IOC as system service and actually starting it as part of the package install are done based on a is-a-target-system flag that is one of the host settings.

You can set up a blank minimal system with a connection to our ITER RPM repository, and installing that single IOC package will bootstrap the machine to run the IOC.
Remote management of such installations using Ansible is being considered.

Cheers,
~Ralph


On Thu, Jul 27, 2017 at 11:57 AM, Michael Davidsaver <mdavidsaver@gmail.com> wrote:
The scheme I put in place while working on NSLS2 had two parts.  Debian
packages for widely used epics modules (eg. streamdevice).  In practice
this were the pieces that didn't change frequently.  Some of the locally
developed code was packaged, but not all.

The other part was running IOCs.  This was done using procServ and the
scripts in the 'sysv-rc-softioc' package (see installed README).

These two parts were joined by having a convention of placing IOC
instances in "/epics/iocs/<instance>/...".  Typically this was a VCS
checkout which built the final IOC executable.  This step was managed by
individual controls engineers.

I hope this is helpful for you.

References:
Debian packages for debian 9 (stretch) ? Carlos Pascual
Re: Debian packages for debian 9 (stretch) ? Carlos Pascual
Re: Debian packages for debian 9 (stretch) ? Carlos Pascual
Re: Debian packages for debian 9 (stretch) ? Michael Davidsaver
Re: Debian packages for debian 9 (stretch) ? Bo Jakobsen
Re: Debian packages for debian 9 (stretch) ? Michael Davidsaver

Navigate by Date:
Prev: Re: IOC error message on camonitor disconnect Michael Davidsaver
Next: Re: Debian packages for debian 9 (stretch) ? Bo Jakobsen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: Debian packages for debian 9 (stretch) ? Michael Davidsaver
Next: Re: Debian packages for debian 9 (stretch) ? Bo Jakobsen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 27 Jul 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·