Hi Abishek, Thank you for your proposal and sharing the slides. I think having such a component is a valuable addition. Some questions popped into my mind when reading the slides:
1. How would you compare your Health Manager to GENIVI's Diagnostic Log and Trace (DLT) [1]? What are the commonalities, what are the differences? DLT aims to be Autosar 4.0 compliant. Is that a goal for the HM too? 2. Since you are building on dbus and systemd, have you considered journald as logging mechanism? I think it would be beneficial having all system logs in one database. 3. What security mechanisms are you putting in place to protect the logs? 4. What mechanisms is HM providing for remote access to the logs? 5. The block diagram includes a box labeled "Automotive Peripheral Framework (CAN/LIN/MOST)". Are you intending to use the Automotive Message Broker (AMB) of Tizen IVI for that functionality? 6. When you are referring to "services" that the HM monitors are these daemons and processes that are managed using systemd? 7. Can any service be monitored by HM or does a service have to be prepped for that? The block diagram seems to suggest that the services have to implement specific APIs and expose them via the Session DBus. Thanks, Rudi [1] http://projects.genivi.org/diagnostic-log-trace/ On Mon, Apr 14, 2014 at 10:30 PM, Abhishek Sharma <[email protected]>wrote: > Dear All, > > > > We would like to propose a new component called System Health Manager for > Tizen IVI. > It is imperative that automotive platform should provide a means to monitor > critical services and take corrective action whenever a failure or deviation > from expected services is detected. > In that respect, the proposed > Health Manager (HM) shall seamlessly integrate with Tizen IVI for providing a > limited fault-tolerance capability. Attached > please find the presentation slides which describe overall functioning and > features of the proposed HM. We request you to provide your > comments/feedback on our proposal, and ways for taking this initiative > forward. > > > > > The key features of the proposed HM include detecting disruption of services, > logging data required for diagnosis and applying directed recovery > strategies.The proposed HM uses > *systemd * > interfaces and signals to monitor configured critical services and recover > them, if failed. > > > > The initial development is undergoing and can be released at tizen.orgfor > open source contributions following the feedback and internal due > process for releasing the code. At the moment, we have basic structure > for HM core, Dbus Communication and Fault-database. We have also designed a > placeholder for dummy recovery client at the moment. Going forward this > needs to be developed as per system requirements. > > > > Looking forward to your suggestions, feedback and active contributions of > this feature on tizen.org for IVI profile. > > > > Regards > > Abhishek > > > > > > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > > -- -- *Rudolf J. Streif* Director of Embedded Solutions The Linux Foundation [email protected] Phone: +1.619.537.6646 Skype: rudolfstreif PGP: RSA 2048/2048 9B4634F239284B24 Linux Foundation Events Schedule: events.linuxfoundation.org Linux Foundation Training Schedule: training.linuxfoundation.org
<<inline: 201404151100980_QKNMBDIF.gif>>
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
