Your SlideShare is downloading. ×
  • Like
Forecast odcau5 100_ak2
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply


Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. ODCA U: INTEROP ACROSS CLOUDSCa therine S pence, Intel ITPankaj Fichadia, National AustraliaBa nk
  • 2. AGENDA Interop Usage Models• Interoperability Across Clouds• VM Interop• PaaS Interop• Long Distance Migration (LDM)• SaaS Interop• Commercial Framework Key Take-aways Information and assets Questions2
  • 3. INTEROP USAGE MODELS1. InteroperabilityAcross CloudsIaaS:Moving SystemsPaaS:Moving AppsSaaS:MovingCapabilities4. Long Distance Migration(LDM)2. VM Interop 3. PaaS Interop 5. SaaS Interop6. Commercial Framework3
  • 4. 1. INTEROPERABILITY ACROSS CLOUDS Cloud apps & services must co-exist and interactwith one another and non-cloud systems, for:• Rapid adoption of cloud services by cloud subscribers• Ability to combine cloud services from multiple providers Perspectives:• Portability = serial process of moving from one environment to another• Interconnectability = parallel process to communicate and interact4
  • 5.  Key points:• Requires an open and complete transportation path – reserve resources at target• Sufficiently like environment at target & source to effect the transfer• UM contains MoSCoW prioritization of requirements• Providers must support common standards, and subscribers must understand and alignto these standards (and ask for them)2. VM INTEROP Scenarios:• Check interop• Move/copy between 2 clouds• Leverage common operation Relevant Standards:• Packaging - DMTF OVF• Catalog - CIMI• Provisioning – SMPL, OASIS CIMIMigrate live or with downtime5
  • 6. 3. PAAS INTEROP Scenarios:• Rapid app on-boarding• Configure PaaS environment• App scalability (auto scale)• Operation & monitoring• App porting Key points:• No modification of the app is required to execute it within PaaScontainers as the app is deployed to multiple providers• PaaS is constrained to deploying a single application developed for aspecific programming language within a hosted application container• Assumes data as a service or database as a service is in effect6
  • 7. 4. LONG DISTANCE MIGRATION (LDM) Groups of usagescenarios:• Relocate• Extend• SustainLayer Scope RelevantStandards3. Migration ProtocolProcedures, processes, methodologies and checklists includingStart/Halt/Ack/Stop/Failure/FinishNone2. Business; Non-functionalAppliance metadata, disaster recovery, high availability, advance securityconfigurations, compliance requirements, automated scaling parameters,carbon footprint requirementsTOSCA1. Application &System ManagementSoftware binaries, PaaS application stack, Cloud Broker service orappliance, monitoring, logging, auditing, licensing, supportCIMI, SPML,SCIM0. Base RuntimeVirtual appliance including system configurations, additional metadata,session related dataOVF7
  • 8. 5. SAAS INTEROP Scenarios:• Service configuration• Bulk data transfer• Real time data access• Service aggregation• Service transfer Key points:• Service Catalog & self-service provisioning/configuration• Automation & web services to enable data exchange• Subscriber owns their data and can export via self-service• Porting involves end of life at source and new service at target• No relevant industry standards for service transfer8
  • 9. 6. COMMERCIAL FRAMEWORK Scenarios:• Cloud service provider selection• Contract negotiation• Ongoing use and transfer• Termination and reversetransition Key points:• Contractual obligations should consider specific drivers:• Service and Data Location• Intellectual property• Software Entitlement ManagementBusinessrequirementsRegulatorydriversCommercialdriversCommercial FrameworkServices Agreement/ Contract• Control environment• Data management, movement, return• Security, Privacy, Availability, Recoverability9
  • 10. Growing need for open, multi-vendor and interoperablesolutions for all Cloud Computing service modelsCollection of ODCA usage models describe interoperability &cloud service selection, negotiation, use and terminationlifecycleInteroperability includes portability and interconnectabilityperspectivesBig opportunity for standards and automationsolutions, especially moving up the stack with morecomplex IaaS, PaaS and SaaSKEY TAKE-AWAYS FROM THESE UM’S10
  • 11. StandardizedResponse ChecklistsAccelerate TTMShared PracticesDrive ScaleStreamlinedRequirementsAccelerate AdoptionAvailable to Members at: www.opendatacenteralliance.orgURL for Public content: www.opendatacenteralliance.orgINFORMATION AND ASSETS11
  • 12. www.opendatacenteralliance.orgInteroperability Across CloudsFrom engagement to real adoption andimplementationQUESTIONS12
  • 13. © 2013 Open Data Center Alliance, Inc. ALL RIGHTS RESERVED.