1 / 26

Multiplexing, archiving & persistency

Multiplexing, archiving & persistency. Topics coming across CO, OP & Equipment Groups !. From discussions involving : M. Benedikt, B. Frammery, J-J. Gras, M. Lamont, J. Lewis, J-L. Nougaret, R. Steerenberg, J. Wenninger, M. Zerlauth. Main requirements. OP requirements.

braden
Télécharger la présentation

Multiplexing, archiving & persistency

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiplexing, archiving& persistency Topics coming across CO, OP & Equipment Groups ! From discussions involving : M. Benedikt, B. Frammery, J-J. Gras, M. Lamont, J. Lewis, J-L. Nougaret, R. Steerenberg, J. Wenninger, M. Zerlauth

  2. Main requirements b.frammery

  3. OP requirements • Availability of a number of machine settings “alive” in the Front-ends (for multiplexing those machines) • Availability of a large number of machine settings archived in database • Storing complete machine settings to archive • Loading complete machine settings from archive to replace any of the “alive” machine settings • Naming and renaming dynamically sets of machine settings to clarify their usage (mainly requested for PS Complex) . • Create new sets of machine settings starting from settings stored in database b.frammery

  4. Equipment specialists requirements • 3 types of experts settings • Equipment settings beam-dependent: multiplexed on different kind of criteria and with archiving facilities • Configuration parameters : settings only related to hardware configuration. No archiving, no multiplexing needed • Critical settings for LHC and transfer lines from SPS : archiving and solid persistency needed • Specific tools needed to instantiate and manage these settings b.frammery

  5. A first look at the concepts b.frammery

  6. Settings Configuration parameters Settings Front-Ends S1 S2 S3 “Slots” for multiplexed settings S4 Configuration parameters … S22 S23 S24 Settings & parameters in FECs non-multiplexed Front-end memory space b.frammery

  7. Settings Settings Configuration parameters Configuration parameters Front-Ends Front-Ends S1 S1 USER_X S2 S2 USER_D … S3 S3 USER_M … S4 S4 USER_U … … … S22 S22 USER_A non-multiplexed non-multiplexed S23 S23 USER_K S24 S24 USER_J Timing system Basic ingredients Edited by operations T e l e g r a m USER_D … USER Destination Part. type … USER_D d2 p Look up table Front-end memory space b.frammery

  8. Configuration parameters Configuration parameters Configuration parameters Settings Settings Settings S1 S1 S1 USER_X USER_X USER_X S2 S2 S2 USER_D USER_D USER_D S3 S3 S3 USER_M USER_M USER_M S4 S4 S4 USER_U USER_U USER_U … … … … … … S22 S22 S22 USER_A USER_A USER_A S23 S23 S23 USER_K USER_K USER_K non-multiplexed non-multiplexed non-multiplexed S24 S24 S24 USER_J USER_J USER_J Multiplexing Front-Ends USER_D USER_D USER_U USER_K USER_D USER_U USER_D USER_U USER_U Sequence of cycles USER_U USER_K USER_K non-multiplexed USER_K non-multiplexed non-multiplexed Front-ends b.frammery

  9. Configuration parameters Configuration parameters Configuration parameters Settings Settings Settings S1 S1 S1 USER_X USER_X USER_X S2 S2 S2 USER_D USER_D USER_D S3 S3 S3 USER_M USER_M USER_M S4 S4 S4 USER_U USER_U USER_U … … … … … … S22 S22 S22 USER_A USER_A USER_A S23 S23 S23 USER_K USER_K USER_K non-multiplexed non-multiplexed non-multiplexed S24 S24 S24 USER_J USER_J USER_J Storing into archive Front-Ends Front-Ends USER_D USER_D Database USER_D USER_D h/d/m/y non-multiplexed non-multiplexed non-multiplexed b.frammery

  10. Configuration parameters Configuration parameters Configuration parameters Settings Settings Settings S1 S1 S1 USER_X USER_X USER_X S2 S2 S2 USER_D USER_D USER_D S3 S3 S3 USER_M USER_M USER_M S4 S4 S4 USER_U USER_U USER_U … … … … … … S22 S22 S22 USER_A USER_A USER_A S23 S23 S23 USER_K USER_K USER_K non-multiplexed non-multiplexed non-multiplexed S24 S24 S24 USER_J USER_J USER_J Loading from archive USER_Z USER_Z USER_Z Database non-multiplexed non-multiplexed non-multiplexed USER_Z h/d/m/y Front-Ends b.frammery

  11. Configuration parameters Configuration parameters Configuration parameters Settings Settings Settings S1 S1 S1 USER_X USER_X USER_X S2 S2 S2 USER_D USER_D USER_D S3 S3 S3 USER_M USER_M USER_M S4 S4 S4 USER_U USER_U USER_U … … … … … … S22 S22 S22 USER_A USER_A USER_A S23 S23 S23 USER_K USER_K USER_K non-multiplexed non-multiplexed non-multiplexed S24 S24 S24 USER_J USER_J USER_J Persistency Every x minutes Database Backup Archives Front-Ends b.frammery

  12. Handling settings b.frammery

  13. Handling settings (1) • 24 “slots” are defined in every Front-End to hold 24 active sets of machine settings • USER is the only key for archiving machine settings • USER is the main key for multiplexing machine settings • Then, how to multiplex on other keys than USERs? b.frammery

  14. t e l e g r a m … USER Destination … … USER_N d2 … Handling settings (2) • Device settings not multiplexed on USERs are considered as different devices “inside” a USER • Exclusive enabling of one of the devices driven by telegram N Y N USER_N USER_W • Valid only for a few devices ! b.frammery

  15. Handling settings (3) • Complete machine settings are archived: • all the machine settings • all non-multiplexed machine settings • This includes expert settings & critical settings • Archives are organized by USER names & dates • Configuration parameters are not archived b.frammery

  16. Handling settings (4) • Settings are restored from archive • according to USER names & dates • globally per machine … or • by subsets for a given machine …and possibly • with authentication procedures (critical settings) • possibility to restrict the management of subsets of settings to specific specialists b.frammery

  17. Handling settings (5) • Transmission of settings from applications to the FECs according to “strings” containing a USER name • Ex : CPS. SFTPRO. Xxx • The strings are converted to FEC slot numbers by a routine of the timing library (“referred to as “lookup table”). • Active USER names are propagated throughout the control system when a name of an active USER is changed: • Renaming of an active USER, • Replacement of an active USER by another from archive b.frammery

  18. Handling beams in LHC • Beams are managed through “Beam types” • List of these different types not yet known • Critical settings archived separately • Two possibilities (still an opened question) : • Multiplex the LHC on Beam types • then the USER is the Beam type • Not multiplex the LHC • download before every change of Beam type the settings of the parameters sensitive to Beam types (as for critical settings) b.frammery

  19. Who does what ? b.frammery

  20. Timing system • Provides the multiplexing keys (telegram) • Provides the lookup table mechanism to correlate USER name and FEC slots • Propagates USER name changes to the Front-ends and to the application programs (console manager) b.frammery

  21. FESA • As the new Front-end software infrastructure for all the CERN accelerators, FESA has to: • Allows the multiplexing of the injectors including the SPS • Takes care of persisting active machine settings (backup storages ~ every 5 minutes) • Allows for a good management of operations settings, expert settings (and critical settings ?) • Is adequate for non-cycled machines as LHC • Preserve/enhance the functionality existing in the present multiplexing scheme • Propagates a “default” value into the 24 “slots” active in the Front-Ends at instantiation of a new parameter. b.frammery

  22. LSA • LSA handles the archive mechanisms • (few words but heavy task !) • Currently, lots of legacy: transition to be defined b.frammery

  23. Equipment groups • Specific software (RT tasks) for the running of non-USER multiplexed settings • Expert program to access configuration parameters • … b.frammery

  24. Discussion opened … b.frammery

  25. b.frammery

  26. The 2006 SPS USERs 24 USERs defined by OP to cover the whole 2006 year b.frammery

More Related