cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Mikhailovsky <and...@arhont.com>
Subject Re: CoreOS/Docker - a new blog series
Date Tue, 17 Feb 2015 12:29:42 GMT
> > 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? 

Thanks 

Andrei 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message