Computer Science 5204 Operating Systems Fall, 2010

Slides:



Advertisements
Similar presentations
Computer Science 5204 Operating Systems Fall, 2010 Dr. Dennis Kafura Course Overview 1.
Advertisements

Concurrency Issues Motivation, Problems, Directions Dennis Kafura - CS Operating Systems1.
Dr. Kalpakis CMSC 621, Advanced Operating Systems. Fall 2003 URL: Distributed System Architectures.
Computer Science Lecture 18, page 1 CS677: Distributed OS Last Class: Fault Tolerance Basic concepts and failure models Failure masking using redundancy.
Computer Science Lecture 17, page 1 CS677: Distributed OS Last Class: Fault Tolerance Basic concepts and failure models Failure masking using redundancy.
EEC 688/788 Secure and Dependable Computing Lecture 12 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Distributed Database Management Systems
CS-550 (M.Soneru): Recovery [SaS] 1 Recovery. CS-550 (M.Soneru): Recovery [SaS] 2 Recovery Computer system recovery: –Restore the system to a normal operational.
EEC 688/788 Secure and Dependable Computing Lecture 13 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Page 1 Copyright © Alexander Allister Shvartsman CSE 6510 (461) Fall 2010 Selected Notes on Fault-Tolerance (12) Alexander A. Shvartsman Computer.
Chapter 4 Database Management Systems. Chapter 4Slide 2 What is a Database Management System (DBMS)?  Database An organized collection of related data.
Distributed storage for structured data
TRANSACTION PROCESSING SYSTEM Liew Woei Song Muhammad Hofiz Achoson.
Commit Protocols. CS5204 – Operating Systems2 Fault Tolerance Causes of failure: process failure machine failure network failure Goals : transparent:
1 Database Systems CS204 Lecture 21 Transaction Processing I Asma Ahmad FAST-NU April 7, 2011.
Database Management System Module 5 DeSiaMorewww.desiamore.com/ifm1.
File Access and Transfer. Issues 4 Access and transfer are different operations –with different requirements 4 Transfer –move the file from one place.
Chapter 19 Recovery and Fault Tolerance Copyright © 2008.
Week 5 Lecture Distributed Database Management Systems Samuel ConnSamuel Conn, Asst Professor Suggestions for using the Lecture Slides.
Computer Science 5204 Operating Systems Fall, 2011 Dr. Dennis Kafura Course Overview 1.
Introduction. Readings r Coulouris, Dollimore and Kindberg Distributed Systems: Concepts and Design Edn. 3 m Note: All figures from this book.
CMPT 454, Simon Fraser University, Fall 2009, Martin Ester 294 Database Systems II Coping With System Failures.
Chapter 1 Introduction to Databases. 1-2 Chapter Outline   Common uses of database systems   Meaning of basic terms   Database Applications  
CS5204 – Operating Systems 1 Checkpointing-Recovery.
Concurrency Control. Objectives Management of Databases Concurrency Control Database Recovery Database Security Database Administration.
 Distributed file systems having transaction facility need to support distributed transaction service.  A distributed transaction service is an extension.
A Survey of Fault Tolerance in Distributed Systems By Szeying Tan Fall 2002 CS 633.
18 September 2008CIS 340 # 1 Last Covered (almost)(almost) Variety of middleware mechanisms Gain? Enable n-tier architectures while not necessarily using.
Agenda  Quick Review  Finish Introduction  Java Threads.
Computer Science 5204 Operating Systems Fall, 2012 Dr. Dennis Kafura Course Overview 1.
Computer Science Lecture 13, page 1 CS677: Distributed OS Last Class: Canonical Problems Election algorithms –Bully algorithm –Ring algorithm Distributed.
1 CS-550: Materials for the Final Exam - Tue., Dec. 11, 2001, 8 a.m. Distributed Systems 8.Client-server computing Architecture, Relational database applications.
Operating System Reliability Andy Wang COP 5611 Advanced Operating Systems.
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
Presented by Edith Ngai MPhil Term 3 Presentation
Trust Profiling for Adaptive Trust Negotiation
Accessing the VI-SEEM infrastructure
CS4222 Principles of Database System
Training for developers of X-Road interfaces
Processes and threads.
On-Line Transaction Processing
Managing Multi-User Databases
Client/Server Databases and the Oracle 10g Relational Database
Outline Types of Databases and Database Applications Basic Definitions
Last Class: Canonical Problems
Operating System Reliability
Operating System Reliability
IS442 Information Systems Engineering
Computer Science 5204 Operating Systems Fall, 2010
Introduction to Operating Systems
2P13 Week 2.
Database management concepts
Changing thread semantics
Batches, Transactions, & Errors
Operating System Reliability
Operating System Reliability
Outline Introduction Background Distributed DBMS Architecture
Baisc Of Software Testing
Database management concepts
Batches, Transactions, & Errors
Operating System Reliability
Web Information Systems Engineering (WISE)
Operating System Overview
Distributed Systems (15-440)
Abstractions for Fault Tolerance
Concurrency Control.
Last Class: Fault Tolerance
Operating System Reliability
Operating System Reliability
Distributed systems A collection of autonomous computers linked by a network, with software designed to produce an integrated computing facility A well.
Presentation transcript:

