Presentation is loading. Please wait.

Presentation is loading. Please wait.

OGSA Use Case Description Online Media & Entertainment v 0.1 mini 06-Feb-2002 Tan LuIBM Corporation Boas BetzlerIBM Corporation

Similar presentations


Presentation on theme: "OGSA Use Case Description Online Media & Entertainment v 0.1 mini 06-Feb-2002 Tan LuIBM Corporation Boas BetzlerIBM Corporation"— Presentation transcript:

1 OGSA Use Case Description Online Media & Entertainment v 0.1 mini 06-Feb-2002 Tan LuIBM Corporation tanlu@us.ibm.com Boas BetzlerIBM Corporation boas@de.ibm.com

2 Resources Distributed Server Networked storage Secure network (firewalls) Player Consoles Etc. Services Security services (authentication / authorization, identity) Financial services (billing, rating, accounting) Contracting / settlement services Media / Entertainment services Management service (capacity management, workload management) Etc. Resources and Services

3 Undefined business model Lack competency in network / server programming No system test environment Scalability Upfront finical commitment. Increasing capacity requires significant redesign. Stovepipe solutions. Each has to be managed differently. Infrastructure are not reusable. Hard to add new functions. (e.g. eCommerce or increase capacity) Over provisioned infrastructure Customer Pain Points

4 Standard Pluggable Components (e.g. billing service, customer relations service) On Demand capacity On Demand aggregation / selection of new services. On Demand integration with other companies that has needed competencies. Trust Industry Standards Best Practice Autonomic scalability according to workload. Solutions Needed

5 Required Infrastructure Functions Discovery Instantiate new services Service Level Management Grouping / Aggregation of Services –Policy –Selection –Aggregation –Transformation –Context –Filtering –Topology Security Certification Lifecycle / Change management Failure Management Workload Management Capacity Management Application Specific (e.g. eUI correlation engine, Logging, Problem Determination, etc)

6 Base OGSA Functions Enabling Standard Pluggable Components Discovery –OGSA services must be discoverable at both runtime and setup time. For example, a game developer needs to discovery a set of rendering engines (services). Instantiate new services –Deployment (e.g. deploy Quake engines on servers.) –Scheduling / Dispatching (e.g. scheduling a server to run AI logic.) Service Level Management –For example, guarantee 50 ms response time for first person game, and 100ms for RPG. Grouping / Aggregation of Services -- based on policy and functional requirements –Selection (e.g. select the fastest MP3 encoder.) –Aggregation (e.g. accounting service and rating services are used together to produce billing records.) –Transform syntax and/or semantics of data or interface (e.g. transform a billing record format) Infrastructure Security (e.g. server security, container security, etc.)

7 OGSA Management Functions On Demand and Autonomics Security –Support for single sign-on, digital rights management, intrusion detection Certification –A trusted party certifies that a particular service has certain semantic behavior. (e.g. A company will only use e-commerce services certified by yahoo shopping.) Lifecycle / Change management –Upgrade services or retire services with minimal impact to deployed and/or running services. Failure Management –Capture failure and trigger recovery actions. For example, when a game servers performance is degraded because of a software problem, apply patch. Capacity Management –Use just enough capacity to meet the required service level agreements in both a predictive and a reactionary fashion. On-line games workloads are very close to uniform sinusoidal waves, but typical server farms are still only about 20% utilized. Workload Management –Workload balancing in the existing resource pool. For example, when a particular part of an online game becomes over-utilized, redistribute workloads across servers with idle capacity. Application Specific (e.g. multimodal input)

8 Back Up

9 Possible OGSA Porttype / Services: Base porttypes Factory porttype Notification porttypes Registration porttypes Handle Mapping Additional porttypes Discovery (e.g. find by handle, find by WSDL, etc.) Transport (for deployment, same as defined by DAI?) Dispatch / Schedule Policy (including SLA management, WSLA, etc) Relationships and Dependency Workflow Additional Services Security Transformation services (e.g. data, policy, interface) Certification services (could this be part of WSIF?) Management services Application specific services OGSI OGSA


Download ppt "OGSA Use Case Description Online Media & Entertainment v 0.1 mini 06-Feb-2002 Tan LuIBM Corporation Boas BetzlerIBM Corporation"

Similar presentations


Ads by Google