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] (TOSCA-276) F.5.2 tosca.nodes.network.Port is a NIC and we call it Port


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

Luca Gioppo commented on TOSCA-276:
-----------------------------------

Revising the YAML standard I can see that we use "port" in both concepts and this is not good.
Overloading apart we cannot have the same work in the same document mean two different things (at least not in a standard).
Since the most known "application" approach give to "port" the meaning of an endpoint of communication in an operating system.
As such this should be part of the OS node and not of the compute.
The "physical port connector" in my opinion should not be part of the spec since we have no interest in mapping the connector, but we are interested in mapping the Network Interface Controller that has a lifecycle of its own and can be a virtual thing that gets attached to the Compute node and has a multiplicity of 0..n
This would also help the networking part of the standard since if I have to define that I want 3 NIC on a Compute node the only approach I have is defining 3 NIC nodes to relate to the Compute

> F.5.2 tosca.nodes.network.Port is a NIC and we call it Port
> -----------------------------------------------------------
>
>                 Key: TOSCA-276
>                 URL: https://issues.oasis-open.org/browse/TOSCA-276
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: NFV, Profile-YAML
>            Reporter: Luca Gioppo
>
> As stated in the documentation the F.5.2 tosca.nodes.network.Port is a NIC but we call it Port that is something very different.
> Proposal is to change the name of this node to NIC and not Port to help also better understanding.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]