OGSA-Basic Services
• Introduction
• Common Management Model
• Policy Architecture
• Security Architecture
• Metering and Accounting
• Distributed Data Access and Replication
Network
OGSA Enabled
Storage
OGSA Enabled
Servers
OGSA Enabled
Messagin g
OGSA Enabled
Directory
OGSA Enabled
File Systems
OGSA Enabled
Database
OGSA Enabled
Workflo w
OGSA Enabled
Security
OGSA Enabled
Web Services
OGSA – Open Grid Services Architecture
OGSI – Open Grid Services Infrastructure Grid Data
Services Grid Core
Services Grid Program
Execution Services
Domain Specific Services OGSA Architected Services
Applications
Open Grid Services Architecture (OSGA)
Open Architecture
Enabled Hardware and Operating System Platforms
Enabled “general purpose” middleware
Support for web services on a variety of platforms,
languages and protocols Open architecture for
interoperability Open and value-added vendor implementations Applications & systems
built on standards
The OGSA Platform
OGSI
Transport Protocol Hosting Environment
Hosting Environment
Host. Env. & Protocol Bindings OGSA Platform services: registry,
authorization, monitoring, data access, etc., etc.
More specialized &
domain-specific services
M od els fo r r es ou rc es & o th er e nt itie s O th er m od els
Environment- specific profiles Domain-
specific profiles
OGSA
Platform
Network
OGSA Enabled
Storage
OGSA Enabled
Servers
OGSA Enabled
Messagin g
OGSA Enabled
Directory
OGSA Enabled
File Systems
OGSA Enabled
Database
OGSA Enabled
Workflo w
OGSA Enabled
Security
OGSA Enabled
Web Services
OGSA – Open Grid Services Architecture
OGSI – Open Grid Services Infrastructure Grid Data
Services Grid Core
Services Grid Program
Execution Services
Domain Specific Services
Open Architecture
Enabled Hardware and Operating System Platforms
Enabled “general purpose” middleware
Support for web services on a variety of platforms,
languages and protocols Open architecture for
interoperability Open and value-added vendor implementations Applications & systems
built on standards
Web Services Evolution
OGSA Architected Services
Applications
WS-Addressing
WS-Transaction
WS-Notification WS-Security
WS-Trust
Open Grid Services Architecture (OSGA)
OGSA Manageability
• Management is a high-priority OGSA effort
– GGF Common Management Model (CMM) WG
• Goal:
– Define standard schema and interfaces for a manageable resource (modeled as a service)
• And also:
– Allow existing models to be used & exposed – Leverage CIM schema when applicable
– Define how CMM interfaces can integrate with higher-level interfaces
(e.g., provisioning)
Common Management Model
• A manageable resource is a Grid service, thus
– Global resource names: Grid service handles – State data modeling + access: SDEs
– Lifetime management
– Service Group for grouping resources – Interface definition language: WSDL
• Plus additional schema & operations
– Standard manageable resource SDE schema
– Interfaces for extensible lifecycle and relationship management
Þ BaseManageableResource interface
Manageable Resource Facade
Grid Service Façade
To
Managed Resource
Manageability Interface Domain Specific
Interface
Resource
GSH
CMM Specification
• Defines three aspects of manageability
– An XML schema(XSD) for modeling the resource manageability information
– A collection of manageability portTypes
– Guidelines for modeling resources
New Constructs for Resource Modeling
• Defines additional data types
• New data types: Counter and gauge
• CMM defines new data types
– Versions related – Unit related
– Lifecycle characteristics
Base Manageable Port Types
GridService
Locate RelationshipLifecycleModel
BaseManageableResource
ServiceGroup HandleResolver
OGSA port types
CRM port types
SDE in Base Management portType
• LifeCycleModel
• currentLifeCycleState
• serviceGroupType
• searchProperty
• relatedInstance
• relatedType
Basic Manageability Port Types
• Needed to manage the resource – lifecycleModel
– relationship – locate
• Others defined
– From CIM schema, e.g., opererational operations (start/stop/resume/pause)
– By OGSO spec, e.g. grid service, notification – By other OGSA components, e.g. policy,
logging/metering
lifecycleModel Port Type:
A Container for Lifecycle States
• There may be multiple models, but only one for a given resource’s port type
• Example: Get/set resource’s lifecycle state – down, starting, up, stopping, failed – Each state has additional info, e.g.,
• up state: idle, busy, degraded
Down Starting
Up Stopping
Failed
Relationships & Dependencies
• Relationships describe existence and type of connections between resource instances
– Relationships are discovered through the relationship port type and its relatedResource service data element
– Relationship port type allows a view of relationships as they are known by the resources at each end of the relationship
• Set of predefined relationship types
– Hosts, Contains, Federates, Aggregates, Uses, Implements
Locate Port Type
• Provided to help in the location of manageable resources of a given type
• Contains two service data elements
– serviceGroupType, port type that provides the ServiceGroup function for manageable resources of this type
– searchProperty, zero or more service data elements that are
likely to be used for searching for a manageable resource, and
are thus worth caching in the manageable resource registry
Service Domains
• High-level abstraction model to describe the behaviors, attributes, operations, and
interfaces to allow a collection of services to
function as a single unit.
Service Domains
Service Orchestration Engine
Service dispatch Service Registry
Policy
Private registries Incoming message
Outgoing
Message/events
Provided
Services
Service Domains: Components
• Service Registration and Collection
• Service Routing and Selection
• Service interoperation and transformation
• Flexible service composition
• Automatic service orchestration
• Note:Uses OGSI ServiceCollection port Type.
Service Domains: behaviours
• Filter
• Selection
• Topology
• Enumeration
• Discovery
• Policy
Policy Architecture
• Provides a framework for creating, managing, validating, distributing, transforming,
resolving, and enforcing policies in distributed
environment.
Policy Architecture
• PolicySet
• PolicyRule
• PolicyGroup
• PolicyCondition
• PolicyAction
Levels of Policy Abstractions
• Business Level
• Domain Level
• Device Level
Security Architecture
Integrate
(Extensible architecture)
Interoperate Trust
OGSA Architecture
Security Components
Bindings Security
(transport, protocol, message security)
Credential and Identity Translation
(Single SignOn)
User Management
Management Key Intrusion Detection
Service/End-point Policy
Audit &
Non-repudiation
Anti-virus Management
S e cu re L o g g in g
T ru st M o d e l
Authorization
Policy Privacy
Policy Secure
Conversations
Policy Expression and Exchange
Policy Management
(authorization, privacy, federation, etc)
Mapping Rules
Access Control
Enforcement
Metering and Accounting
• OGSA proposes utilization CMM for metering
and accounting
Metering Resource Consumption
• At what granularity do services report resource consumption?
• How do they report it?
• How are services metered?
Billing
C on tr ac t S er vi ce
Accounts
Rate Packages
ASPIC CBI
ASPIC CBI
Resource Instrumentation
Metering Handler
Logging Service
Rating
Meter event adaption
Billable Record Listener
Aggregation and Correlation Usage Information
