1. Partner Logo Olof Bärring, WP4 workshop 10/12/2002 - n° 1 (My) Vision of where we are going WP4 workshop, 10/12/2002 Olof Bärring

2. Olof Bärring, WP4 workshop 10/12/2002 - n° 2 Outline u Fabric automation architecture u Today and tomorrow subsystem by subsystem u Important steps towards tomorrow u How to use this workshop

3. Olof Bärring, WP4 workshop 10/12/2002 - n° 3 Automation Architecture PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Software repository Authorisation

4. Olof Bärring, WP4 workshop 10/12/2002 - n° 4 Today Software repository PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Authorisation

5. Olof Bärring, WP4 workshop 10/12/2002 - n° 5 Configuration: Today Node profile Configuration Database Node profile Configuration Database Abra-cadabra Hocus-pocus HLDL template CDB API PAN PC

6. Olof Bärring, WP4 workshop 10/12/2002 - n° 6 Configuration: … and tomorrow (February) Node profile Configuration Database Node profile Configuration Database Abra-cadabra Hocus-pocus HLDL template CDB API PAN Cache Node profile NVA API PC

7. Olof Bärring, WP4 workshop 10/12/2002 - n° 7 PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Software repository Authorisation

8. Olof Bärring, WP4 workshop 10/12/2002 - n° 8 Monitoring: Today Monitoring repository FlatFile DB Agent Repository server Repository API PC Transport Sensor

9. Olof Bärring, WP4 workshop 10/12/2002 - n° 9 Monitoring: … and tomorrow (March) Monitoring repository Agent Repository server Repository API Transport SQL DB Alarm GUI PC Node profile Sensor Monitoring Component

10. Olof Bärring, WP4 workshop 10/12/2002 - n° 10 PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Software repository Authorisation

11. Olof Bärring, WP4 workshop 10/12/2002 - n° 11 Fault tolerance: Today Fault Tolerance Rule Editor Correlation Engine Rule XML Monitoring API PC Actuator

12. Olof Bärring, WP4 workshop 10/12/2002 - n° 12 Fault tolerance: … and tomorrow (summer???) Fault Tolerance Rule Editor Correlation Engine Rule HLDL Node profile Monitoring API PC CDB Job scheduling Actuator FT Component ???

13. Olof Bärring, WP4 workshop 10/12/2002 - n° 13 PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Software repository Authorisation

14. Olof Bärring, WP4 workshop 10/12/2002 - n° 14 Installation&Maintenance: Today PC RPM Software repository RPM Component.def/.h Component LCFGng

15. Olof Bärring, WP4 workshop 10/12/2002 - n° 15 Installation&Maintenance: … and tomorrow (April) PC RPM Software repository RPM Cache Node profile Component cdispd SPM Component SPM rpmtpkgt??

16. Olof Bärring, WP4 workshop 10/12/2002 - n° 16 PC RPM Node profile Fault Tolerance Job scheduling Configuration Database Monitoring repository Software repository Authorisation

17. Olof Bärring, WP4 workshop 10/12/2002 - n° 17 Resource mgmt Today Job scheduling Scheduler Runtime Control PBS Admin API

18. Olof Bärring, WP4 workshop 10/12/2002 - n° 18 Resource mgmt … and tomorrow (spring??) Job scheduling Scheduler Runtime Control PBS Admin API LSF RMS Component Node profile Monitoring??

19. Olof Bärring, WP4 workshop 10/12/2002 - n° 19 Important steps towards tomorrow u WP4 subsystems need to be n Configured n Monitored n Repaired

20. Olof Bärring, WP4 workshop 10/12/2002 - n° 20 Important steps towards tomorrow (1) u WP4 subsystem needs to be configured n Identify what potentially needs to be (re)configured n Define your configuration parameters and how they should fit into the global schema n Write HLDL templates for your subsystem (learn from exercises this week) n Write “configuration components” that calls the NVA API and generates configuration files for your services

21. Olof Bärring, WP4 workshop 10/12/2002 - n° 21 Important steps towards tomorrow (2) u WP4 subsystem needs to be monitored n Identify what can go wrong  define the subsystem health metrics n Implement a sensor that measures the health metrics n Configure the monitoring subsystem to become aware of your sensor/metrics. How is this done best? s Keep the configuration together with your subsystem and “link” it to the monitoring? s Or should the configuration be added directly to the monitoring HLDL template?

22. Olof Bärring, WP4 workshop 10/12/2002 - n° 22 Important steps towards tomorrow (3) u WP4 subsystem needs to recover from unhealthy states n Determine how to recover the subsystem from the identified set of unhealthy states n Implement actuator scripts that performs the repairs n Define the rule that links your health metrics to your recovery actuator

23. Olof Bärring, WP4 workshop 10/12/2002 - n° 23 Important steps towards tomorrow (3) u WP4 subsystem needs to recover from unhealthy states n Determine how to recover the subsystem from the identified set of unhealthy states n Implement actuator scripts that performs the repairs n Define the rule that links your health metrics to your recovery actuator

24. Olof Bärring, WP4 workshop 10/12/2002 - n° 24 Open issues (to think over during the exercises) u Who launches the recovery actuator scripts? I see two cases: n Repair that do not involve a configuration change, e.g. restart daemon; clean /tmp; n Repair that do involve a configuration change, e.g. service client reconfiguration when a central service falls over u Desired state versus actual state duality: how to enter a reference to the desired state in a FT rule? n FT rules naturally reference actual state through monitoring metrics. How can the same be done for the desired state?

25. Olof Bärring, WP4 workshop 10/12/2002 - n° 25 How to use this workshop u The objective for this workshop to facilitate the integration of WP4 subsystems. It is not for you to show how nice your software is written and how well your task has been working, so n Teachers: please make sure to focus your exercises on important interfaces and how to use them. Leave out cool features unless the time allows for it n Participants: use the exercises to understand how to interface your subsystem. Identify potential problems with the interfaces from your subsystem point of view. Save those issues for the Friday brainstorming session u In the brainstorm in Friday: discuss possible open issues or problems identified during the hands-on exercises.