Welcome to DEAS 2005 Design and Evolution of Autonomic Application Software David Garlan, CMU Marin Litoiu, IBM CAS Hausi A. Müller, UVic John Mylopoulos,

Slides:



Advertisements
Similar presentations
Tivoli Software from IBM Storage Resource Management Webcast
Advertisements

Manage your technology for optimal return on investment (ROI) The Tivoli ® Configuration & Operations management solution from IBM.
Protecting Software Code By Guards - by Hoi Chang and Mikhail J. Atallah “Many software-based mechanisms for protecting program code are too weak[…] or.
Self-Managing Anycast Routing for DNS
KAIS T The Vision of Autonomic Computing Jeffrey O. Kephart, David M Chess IBM Watson research Center IEEE Computer, Jan 발표자 : 이승학.
Autonomic Systems Justin Moles, Winter 2006 Security in an Autonomic Computing Environment Paper by: D. M. Chess, C. C. Palmer S. R. White Presentation.
Fabián E. Bustamante, Winter 2006 Autonomic Computing The vision of autonomic computing, J. Kephart and D. Chess, IEEE Computer, Jan Also - A.G.
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA Dennis Smith, David Carney and Ed Morris DEAS.
May 12, 2015IEEE Network Management Symposium Page-1 Requirements for Configuration Management of IP-based Networks Luis A. Sanchez Chief Technology Officer,
Cloud Computing Part #3 Zigmunds Buliņš, Mg. sc. ing 1.
Yingping Huang and Gregory Madey University of Notre Dame A W S utonomic eb-based imulation Presented by Tariq M. King Published by the IEEE Computer Society.
Autonomic DBMSs: System Tune Thyself! Pat Martin Database Systems Laboratory School of Computing Supported by IBM, CITO and NSERC.
A Game-theoretic Approach to the Design of Self-Protection and Self-Healing Mechanisms in Autonomic Computing Systems Birendra Mishra Anderson School of.
1 Sensor Networks and Networked Societies of Artifacts Jose Rolim University of Geneva.
Improving Software Quality with Generic Autonomics Support Richard Anthony The University of Greenwich.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Autonomic Computing Shafay Shamail Malik Jahan Khan.
Managing IT with Tivoli. 2 Tivoli Value Proposition - Customer need driven Deliver higher availability, performance, security, asset utilization Manage.
“Autonomic Computer Systems and their potential application to Road Network Management” Lee McCluskey Dept of Informatics.
Introduction to the new mainframe: Large-Scale Commercial Computing © Copyright IBM Corp., All rights reserved. Chapter 8: Autonomic computing.
(Slides are taken from the presentations by Alan Ganek, Alfred Spector, Jeff Kephart of IBM)
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
Cloud Usability Framework
Demonstrating IT Relevance to Business Aligning IT and Business Goals with On Demand Automation Solutions Robert LeBlanc General Manager Tivoli Software.
Trends & Challenges Systems Supporting M-Commerce Nour El Kadri University of Ottawa.
Self-Adaptive QoS Guarantees and Optimization in Clouds Jim (Zhanwen) Li (Carleton University) Murray Woodside (Carleton University) John Chinneck (Carleton.
Rainbow Facilitating Restorative Functionality Within Distributed Autonomic Systems Philip Miseldine, Prof. Taleb-Bendiab Liverpool John Moores University.
1 Autonomic Computing An Introduction Guenter Kickinger.
Smart Grid Technologies Damon Dougherty – Industry Manager.
An Approach to Test Autonomic Containers Ronald Stevens (IEEE Computer Society & ACM Student Member) August 1, 2006 REU Sponsored by NSF.
Autonomic Computing Presented By: Renuka Kandimalla( )
1 Panda Malware Radar Discovering hidden threats Channel Presentation Name Date.
WELCOME. AUTONOMIC COMPUTING PRESENTED BY: NIKHIL P S7 IT ROLL NO: 33.
Computer Science Open Research Questions Adversary models –Define/Formalize adversary models Need to incorporate characteristics of new technologies and.
Automating service management Tiina Niklander Faculty of Science Department of Computer Science In AMICT 2008 Petrozavodsk, May 2008.
Action ADAPT / IDM, November 13th, 2008 Dynamic Adaptive Software Components: The MOCAS Approach1.
Distributed Systems: Concepts and Design Chapter 1 Pages
SelfCon Foil no 1 Design of Self-Adaptive Systems Course introduction 2013 Rolv Bræk, ITEM.
A Self-Manageable Infrastructure for Supporting Web-based Simulations Yingping Huang Xiaorong Xiang Gregory Madey Computer Science & Engineering University.
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
What caught your eye at DEAS 2005? 40 DEAS 2005 Participants.
Distributed Database Systems Overview
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
1 ACTIVE FAULT TOLERANT SYSTEM for OPEN DISTRIBUTED COMPUTING (Autonomic and Trusted Computing 2006) Giray Kömürcü.
THE VISION OF AUTONOMIC COMPUTING. WHAT IS AUTONOMIC COMPUTING ? “ Autonomic Computing refers to computing infrastructure that adapts (automatically)
App. TypeApp. Name Distributed or Parallel A parallel version of the Gaussian elimination application SAGE (SAIC's Adaptive Grid Eulerian hydrocode) Adaptive.
A Systematic Survey of Self-Protecting Software Systems
A Self-Configuring Test Harness for Web Applications Jairo Pava School of Computing and Information Sciences Florida International University Courtney.
Enabling Self-management of Component-based High-performance Scientific Applications Hua (Maria) Liu and Manish Parashar The Applied Software Systems Laboratory.
SelfCon Foil no 1 Variability in Self-Adaptive Systems.
The Vision of Autonomic Computing Self-Management Unit 7-2 Managing the Digital Enterprise Kephart, and Chess.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
03/03/051 Performance Engineering of Software and Distributed Systems Research Activities at IIT Bombay Varsha Apte March 3 rd, 2005.
Globus: A Report. Introduction What is Globus? Need for Globus. Goal of Globus Approach used by Globus: –Develop High level tools and basic technologies.
WOSS 04 1 Task-based Self-adaptation David Garlan Bradley Schmerl Joao Sousa Vahe Poladian Carnegie Mellon University WOSS’04.
For More Tutorials ACC 210 WEEK 1 DQ 1  How does information flow between departments at your organizations? Why do some organizations.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
AUTONOMIC COMPUTING B.Akhila Priya 06211A0504. Present-day IT environments are complex, heterogeneous in terms of software and hardware from multiple.
ASPECT ORIENTATED PROGRAMMING RESEARCH
ASPECT ORIENTATED PROGRAMMING RESEARCH
The Vision of Autonomic Computing
Jigar.B.Katariya (08291A0531) E.Mahesh (08291A0542)
Presented By: Darlene Banta
Self-Managed Systems: an Architectural Challenge
Challenges Of Network Security
Presentation transcript:

Welcome to DEAS 2005 Design and Evolution of Autonomic Application Software David Garlan, CMU Marin Litoiu, IBM CAS Hausi A. Müller, UVic John Mylopoulos, UofT Dennis B. Smith, SEI Kenny Wong, UofA

2 Agenda  9:10 – 10:30 Self-healing  David Garlan, CMU  10:30 – 11:00 Nutrition Break  11:00 – 12:30 Applications  Marin Litoiu, IBM  12:30 – 2:00 Lunch Break  2:00 – 3:30 Requirements  Dennis Smith, SEI  3:30 – 4:00 Nutrition Break  4:00 – 5:30 Interoperability  Ken Wong, UofA Sessions 20 mins per talk 1 hours for 3 talks 30 mins discussion break

3 Proceedings  21 papers  131 pages  To appear in ACM Digital Library  Copyright ACM /05/0005  One paper did not make it into the proceedings due to copyright issues, but a copy of the paper is available here  Thank you for submitting the copyright forms   Bookmarks fixed

4 What is Autonomic Computing?  Self-managed systems …  Systems that self-manage  self-configure, self-tune, self-repair, self-protect, self-…

5 What is Autonomic Computing?  Webster’s definition  Acting or occurring involuntarily; automatic: an autonomic reflex  Relating to, affecting, or controlled by the autonomic nervous system or its effects or activity  Autonomic nervous system: that part of the nervous system that governs involuntary body functions like respiration and heart rate  IBM’s definition  An approach to self-managed computing systems with a minimum of human interference  The term derives from the body's autonomic nervous system, which controls key functions without conscious awareness or involvement

6 Most famous Autonomic System

7 Characteristics of Autonomic Computing Systems  Reflexivity, identity  Possesses a system identity  Must know itself  Needs detailed knowledge of its components, current status, interconnections with other systems and available resources to manage itself  Able to configure and reconfigure itself under varying and unpredictable conditions  For example, adaptive algorithms running on each learn the best configurations to deliver functionality in different ways to achieve mandated performance  Continually seek to optimize its operations  Adaptive algorithms for monitoring and execution

8 Characteristics of Autonomic Computing Systems  Able to recover—without loss of data or noticeable delays in processing—from events that might cause some of its parts to malfunction  Recovery mechanisms  At the system and application layer  Human effort supplemented with self-learning algorithms  Capable of protecting themselves  Using pattern recognition to detect and deter threats  Aware of and adaptive to environment and context  Technology independent control theory

9 Characteristics of Autonomic Computing Systems  Able to function in a heterogeneous world based on open standards  Web services, control and data integration; connecting sensors and actuators  Complex heterogeneous infrastructures are a reality  Perform in an environment where computer resources are shared (e.g., in a distributed, grid-like manner)  Carry out various functions and anticipate the resources needed while keeping complexity hidden

10 Characteristics of Autonomic Computing Systems  A software system is autonomic, if it supports behaviors in the following range  Self-configuring — choosing a suitable behaviour, based on user preferences, context, …  Self-tuning — choosing behaviors that optimize certain qualities (performance, year-end profits, …)  Self-repairing — shifting execution to another behaviour, given that the current one is failing  Self-protecting — choosing a behaviour that minimizes risks (attacks, viruses, …)

11 Increased Responsiveness Adapt to dynamically changing environments Business Resiliency Discover, diagnose, and act to prevent disruptions Operational Efficiency Tune resources and balance workloads to maximize use of IT resources Secure Information and Resources Anticipate, detect, identify, and protect against attacks Autonomic computing attributes Self-managing systems that deliver

12  An autonomic manager contains a continuous control loop that monitors activities and takes actions to adjust the system to meet business objectives  Autonomic managers learn from past experience to build action plans  Elements need to be instrumented consistently, based on open standards Self-management and autonomic managers

13 Level 2Level 3Level 4Level 5Level 1 Basic Managed Predictive Adaptive Autonomic Manual analysis and problem solving Centralized tools, manual actions Cross-resource correlation and guidance System monitors, correlates and takes action Dynamic business policy based management Evolution not revolution Levels of autonomic maturity

14 Agenda  9:10 – 10:30 Self-healing  David Garlan, CMU  10:30 – 11:00 Nutrition Break  11:00 – 12:30 Applications  Marin Litoiu, IBM  12:30 – 2:00 Lunch Break  2:00 – 3:30 Requirements  Dennis Smith, SEI  3:30 – 4:00 Nutrition Break  4:00 – 5:30 Interoperability  Ken Wong, UofA Sessions 20 mins per talk 1 hours for 3 talks 30 mins discussion break

Have Fun! Ask Questions ContributeInteract