[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=59810#comment-59810 ] 

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

I agree on the fact that NIC needs to be node_type but we need to define proper relatoinship_type for them to state if is the default NIC (the one with the default gateway) and so on.
This will help the orchestrator to "manage" the Compute node knowing that it cannot be managed alone but it needs to be managed looking at some related nodes that represent NIC, volumes etc.
We need a property in the Compute node to instruct the orchestrator that it needs to treat this node in this way (we cannot count on the fact the it is a Compute type, there could be also other node_type that needs to be managed together).
Also the two attributes in my opinion are a too simple representation that I understand are helpful for the 95% of the cases and are useful for hackoing the orchestrator in a shortcut BUT ... we are defining a standard and in my opinion we need to express generic things in the proper way:
is not true that the VM will have always 1 public_ip and so what is the interoperable behaviour of the orchestrator when there is none or more than one? Either we state that in the attribute or we run the risk of having TOSCA files that depend on that attribute and could not properly work.
Same for private_IP.
Could we say that are array?
In this case they represent an alias for the orchestrator to go to the releted NIC nodes and look for the information there?


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