I tested the proposed update-based solution and it does *not* seem to
work:
* Added the avahi-publish upstart job
* Restart cluster
* Cluster has:
$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:13:20:f8:4d:11 brd ff:ff:ff:ff:ff:ff
inet 169.254.169.254/32 scope link eth0:metadata
inet 192.168.0.127/24 brd 192.168.0.255 scope global eth0
inet6 fe80::213:20ff:fef8:4d11/64 scope link
valid_lft forever preferred_lft forever
* Launch UEC node install : euca_find_cluster says 192.168.0.127:8774
* On Cluster, add an IP address: sudo ip addr add 192.168.0.230 dev eth0 label
eth0:pub
* Cluster now has:
$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:13:20:f8:4d:11 brd ff:ff:ff:ff:ff:ff
inet 169.254.169.254/32 scope link eth0:metadata
inet 192.168.0.127/24 brd 192.168.0.255 scope global eth0
inet 192.168.0.230/32 scope global eth0:pub
inet6 fe80::213:20ff:fef8:4d11/64 scope link
valid_lft forever preferred_lft forever
* Launch UEC node install: euca_find_cluster now says 192.168.0.230:8774
You still have to explicitly disable IP address publication for it to work:
Add "publish-addresses=no" to [publish] section in avahi-daemon.conf
Then new addresses won't be published and resolution will always work.
--
When installing a node, euca_find_cluster fails to locate the cluster
controller if instances are running
https://bugs.launchpad.net/bugs/458904
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
