[OASIS Issue Tracker] (TOSCA-176) DEFER - Add connectivity ability to Compute

[ https://issues.oasis-open.org/browse/TOSCA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52570#comment-52570 ] 

Matthew Rutkowski  commented on TOSCA-176:
------------------------------------------

TOSCA TC approved deferment of this issue at the 2014-11-20 meeting.  See https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/54595/TOSCA%20Minutes%202014-11-20.docx

> DEFER - Add connectivity ability to Compute
> -------------------------------------------
>
>                 Key: TOSCA-176
>                 URL: https://issues.oasis-open.org/browse/TOSCA-176
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Moshe Elisha
>            Assignee: Moshe Elisha
>
> This issue is suggesting to add the ability for the TOSCA container to connect to a Compute in order to manage it and invoke life-cycle operations.
> In order to invoke life-cycle operations (such as start, stop, uninstall) we are missing the connectivity information from the tosca.nodes.Compute.
> We would like to think of a way to add connectivity params to a compute such as :username, keypair and script working directory.
> We have two options that we thought about to express the additional information. One is based on node type inheritance and the other is based on connectivity information as a capability.
> In NFV use-cases, we do see a need for a Compute that has no connectivity information - for example, the Compute might be an appliance VM (for example, firewall) that has everything built-in inside the image and there is no need or way to connect to that VM.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)