EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: IOC Redundancy in R3.14.10
From: "Schoeneburg, Bernd" <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: [email protected], [email protected]
Date: Thu, 10 Jul 2008 14:47:15 +0200
Hi Andrew,

Andrew Johnson wrote:
The last time we talked about that you hadn't actually set that attribute on any of the base record types, so I wasn't sure whether you still need it or not. I don't think it would be too hard to provide the attribute information to the CCE outside of the original DBD file, although admittedly it might complicate the code a bit. ...
Up to now we have not so very big databases and the ioc hardware is fast enough. So we could live without that at all. But if we need it one day we won't like it very much to have a second set of "dbd's". So for now we should (temporary) forget it and keep it in mind.

... if you don't need control over the individual tasks then you can use those calls instead, and that would simplify some of my changes. I suspect Jeff would much prefer that we provide only rsrv_pause() and rsrv_run() than to make the individual server subsystems visible in the way I currently do. I wasn't sure whether that would be Ok or not for the RMT since you then wouldn't have a 1:1 mapping between server tasks and start/stop routines, but I'm happy to take the extra routines out of rsrv if you don't need them.
The RMT starts and stops all registered tasks without looking what kind they are. We could in principle understand the whole base tasks as one. The Epics task watchdog does the supervision already. When we subscribe for a change of state (suspended) then a single combined state could be offered to the RMT. Detailed information could be made available to the RMT by the RMT get_info methode. In other words rsrv_pause and rsrv_run would be sufficient. Other individual subsystem controls would be nice but not absolutely necessary. If iocPause and iocRun stops/starts the individual tasks in the right order it would be better than we can do with the RMT.

Bernd

References:
IOC Redundancy in R3.14.10 Schoeneburg, Bernd
Re: IOC Redundancy in R3.14.10 Andrew Johnson
Re: IOC Redundancy in R3.14.10 Bernd Schoeneburg
Re: IOC Redundancy in R3.14.10 Andrew Johnson

Navigate by Date:
Prev: Re: IOC Redundancy in R3.14.10 Ben Franksen
Next: Re: IOC Redundancy in R3.14.10 Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: IOC Redundancy in R3.14.10 Benjamin Franksen
Next: Re: IOC Redundancy in R3.14.10 Artem Kazakov
Index: 2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·