1. Rainbow Facilitating Restorative Functionality Within Distributed Autonomic Systems Philip Miseldine, Prof. Taleb-Bendiab Liverpool John Moores University

2. Scope of Talk Introduction to Rainbow What is Rainbow? The research motivation What can it do? Introduce Neptune and Clouds The technologies that underpin Rainbow Conclude with a demo of Rainbow

3. Motivation Self Regenerative Systems Self-awareness Restorative Qualities Detect detrimental system behaviour Actively remove vulnerability Adaptive Infrastructure Sensor / Instrument monitoring

4. Motivation What exists nowadays? Dynamic AOP Runtime Dynamism BDI Agent Models Generative Software Paradigms...Complete System Backup :)

5. Motivation Neptune RainbowClouds

6. What is Rainbow? Provides the following functionality for autonomous systems: Storage of configuration External analysis of configuration Safe adaptation of configuration Restoration of earlier configurations Think of it as Windows Restore for Autonomic Systems. But smarter!

7. Configuration Data Configuration data encompasses: Rules and policies that underpin the behaviour of an autonomous system. Associations between services of the system. State information of services and agents within the system.

8. What is Rainbow? Rainbow is a service framework Monitoring the underlying system......capturing its logical representation

9. What is Rainbow? These snapshots are centrally stored in an introspective format: allowing analysis and adaptation 3rd party tool access We’ll talk more about the format later! Snapshots can be restored when required, or automatically...

10. A Word on Context We all make choices based on the context of (amongst other things): What we’re being asked to do What the effect of our action will be Both on ourselves And our environment

11. A Word on Context The same is true for autonomous systems: By capturing not just what the system is doing (its configuration) But its operational context too: When we find ourselves back in the original context We have a verified configuration snapshot to use

12. What is Rainbow? Monitoring of the underlying system is two-fold: Analysing when to take snapshots based on intentions Analysing when to reintroduce snapshots based on context

13. What is Rainbow? On system stability: Snapshot taken of configuration Snapshot of context taken On system instability: Context compared against stored snapshots Configuration snapshot restored

14. Neptune An Introspective Language for Describing System Intentions

15. Neptune? A runtime introspective language Allows the inspection and modification of represented logic at runtime without: Recompilation Prior structural knowledge Affecting system performance (no downtime)

16. Neptune? Runtime introspection allows both humans and more importantly, machines to formalise intentions. Software can both write and inspect itself, allowing complete autonomous control over its function, architecture, and deployment configuration.

17. Neptune? Object form allows compiled outputs to be XML serialisable: Neptune Objects can be stored on: Databases Served through SOAP Stored as XML

18. Neptune 101 User or machine provides an intention for the system (a system concept)

19. Neptune 101 For us humans, Neptune Script is a language that enables these intentions to be encoded: define concept Availability as Boolean { if (Instrument[“RoundTripTime”] > 500) { return true; } else { return false; } }

20. Neptune 101 Workflow can also be graphically defined:

21. Neptune 101 For computers, Neptune Script is compiled into object form:

22. Neptune and Rainbow With full autonomous specification of policy and structure defined in Neptune Objects: Simply a case of co-ordinating retrieval and storage of the underpinning objects. This co-ordination is performed by the Cloud Framework...

23. Clouds Distributed, Flexible Architecture Framework

24. Cloud Framework Service Orientated Architecture “a system with loose boundaries which can interact and merge with other such systems” Co-ordination through distributed shared memory Provides instrumentation framework to assess context

25. Cloud Framework Operates through standards SOAP, XML, UDDI, HTTP... Core framework is Cross- platform C#.NET for Windows Cocoa / Objective-C for Mac OS-X Java for everything else! Service Orientated Architecture “a system with loose boundaries which can interact and merge with other such systems” Co-ordination through distributed shared memory Provides instrumentation framework to assess context

26. Cloud Framework Instrumentation (sensors) provided by the Cloud Instrumentation Framework: Use any source as a data provider Database (SQL query) OS-specific Windows (WMI-SQL) Mac OS-X (AppleSense) XML Source

27. Cloud Framework Instruments are typed: Instruments can be defined by: Attribute Method Different resources can use same instrument based on its type Distribution of instruments controlled by their type

28. Cloud and Neptune Hosts Neptune Object Execution And adaptation Provides Neptune with real-time instrumentation Using CIF (Cloud Instrumentation Framework) Provides control methodology based on adaptable, multi-layered policies Using, guess what...Neptune :)

29. CA-SPA The design of Neptune allows for powerful functionality to be built. CA-SPAs componentised form of system policy documentation written in Neptune Using system defined concepts and actions, higher order policies can be built that automatically adapt on changes to the base components

30. CA-SPA A CA-SPA document contains 3 sections that determine its policy role: Situation: A formalisation of a state of a system component. Prediction: A formalisation of the preferred state of a system component. Action: Ontological view of the changes that need to be made to bring about the system change.

31. CA-SPA, Cloud, Neptune

32. Clouds and Rainbow The Cloud provides the control and storage mechanisms for Rainbow Snapshots stored and analysed in Shared Memory Instrumentation provides notion of context CA-SPA policy enables snapshots to be taken upon reaching a situational state. Co-ordination through distributed shared memory Provides instrumentation framework to assess context

33. Rainbow Example E-Commerce Scenario for Rainbow Services

34. AcmeOnline In normal operation, the system is configured to handle x number of customers Rainbow, sensing system stability, takes a snapshot of the configuration.

35. AcmeOnline The approach of Christmas provides many more customers. The system, through the use of CA-SPAs adapts to this new operating context.

36. AcmeOnline After adaptation and evolution, the system becomes stable. Sensing stability, Rainbow takes a snapshot of the system

37. AcmeOnline After Christmas, the system returns to its original customer load. Rainbow, sensing a change of context, reintroduces the original configuration snapshot.

38. Conclusions Benefits: Reaction to change captured System evolution open to analysis Attack the Mess with the Mass With many optimally known configurations, anomalies can be identified.

39. Conclusions In the context of Regenerative Software: Neptune + CIF = Self Awareness Cloud = Co-ordination Rainbow: Restorative Functionality Vulnerability detection

40. Thank You :)