1 / 22

Replacement for Current State: Easier Maintenance and Improved Interface

The current state system has been in use for several years but maintenance is becoming increasingly difficult due to older technology. The replacement system offers transparent changes for end users, making it easier to maintain in the long run. It also provides an interface to import previous configurations and access the old state through GUI tools.

mdodson
Download Presentation

Replacement for Current State: Easier Maintenance and Improved Interface

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. Current State - and Replacement Oct. 2008 Kay Kasemir kasemirk@ornl.gov Managed by UT-Battelle for the Department of Energy

  2. Current State Has been in use for several years Works OK, but maintenance increasingly difficult – Installation, dependence on older technology – Maintenance of installed instances 2 Managed by UT-Battelle for the Department of Energy

  3. Replacement Transparent to end users – Except maybe better than before Easier to maintain in the long run Still interface to previous setups – Allow import of previous configurations – GUI tools access old state and replacement 3 Managed by UT-Battelle for the Department of Energy

  4. 4 Managed by UT-Battelle for the Department of Energy

  5. Previous Setup IOC “ASCII” Config. Channel Access Archive Engine config.xml Binary Data Files Data Server History ~2000: Started by Bob Dalesio ~2003: Index Tools, Data Server ~2007: CSS Client XML-RPC CSS-based OPI 5 Managed by UT-Battelle for the Department of Energy

  6. Details Older Java “archive viewer” also available. Archive Engines running on “sampling” computer, data server on “serving” machine. Scripts to restart engines, copy data, update indices. Headaches with data maintenance: – Index time grows with data – Stuck when index files reach 2GB – SNS Users faced with ~80 sub-archives – No clue what needs fixing after network/power problems – No idea who contributes how many samples – No way to remove selected channels or time ranges – Improving on this means implementing an RDB 6 Managed by UT-Battelle for the Department of Energy

  7. New Setup IOC Channel Access ArchiveEngine Samples Config. config.xml RDB Other tools for config & samples EngineConfig -Import (Oracle/MySQL) CSS-based OPI 7 Managed by UT-Battelle for the Department of Energy

  8. RDB Setup Currently supported: MySQL or Oracle – Main table difference: Oracle TIMESTAMP has nanosecs, MySQL has separate nanosecs col. – All tools auto-configure based on JDBC URL Table Schema – ERD, MySQL DBD (in org.csstudio.archive.rdb/dbd) – Setup for Oracle (table types, partitioning) not final 8 Managed by UT-Battelle for the Department of Energy

  9. Configure Sample Engines Configuration is in RDB – Directly use SQL – EngineConfigImport for legacy config files – View/Edit via web Hierarchical: – Sampling engine (name, where to run, …) Groups – Channels No more duplicate channels! 9 Managed by UT-Battelle for the Department of Energy

  10. Web Interface to Engine Config in RDB Tomcat/JSP/Servlets to view and edit 10 Managed by UT-Battelle for the Department of Energy

  11. Web Config View: Channel Stats 11 Managed by UT-Battelle for the Department of Energy

  12. Web Config View: Sample Stats ?? OK 12 Managed by UT-Battelle for the Department of Energy

  13. Run Archive Engine Command-line tool similar to previous engine – More settings (RDB, Logging, JCA/CAJ, …) Compiled-in defaults from “preferences.ini” and “plugin_customization.ini” Can specify overrides via -pluginCustomization my_plugin_customization.ini Mandatory command-line options for instance – engine_name to locate config in RDB – port for consistency, must match settings in RDB Built-in web server for status, restart, stop: http://host:port/: Empty page (used to be ‘main’) …./main: Main page …./reset: Reset statistics …./restart: Stop, re-read configuration, start again …./stop: Stop 13 Managed by UT-Battelle for the Department of Energy

  14. View Data CSS Data Browser: – As before, just different URL jdbc:oracle … Web Config View shows some stats Custom reports based on RDB data 14 Managed by UT-Battelle for the Department of Energy

  15. Report Example, SNS Beam Instr. Group May be SNS-specific, but shows usefulness of data in RDB 15 Managed by UT-Battelle for the Department of Energy

  16. Hurdles Months: Get new Oracle server configured – Interface cards for storage array, fiber switches – Firewall holes for office access, backup, admin Changes in 10g – SELECT MIN(stamp), MAX(stamp) -> NULL, NULL – No “range” partitioning on Index-Organized-Tables Configuration issues – ORA-01654: unable to extend … – ORA-00257: archiver error What used to be impossible is now “easy”, but may still expensive – DELETE FROM SAMPLES WHERE … 16 Managed by UT-Battelle for the Department of Energy

  17. Stats 37 sample engines, 78000 channels Host that runs sampling engine: – CPU load 45%, zero disk I/O wait, very responsive Oracle performance – 8000 samples/sec peak – Sustained maybe ¼ of that Details of Oracle server load, data storage, backups, network access to data: – No longer have to care 17 Managed by UT-Battelle for the Department of Energy

  18. Other Ideas Jlab’s MyA – Operational, but Wrapper code around MySQL to create ‘cluster’ Handles less meta info (units, limits, …) Only ‘monitor’ mode, no ‘scan’ Viewer is one-of C++/TCL/Tk Gabriele Carcassi mentioned RDDTool – Toolset for logging data with data-aging – Command-line RPN tools, web viewer – May be faster than general-purpose RDB but lacks advantage of gpp RDB 18 Managed by UT-Battelle for the Department of Energy

  19. Message to take home All the pieces have been running for a few weeks Looks more sustainable than previous setup .. but not operational, yet Thanks go to – Oracle: Jeff Patton – JSP: Katia Danilova – Beam Instr. Reports: Mariano Padilla, Jeff, Douglas Edwardson – IT: Greg Lawson 19 Managed by UT-Battelle for the Department of Energy

  20. Stuff 20 Managed by UT-Battelle for the Department of Energy

  21. SNS Setup for EngineConfigImport Tool – Imports existing XML config files into RDB – On srv02 in …/imported_config *.xml files copied from archive1, includes some editing to remove duplicate channels Review *.log files – 'chmk/chmkhebt/PPS_HEBT:PLC_B:Chmk100AlarmContactA’ already in 'pps/pps_hebt’ Maybe edit “your” *.xml file, refer to import.sh to re- import 21 Managed by UT-Battelle for the Department of Energy

  22. Getting Sources, Building binaries Get sources from DESY CVS repository – Maybe binaries “real soon” from ChannelArchiver web page Build binaries – Find somebody who understands “Eclipse RCP”, how to use org.csstudio.archive.rdb/EngineConfigImport.product org.csstudio.archive.engine/ArchiveEngine.product org.csstudio.sns.product/SNS_CSS.product (or DESY CSS.product) – Settings Compile-time defaults usually in “preferences.ini” and “plugin_customization.ini” files. Either change, or prepare file for -pluginCustomization command-line option 22 Managed by UT-Battelle for the Department of Energy

More Related