Next Grid Sla Req

628 views

Published on

Fashion, apparel, textile, merchandising, garments

Published in: Business, Lifestyle
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
628
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This presentation is about the requirements on monitoring and management in a NextGrid context. NextGrid’s main goal is to make the Grid suited to commercial resource and capacity trading between businesses. SLA Management as known from the application and internet service provisioning plays a fundamental role in achieving this, and is therefore the focus of this talk. Disclaimer, NextGrid just had its first set of Kick-Off meetings this week so this is still very preliminary work in progress. To map some of the requirements to a real deployed Grid system, SGAS and its requirements are presented. Focus on resource management.
  • Next Grid Sla Req

    1. 1. NextGRID Monitoring and Fabric Management Requirements SLA Management Example: SweGrid Accounting System and Test-bed Thomas Sandholm, KTH, sandholm@pdc.kth.se
    2. 2. NextGRID <ul><li>How do we make </li></ul><ul><li>the Grid sustainable? </li></ul>
    3. 3. Outline <ul><li>NextGrid WP4: Grid Foundations - Advanced Deployment, Service Management and Migration </li></ul><ul><li>SLA Management Lifecycle: Construction, Negotiation, Attainment, Charging </li></ul><ul><li>Towards Adaptive Systems: SLA Manager Bag of Services </li></ul><ul><li>Example Test-bed: SweGrid & SGAS </li></ul><ul><li>Example SLA Usage: SLA Management in SGAS </li></ul><ul><li>Requirements Checklist </li></ul>
    4. 4. NextGRID WP4: Grid Foundations - Advanced Deployment, Service Management and Migration <ul><li>Work Package - Grid Foundations: </li></ul><ul><ul><li>Address basic properties, protocols, and core services of individual OGSA services, e.g., QoS & Manageability – engineer reference solution </li></ul></ul><ul><li>Task - advanced deployment, service management and migration: </li></ul><ul><ul><li>Requirement: Decentralized automatic control needed over hardware comprising Grid fabric as well as applications and services running on that fabric </li></ul></ul><ul><ul><li>Requirement: Incremental evolution to avoid loss of service </li></ul></ul><ul><ul><li>Focus on autonomous service management and SLA management </li></ul></ul><ul><ul><li>Phase 1: analyse available monitoring and supervision solutions. Requirements from existing Grid projects, e.g., Framework 5 Projects, GRASP, Android, SweGrid </li></ul></ul><ul><ul><li>Phase 2: develop management framework ,SLA+negotiation </li></ul></ul><ul><ul><li>Phase 3: integrate monitoring and management solution and introduce intelligent decision-making process . </li></ul></ul><ul><li>NG Partners: British Telecom (UK), HLRS (Germany), KTH (Sweden) </li></ul>
    5. 5. SLA Management Lifecycle <ul><li>Construction Phase: offers prepared by service providers (or their agents) with fixed and negotiable terms , service requests with QoS requirements prepared by customers (or their agents) </li></ul><ul><li>Negotiation Phase: negotiation protocol needed to settle on negotiable terms and sign SLA. SLA-SLS mapping . </li></ul><ul><li>Attainment Phase: monitoring , policing, re-negotiation, re-configuration, obligation fulfillment. </li></ul><ul><li>Charging Phase: accounting , usage recording, auditing, archiving, price rating, billing. </li></ul>
    6. 6. Towards Adaptive Systems: SLA Manager Bag of Services SLA Manager Policy Manager (PAP, PIP, PDP, PEP) Policy Rule Base (XACML, FuzzyLogic) SLA Provider (WS-Agreement, WSLA) Access Flow Policing/Shaping (DiffServ Packet Dropping) Service Registration/Discovery (WS-RF, UDDI) Pricing Manager (GridBank Trader Service) Service Monitor/Controller (GGF-CMM, WSDM, WS-RF) Negotiation Agent (Contract Net, WS-AgreementNegotiation) Meta-Data Repository (Ontologies, WSDL) Usage Tracker/Analyzer (GGF-UR, Nework Traffic Analyzers) Knowledge Repository Usage Repository P2P Event Manager
    7. 7. Example Test-bed: SweGrid & SGAS <ul><li>Swedish nation-wide computational resource comprising 600 Intel P4 at 6 HPC Centers interconnected with 10Gb/s GigaSunet network </li></ul><ul><li>Resources allocated to promising research projects with demanding computational and storage needs by national allocations comittee (SNAC) </li></ul><ul><li>SweGrid Accounting System (SGAS) provides soft real-time allocation enforcement across all centers in the Grid based on SNAC quota </li></ul><ul><li>3-party policy-driven resource access (user resource specification, local resource policy, allocation authority policy) </li></ul><ul><li>Java Web services, OGSA, WS-Security, GSI, GGF-UR, XACML standards-based Infrastructure </li></ul><ul><li>Integration platform for workload managers and local accounting systems/schedulers </li></ul><ul><li>Currently built with GT3 (OGSI), transition to GT4 (WS-RF) next year </li></ul>
    8. 8. Example NextGRID Deliverable Use: SLA Management in SGAS Allocation Authority Reservation Manager Usage Tracker Policy Manager Resource Specification Policy Manager Bank Resource Service Registration/Discovery Service Monitor 3rd Party (ARC/Globus) Remote Execution Service Negotiation Agent Negotiation Agent
    9. 9. Requirements Checklist (incomplete in random order) <ul><li>Decentralized automatic control needed over hardware comprising Grid fabric as well as applications and services running on that fabric (WP4) </li></ul><ul><li>Incremental evolution to avoid loss of service (WP4) </li></ul><ul><li>Common information models for service level agreements and for the management information that is required to deliver end-to-end application quality (WP3) </li></ul><ul><li>Techniques for adapting the representation of information according to its context (WP3) </li></ul><ul><li>Standardized QoS Ontologies to allow monitoring on predefined SLA parameters with well-defined metrics </li></ul><ul><li>Sensors and Controllers on various levels (e.g. Resource, Workflow) wrapping instrumented code – accessed using standard protocols defined in WSDL </li></ul><ul><li>Registration/Discovery of Sensors and Controllers – using standard protocols defined in WSDL </li></ul><ul><li>Both Push and Pull Event Handling of messages of various criticality (filterable) </li></ul><ul><li>Virtualization of Resources, Abstract Runtime (Hosting) Environments </li></ul><ul><li>Back-end SLS Control : CPU, Bandwidth, Storage, Memory </li></ul><ul><li>Front-end SLA Request : availability, run time, jitter, cost </li></ul>
    10. 10. Example Test-bed Experience: SGAS Resource Administrator Interaction and Policy Introduction <ul><li>Involve RAs early in the process with surveys </li></ul><ul><li>Feedback from running system crucial to move from prototype to production </li></ul><ul><li>Use a phased low-risk, low-intrusion deployment approach </li></ul><ul><li>Allow all stake-holders (e.g. RAs, users, resource owners) to customize local policies easily through XML document centric configurations and transformations, e.g. RSL, XACML, GGF-UR Style sheets. Provide sensible defaults. </li></ul>

    ×