Self-Organizing Architectures SOAR 2010

1. Self-Organizing ArchitecturesSOAR 2010 International Conference on Autonomic Computing and Communication, ICAC Washington DC, USA June 7, 2010

2. Overview • Goals of the workshop • Schedule • Breakout session

3. Goals of the workshop • SOAR 2009 • Goals SOAR 2010

4. Self-Adaptive Systems Community Self-Organizing Architectures Self-Organizing/ Multi-Agent Systems Community

5. SOAR 2009 Analysis Planning Analysis Planning Coordination Coordination Coordination Coordination Local Models Local Models • “The objective of the first SOAR was mainly EXPLORING the middle ground between the self-adaptive and self-organizing perspective • At least we have put the first bricks of the bridge!” Monitoring Executing Monitoring Executing Coordination Coordination Coordination Coordination Application Application

6. Since SOAR 2009 • Book “Self-Organizing Architectures” LNCS vol. 6090 • 13 papers (incl. 4 invited papers) • Self-adaptive approaches; self-organizing approaches; hybrid approaches • Reference model self-adaptive systems (ICAC 2010) • Three perspectives so far: • Reflection perspective • MAPE perspective • Distributed coordination perspective • Formally specified in Z

7. Goals SOAR 2010 • Continue the work on the bridge • To better understand how principles from self-organizing/agent-based systems can be utilized to engineer decentralized self-adaptive systems • To better understand how principles from self-adaptive systems can be utilized in engineering self-organizing/agent-based systems • To explore potential synergy • Combine scalability, robustness, resilience... from self-organizing with separation of concerns, engineering principles, guarentees of system behavior,… from self-adaptation

8. Today’s challenge Hardware elements Software elements Adaptation logic for performance Design a self-organizing architecture for achieving certain objective (e.g. performance improvement, fault tolerance) Node Domain logic (existing system) Network Constraint: only partial knowledge on nodes

9. Schedule • 9:15AM – 10:05AM: Keynote Jeff Kephart • 10:05AM – 11:30AM: Engineering Self-Organizing Architectures • 10:30AM – 11:00AM: BREAK • 11:30AM – 12:30AM: Coordination • 12:30AM – 2:00PM: LUNCH • 2:00PM – 2:50PM: Engineering Self-Organizing Architectures II • 2:50PM – 4:00PM: Breakout sessions • 4:00AM – 4:30AM: BREAK • 4:30AM –5:30AM: Plenary discussion & conclusion

10. Breakout Session

11. Organization • Forming groups • 5 people, preferable different background • 14.50-16.00 Discussions • 16.30-17.30 Plenary Presentations

12. Today’s challenge Hardware elements Software elements Adaptation logic for performance Design a self-organizing architecture for achieving certain objective (e.g. performance improvement, fault tolerance) Node Domain logic (existing system) Network Constraint: only partial knowledge on nodes

13. Guiding questions • What are the elements of your design? • How do you deal with conflicts between the two concerns? • What kind of coordination mechanism(s) have you used? • What kind of information do nodes have to exchange? • What are the guarentees does your solution provides?