1. Objective Propose a simple and concise set of “Core” Entities and Relations for TOSCA useful for any application deployment in a cloud Enable users to easily subclass from Core versus having to invent top level objects Enable domain experts to easily define their own specialized entities and relations Assemble application stacks and topologies using relations with strong typing Enable template validation Don’t try to define entire set of subclasses ever needed. E.g. all operating system types, VM Image types, … or policy types or deployment artifact types Apply this to the SugarCRM usecase as a concrete example Focus on Iaas case now, and represent Paas case next

2. Notde Type Categories Core – Top level from which all other TOSCA entities are derived Basic – Common entities which used often enough that they should be defined in TOSCA to avoid proliferation of similar types – Realized by sub-classing Core entities Custom – Defined by users and domain experts to realize specific deployment needs (Not defined in TOSCA) – Realized by sub-classing Core or Basic entities

3. SugarCRM Service SugarCRM Usecase Zone1 WebServerTier Apache Web Server SugarCRM App PHP Module DBServerTier MySQL SugarCRM DB HTTP Client Application EndPoint HTTP Port 80 ContextPath:/SugarCRM Database client requires client credentials, DB Name, host and port Admin Access and/or Management Access possibly over separate isolated networks with different client credentials requires MySQL Client Endpoint Port 3306 Database content must be placed on storage of required capacity, availability and performance

4. SugarCRM Hierarchy WebTier: ScalableTier WebVM: VMImage CentOS5.4: OperatingSystem WebServer: ApacheWebServer SugarCRM App: ApacheWebApp PHP Module: ApacheMdule dependsOn DBTier: SingleNodeTier DBVM: VMImage CentOS5.4: OperatingSystem Database: MySQLDatabase SugarCRM DB: MySQLDatabase Content SugarCRM DB: MySQLDatabase Content SugarCRM: ApplicationContainer ConnectsTo Instance nameType name Each contained object represents the use of a hostedOn relation

5. Application Container Represents deployment of the application in the cloud Application lifecycle/management operations Represents the public/private communication boundary (access the application) Management scope for application SLAs, compliance, security

6. Tier Homogeneous set of identical computing elements Well defined scaling and availability semantics Provide EndPoints for other tiers and public network Consume EndPoints from other tiers and public network

7. Relation Type Notes A valid hostedOn hierarchy can be inferred by defining specific instances of the hostedOn relation with strongly typed ends. Multiple valid hierarchies may be possible The connectsTo relation enables resolution of components requiring or providing a desired capability or function The dependsOn relation implies that the presence of another component is required although it may not directly be hostedBy or connectedTo by the depending component

8. HostedComponent Represents a software component in a hostedOn hierarchy. E.g.: – WebApplication hostedOn WebServer – ELB hostedOn J2EEServer HostedComponents are containers – They may contain other HostedComponents The “root-most” HostedCompoment is hostedOn the VM/OS

9. Relations Types All relations strongly typed for validation and assembly HostedOn – Represents containment. E.g. one component hosts another DependsOn – One component requires the existence of another ConnectsTo – A component requires the functionality of another component. E.g. a WebServer requires a Database via a database connection with a specific protocol, port number and credentials – Built on top of semantics

10. See UML Diagram

11. SugarCRM Service SugarCRM Service Model Zone1 WebServerTier Apache Web Server SugarCRM App PHP Module DBServerTier MySQL SugarCRM DB MySQL ClientServer Connector Required MySQL EndPoint Provided MySQL EndPoint HTTP Client ContextPath:/SugarCRM HTTP Content EndPoint Port 80 HTTP EndPoint Database Server EndPoint propagates client credentials, DB Name, host and port client EndPoint (Web Server)