[Swift-devel] [ZeptoOS] hostname returns none in Surveyor

Michael Wilde wilde at mcs.anl.gov
Sat Mar 3 21:39:39 CST 2012


Emalayan,

I wasnt paying much attention to the actual IP address returned by hostname in the zeptoos profile.

Since these are the addresses that Mosa will communicate over, I think you *do* want them to be the 192.168.1.* addresses of the nodes on the torus network (in other words tun0).

So, since both profiles return 192.168.1.64 for the tun0 IP, I think thats what you should use. So try replacing `hostname` in worker.pl with something like:

  `ifconfig | grep 192.168 | sed -e 's/^inet addr://' -e 's/ .*//'`

You may have to adapt this a bit to meet your needs. Im assuming that the only code that will uses these IPs is MosaStore.

- Mike


----- Original Message -----
> From: "Kazutomo Yoshii" <kazutomo at mcs.anl.gov>
> To: zeptoos at lists.mcs.anl.gov
> Sent: Saturday, March 3, 2012 8:52:00 PM
> Subject: Re: [ZeptoOS] hostname returns none in Surveyor
> Hi Emalayan,
> 
> The zeptoos profile returns the IP address of associated I/O node,
> which is kind of wrong in my opinion (influence of IBM CNK).
> ifconfig on compute nodes returns CN's IP address, which is correct.
> e.g. tun0 192.168.1.64
> 
> If you want to find associated ION's IP address from CNs,
> do something like this.
> 
> $ grep BG_IP= /proc/personality.sh
> 
> - kaz
> 
> On 03/03/2012 08:25 PM, Emalayan Vairavanathan wrote:
> > Hi All,
> >
> > I am trying to run some experiments in Surveyor. The software I am
> > using
> > gets the IP-address of compute-nodes using hostname command.
> >
> > With zepto-vn-eval/mosatest profile hostname command returns none.
> > But with zeptoos profile hostname returns the correct IP address.
> >
> > Is this due to some configuration issues in zepto-vn-eval/mosatest
> > profile?As a workaround I tired to use ifconfig with both profiles,
> > but
> > it seems ifconfig is not returning the correct IP address.
> >
> > Is there any command / files which I can used to retrieve the
> > hostname
> > on compute nodes? I have pasted the console output with both
> > profiles
> > below. Please let me know if you need more details.
> >
> > Thank you
> > Emalayan
> >
> >
> > =======================With zeptoos profile
> > ===============================
> >
> > / # hostname
> > 172.18.3.19
> > / #
> > / # cat /proc/sys/kernel/hostname
> > 172.18.3.19
> > / #
> > / #
> > / # ifconfig -a
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > tun0 Link encap:UNSPEC HWaddr
> > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> > inet addr:192.168.1.64 P-t-P:192.168.1.254 Mask:255.255.255.255
> > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:65535 Metric:1
> > RX packets:2662 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1772 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:500
> > RX bytes:140206 (136.9 KiB) TX bytes:125412 (122.4 KiB)
> >
> >
> >
> > =======================With zepto-vn-eval/mosatest profile
> > ===============================
> >
> > /etc # hostname
> > (none)
> > /etc #
> > /etc # cat /proc/sys/kernel/hostname
> > (none)
> > /etc #
> > /etc # ifconfig -a
> > eth0 Link encap:Ethernet HWaddr 00:80:46:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > eth1 Link encap:Ethernet HWaddr 00:80:47:00:00:00
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > sit0 Link encap:IPv6-in-IPv4
> > NOARP MTU:1480 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
> >
> > tun0 Link encap:UNSPEC HWaddr
> > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> > inet addr:192.168.1.64 P-t-P:192.168.1.254 Mask:255.255.255.255
> > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:65535 Metric:1
> > RX packets:965 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:627 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:500
> > RX bytes:50984 (49.7 KiB) TX bytes:50530 (49.3 KiB)
> >

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory




More information about the Swift-devel mailing list