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

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

But doesn't this generate confusion?
Doesn't "port" usually have another meaning?
When I read port I imagine port 80 or a "port on a NIC".
The meaning in the description is NIC.
Could another name be better to obtain the abstraction needed?
I do not understand why we need to call the NIC with a different name and with the one already used for the port.

> 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: 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]