150 likes | 163 Views
Resilience through Dynamic Reconfigurations in Agent Systems. Ilya Lopatkin Newcastle University, School of Computing Science. Multi- A gent S ystem (MAS) . Resource. Active agents Resources Communication. Agent. Agent. Agent. Agent. Resource. Multi- A gent S ystem (MAS) . Agent.
E N D
Resilience through Dynamic Reconfigurations in Agent Systems Ilya Lopatkin Newcastle University, School of Computing Science
Multi-Agent System (MAS) Resource Active agents Resources Communication Agent Agent Agent Agent Resource
Multi-Agent System (MAS) Agent Active agents Passive agents Communication Agent Agent Agent Agent Agent
Threats and reconfiguration in MAS • Agent is unavailable • Abnormal behaviour • Disconnection • Inadequate quality of data • Inadequate QoS • Lack of required characteristics Agent Agent Agent ? ? Agent Agent Agent ? Questions concerned: • how to find appropriate components to use after failures? • which of them to choose?
The place of the search mechanism in FT Error detection Damage confinement and assessment Fault treatment and continued service Error recovery Search mechanism * T. Anderson, P. A. Lee. Fault Tolerance: Principles and Practice. Prentice Hall, London, 1981
Scope of work Error detection Reconfiguration Search • Location addresses • Request List of locations Searcher Criteria
CAMA abstractions Device Device Platform Agent Location Middleware Platform Agent Middleware Agent Middleware
Evaluation of locations Location Agent evaluates Searcher produces Value* * G. Di Marzo Serugendo, J. Fitzgerald, A. Romanovsky, and N. Guelfi. A Metadata-Based Architectural Model for Dynamically Resilient Systems. In 22nd ACM Symposium on Applied Computing, Seoul, Korea, March 11-15, 2007. pp 566-573. ACM, 2007.
Sharing values among agents Criterion uses uses Agent B Agent A saves to reads from uses evaluates Value A2 Value A2 Location 1 Location 2
Aggregating values Value PQ2 Value Q2 contains Location 1 aggregates into reads Q2 Agent A Location 2 saves PQ2 readsP2 Value P2 contains Location 3
Criteria • Application-specific • Evaluate, aggregate, and compare values • May include any resilience criterion Examples: • Availability. Value: estimated time per week/month/year • Connection properties, latency. Value: average time in ms • Number of failures. Value: integer • Quality of service. Value: some complex structure
Threats and reconfiguration in MAS meta-data • Agent is unavailable • Abnormal behaviour • Disconnection • Inadequate quality of data • Inadequate quality of service • Lack of required characteristics Agent Agent Agent ? ? Agent Agent Agent ? Questions concerned: • how to find appropriate components to use after failures? • which of them to choose? meta-data
Advantages • Works for any type of components • Leads to <reconfiguration type you've just remembered> • Any resilience criteria • Autonomous agents • High scalability
Problems • First wave of agents • Too many locations • Lack of values • Different treatment of the same values • Need for a general ontology to represent values • Hidden stigmergy may lead to unpredictable behaviour