OGSAWG Use Cases

1
OGSA-WG Use Cases
GGF8 OGSA-WG

• 06/23/2003
• Hiro Kishimoto, Ph.D
• Fujitsu

2
OGSA-WG Charter and Scope

• To produce and document the use cases that drive
  the definition and prioritization of OGSA
  Platform components, as well as document the
  rationale for our choices.
• To identify and outline requirements for, and a
  prioritization of, OGSA Platform services.
• hosting environment and protocol bindings
• models for resources and other important
  entities.
• interoperability requirements
• To define standard OGSA profiles, i.e., sets of
  OGSA components that meet specific requirements.
  
• To define relationships between GGF and other
  standards bodies activities

The Open Grid Service Architecture Platform,
draft-ggf-ogsa-platform-2, Feb. 16, 2003
3
OGSA roadmap
Use cases
Commercial Data Center
Analyze Extract
Requirements (Functions)
OGSA-WG
Data Sharing
Evaluate Prioritize
Mechanism (Services)
Data Management
Dispatch
OGSA-DAI
interface
Existing or new WGs
DAIS-WG
4
Functions, Services, and Interfaces

• Functions
• High level requirements
• Important and apparently broadly relevant
  characteristics of Grid environments and
  applications
• Will be described in OGSA Platform document
• Services
• Features and associated behaviors that provide
  the above functions
• Will be described also in OGSA Platform
  document
• Interfaces
• portType detailing the above services
• Actual Specifications that will be defined by the
  other WGs

5
OGSA Platform Services
More specialized
domain
-
specific
services
OGSA Platform services registry,
authorization, monitoring,
Data mgmt, CMM, etc., etc.
OGSI
. Protocol Bindings
Host.
Env
Transport
Hosting Environment
Protocol
Hosting Environment
The Open Grid Service Architecture Platform,
draft-ggf-ogsa-platform-2, Feb. 16, 2003
6
Outline

• Use cases for OGSA
• Science Grid
• Commercial Grid
• Grid Technologies
• Function requirements
• Platform services

7
OGSA Use Cases

• Science Grid
• National Fusion Collaboratory (Kate Keahey)
• Severe Storm Modeling (Dennis Gannon)
• Virtual Organization Grid Portal (Charles
  Severance)
• Commercial Grid
• Commercial Data Center (Hiro Kishimoto)
• IT Infrastructure and Management (Ravi
  Subramaniam)
• Online Media and Entertainment (Tan Lu)
• Grid Technologies
• Grid Resource Reseller (Jon MacLaren)
• Service-Based Distributed Query Processing (Nedim
  Alpdemir)
• Grid Workflow (Takuya Araki)

See Open Grid Service Architecture Use Cases in
detail
8
National Fusion Collaboratory

• Providing codes as network services
• portability issues
• provisioning issues
• Different execution objectives
• Real-time constraints (betw. Experimental pulses
  15mins)
• Batch jobs where accuracy is important
• Pre-emption
• Fusion Experiments
• Pulses every 15-20 minutes
• QoS-based, time-critical execution
• Objective
• Run more codes in that critical time window
• Reduce the time/cost to maintain the software

9
NFC Scenario
Clients view
Service Providers view
Submit a job with end-to-end QoS constraints
Meta-data describes resource capabilities as
well as multiple, differently configured
service installations
Data Source (MDSplus)
(1)
(2)
(3)

• Service Agreements (for time critical execution)
• End-to-end QoS-driven execution
• Combining and managing multiple activities
• Adaptive capabilities to satisfy composite QoS

10
NFC Requirements

• Fusion codes as network services
• Time-bounded execution
• Agreement-based execution
• Use policies
• Flexible delegation of rights
• Delegating a subset of rights based on need
• Community accreditation
• dynamic accounts

11
Commercial Data Center

• Managing the resources of a distributed data
  centers of enterprises
• Out-sourced the IT component of their business
• Grid Administrator
• Managing and providing IT resources
• Business activity manger
• Providing the specific IT services, e.g. Tickets
  sales or database/data archive
• IT System Integrator
• Construct heterogeneous systems

12
Commercial Data Center
Business Activity Manager
Business Activity
Grid Administrator
Business Activity
IT system
IDC infrastructure

• Business Activity Manager needs
• Scalable and reliable platform at low cost
• End user level QoS
• Grid Administrator wants
• High utilization of resources
• Policy based management
• IT System Integrator wants
• Reduce complexity of dist. and hetero system
• Responding to frequent service spec. changes

IT System Integrator
13
CDC Scenarios

• Multiple in-house systems
• Consolidate In-house systems and allocate
  resource on-demand reduces cost and increases
  resource utilization
• Limited time commercial Campaign
• Provide necessary resource on demand
• E.g. concert ticket sales, sales promotion
  Champaign
• Disaster recovery
• Provide a standard disaster recovery framework
  across remote CDCs at low cost
• Global load balancing
• Remote CDCs can share workload and provide
  scalability

14
Online Media and Entertainment

• Two main categories of entertainment
• Consumption of content with less user interaction
• E.g. video on demand
• Interaction with content
• E.g. online games
• Very important to guarantee response times
• Roles of actors
• A consumer who consumes the content
• A service provider that hosts the content
• A publisher that offers the content
• A developer that consumes the Content.

15
Provisioning for On-line media

• On-line games workloads are very close to
  uniform sinusoidal waves
• Typical server farms are still only about 20
  utilized
• Providers should use just enough capacity to meet
  the required service level agreements
• Predictive and Reactionary fashion

