[ https://issues.apache.org/jira/browse/BROOKLYN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838426#comment-15838426 ]
Geoff Macartney commented on BROOKLYN-429: ------------------------------------------ This PR may be relevant - https://github.com/apache/brooklyn-server/pull/529, might even fix this problem? > Brooklyn doesn't select correct public IP in OpenStack > ------------------------------------------------------ > > Key: BROOKLYN-429 > URL: https://issues.apache.org/jira/browse/BROOKLYN-429 > Project: Brooklyn > Issue Type: Bug > Affects Versions: 0.11.0 > Environment: Openstack Mitaka > Reporter: Duncan Godwin > Priority: Minor > > When launching a VM in an OpenStack instance from a Brooklyn hosted in the > same OpenStack private network, if > {{jclouds.openstack-nova.auto-create-floating-ips: true}} is selected to > create a floating public IP, this IP is not the one used in {{host.address}}. > This means that external services are unable to use values such as > {{main.url}} outside of the private OpenStack network. > Presumably this is because the logic to select which IP is used for the > public address does not properly take into account this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)