Semantically enhanced SLA Negotiation

  • View
    14

  • Download
    2

Embed Size (px)

DESCRIPTION

Semantically enhanced SLA Negotiation. Bastian Koller, High Performance Computing Center Stuttgart. Motivation. Contractual relationships between customer and providers require to support both in the process of service trading - PowerPoint PPT Presentation

Transcript

  • Semantically enhanced SLA NegotiationBastian Koller, High Performance Computing Center Stuttgart*Semantic Week, AmsterdamPage *

    IOS 2009, Brussels

  • *MotivationContractual relationships between customer and providers require to support both in the process of service tradingThe contract is the result of a negotiation process between both parties An SLA can be used as electronic representation of contractual termsIt is important to have a SLA description for SLA templates and the SLA specificationterms for the provision of the service (service description), Quality of service (QoS) level to be maintain, Information about resources to be provided, the liability to compensation if SLAs are not met.WS-Agreement covers the syntactic aspects in the description of SLA, but not the vocabulary termsAdditionally Current SLA descriptions lack in interoperability:Open marketplace: Providers and consumers are collaborating on a global scale competing for offering and consuming services not possible

    *Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • Problem AreaNegotiationNegotiationDifferent languages, different metricsANSYS request

    CPUName: IntelCore DuoCPU Speed: 2 GHzCapacity: 400 MBPrice: 27 euros per dayDiskSpace: 250GB

    CUSTOMERSoftware engineering companyRAMMemory: 7.5 GBComputeUnit: 4 ECUStorage: 850GBPlatform: 64 bitPrice: $0.4 per instance hourAMAZONMemoryPerTask: 7.5 GBClockCPUSpeed: 100 MHz / processStorageCapability: 850GBCost: 5 euros/task/hourBSC*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • BREIN (SA)SLAsIntroduction of semantic annotations in current SLA template filesBased on SA-WSDLWS-Agreement + WSLA compatible (as based on a merge of both)Allows for annotating SLA description with pointers to semantic conceptsAnnotation of: SLA Parameters. Metrics

    MetricParameterSLOmodelReferencesSchemaMappingsNon-semantic descriptionsSemantic descriptionsRDF, OWL, WSMLSA-SLASLA templateQoS metricsSLA terms*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • A Customer needs somethingI need somethingI need this with a duration of 10 minutesService Provider Can you provide?CustomerI am offering somethingwith an execution time between 8 and 12 minutesI can with execution timeBut I need with durationI can with execution timeBut I need with durationI can with execution timeBut I need with durationWelcome to Babel*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • What we want to achieveCustomers and Service Provider need to be enabled to understand each other on a common levelOntologies can help to overcome this problemIntroduction of Semantic Components, enhancing the SLA Negotiation ProcessProvisioning of a specification for Semantic Annotated Service Level Agreements SA-SLAs*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • Service Provider Domain

    duration = ???I need something with durationI need the ontology for this customerHere you areThe SLA Mediator is able to match SA-SLA requests and offers, by converting SLA documents from other domains (e.g. bids or templates) into the local SLA model to be usable inside the respective domain. It can either query the Translator for the matching Ontology or, in case the Ontology is not available, request this from a third party Ontology Provider. With the Mediator, the high level SLA Parameters (between Provider and Customer) can be mapped down to the Service Provider Infrastructure level. The Mediator is a component in both domains. The SLA translator is an ontology repository, which allows for managing the local domain ontology. Within it, the domain rules are formalized. The Translator is a component in both domains.The Ontology Repository is a third party storage, where Service Providers as well as Customers can store their Ontologies to make them available for other parties and vice versa, other parties can query this for ontologiesduration = execution time!!!Yes we can!!*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • The Architecture*Page *Customer sideThird partyQoS common ontologySend BidSLA NegotiatorSA-SLASLA NegotiatorProvider sideLocal domainknowledgeSLA Template repositoryCreate InstancesMatch requestDo SPARQL querySLA MediatorTSLASelectorTSLA ParserOntology ManagerSend OfferSA-SLATemplates scoresSemantic Week, Amsterdam

    IOS 2009, Brussels

  • DemoANSYS request

    CPUName: IntelCore DuoCPU Speed: 2 GHzCapacity: 400 MBPrice: 27 euros per dayDiskSpace: 250GB

    RAMMemory: 7.5 GBComputeUnit: 4 ECUStorage: 850GBPlatform: 64 bitPrice: $0.4 per instance hour*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • BREIN approach

    SLA file semantic annotatedCapacity -> qos:RAMMemoryCPUSpeed -> qos:CPUSpeedDiskSpace -> qos:StorageCapacityANSYS request

    CPUName: IntelCore DuoCPU Speed: 2 GHzCapacity: 400 MBPrice: 27 euros per dayDiskSpace: 250GB

    RAMMemory: 1.7GBComputeUnit: 1 ECUStorage: 160GBPlatform: 32 bitI/O Performance = moderatePrice: $0.10 per instance hourRAMMemory: 7.5 GBComputeUnit: 4 ECUStorage: 850GBPlatform: 64 bitPrice: $0.4 per instance hourRAMMemory: 15 GBComputeUnit: 8 ECUStorage: 1690GBPlatform: 64 bitPrice: $0.8 per instance hourSLA file semantic annotatedRAMMemory -> qos:RAMMemoryECU -> qos:EC2_ComputeUnitStorage -> qos:StorageCapacity*Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • What happens in the demo?

    *Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • With the BREIN solutionEnhanced Interoperability Optimal Offer/Counter Offer creation Support when needed Due to the non-invasive annotations

    *Page *Semantic Week, Amsterdam

    IOS 2009, Brussels

  • BACKUP SLIDES*IOS 2009, Brussels Page *

    IOS 2009, Brussels

  • SLA NegotiatorSLA Negotiator Client SideOn behaver of customerReceiving a bid from customer, which filled with desired QoS values .Taking responsible to interact with SLA Negotiator Server

    SLA Negotiator Server SideOn behaver of Service provider Checking service availablability Using semantic MatchingGiving back a offer to Negotiator Client *BREIN Vienna GA Page *

    IOS 2009, Brussels

  • availablability Negotiation Process for demo*BREIN Vienna GA Page *SLANegotiatorClientPage *bid, Negotiator URISLA Negotiator(URI:http://localhost: http://localhost:8080/wsrf/services/Brein/demo/sla-negotiation)SLA Mediator (URI://localhost(SLAT/SLATServlet)SLA Mediator(URI://localhost(SLAT/SLATServlet )Ontology ManagerSLA Repositoy(URI://localhost/sla/repositoy)Mediator URIoffer URI

    IOS 2009, Brussels

  • The negotiation sequence on the SP side*IOS 2009, Brussels Page *

    IOS 2009, Brussels

  • SLAs in BREINWith the integration of Multiagent and Semantic Web concepts in BREIN, we foresee to enablediscovery on basis of SLA capabilitiesCustomers will be able to define their requirements in their language, whereas the system understands this and is able to perform discover accordingly a clear understanding of different SLA "languages" (term definitions)Current solutions require in-depth knowledge from the Users about the used SLA language too much efforts, especially for SMEsmapping between contractual terms and system termsContractual terms are on a much higher level then system terms. (timetocomplete vs 4CPUs, 2days running)Automate the setup of the infrastructure according to the SLA and other requirements

    *IOS 2009, Brussels Page *

    IOS 2009, Brussels

  • SLAs in BREIN (ii)Enable to.Dynamically negotiate QoS termsFrom discrete offer negotiation (one phase) to a multiphase negotiation, with offers and re-offersAutomatically understand the infrastructure capabilities for negotiation purposesCan I or cant I offer this value (and I need to know this quick)Optimize negotiation wrt business goals & policiesIs it in my interest to negotiate this ServiceIf I agree on an SLA of a high value customer, do I take the risk (intentionally) to violate an already running SLA of anotherCompare current SLAs to prioritize (intentionally violation)Optimize resource usage whilst still meeting the SLA

    *IOS 2009, Brussels Page *

    IOS 2009, Brussels

    **SA-SLA is a set of extension for SLA template which provides a standard description format for SLA template filesSA-SLA allow for annotating SLA description with pointers to semantic conceptsGround with expressive ontologies (OWL, WSMLSoftware components can interpret these concepts and automate tasksSA-SLA extensions? (reused from SAWSDL)Model references: association between a SLA schema and a concept in some semantic model Schema mappingsliftingSchemaMapping and loweringSchemaMapping, for specifying mappings between semantic data and XML.*ANSYS defines a SLA file in its own terms: memory and CPU2.- ANSYS sends the SLA file to resource provider3.- The resource provider (BSC) should allocate resources taking into account the SLA received. Components providers only understand providers metricsProvider metrics: MemoryRequirement, CPURequirement2They are using the same metrics (memory and CPU) with different representations and they cannot understand

    *ANSYS defines a SLA file in its own terms: memory and CPUANSYS annotates the file a SLA file request in their own terms (memory, cpu) MemoryUsedForTask and CPUUsedForTask

    **