16
Provisioning Management
Proxy
DB
Gateway
Servers
Servers
Server
Game/
Assist
Game
GW
Assist
Server
add and remove server
Server
Server
Resource
Monitoring
additional
Free
gamers
Server
eUtility Infrastructure
Server Resource Manager
Free Servers
Server Resource Services
Server Resource Service
Server Resource Service
Server Instantiation Service
Network Configuration Service
ODRM server (WebSphere)
17
Grid Resource Reseller

• Inserting a supply chain between the resource
  owners and end users will allow the resource
  owner to concentrate on their core competence and
  avoid providing costly interaction
• End users can purchase resources bundled into
  attractive packages by the reseller
• The resellers can make money from reselling
  aggregated computational resources without having
  to own any resources themselves
• The reseller maintains resource provision by
  sustaining their relationships with upstream
  providers.
• To protect the agreed service level with the end
  users, the reseller may occasionally find it
  necessary to switch provider
• The reseller can focus on providing good customer
  care as well as marketing resource bundles to
  their target market(s).

18
Grid Resource Reseller

• GRR picture here

19
Outline

• Use cases for OGSA
• Function requirements
• Basic functions
• Security functions
• Resource management functions
• System properties
• Platform services

20
OGSA Basic Functions

• Discovery and brokering
• Metering and accounting
• Data sharing
• Virtual organizations
• Monitoring
• Policy

The Open Grid Service Architecture Platform,
draft-ggf-ogsa-platform-2, Feb. 16, 2003
21
Use case x Function Matrix
OGSA Basic Functions
Pink cell indicates difference between use case
requirement and The OGSA Platform document
definition
22
Matrix Example Metering and accounting function

• Definition from platform document
• Applications and schemas for metering, auditing
  and billing
• Commercial Data Center
• During job execution, the metering service keeps
  track of resource usage.
• The information is passed to the accounting
  service.
• IT infrastructure and Management
• Metering Record the usage and duration esp.
  meter the usage of licenses.
• Auditing Audit usage and application profile on
  machine
• Billing Based on metering bill the user.
• Service-Based Distributed Query Processing
• SB-DQP can potentially use many GDSs and other
  grid and web services. Each of these may have its
  own impact on the overall billing cost
• SB-DQP must be able to integrate into metering,
  accounting and billing mechanisms employed by
  other participating data sources and/or services
• Grid Resource Reseller
• Different charging schemes should co-exist in
  OGSA Platform.
• The accounting systems to operate autonomously
  for the vast majority of circumstances

23
OGSA Security Functions

• Multiple security infrastructures.
• Perimeter security solutions.
• Authentication, Authorization, and Accounting
• Encryption
• Application and Network-level Firewalls.
• Instantiate new services
• Service Level Management
• Certification

Pink-underline functions are needed by use
case(s) but are not mentioned in the The OGSA
Platform document
24
Resource management functions

• Provisioning.
• Resource virtualization.
• Optimization of resource usage while meeting cost
  targets
• Transport management.
• Usage models
• management and monitoring
• CPU scavenging
• Advanced Reservation
• Scheduling
• Load balancing
• Notification/Messaging
• Logging
• Workflow management

Pink-underline functions are needed by use
case(s) but are not mentioned in the The OGSA
Platform document
25
System Properties

• Fault tolerance.
• Disaster Recovery.
• The self-healing capabilities
• Strong monitoring
• Legacy application management.
• Administration.
• Agreement-based interation.
• Grouping / Aggregation of Services -- based on
  policy and functional requirements
• Workload Management
• Extended Service Level Agreements

Pink-underline functions are needed by use
case(s) but are not mentioned in the The OGSA
Platform document
26
Outline

• Use cases for OGSA
• Function requirements
• Platform services
• List of services
• Use case x service matrix

27
Platform Services

• Name resolution and discovery
• Service domains.
• Security.
• Encryption
• Policy.
• Data management.
• Messaging, queuing, and logging.
• Events.
• Metering and accounting.
• Transaction

• Service orchestration
• Administration
• Provisioning and resource mgmt
• Reservation
• Brokering
• Scheduling
• Fault handling
• Monitoring
• Deployment
• Web-service access interfaces

Pink-underline service is needed by use case(s)
but are not mentioned in the The OGSA Platform
document
28
Use case x Service Matrix
Pink rows indicate missing services and Pink
cell indicates difference between use case
requirement and The OGSA Platform document
definition
29
Matrix example Brokering

• Definition (by SD-WG)
• Performs resource quoting or resource discovery
  and selection based on various strategies,
  assigns application task(s) to those resources
• Commercial Data Center
• Standard description of Job submission and
  resource request are necessary. Standard archive
  format for program, parameters, and data are also
  essential.
• IT infrastructure and Management
• It is used for resource selector
• Severe Storm Modeling
• Compute and data resource brokering services.
  Scheduling and co-scheduling services will be
  needed.
• Online Media and Entertainment
• Grid Resource Reseller
• Brokering functionality is required. The policy
  matching aspects of this are probably to be
  handled by the Policy interface.

Grid Scheduling Dictionary of Terms and Keywords
(SD-WG)
30
Call to Action

• The current list of Grid use cases is incomplete
  and use case descriptions are unequal
• Function and service discussion is just started
• Provide your use cases
• E.g. Physics Data Grid use case
• Give more detailed and prioritized requirements
  to identify functions
• Input your thought to identify and prioritize
  important services

31
Next Steps

• OGSA use cases
• Collect and refine use case descriptions
• Use case document final draft hopefully at GGF9
• Requirements and services
• Analyze and extract requirements from use cases
• Evaluate and prioritize platform services
• Update and submit OGSA platform document
  hopefully first draft at GGF9
• Build spec creation process consensus and
  initiate