You've got some typos in your config file, but I'll assume they are copy/paste errors and not the root cause. (e.g., id for ip).
I confess, getting the networks set up along with the DNS on clearwater trips me up every time. I always learn something new. I think it is like this
eth0 = first interface. Always management. IP value is local_ip. If you only have one interface, then this is going to carry signaling as well and be public_ip too. Unless you are in a cloud and are using floating IP/VPC to make this particular node reachable by end users, in which case public_ip = your floater.
eth1 = second interface. Only exists in a signaling namespace. Treat the floating/VPC case as above. Otherwise public_ip is the IP of eth1 in this namespace. I'm not sure if you have to create eth1 in /etc/network/interfaces.d or just build the namespace and assign eth1 to it. My experience suggests the latter.
publicIP = the address that 'outsiders' use to reach nodes like bono.
privateIP = value of the node's internal IP. = local_ip. = IP of eth0.
Finally, IPs used with etcd seem to be mgmt interface IPs (the page on multiple network support doesn't say this). For chronos, it seems to want to use the signaling interface IP (despite the comment about using the value of privateIP).
--keller
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
