150 likes | 383 Views
Technical Demonstrator SLA-driven Service Management. Bastian Koller, Philipp Wieder, . All services in NextGRID need a SLA. To offer an SLA it must be possible to manage the service otherwise the cost to the service provider can become prohibitive
E N D
Technical DemonstratorSLA-driven Service Management Bastian Koller, Philipp Wieder, (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
All services in NextGRID need a SLA • To offer an SLA it must be possible to manage the service • otherwise the cost to the service provider can become prohibitive • Demonstrate a generic framework to provide this management functionality • parameterised for each application (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
SLA Lifecycle Discovery and Negotiation (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium Telemanagement Forum
SLA Based Service Management Customer Service Provider Template Registry SP Template Repository Discovery Coordinator Signer Template Generator Customer Client Negotiation Coordinator BLO Retriever BLOs Constraint Checker QoS Analyser Operational QoS History QoS Info Provider Service Utilisation Policy Generator Management Framework Service Supervisor Allocator SP Relation History Accounting + Billing Deployer Evaluator Demonstration covers SLA Lifecycle Stages 2-5 and components from WP4/5 MID Service (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Scenario • The Service: • The Credit Card Check service allows the customer to check whether a credit card is valid. • Customer Requirements from Service: • Functionally Accurate • Reliable • Performance • Transparent Pricing (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
The SLA As part of this agreement the SP guarantees the following service level: • The service will process 5000 transactions per hour • 95% of these 5000 transactions will complete within a second • The SP promises to complete 99.99% of all submitted transactions up to the defined limit of 5000 transactions per hour. The customer constraints are: • Maximum of 100 transactions submitted in 1 min (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Components Service Provider Domain HLRS Customer Domain Bob SLA Template Repository Registry Service Provider Negotiator Customer GUI UDAP Service Provider Domain BT * Colour-Legend * SLATemplate Repository HLRS NEC FZJ Service Provider Negotiator (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Service Provider Domain HLRS SLA Template Repository Service Provider Negotiator <CreditCardRegistryEntry …> <ServiceType…> CreditCardServiceGold </ServiceType> <add:EndpointReference> … </add:EndpointReference> </CreditCardRegistryEntry> <CreditCardRegistryEntry …> <ServiceType…> CreditCardServiceGold </ServiceType> <add:EndpointReference> … </add:EndpointReference> </CreditCardRegistryEntry> Service Provider Domain BT SLA Template Repository Service Provider Negotiator Prerequisites Registry BT & HLRS have registered their services at the registry (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
<udap:UDAPRequest xmlns:udap="http://nextgrid.org/2006/05/udap"> <udap:Id>AUniqueRequestID</udap:Id> <udap:Resource> <udap:Id>CreditCards1</udap:Id> <udap:Type>CreditCardResource</udap:Type> <udap:ResourceDescription Dialect="http://nextgrid.org/2006/9/11/ ccquality"> <ccqual:CreditCardQuality xmlns:ccqual="http://nextgrid.org/2006/9/11/ccquality">Gold</ccqual:CreditCardQuality> </udap:ResourceDescription> </udap:Resource> </udap:UDAPRequest> ? ! Discovery I Registry • Define Udap Request Customer Domain Bob 2. Send Udap Request 3. Query Registry 4. Request Templates from the different SLA Template Repositories Customer GUI UDAP (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Service Provider Domain BT SLA Template Repository Service Provider Negotiator Service Provider Domain HLRS SLA Template Repository Service Provider Negotiator Discovery II • Request Templates from the different SLA Template Repositories UDAP (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Discovery III Customer Domain Bob • Receive Addresses of Service Providers (Negotiators) as well as information about offered services UDAP Customer GUI 2. Decide on candidates for negotiation (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Customer Domain Bob <SLA Bid> … </SLA Bid> <SLA Bid> … </SLA Bid> Customer GUI Negotiation I Service Provider Domain HLRS SLA Template Repository Service Provider Negotiator Service Provider Domain BT • Create Bid based on template SLATemplate Repository • Send Bid and request offer from the respective Service Providers Service Provider Negotiator (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
? <SLA Offer> …. …. </SLA Offer> Negotiation II Service Provider Domain • Query Repository for matching Service Templates 2. Decide whether to offer an SLA Offer SLATemplate Repository 3. (Create Offer) • (Send Offer to Customer) Service Provider Negotiator (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Customer Domain Bob Customer GUI <SLA Offer> …. …. </SLA Offer> Negotiation III • Analyze Offer(s) • Decide whether to accept or reject the offer(s) (In this case the customer selects the service with the maximum possible submission rate) (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium
Customer Domain Bob Reject Accept Customer GUI Negotiation IV Service Provider Domain HLRS SLA Template Repository Service Provider Negotiator Service Provider Domain BT • Send Acceptance • Send Rejection SLATemplate Repository Service Provider Negotiator (c) 2006 BT, HLRS, FZJ, UoE and other members of the NextGRID consortium