Computer Science 5204 Operating Systems Fall, 2010 Dr. Dennis Kafura Course Overview

Reading intensive Balance Organization Syllabus on web site 35 +/- papers No required text Balance Theory vs. technology Contemporary vs. classic Survey vs. depth Centralized vs. distributed Syllabus on web site CS 5204 – Operating Systems

Course Web site CS 5204 – Operating Systems http://courses.cs.vt.edu/~cs5204/fall10--kafura-NVC CS 5204 – Operating Systems

Major Topics and Themes Atomicity Order Consistency Theory Google 1. Concurrency x 2. Security 3. File systems 4. Fault tolerance CS 5204 – Operating Systems

1. Concurrency How can concurrent processing be structured on a single processor? What are the problems and issues in developing systems with concurrent activities? What are emerging models for concurrent programming? How can the problems with multi-threaded programming be alleviated? How can transaction-style semantics be supported locally in hardware or software? How can concurrency and communication be represented formally? CS 5204 – Operating Systems

Process vs. Thread Models . . . user kernel process-centered thread-centered CS 5204 – Operating Systems

Models of Concurrent Computation MapReduce Concurrent Collections (CnC) step item tag CS 5204 – Operating Systems

Thread-per-process models Sequential process Communication channel Communicating Sequential Processes Sammati Grace CS 5204 – Operating Systems

Supporting Transaction Semantics repeat { BeginTransaction(); /* initialize transaction */ <read input values> success = Validate(); /* test if inputs consistent */ if (success) { <generate updates> success = Commit(); /* attempt permanent update */ if (!success) Abort(); /* terminate if unable to commit */ } EndTransaction(); /* close transaction */ } until (success); TM Object Transaction New Object Old Object Locator object data CS 5204 – Operating Systems

π-Calculus An algebra that captures the notions of communication, interaction, and synchronization among concurrently executing entities. talk1 switch1 talk2 switch2 IdTrans Trans Idtrans Trans lose2 lose2 lose1 lose1 gain1 Control gain2 gain1 Control gain2 CS 5204 – Operating Systems

2. Security How can rights for access control be structured for effective use and management? How can a digital document be “signed” so as to identify authorship? How can communicating parties be confident of each other’s identities? How can a platform attest to the validity of its execution environment? How can access policies be expressed and enforced? CS 5204 – Operating Systems

Security Overview server Certificate Authority certificate refers to identity public key certificate refers to Certificate Authority issues private key trusts/ verifies establish server information resources access control secure communication channel CS 5204 – Operating Systems

Security in distributed systems Describe explicit trust relationships Express security token issuance policies Provide security tokens that contain identities, capabilities, and/or delegation policies Express resource authorization and delegation policies CS 5204 – Operating Systems

3. File Systems What does a “typical” file structure look like? What problems can arise in the file sytems when systems fail? How can file systems be structured to withstand (or more easily recover from) system failures? How can file systems be structured to handle tera-bytes of information? CS 5204 – Operating Systems

Local File Systems Structures Log-structured file system Storage Stack Local File Systems Structures Log-structured file system Journaling and soft updates Google File System CS 5204 – Operating Systems

4. Fault Tolerance How can events be ordered in a distributed system lacking a shared clock? How can this ordering give rise to a form of virtual time? What are basic approaches to recovery from failure? What is the taxonomy of strategies of “backward” recovery? How can the state of system be captured so that it can be recovered in the event of failure? How can distributed elements agree on commit to accepting a change in the system state? CS 5204 – Operating Systems

P Q Event Ordering P1 Q1 P3 P2 Q3 Q2 How can the events on P be related to the events on Q? Which events of P “happened before” which events of Q? When does it matter how we answer these questions? CS 5204 – Operating Systems

Recovery erroneous state error valid state failure causes fault leads to recovery An error is a manifestation of a fault that can lead to a failure. Failure Recovery: backward recovery operation­based (do­undo­redo logs) state­based (checkpoints) forward recovery CS 5204 – Operating Systems