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-235) Endpoint capability needs support for Fixed IPs


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

Matthew Rutkowski  commented on TOSCA-235:
------------------------------------------

Now that we have LoadBalancer Node Type and Endpoint.Public we can show examples of both "floating" IPs which declare no ip_address and fixed IPs that declare (one or more fixed IPs).

Note: we would discourage use of Fixed IPs as this is not compatible with the desired (auto)scaling  characteristics of Cloud compute resources.

> Endpoint capability needs support for Fixed IPs
> -----------------------------------------------
>
>                 Key: TOSCA-235
>                 URL: https://issues.oasis-open.org/browse/TOSCA-235
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Matthew Rutkowski 
>
> The tosca.capabilities.Endpoint has no way (e.g., property) to declare a Fixed IP.  We could choose to use the "ip_address" attribute as a property and when it is filled in treat it as a Fixed IP.   
> Note: This ip_address property could also be used to reference a known Floating IP from a public network if we have a way to declare it as "floating".



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