Matt, I confirmed that if you stop and start an instance again, the IP addresses change. The private and in fact the public IPs changed on all my instances after I had started them again. This redoing DNS and going back to each one and redo ing the config file ;-(
This got me thinking. 90% of the config file is exactly the same for all the nodes. The only thing that changes is the local, public IP and public hostname. The public IP and host name are already in DNS, so this is a duplication and the public IP and name do not get used on the internal servers as far as I know. Would it make sense to remove this from the config file and rely entirely on DNS? You already dictate that the DNS entries have fixed names off the TLD like hs, homer, etc. so this would tie the private and public IPs to the names for all servers without the need to explicitly configure it in DNS and also in the config file. Not sure how much work this is, but it would simplify the manual setup and also I think the chef updates, since all info goes into DNS and not also into the config files. Let me know what you think? Thanks Des Hartman
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
