[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (TOSCA-90) Use Case: Describe applications with specific hardware requirements
Use Case: Describe applications with specific hardware requirements
-------------------------------------------------------------------
Key: TOSCA-90
URL: http://tools.oasis-open.org/issues/browse/TOSCA-90
Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
Issue Type: Task
Components: Interop
Environment: Use case for development against TOSCA-v1.0-cs01.
Reporter: Matthew Rutkowski
Assignee: Aaron Zhang
Aaron agreed to provide during the Interop SC meeting on 2013-04-08
Example:
Aaron agreed to provide during the Interop SC meeting on 2013-04-08
Notes:
Aaron: This is a consideration for some Telco domain services.
Matt: Need to further describe. How does this go beyond specifying additional node-types (perhaps derivative types to the ones we are looking to normalize) for IaaS components (implementations) that could be packaged within a service template?
Derek: These could be additional nodes in the template that describe specific provider infrastructure hardware. This would limit interoperability of the application.
Matt: Of course this would restrict the template to specific providers.
Reference:
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48504/New%20Scenarios%20for%20TOSCA%20from%20Huawei.pptx
--
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]