On Feb 17, 2015, at 1:29 PM, Andrei Mikhailovsky <[email protected]> wrote:
>>> etcd: >>> name: <server-name> >>> discovery: https://discovery.etcd.io/<token> >>> addr: <private_ip>:4001 >>> peer-addr: <private_ip>:7001 >>> >>> You need to change the values between <> to suite your environment. >>> >>> I've read that there should be variable $private_ipv4 to >>> automatically inject your private IP, however, it doesn't seem to >>> work for some reason. Will need to investigate further >>> > >> try with $public_ipv4 > >>> Andrei >>> > > Seb, > > I've tried to use the $public_ipv4 and it seems to have made the sabstitube > to the public ip. At least I can see the messages in journal: > > Feb 17 12:15:10 coreos-04022015-6 etcd[614]: [etcd] Feb 17 12:15:10.537 INFO > | coreos-04022015-6 joined the cluster via peer 10.0.1.45:7001 > Feb 17 12:15:10 coreos-04022015-6 etcd[614]: [etcd] Feb 17 12:15:10.539 INFO > | etcd server [name coreos-04022015-6, listen on :4001, advertised url > http://178.248.xxx.xxx:4001] > Feb 17 12:15:10 coreos-04022015-6 etcd[614]: [etcd] Feb 17 12:15:10.540 INFO > | peer server [name coreos-04022015-6, listen on :7001, advertised url > http://178.248.xxx.xxx:7001] > > However, I would like to use the private ip range for that. The substitution > did not work when i've tried the $private_ipv4. Is it working you you? > I haven't looked deep into it, my guess is there might be a problem with the cloudstack metadata. Can you check if private_ipv4 exists and is what you expect it to be: curl your virtual router to get the metadata: http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.4/api.html?highlight=metadata#user-data-and-meta-data I have a hunch it's not defined and thus coreOS does not work with it. I could be wrong but could be a cloudstack bug. > Thanks > > Andrei
