Jun 15, 2004 - software/service starting, stopping, deleting, upgrading or configuration. â« tracing, maintenance of several software versions, selective or.
Department of Telecommunications
Mobile Agent-based Software Management in Grid Gordan Jezic, Mario Kusek, Tomislav Marenic, and Ignac Lovrek Department of Telecommunications Faculty of Electrical Engineering and Computing University of Zagreb, Croatia Sasa Desic and Bjorn Dellas Research and Development Center Ericsson Nikola Tesla Krapinska 45, HR-10000 Zagreb, Croatia
Workshop on Emerging Technologies for Next Generation GRID (ETNGRID-2004) June 14-16, 2004, University of Modena and Reggio Emilia, Italy
Outline Department of Telecommunications
♦ ♦
Motivation Remote Maintenance Shell Concept Architecture Prototype
♦
Case Study Software
Upgrade Advanced Version Handling ♦
Conclusion
ETNGRID 2004
June 15, 2004
2 of 18
Motivation Department of Telecommunications
♦
Large distributed systems Software
is distributed over a wide area network Software is shared across the dynamic, heterogeneous, and geographically dispersed networks Many nodes Different versions of software Software malfunctions System in operation ♦
Software flexibility
♦
Goal: Remote software management
ETNGRID 2004
June 15, 2004
3 of 18
GRID Department of Telecommunications
♦ ♦
Large-scale distributed software system Open Grid Service Architecture
Grid service integrates distributed resources service discovery dynamic creation manageability and upgradeability
♦
Dynamic management of new services
ETNGRID 2004
software/service starting, stopping, deleting, upgrading or configuration tracing, maintenance of several software versions, selective or parallel execution, version replacement
June 15, 2004
4 of 18
Requirements Department of Telecommunications
♦ ♦ ♦ ♦
Independent upgrade Without disrupting regular operations Simultaneous management of multiple nodes Execution control starting
♦ ♦
and stopping at will
Software testing and tracing remotely An administrator should not be physically present at the location of the managed node
ETNGRID 2004
June 15, 2004
5 of 18
RMS System Department of Telecommunications
♦
Remote Maintenance Shell (RMS) agent
based system perform software management remotely on target systems without suspending or influencing regular operation of the current service "in work" protected environment software installation software upgrading software testing software maintenance ETNGRID 2004
June 15, 2004
6 of 18
Agent benefits Department of Telecommunications
♦
Complete decentralization of operation execution there
is no need to keep open connections and communicate with potentially many remote systems simultaneously
♦
Increased asynchrony
♦
user is disconnected from the network
Reduction of sensibility to network latency there
♦
is no interactions during software management
Flexible configuration of remote testing procedures it
ETNGRID 2004
is possible to dynamically reconfigure agent operation June 15, 2004
7 of 18
RMS Concept Department of Telecommunications
• Distributed system consisting of two main components – RMS Console – Maintenance Environment (RMS Core)
Agent platform
Software Software testbed
Software Software testbed
Network
RMS Console
Agent platform
Management station
ETNGRID 2004
Maintenance Environment
Remote system
June 15, 2004
8 of 18
RMS Advantages Department of Telecommunications
♦ ♦
Testing and tracing of software on the actual target system where it must be deployed Provides three execution modes suitable for introducing new service or upgrading the existing one without stopping the system Normal
execution of a defined version of the software Selective
and Parallel
requires two versions Application Testbed enables resource sharing between versions ETNGRID 2004
June 15, 2004
9 of 18
Parallel mode Department of Telecommunications
♦ ♦ ♦ ♦
Execution of two versions in parallel way Both versions are executed with the same inputs One version is designated as the main version Direct comparison of two versions Service
Service
Version 1 Version 2
Version 1 Version 2
100%
100%
ServiceTestbed
ETNGRID 2004
Service Testbed
June 15, 2004
10 of 18
Selective mode Department of Telecommunications
♦ ♦ ♦
Execution of two versions Requests are distributed according to predefined percentages Gradual introduction of new version Service
Service
Version 1 Version 2
Version 1 Version 2
n%
(100-n)%
Service Testbed
ETNGRID 2004
Service Testbed
June 15, 2004
11 of 18
RMS Architecture Department of Telecommunications
♦
Multi-agent system, three groups of agents:
Console agents - master agent Multi-operation agents - team agents ME agents Console agents ME agents Service
MultiOperation Agents
Agent Platform
Service Testbed
RMS console
Management station
ETNGRID 2004
Universal mobile agents Maintenance Environment
Network Agent Platform
Remote System
June 15, 2004
12 of 18
RMS Prototype Department of Telecommunications
♦ ♦ ♦
Support for managing multiple remote systems at the same time RMS user defines only the desired final state GUI support Presentation
of differences between the current and the desired state of the remote systems Interactive tracking of operation execution ♦ ♦
Support for complex software installation procedures Installation of a large software
ETNGRID 2004
June 15, 2004
13 of 18
Case Study Department of Telecommunications
♦ ♦
Management of distributed software in Grid MonALISA software software
for monitoring large distributed systems employed in the test Grid environments in CERN ♦
Grid environment: three simple HEs the
♦ ♦
same user application
Mechanisms for introduction of new software and software upgrading Scenarios for gradual release of software into full operation
ETNGRID 2004
June 15, 2004
14 of 18
Scenario: Software Upgrade Department of Telecommunications
♦
Desired end state: new software starting delivering
of software to HEs MC agent generates necessary operations MC agent establishes interpendencies between operations operations include: software migration, testbed migration, installation, setting execution parameters, starting ♦
Desired end state: software upgrading delivering
and installation a newer version to HEs operations include: new software migration, new software installation, old software stopping, setting execution parameters, new software starting ETNGRID 2004
June 15, 2004
15 of 18
Agent Distribution Department of Telecommunications
♦
RMS ME Agent2 Agent1
♦
HE1 Agent1 Agent2
Agent3
RMS ME Agent3 Agent1 HE2
Agent4 RMS Console Management Station
♦
Multi-operation agents are created as a team Separate agent migrates the software on all servers Separate agents perform the operations for one remote server
RMS ME Agent4 Agent1 HE3
ETNGRID 2004
June 15, 2004
16 of 18
Advanced Version Handling Department of Telecommunications
♦ ♦ ♦ ♦
Support for gradual introduction of a newer version Parallel and selective modes combined Without stronger influence on regular operations Version replacement steps: parallel
mode of new and old versions (new version verification) selective mode with low probability for a new software (checking of new service behavior in real env.) increasing of execution probability for new service gradually finally, complete load turn to new service ETNGRID 2004
June 15, 2004
17 of 18
Conclusion Department of Telecommunications
♦ ♦ ♦
Framework for software management in the large distributed systems Software delivery, control upgrading and testing Method is based on cooperative mobile agents master
agent team of agents ♦ ♦ ♦
Case study of Grid service upgrading MonALISA software Future work: additional RMS management features
ETNGRID 2004
June 15, 2004
18 of 18
