1 / 23

Deployment of Distributed Multi-Agent Systems

Deployment of Distributed Multi-Agent Systems. Alexander Pokahr Karl-Heinz Krempels Lars Braubach Winfried Lamersdorf Presentation: Dirk Bade University of Hamburg. Outline. Motivation What can be learned from OO-Deployment ? Requirements Deployment Reference Model

sawyer
Download Presentation

Deployment of Distributed Multi-Agent Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deployment of Distributed Multi-Agent Systems Alexander PokahrKarl-Heinz KrempelsLars Braubach Winfried Lamersdorf Presentation: Dirk Bade University of Hamburg

  2. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  3. Observation (1) • The agent-metaphor is … • useful for modeling & building complex applications • making complexity manageable at a conceptual level • seen as natural successor of the OOP • Agent-applications have already been developed for various domains, but … Why aren‘t agent applications widely used ?

  4. Observation (2) • Development of MAS is … • quite difficult and error-prone • not based on generally accepted methodologies • poorly supported by tools • Deployment of MAS is … • difficult because of software‘s dynamic & distributed nature • not supported by systematical guidelines • Our approach: • specify agent-applications at a high levelusing constraints to declare system-properties,that have to be fulfilled for the application to work properly

  5. Observation Implication • Constraints • e.g. demand certain agent-roles or services to be available • interpreted & supervised by deployment environment • High level deployment achieved through … • reference model for launching distributedmulti-agent applications • specifies which, how many and in what orderagent instances shall be launched • includes generic meta-model consisting of 2 layers • definition of agent-types • ordered composition of agent-instances • applied to a prototype deployment manager

  6. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  7. OO-Deployment • Object Management Group, Deployment: "The processes between acquisition of software and the execution of software" The deployment process phases • installation • functional configuration • creation of a deployment plan • preparation phase • launching and runtime configuration

  8. Learnt from OO-Deployment (1) • Deployment of agent-based applications is similiar, but more dynamic and flexible • installation • infrastructure- & application specific agent software • functional configuration • adjust agent start-parameters & tune number of agents • deployment plan + preparation phase • placement of infrastructure- & application-code on nodes • launching and runtime configuration • differs to a great extent …

  9. Learnt from OO-Deployment (2) • Launching & runtime configuration • Properties of OO-applications • hierarchical structure • usually launched using a single starting point • Properties of agent-based applications • bundle of autonomous, self-dependent actors • more abstract launching-concept necessary Directly related: • Monitoring & dynamic reconfiguration

  10. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  11. Requirements for Launching and Configuring MAS (1) • Terms: • agent type vs. agent instance • type: static implementation parts • instance: concrete description of an agent • society type vs. society instance • type: static application properties composition of agent types + constraints • instance: special application configuration composition of agent instances + constraints

  12. Requirements for Launching and Configuring MAS (2) • Basic Management Services: • starting/stopping of agent- and society instances • on local platform by local platform management • on remote platforms by requests to remote service-agents delegate startup of remote subordinated agents local agents started by local platform delegate startup of remote agents initiating node node running an agent-platform and service-agent

  13. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  14. Deployment Reference Model (1)

  15. Deployment Reference Model (2) • Launching, monitoring & reconfiguration-services are based on specification of agents & societies. The AgentType-model <agent name="Host“ package="examples.party“ class="HostAgent“ type="jade"> <parameter name="guestsToWaitFor“ type="String“ optional="false"> <value> 5 </value> </parameter>

  16. Deployment Reference Model (3) The SocietyType-model <society name="PartySociety" package="examples.party“> <imports> <import>examples.partyservice</import> </imports> <agenttypes> <agenttype name="examples.party.Guest"/> </agenttypes> <societyinstanceref name="MySubSociety" societytype="PartySociety“ societyinstance="Female Guestpool"> <launcher name="ascml@vsispro3:1099/JADE"> <address> http://134.100.11.53:80 </address> </launcher> </societyinstanceref> <societyinstance name="Small Party"> <agentinstance name="PartyHost" type="Host"> <parametervalue name="guestsToWaitFor"> 10 </parametervalue> <tooloption type="debug">true</tooloption> </agentinstance> <agentinstance name="Guest_1" type="Guest"/>

  17. Deployment Reference Model (4) The Dependency-model <dependency active=“true”> <agentinstance name="PartyHost"> <provider name="ascml@MyComputer:1099/JADE"> <address> http://192.168.1.2:7778 </address> […]

  18. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  19. Prototype Implementation (1) • ASCML service-agent • self-contained component • standardized interface  easy porting to other FIPA-compliant platforms

  20. Prototype Implementation (2) • Currently implemented for JADE- and Jadex platforms • Currently used & tested by the DFG priority research program SPP 1083 • publicly available at the beginning of 2005 ?

  21. Outline • Motivation • What can be learned from OO-Deployment ? • Requirements • Deployment Reference Model • Prototype Implementation • Conclusion

  22. Conclusion and Outlook • Agent application deployment should be better supported • esp. configuration and launching issues • concepts besides agents are needed (e.g. the notion of an agent application or society) • ASCML as a first approach • Combination with organisational approaches (AGR-Ferber, AUML-Odell)

  23. Questions ? ? ? ? ? ? ? ? ? ??? ? ? ? ? ? ? ?

More Related