OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (TOSCA-2) Review Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest


    [ http://tools.oasis-open.org/issues/browse/TOSCA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29652#action_29652 ] 

Tobias Kunze  commented on TOSCA-2:
-----------------------------------

Here is a sample YAML manifest as used on Red Hat's OpenShift PaaS. (See http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45328/manifest.yml.pdf for a PDF version that preserves syntax highlighting.)

--------------------------
Name: mongodb-2.0
Display-Name: MongoDB v2.0.0 (x86-64)
Description: Cartridge packaging MongoDB
Version: 2.0.0
License: ASL 2.0
Vendor:  mongodb.org
Provides:
  - "mongodb"
  - "mongodb(version) = 2.0.0"
Requires:
Conflicts:
Native-Requires:
  - mongodb-server
  - mongodb-devel
  - libmongodb
  - mongodb
Architecture: x86-64
Reservations:
  - MEM >= 1GB
Profiles:
  basic:
    Provides: mongodb-basic-mode
    Reservations:
      - MEM >= 100MB
    Components:
      mongod:
        Publishes:
          get-db-connection-info:
            Type: "NET_TCP:db:connection-info"
          get-mongo-connection-info:
            Type: "NET_TCP:db:mongodb"
    Groups:
      singlenode:
        Components:
           mongod-process: mongod
        Scaling:
          Min: 1
          Max: 1
  replica-sets:
    Provides:  mongodb-replica-sets
    Reservations:
      - MEM >= 1GB
    Components:
      router:
        Subscribes:
          set-replicaset:
            Type: "NET_TCP:db:mongodb:replica-servers"
          set-doc-root:  #  Best-practices: run router where appserver runs.
            Type: "FILESYSTEM:doc-root"
      configsvr:
        Publishes:
          get-replicaset:
            Type: "NET_TCP:db:mongodb:replica-servers"
          get-arbiter:
            Type: "NET_TCP:db:mongodb:arbiter"
          get-db-connection-info:
            Type: "NET_TCP:db:connection-info"
          get-mongo-connection-info:
            Type: "NET_TCP:db:mongodb"
        Subscribes:
          set-replicaset-member:
            Type: "NET_TCP:db:mongodb:replica"
      replicaset_member:
        Publishes:
          get-replicaset-member:
            Type: "NET_TCP:db:mongodb:replica"
    Groups:
      arbiter:
        Components:
          arbiter_config_server: configsvr
          arbiter_replica: replicaset_member
        Scaling:
          Min: 1
          Max: 1
      config_servers:
        Components:
          config_server: configsvr
      routers:
        Components:
          router: router
      replica_set:
        Components:
          replica: replicaset_member
        Scaling:
          Min: 2
          Max: -1
    Connections:
      arbiter-config-server-router-connections:
        Components:
          - arbiter_config_server
          - router
      arbiter-replica-config-server-connections:
        Components:
          - arbiter_replica
          - arbiter_config_server
      config-server-router-connections:
        Components:
          - config_server
          - router
      replica-set-config-server-connections:
        Components:
          - replica
          - config_server
    Start-Order:  [arbiter_config_server, arbiter_replica, config_server, router, replica]
    Group-Overrides: [ config_servers == replica_set ]

  master-slave:
    Provides:  mongodb-master-slave
    Components:
      master:
        Publishes:
          get-master:
            Type: "NET_TCP:db:mongodb:master"
          get-db-connection-info:
            Type: "NET_TCP:db:connection-info"
          get-mongo-connection-info:
            Type: "NET_TCP:db:mongodb"
        Subscribes:
          set-slave:
            Type: "NET_TCP:db:mongodb:slave"
      slave:
        Publishes:
          get-slave:
            Type: "NET_TCP:db:mongodb:slave"
          get-db-connection-info:
            Type: "NET_TCP:db:connection-info"
        Subscribes:
          set-master:
            Type: "NET_TCP:db:mongodb:master"
    Groups:
      master:
        Components:
          master: master
        Scaling:
          Min: 1
          Max: 1
      slaves:
        Components:
          slaves: slave
    Connections:
      master-slave-connections:
        Components:
          - master
          - slaves
    Start-Order:  [master, slaves]
Default-Profile: basic


> Review Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-2
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-2
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Spec
>            Reporter: Diane Mueller
>            Assignee: Diane Mueller
>
> Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest 
> Before going too deep with creating a interoperable portable framework for supporting complex application deployments on the cloud.  TOSCA should ensure that the simple web applications, those using common web frameworks like spring, play, django, rails, psgi, or node.js, have basic requirements of apache or nginx as web servers,  and need to deploy a mysql, redis, mongodb or other open source databases - are easily supported with whatever approach we decide to take. Many aspects of an application  can be affected by cloud infrastructure that one chooses to install the application on. This process can be made easier and others more difficult depending on the level of complexity involved in specifying the the apps configuration and deployment requirements  - even for the simplest of web applications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]