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] Updated: (TOSCA-113) Explore Software Environment Centricity vs. Application Driven


     [ http://tools.oasis-open.org/issues/browse/TOSCA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krishna Raman updated TOSCA-113:
--------------------------------

    Description: 
Explore if TOSCA specs should be built from an application driven point and only allow definition of connections between components or it should allow definition of lower level hardware requirements as well.

Hardware requirements may include networking details, VM requirements etc.

---

Use Case: Network connection between application components

Scenario: An application has 2 components Java and MySQL which need to communicate with each other.

Option 1: Application just specifies the 2 components and that there must be a connection between the two. Possibly specifying the protocol and port number on the MySQL side.
Option 2: Application specified additional details including # of cores, memory, Firewall configuration etc. of MySQL component in addition to what is specified in Option 1.

---

Will supporting these hardware requirements be mandatory? How do we allow TOSCA to be generic enough to accomodate PaaS platforms that abstract away the hardware details from the application?

  was:
Explore if TOSCA specs should be built from an application driven point and only allow definition of connections between components or it should allow definition of lower level hardware requirements as well.

Hardware requirements may include networking details, VM requirements etc.

Will supporting these requirements be mandatory? How do we allow TOSCA to be generic enough to accomodate PaaS platforms that abstract away the hardware details from the application?


Added some additional details

> Explore Software Environment Centricity vs. Application Driven
> --------------------------------------------------------------
>
>                 Key: TOSCA-113
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-113
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Spec
>            Reporter: Krishna Raman
>
> Explore if TOSCA specs should be built from an application driven point and only allow definition of connections between components or it should allow definition of lower level hardware requirements as well.
> Hardware requirements may include networking details, VM requirements etc.
> ---
> Use Case: Network connection between application components
> Scenario: An application has 2 components Java and MySQL which need to communicate with each other.
> Option 1: Application just specifies the 2 components and that there must be a connection between the two. Possibly specifying the protocol and port number on the MySQL side.
> Option 2: Application specified additional details including # of cores, memory, Firewall configuration etc. of MySQL component in addition to what is specified in Option 1.
> ---
> Will supporting these hardware requirements be mandatory? How do we allow TOSCA to be generic enough to accomodate PaaS platforms that abstract away the hardware details from the application?

-- 
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]