[OASIS Issue Tracker] (TOSCA-255) Refactor NIC concept in Compute

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Luca Gioppo commented on TOSCA-255:
-----------------------------------

Proposal to remove the endpoint capability and use a NIC node either contained or related to the Compute

> Refactor NIC concept in Compute
> -------------------------------
>
>                 Key: TOSCA-255
>                 URL: https://issues.oasis-open.org/browse/TOSCA-255
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Luca Gioppo
>            Priority: Critical
>
> The Compute needs a set of properties to enable libraries like JClouds or similar to create a complex VM: i.e. A VM with a specific service offerings (CPU+RAM) different volumes, 3 NIC linked to 3 different network offerings.
> We need to have these expressed as properties.
> The private_ip and public_ip are wrong concept not enough general to allow the generic deployment.



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