100 likes | 304 Views
Post Mortem Prototyping G.Kruk. Post Mortem (Data transfer - initial idea). PM Data sent from systems to the PM Server in a binary format over CMW PM Server receives the data and saves it on the file system (as it comes)
E N D
Post Mortem (Data transfer - initial idea) • PM Data sent from systems to the PM Server in a binary format over CMW • PM Server receives the data and saves it on the file system (as it comes) • Once the data is safe (and saved) another process converts the binary files into the final format (accessible for analysis tools)
Post Mortem (Data transfer - initial idea) PM analysis tools ASCII files Binary files PM server PM Server (CMW) Binary data sent over CMW CMW Systems Browser Other analysis tools QPS PIC PC
Post Mortem (Status) • Prototype of CMW server implemented (S.Pasinelli) • Tested successfully from PC (S.Page + S.Pasinelli) (there is still a CMW threading problem but hopefully will be solved soon) • Binary data / metadata successfully transferred (plus conversion to the “Rosali” format)(G.Kruk) • Prototype of a generic PM Browser in place (G.Kruk)
Post Mortem (Status) Conversion to an ASCII format + analysis tools G.Kruk PM Server S.Pasinelli PM Server (CMW) Data transfer CMW S.Page Browser Other analysis tools QPS PIC PC
Post Mortem PM analysis tools ASCII files Binary files PM server PM Server (CMW) Binary data sent over CMW CMW PM Client PM Client PM Client Systems Browser Other analysis tools PIC QPS PC Lynx OS Lynx OS (FESA) Linux
Post Mortem (PM Client) PM Client functionality: • Wrapper to CMW client used by systems to send the PM data • Takes care of re-sending data in case of communication problems • Possibly saves data locally* in case of unsuccessful transfer or even before sending the data - What to do in a diskless system? • Possibly checks availability of the PM server (heart beat) • Possibly sends alarms to the Laser system in case of problems
Post Mortem (PM Client) Advantages of having the PM Client: • Decreases work which probably would have to be repeated in all systems • Simplifies and decreases testing (one code instead of several) • Takes care of correct formatting data sent to the server (all required fields, etc.) and decreases a risk that the server will receive unexpected data • If for some reason there is a need to modify the interface (protocol, data formatting, …) it will be modified (and tested) only once in the Client code instead of asking each system to adapt their code. • …
Post Mortem (Issues + further work) • Implementation of the PM Client => seems as a good idea - Who does this? • Implementation of the PM Server => proto is done - (Who does the operational version? => extension of the existing prototype) • Data transfer over CMW • Define configurations and descriptors of the PM data sent by all involved systems (used to convert binary to ASCII files and possibly used by analysis tools) • Select the data that should be stored permanently (in a database) and • Write an appropriate application which will do it • Move the PM Server to an operational machine and provide space and directory structure
Post Mortem (Conclusions) • We have proposed a solution for the transfer and storage of the PM data • We have implemented a prototype of PM Server, conversion to an ASCII format and a prototype of a PM Browser • We have performed initial tests (using PC) of proposed solution (without the client API) • The main technical issues (PM client, server, CMW) must be resolved asap