1 / 12

The Virtual Resource Market – SLAs as derivatives contracts for the data centre

The Virtual Resource Market – SLAs as derivatives contracts for the data centre. Date: 8 May 2007 Produced by: Chris Swan. The materials may not be used or relied upon in any way. Agenda. A financial metaphor for the data centre Where virtualisation fits into the picture

gillian-nguyen
Download Presentation

The Virtual Resource Market – SLAs as derivatives contracts for the data centre

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Virtual Resource Market – SLAs as derivatives contracts for the data centre Date: 8 May 2007 Produced by: Chris Swan The materials may not be used or relied upon in any way.

  2. Agenda • A financial metaphor for the data centre • Where virtualisation fits into the picture • The virtual resource market • SLAs – the cornerstone to success • Integrating SLAs into the software development lifecycle • Questions

  3. OGF technical reference model – axes only

  4. OGF reference model – top and bottom layers only

  5. OGF reference model - A financial metaphor

  6. A layered view (from OGF technical reference model) Each physical layer provides Abstraction to the layer above Each Virtualized layer provides a flexible mapping/management point

  7. Balancing the infrastructure Service Level Agreements (SLAs) Capacity & Performance Management (VRM) Assets

  8. Virtual Resource Market Virtual Resource Market - Details $/Unit Performance $/Fabric $/Virtual Unit Performance $ for SLAs (Budget) Match $ for SLA to $/Virtual Unit Performance Compute Fabrics Compute Fabric C1 Bid for Compute Fabric Offers of C1 Compute Fabric C2 Bid for Network Fabric Offers of C2 Bid for Storage Fabric Canonical Architecture A Network Fabric N1 Network Fabrics Offers of N1 Bid for Compute Fabric Bids Offers Network Fabric N2 Bid for Network Fabric Canonical Architecture B Offers of N2 SLA Storage Fabric S1 Storage Fabrics Bid for Storage Fabric Offers of S1 Bid for Compute Fabric Storage Fabric S2 Bid for Network Fabric Offers of S2 Canonical Architecture C Canonical Application Architectures Time Slice Bids Time Slice Offers Minimize $/Unit Performance Maintain SLAs Virtualized Resources Physical Resources

  9. SLAs work just like any other piece of software • From the classic waterfall process (or SDLC+): • Initiation (Concept)If we are going to have a system then we will need an SLA • Requirements definitionIdentify at a coarse level what the parameters covered by the SLAwill be • System and software designDetermine high level metrics (key performance indicators) then refine to get specific metrics • Implementation and unit testingThis creates and verifies the functional parts of the SLA • Integration and system testingAt this stage it should be possible to validate that the non functional aspects are achievable • Deployment / maintenanceEnsure that the system performs within the SLA and respond to exceptions • EvaluationDoes the SLA actually represent the service to fit the business need that drove the original concept? } These stages are where efforts are typically focused with existing performance management tools. Many systems are integrated and tested for ‘ultimate’ performance because no SLA has been defined, designed or developed earlier in the cycle.

  10. Tools and technology • XML has become increasingly popular for modelling derivatives, with FPML emerging to cover most of the common ground • We need standard XSDs for SLAs • Composition is crucial – we don’t code from scratch, so we won’t build SLAs from scratch • Common models (canonical forms) can be reused • These may well have repeatable behaviour as well as shape • Components and frameworks have yet to emerge • SLAng (UCL) shows the way, WS-CDL may help with behaviour • Eclipse plugin for SLAs – coming soon?

  11. Questions?

More Related