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-277) How to map Acquired IP form the cloud?


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

Sridhar Ramaswamy commented on TOSCA-277:
-----------------------------------------

@Luca - based on the description, I believe you are describing "Floating IP" (or Elastic IP as AWS calls it) in cloud environments. This is supported in OpenStack and AWS (possibly others). So this is a valid ask and we need this supported in the Simple YAML Profile. IMO, "tosca.nodes.network.Port" node_type is the appropriate place to define this as it already has the internal ip-address. See Sec 7.5.2 below,

http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/csprd02/TOSCA-Simple-Profile-YAML-v1.0-csprd02.html#_Toc445238280

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


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