Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cloud4SOA SLA Management Layer

1,036 views

Published on

  • Be the first to comment

Cloud4SOA SLA Management Layer

  1. 1. www.cloud4soa.euFrancesco D’Andria (ATOS)francesco.dandria@atos.netWorkshop on“Cloud Computing SLAs in FP7 - Exploitation of Research Results”European Commission DG CONNECT,Brussels, 27 May 2013, Av. De Beaulieu 25, Room 0/S9
  2. 2. Outline1. Cloud4SOA at a glance• Core Capabilities• Cloud4SOA Architecture1. Cloud4SOA SLA achievements andchallenges• Why we need dynamic SLAs• SLA Management Life-cycle1. Real-Time/Unified applicationsmonitoring2. In-depth with the technology3. Future challenges
  3. 3. Cloud4SOA at a glance• The Cloud4SOA projecthelps empowers a multi-cloud paradigm at PaaSlevel• Provides an interoperableframework for PaaSdevelopersDuration: 36 months – (09 / 2010 – 08 / 2013)Budget: 4.13 M Euros /Funding: 2.73 M EurosResearch Programme: FP7-ICT-2009-5Obj1.2Project coordinator: Atos (Spain)Partners:• The system supports Cloud-based application developers withmultiplatform matchmaking, management, monitoring and migration• Interconnects heterogeneous PaaS offerings across differentproviders that share the same technologyappappapp
  4. 4. Matchmaking Management andMigrationMonitoringSemantic profiles of:• User and Applications• PaaS offeringsDefinition of equivalence and compatibilityrules• Same tools manage different clouds• Cloud4SOA harmonizes different providersAPI• Use the same interface to deploy andmigrate applications between PaaS providers• Cloud4SOA defines unified metrics (acrossPaaS providers) to monitor applicationperformances• Cloud4SOA defines Service Level Agreementterms and monitors SLA breakages
  5. 5. Cloud4SOAArchitecture
  6. 6. SLA Achievements & Challengesdelivers an enhanced and distributed architecture for business applicationgovernance, monitoring and service level agreement management– Management Components support the efficient runtime Governance of Application onSpecific PaaS offering.– Monitoring Component based on unified platform-independent metrics– Light, dynamic and stand-alone PaaS technological-independent Service LevelAgreement framework to enforce agreements and violation policies at runtime
  7. 7. Why we need dynamic SLAs?From product and established long-term contracts to on-demand based business models –need for dynamic SLAs that the PaaS ecosystem is not providing:– SLA’s today are static, long term contracts / almost no state-of-the-art for DynamicSLA Management. Does not support business dynamics and changing customer needs PaaS providers in the market currently do not have any dynamic SLA capabilities This makes it difficult to envision an SLA negotiation mechanism, since theproviders won’t be an active party taking part in it.Max capacitypeakdemandunder -utilisationtimeUsageUsageNeed to negotiate flexibly between standard and customized SLAsNeed for business-performance related SLA metricsUsersNeed for customer oriented SLA Managementtools which are able to define, monitor, redefine,correct and report the most important SLAconditions (life cycle approach)UsersNeed for customer oriented SLA Managementtools which are able to define, monitor, redefine,correct and report the most important SLAconditions (life cycle approach)ProvidersNeed for SLA tools which enable PaaSproviders to analyse their ownperformance to offer reasonableBusiness Application SLAProvidersNeed for SLA tools which enable PaaSproviders to analyse their ownperformance to offer reasonableBusiness Application SLA
  8. 8. SLA Management Life-cycleTemplateCreation /PublicationCloudDiscoveryNegotiationMonitoringandEvaluationReactionOff-Line time: Cloud OfferingPublication (WS-Agreement)Design-Time: Search withApplication QoS requirementsAgreement CreationCloud Resource /Application metricsmonitoring –enforcement of thesigned agreementPolicy to react when theagreement is not fulfilled PaaS SemanticProfileMatchmaking1Matchmaking 2Monitoring &EvaluationViolation:Migration / Rating Design-Time: Develop policies to defineviolation when breaches of theagreement occursLimitation of the approachNo commitment of the underling Clouds C4S (multi-cloud) acts on behalf of the offeringsThe result is an agreement Not a real contractViolation Not Penalties or DiscountsNo Charging info in the loop
  9. 9. Real-Time and Unified applications monitoring9The problem: diversity of metrics and API (dissimilar provider with different metrics withthe same name)Cloud4SOA’s answer:•unified metrics, unified interface – overlooking all your deployments at once•empowers developer to compare, contrast, test•brings a unique application based user-defined applications policies monitoring• Application/DataBase RT• Cloud RT• Web Container RT• Application Status• Memory Consumed• CPU Consumed
  10. 10. In-depth with the technologyWS-Agreement CompatibleCloud4SOA provides a JAVA REST-full implementation of a SLAManagement layer fully-compatible with the WS-Agreement specification.•Agreement Template publication and Discovery . The cloud offering is embedded in theCloud4SOA Semantic Ontology (OWL)https://dl.dropboxusercontent.com/u/17326703/c4s_spec/c4sModel.html•SLA Negotiation. Automate negotiations on behalf of PaaS providers, based on the semanticdescription of offerings and the QoS requirements specified by the Application Developer.•SLA Enforcement. Supervise that all the agreements reached in a SLA agreement arerespected (i.e. measurements are within the thresholds established in SLA agreement for QoSmetrics).•SLA violation recovery. Whenever the execution of the business application does not satisfythe SLA (i.e. breaches of the agreement occurs), the most appropriate recovery action (e.g.warning messages, stop or migration of the application) is suggested based on the policiesdefined by the software developer.The code is released under Apache 2.0 license,please email me if you want the code: http://demo.cloud4soa.eu/
  11. 11. Future challenges Work on standards (CAMP TWG from OASIS) Improve performance SLA Management– Extend the mechanism to manage complex agreements– Put in the loop the cloud providers as well (issue so far) Unified Metrics– Find out more (unified) monitoring metrics, and categorize them for commercialand internal usersUseful links:•Demo Platform: http://demo.cloud4soa.eu/cloud4soa/•Standalone Matchmaking:•http://paas-match.cloud4soa.eu/standalone/•Forum: http://www.forum.cloud4soa.eu/cloud4soa_forum/•Github: https://github.com/Cloud4SOA/Cloud4SOA•Please email me @ francesco.dandria@atos.net for detailed design, papers or code.
  12. 12. www.cloud4soa.euConsortiumConsortiumFollow us at the LinkedInCloud4SOA group!http://bit.ly/V9xaIgFrancesco D’Andriafrancesco.dandria@atos.net
  13. 13. MOdel-Driven Approach for design andexecution of applications on multipleCloudsFrancesco D’AndriaFrancesco.dandria@atos.netOn behalf of Danilo Ardagna (Politecnico di Milano)danilo.ardagna@polimi.it
  14. 14. MODAClouds challenges &objectives• Focus on needs of Cloud-based Application Developers andOperators• Challenges• Avoid vendor lock-in• Support risk analysis and management• Guarantee quality assurance• To provide methods, a decision support system, an IDE and aruntime environment to support• Cost and business model comparison• High-level design• Early prototyping• Semi-automatic code generation• Automatic (re)deployment• Monitoring and self-adaptationof applications on multi-Clouds with guaranteed QoS14
  15. 15. MODAClouds expectedresults15DeveloperCIMDSSCPIMCPSMSemi-automatic transformationAutomatic deploymentDecision makingNew or legacyapplications designCode developmentDesign-timeRun-timeGoal: QoS assurance & costs minimization12453Availability24h/dayResponse time <0.4sCIMB-1VM-Large CPUInstanceA-1VM-Small CPUkey-valuedDBInst. numb. >2Deployon PublicCloudCPIMCPSMkey-valuedDBAReliableResource BHigh perf.ResourceCLarge memoryResourceA-1VM-Small CPUB-1VM-Large CPUInstanceA-2PaaSB-2PaaSCPaaSGoal: Cost & Risk AnalysisHigh-level Model-DrivenApplication DesignGoal: Verification & validation of requirementsQoS property analysisGoal: Cloud IndependentModel Representationspanning across allabstraction layersGoal: Cloud SpecificCode RepresentationIDEMonitoring & Data syncronizationRun-time adaptationServiceOperatorManagement
  16. 16. 16 Define and SLA and Monitoring architecture supports multi-cloudapplication scenarios.Support the definition of QoS constraints (hard and softconstraints):For design time explorationTriggers for adaptation in case of run-time violationsEnforce agreement at run-timeAutomatic triggering of adaptation actions in case of run-timeviolations (automatic re-negotiation)Based on unified run-time monitoring metrics (from IaaS andPaaS)1. Reuse outcome from past projects: (cloud4SOA, mOSAIC and other)2. Still collecting requirements3. Architecture not yet defined4. The consortium is willing to use the WS-Agreement specification.5. First version of the code available only by the next winterSLAapproach
  17. 17. Contact details• Project started October 2012• Website http://www.modaclouds.eu/• Partners17

×