A Negotiation Architecture for Cooperating Components

Slides:

Advertisements

Similar presentations

When Applications can Roam Freely OSGi Service Platform R4 Peter Kriens Technical Director OSGi

Advertisements

Policy based Cloud Services on a VCL platform Karuna P Joshi, Yelena Yesha, Tim Finin, Anupam Joshi University of Maryland, Baltimore County.

Siebel Web Services Siebel Web Services March, From

A Cooperative Approach to Support Software Deployment Using the Software Dock by R. Hall, D. Heimbigner, A. Wolf Sachin Chouksey Ebru Dincel.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 2.

JINI Shashwat Shriparv InfinitySoft.

THE JINI TECHNOLOGY Alessio Zumbo

SmartER Semantic Cloud Sevices Karuna P Joshi University of Maryland, Baltimore County Advisors: Dr. Tim Finin, Dr. Yelena Yesha.

Interactive Systems Technical Design Seminar work: Web Services Janne Ojanaho.

Adding Organizations and Roles as Primitives to the JADE Framework NORMAS’08 Normative Multi Agent Systems, Matteo Baldoni 1, Valerio Genovese 1, Roberto.

1 Quality Objects: Advanced Middleware for Wide Area Distributed Applications Rick Schantz Quality Objects: Advanced Middleware for Large Scale Wide Area.

CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.

Software Engineering and Middleware: a Roadmap by Wolfgang Emmerich Ebru Dincel Sahitya Gupta.

Chapter 13 Physical Architecture Layer Design

Mobile Agents: A Key for Effective Pervasive Computing Roberto Speicys Cardoso & Fabio Kon University of São Paulo - Brazil.

PROGRESS project: Internet-enabled monitoring and control of embedded systems (EES.5413)  Introduction Networked devices make their capabilities known.

Mobile Agent Systems. Mobility Mobile Agents A Mobile Agent is a software agent that exists in a software Environment and can migrate from machine to.

Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:

14/06/ A Data-Model for Context-Aware Deployment of Component-based Applications onto Distributed Systems Dhouha Ayed, Chantal Taconet, and Guy Bernard.

Understanding Networked Applications: A First Course Chapter 16 by David G. Messerschmitt.

QoS-enabled middleware by Saltanat Mashirova. Distributed applications Distributed applications have distinctly different characteristics than conventional.

STRATEGIES INVOLVED IN REMOTE COMPUTATION

A Cloud is a type of parallel and distributed system consisting of a collection of inter- connected and virtualized computers that are dynamically provisioned.

Interoperating with Services in a Mobile Environment Andreas Dahl, Pål Rolfsen Grønsund, Per Thomas Kraabøl,

Enterprise Java Beans Java for the Enterprise Server-based platform for Enterprise Applications Designed for “medium-to-large scale business, enterprise-wide.

ASG - Towards the Adaptive Semantic Services Enterprise Harald Meyer WWW Service Composition with Semantic Web Services

SelfCon Foil no 1 Self configurating systems - a starter Rolv Bræk, Item.

Slide 1 Physical Architecture Layer Design Chapter 13.

1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.

1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.

A semi autonomic infrastructure to manage non functional properties of a service Pierre de Leusse Panos Periorellis Paul Watson Theo Dimitrakos UK e-Science.

INTERNET AND ADHOC SERVICE DISCOVERY BY: NEHA CHAUDHARY.

Future Directions in Middleware Research and Technology Fabio Kon Department of Computer Science University of São Paulo, Brazil

Hwajung Lee.  Interprocess Communication (IPC) is at the heart of distributed computing.  Processes and Threads  Process is the execution of a program.

Presented By:- Sudipta Dhara Roll Table of Content Table of Content 1.Introduction 2.How it evolved 3.Need of Middleware 4.Middleware Basic 5.Categories.

Common Object Request Broker Architecture (CORBA) The Common Object Request Broker Architecture (CORBA) is a specification of a standard architecture for.

Jini Architecture Introduction System Overview An Example.

Kemal Baykal Rasim Ismayilov

CONTENT 1.Software Process 2.Object Technology 3.UML 4.UML For Java.

Jini Architectural Overview Li Ping

1 BBN Technologies Quality Objects (QuO): Adaptive Management and Control Middleware for End-to-End QoS Craig Rodrigues, Joseph P. Loyall, Richard E. Schantz.

Notes from Coulouris 5Ed Distributed Systems Notes on Components.

XML: The Three Revolutions

Clouding with Microsoft Azure

The Post Windows Operating System

Web-based Software Development - An introduction

Chapter 12: Architecture

Chapter 6: Securing the Cloud

Autonomic Resource Virtualization in Cloud-like Environments A

IBM Tivoli Provisioning Manager Red Hat 5 patch management

Globus —— Toolkits for Grid Computing

Service Oriented Architecture

Systems Analysis and Design With UML 2

University of Technology

Introduction to Operating Systems

Policy based Cloud Services on a VCL platform

20409A 7: Installing and Configuring System Center 2012 R2 Virtual Machine Manager Module 7 Installing and Configuring System Center 2012 R2 Virtual.

Chapter 12: Physical Architecture Layer Design

Unit V Mobile Middleware.

MWCN`03 Singapore 28 October 2003

JINI ICS 243F- Distributed Systems Middleware, Spring 2001

Quality Assurance for Component-Based Software Development

COMPONENTS – WHY? Object-oriented source-level re-use of code requires same source code language. Object-oriented source-level re-use may require understanding.

Seminarium on Component-based Software Engineering

Self-Managed Systems: an Architectural Challenge

From Use Cases to Implementation

EKSE: A Command Line Interface for EGS-CC based Systems

Presentation transcript:

A Negotiation Architecture for Cooperating Components Endeavor A Negotiation Architecture for Cooperating Components R. Wilensky

Problem Individual computing components currently require lots of manual configuration: OS, software installation Local data (solved by oceanic storage!) Configuration to access services Even now, with each of us having a small number of machines, (manual) configuration is a problem. State (software/data) is inconsistent across machines. Manual updating is time-consuming. Degrades poorly in the presence of failure/change. With several orders of magnitude more machines per individual, manual configuration will be completely infeasible.

Solution: Negotiation Architecture for Auto-Configuration Allow components to dynamically configure themselves by having components. specify the potential services they provide, the terms and conditions, and to whom disseminate the availability of these services specify the services they require, and their terms and conditions discover other objects that provide required services allow objects to enter into multi-phase negotiations of contracts, committing to provide services under terms and conditions provide compliance monitoring services of contracts provide means for dealing with non-performing confederates

What’s Out There Now Various pieces of object-oriented middleware systems CORBA Java and JavaBeans Lots of agent-negotiation work JINI NINJA service discovery service

What We Will Do Develop a language for specifying services, and their terms and conditions a protocol for negotiating contracts between objects infrastructural services, including discovery, service availability dissemination, and compliance monitoring services means to adapt to a non-performing service Emphasis on system architecture, and easy of use. E.g., standard, parameterized “boilerplate” contracts between components, with standard “compliance officers” Some related issues: Can we assure interesting adaptive properties?

How this relates to other work I am doing DLIB project has potential connections to other aspects of Endeavor. CONTROL, GiST MVD configurable client