1 / 31

TOSCA* & The Government Sector

TOSCA* & The Government Sector. Tobias Kunze, Red Hat. * T opology and O rchestration S pecification for C loud A pplications. Motivation. Why Standards?. Use Cases. Use Cases Addressed. Deploy: Dependency resolution, Install, Configuration, Orchestration

xia
Download Presentation

TOSCA* & The Government Sector

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. TOSCA*& The Government Sector • Tobias Kunze, Red Hat * Topology and Orchestration Specification for Cloud Applications

  2. Motivation

  3. Why Standards?

  4. Use Cases

  5. Use Cases Addressed • Deploy: Dependency resolution, Install, Configuration, Orchestration • Operate: Start, Stop, Patch, Scale • Migrate: Disaster Recovery, Geo-Redundancy, Cost Optimization, Promotion

  6. ServiceCatalog Other Scenarios: Creating a Market For Cloud Applications 3. Browseand Select 5. Use 4. Provision Service Instance 2. Publish Service Template 1. Create

  7. How it Works

  8. What Is “(Cloud) Service Template” All About? • A new language (“metamodel”) to specify • the building blocks of your application • the management functions thesebuilding blocks offer to be managed • the relations between these building blocks • Collection of node types and relationship types(for reuse purposes) • the procedures to follow in order to manage your application as a whole NodeTypes Topology(Template) Rel.shipTypes (Cloud) Service Template GroupTemplate Plans

  9. Graphical Representation Service Template Node Types Topology Template Node Type type for Interfaces Properties Relationship Template Relationship Types Relationship Type type for Properties Node Template Plans Group Template

  10. Script - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Create Cluster WebSphere Cell How Plans and Nodes Fit Together • Task of a plan refers to interface of a topology node • Topology node specifies all interfaces offered to manage it • Interface is bound to a concrete implementation • Implementation already available at providers side, or • Implementation is copied from somewhere, or • A standardized Cloud Interface (Iaas, PaaS, SaaS) is used, or ... … … …refers to… … …bound to…

  11. More Colorful… Topology Orchestration (Plans)

  12. ---- ---- ---- ---- ---- ---- ---- ---- ---- OVF OVF OVF Refined View How ... With ... BPEL EAR (EJBs,…) Scripts Workflows The business processes of the application (BPEL, BPMN, Human Tasks,…) The business logic of the application, e.g. EJBs, JSPs, JPEG,… The images of the middleware (DB2, Websphere,…) required to run the application (Existing) scripts used by task of plans to manage the cloud application (Existing) workflows used by subprocess-tasks of plans

  13. Baseline • TOSCA is modular and composable • It does not reinvent the wheel, i.e. it uses existing standards wherever possible • E.g. WSDL, BPMN, OVF,…

  14. The Service Template <ServiceTemplate …> <Extensions/>? <Import />* <Types/>? ( <TopologyTemplate/> | <TopologyTemplateReference/> )? <NodeTypes/>? <RelationshipTypes/>? <Plans/>? </ServiceTemplate> YAML as well

  15. Effort

  16. History Industry consortium formed (IBM, SAP, Red Hat, CA, Citrix, WSO2) Addt’l members: Capgemini, Cisco, Citrix, EMC, NetApp, PwC, Software AG, Virtunomic Charter submitted to OASIS Call for Participation Renamed TOSCA First TC meeting May 2011 Sep 2011 Oct 2011 Nov 2011 Dec 2011

  17. Members

  18. Public Draft Candidate Standard Candidate Standard Future Public Review Public Review Initial Draft Draft 2 … Draft n Jul 2012 Oct 2012 Nov 2012 Dec 2012 Mar 2012 Aug 2012 Sep 2012

  19. Q&A

  20. Appendix: Examples

  21. WebSphere Process Server …and this is a bit more clomplex… WebSphere Cell DB2 Server BPEL Files EJBs WSDL Files Example: High Level View Node Template uses deployedOn Relationship Template implementedby deployedOn requires deployedOn requires

  22. Properties, e.g.: WAS install location, Profile name, Node name WAS ND DeployMgrNode DB2 Database Instance IHS Node WAS ND Managed Node Application Server Instance WebSphere Cell DB2 Server WebSphere Cell Cluster DB2 Server Properties, e.g.: ports, servername, weight exists Example: WebSphere Cell Refined 1..* "cluster" 1..* "database"

  23. WAS ND DeployMgrNode WebSphere Process Server IHS Node WAS ND Managed Node Application Server Instance DB2 Database Instance WebSphere Cell Cluster DB2 Server BPEL Files EJBs WSDL Files Example: Overall Topology Template 1..* 1..*

  24. WebSphere Process Server WebSphere Cell DB2 Server BPEL Files EJBs WSDL Files Example: Amazon uses deployedOn implementedby Amazon deployedOn requires deployedOn requires

  25. WebSphere Process Server WebSphere Cell DB2 Server BPEL Files EJBs WSDL Files …Which is the “Interoperable Service Templates” Scenario (see later) Amazon

  26. WebSphere Process Server DB2 Server (ApplicationData) WebSphere Cell DB2 Server (WAS Data) WebSphere Cell BPEL Files EJBs WSDL Files Example: Amazon – Refined Scenario uses Implemented by deployedOn On Premise Amazon deployedOn requires requires requires

  27. WebSphere Process Server WebSphere Cell DB2 Server (WAS Data) DB2 Server (ApplicationData) WebSphere Cell EJBs WSDL Files BPEL Files Example: Amazon – Refined Scenario(Details) • The Web Services required by the BPEL processes are hosted on premise • The EJBs (e.g.) implementing the Web Services are deployed on WebSphere hosted on premise • The application data of the WS/EJBs are stored in DB2 on premise • This ensures compliance with data privacy/confidentiality rules • Process Server etc is installed and managed at Amazon’s EC2 • The corresponding middleware is provided as AMIs • The process models are deployed on Process Server • Process Server maintains state data in DB2 also running in EC2 uses Implemented by deployedOn On Premise Amazon deployedOn requires requires requires

  28. WebSphere Process Server WebSphere Cell DB2 Server BPEL Files WSDL Files Example: Reusing Existing Services • Only the processes and required middleware is managed on a “known” cloud • The Web Services needed by the BPEL processes are reused “wherever” they are • The existing Web Services are bound to the BPEL process by the established mechanisms • Specifying binding details can be part of the build plan of the application’s Service Template (.ste) „somewhere1“ WS1 uses deployedOn bound to „somewhere2“ WS2 deployedOn requires … requires WSn „somewheren“

  29. Netweaver Oracle SAP Workflow BPEL Files EJB WSDL Files Example: SAP uses deployedOn implementedby SAP deployedOn requires deployedOn requires

  30. .NetAssemblies .Net SQL Server BizTalk BPEL Files WSDL Files Example: Microsoft uses deployedOn implementedby Azure deployedOn requires deployedOn requires

  31. Netweaver Oracle SAP Workflow BPEL Files EJB WSDL Files Example: Different Hosters of a Particular Application uses IBM deployedOn AT&T implementedby T-Systems deployedOn ... requires deployedOn requires

More Related