FWWG

Wednesday 28 Nov 2007, 14:00 → 16:00 Europe/Zurich

13/3-005

Bobby's Slide CMSProductionProjects.pdf CMSProductionProjects.ppt

Fernando's Slide FW_System_Configuration_DB_Demo_Nov_07.pdf FW_System_Configuration_DB_Demo_Nov_07.ppt

Francisca's Slides FW_System_Overview_Tool.pdf FW_System_Overview_Tool.ppt

Participants: Stefan, Robert, Jim, Frank, Bobby, Clara, Alba, Danny, Peter, Piotr, Manuel, Fernando, Francisca, Wayne 1) System Overview Tool Francisca gave a brief presentation on the system overview tool before moving onto a demonstration. Her slides can be found at: http://indico.cern.ch/conferenceDisplay.py?confId=24497 The following major points were raised: - The experiments were asked whether they wanted an OS supervision layer implemented using the LHCb FMC component, i.e. to monitor such items as CPU and disk usage, running processes, etc. All experiments, with the exception of CMS, confirmed that they would like such functionality. CMS said maybe. - Clara asked where the tool got the system hierarchy from. This comes from the System Config DB. - There was a request to include also the local project which currently is not included. - It was noted that the standard FW recommendation is for action that are not available due to lack of privilege to be left by greyed out. It was suggested that the same apply for this tool. - Clara stated that she also wanted to have access to PVSS log info. Fernando stated that this was on the list of features and would use the ATLAS central logging features. There was then a discussion on what information would be in the log and whether it was required to be stored in a DB or not. This discussion was postponed to a later date. - Fernando noted that the use of PMON might have performance issues in large systems as it uses a polling communication. An alternative would be to have a local agent on all machines that only publishes a summarised set of information. It would be useful to test PMON in a large distributed system. - There is a change in this version of the tool compared with the first version in that the logic is now decoupled from the panel, i.e. there is a control script that does the work in the background and hence data can be archived and alarms raised even if the panel is closed. - Frank requested that the PMON information be updated when a particular system is selected or at a minimum the time of the last refresh be shown. - There was a request to have both search and filter capabilities, e.g. find a project with a certain name or show all blocked managers or show the status of all RDB managers - It was felt that eventually there should be a dp for every PVSS manager in every system. - There was also a request to be able to use this tool also for sub-detectors and not just as a central tool for the full system. - It was requested to simplify the hierarchy view by only showing systems and not projects as most systems will not be scattered. The list of managers should cover all projects in a system and if possible show that these are on different machine if that is the case. - One should find out exactly what information PMON gives in different situations, e.g. some managers running but not others. - It was agreed that one level for access control was sufficient for the moment but that is likely to change later. 2) System Config DB Fernando gave a brief introduction to the System Config DB and then demonstrated its use both for locally and centrally managed projects. His slide can be found at: http://indico.cern.ch/conferenceDisplay.py?confId=24497 The following major points were raised: - Clara asked whether it was possible to remove projects and whether it was possible to add projects later to the DB. Yes on both counts. - The tool proposes to create groups of components due to a requirement from CMS. In the local mode it was proposed to create the group automatically with a default name. - Jim asked if it was possible to target a PVSS project with a component that should be installed but without forcing the installation as CMF does. Yes, this is possible for locally managed projects. As soon as one defines in the DB that a project must contain a set of components that do not exist in the project, the agent will inform that there are actions to be performed but it will not do them by itself. - In the future it should be possible to create the DIST entries in the config file from the System Config DB contents. 3) CMS Script Bobby detailed the features of the CMS scripts for creating PVSS projects and configuration them to achieve fully running application in a fully automated manner. His slide can be found at: http://indico.cern.ch/conferenceDisplay.py?confId=24497 In addition, he ran the script to show how if worked. There was a question whether there was a command line command for creating PVSS projects on Windows and Linux. There is. 4) A.o.B Frank asked whether the other experiments were interested in a Fw Component for installing the FSM from the System Config DB. ATLAS is interested and the other two need to consider this further. Clara noted that a FSM hierarchy display widegt is now available with the FSM Component. Manuel reported on the follow up of point 3 of the last FWWG minutes, the config file option to make the OPC client set the invalid bit is mapInvalidAdressToDrvInvalidBit (including the spelling mistake!). He tried it but it didn't seem to work. He is waiting for an answer from ETM.