[OASIS Issue Tracker] (TOSCA-277) How to map Acquired IP form the cloud?

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

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

Luca Gioppo commented on TOSCA-277:
-----------------------------------

Just to reboot this issue.
The proposed solution is based on these facts:
- in TOSCA I do not need to know the landing infrastructure just the orchestrator knows so I need to give him all the needed info
- need to specify that I need a compute node with a NIC on an internal network
- need to specify that I need a "IP node" (something new since there is nothing in the spec and is strange since this is a pretty common part but I could have missed and if so please point me in the right direction)
- need to be able to express the NAT mappings from the "IP node" and the NIC
- need to be able to express the firewall rules for the "IP node"
- need to be able to express the firewall rules for the NIC (and decide where is the proper place to place them in the NIC or in the operative system node)


> How to map Acquired IP form the cloud?
> --------------------------------------
>
>                 Key: TOSCA-277
>                 URL: https://issues.oasis-open.org/browse/TOSCA-277
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: NFV, Profile-YAML
>            Reporter: Luca Gioppo
>
> I use CloudStack Cloud environment and to expose a VM that is running in the cloud on internet I need to "acquire" a public IP address from an aviable network.
> This Address is not a new NIC of the machine but is used to port forward, on specific ports, the traffic.
> How do I map the acquired IP? is not a Port since is not a NIC.
> My idea is to use a relation between the Compute node and the Network Node.
> Obviously I need to declare the network node as "external" (see my previous issues) since the orchestrator does not have to "create" that network but just use it in the process of getting the IP.
> Another option, probably more easy to implement is to create an IP node since that will be easier to implement and than relate it to network and Compute.



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