SRG and MONET research groups

1
2K A Distributed Operating System for Dynamic
Heterogeneous Environments

• SRG and MONET research groups
• Department of Computer Science
• University of Illinois at Urbana-Champaign
• http//choices.cs.uiuc.edu/2K

2
Introduction

• Modern Computing Environments
• Hardware diversity embedded systems, PDAs,
  laptops, workstations, supercomputers.
• Software diversity different programming
  languages, component architectures, operating
  systems.
• Mobile computers
• Mobile users (different accounts in different
  systems)

3
Highly-Dynamic Environments

• Frequent changes
• 1. Structural changes
• HW and SW upgrades, OS patches, protocol updates
• 2. Dynamic changes
• availability of memory, CPU, and network
  bandwidth connectivity, physical location

4
Goal

• Facilitate management of dynamic, heterogeneous
  computing environments for
• Users
• System administrators
• Developers

5
2k Approach

• Network-Centrism
• user profiles, user environments
• services, applications, components
• What You Need Is What You Get (WYNIWYG)
• dynamic instantiation of applications and
  services
• automatic configuration

6
From where can we start?

• Run on multiple hardware platforms
• Run on top of different OSes
• Support different programming languages
• Support dynamism, late binding, components
• Solution
• OMG IDL
• CORBA ORBs
• Standard CORBA Services (Naming, Trading,
  Persistence)

7
But There Was A Problem

• Conventional ORBs were static
• Fixed threading model
• Fixed transport protocol IIOP (over TCP/IP)
• Fixed security strategy
• Fixed scheduling
• Inadequate for a wide range of applications
• Multimedia
• Mobile Computing
• Adaptive Applications

8
Reflective ORB

• Allows inspection and dynamic reconfiguration of
  the ORB internal engine.
• 1. dynamicTAO an extension of the TAO ORB
  Schmidt
• very complete
• big
• 2. LegORB (now UIC) a component-based ORB
• not complete, but expanding
• very small (minimal client 6K or 20K, minimal
  server 30K)

9
What is missing?

• We have
• Reflective Middleware layer supporting
  distributed objects in a dynamically configurable
  way.
• Standard services for Naming, Trading, Security.
• We still need
• Support for automatic configuration.
• Dynamic instantiation of user environments.
• Dynamic resource management.

10
Existing 2K Services

• CORBA Naming and Trading
• Component Repository
• Automatic Configuration
• Distributed Resource Management
• Mobile Configuration Agents
• Distributed QoS Compilation Service

11
Ongoing Work

• Monitoring Service
• User Environment Service
• Security Service
• Distributed QoS Compilation
• Multimedia Services and Applications
• Data Management Service
• Active Spaces (Ubiquitous Computing)

12
The 2K Architecture
13
Automatic Configuration Service

• Automatically instantiates applications and
  services by assembling their components.
• Based on
• Prerequisites representation of component
  requirements.
• ComponentConfigurators dynamic representation
  of inter-component dependencies.

14
ComponentConfiguratorFramework

• Allows browsing, inspection, and reconfiguration
• Can be customized through inheritance
• Clear separation of concerns

15
Mobile Configuration Agents

• Suitable for Large-Scale Systems
• Useful for
• code distribution
• dynamic reconfiguration
• inspection

16
QoS-Aware Distributed Resource Management

• Global Resource Manager (GRM)
• one in each cluster
• maintains an approximate view of the cluster
  resource utilization
• Local Resource Manager (LRM)
• runs in each node
• exports the state of the local resources
• Uses Klaras DSRT Real-Time Scheduler
• admission control, reservation, and scheduling

17
AutoConfig ServiceLoading Several Components