Github user geomacy commented on the issue:
https://github.com/apache/brooklyn-server/pull/529
I tested this successfully: put a brooklyn on ibm-bluebox-lon-pub, and
used it to deploy the blueprint
```
location: ibm-bluebox-lon-pub
services:
- type: server
name: custom
brooklyn.initializers:
- type:
org.apache.brooklyn.location.jclouds.BasicLocationNetworkInfoCustomizer
brooklyn.config:
mode: ONLY_PRIVATE
- type: server
name: default
# implicit use of the default network info customizer.
```
i.e. both servers are deployed to the same location as brooklyn, which is
configured to create a public address
(`jclouds.openstack-nova.auto-create-floating-ips: true`).
The server 'custom' above was assigned a host address on the private
network, while the 'default' one was assigned it on the public network:
```
$ for ename in custom default ; do printf "%s " ${ename} ; br app app1 ent
${ename} sensor host.address ; done
custom 10.101.1.232
default 169.50.81.104
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
