Mac Book Pro top Apps

Just got my MacBook Pro.  Here’s what I install on it:

- iphone SDK

- xcode

- mac ports

- Firefox!

- VMware Fusion

Will update this list as I get more acquanted with this guy.

Change GPFS to run over InfiniBand instead of Gigabit Ethernet (GbE)

I have a cluster where GPFS is running over the Gb Ethernet. To make it so that GPFS goes over InfiniBand Ido the following:

mmshutdown -a
mmchnode --daemon-interface=compute001-ib0 -N compute001

That did it for one node.  To do it for all nodes:

for i in $(nodels compute); do mmchnode --daemon-interface=$i-ib0 -N $i; done

Alternatively, I could have just made a spec file called /tmp/foo with the contents:

s01 --daemon-interface=s01-ib0
s02 --daemon-interface=s02-ib0

Then run:

mmchnode -S /tmp/foo

Once finished, I run mmlscluster and see that all the nodes that I wanted are now communicating over the InfiniBand.  GPFS is so easy!

Then, start things back up:

mmstartup -a

And you’re off to the races.

updating from SLES 10 sp1 to SLES 10 sp2

for some reason I’ve had to do a lot of updates lately of OSes…

SLES 10 SP1 is 2.6.16.53-0.16 kernel for my ppc nodes.

SLES 10 SP2 is 2.6.16.60-0.21

I did my update via yast.

This URL had some helpful info:

http://www.novell.com/support/viewContent.do?externalId=7000387

Trick:  Have to do a symbollic link:

cd /install/sles10.2/ppc/1/patches

ln -s ../suse .

Then you put this directory in yast:

http://mgmt/install/sles10.2/ppc/1/patches

Here is the yast configuration portion on the nodes you are updateing:

Software -> Installation Source -> Add –> specify URL -> http://<mgmt>/install/sles10.2/ppc64/1/patches

You’ll also need to add the SLES 10 SP2 base DVD in there as well.  Do the above, but put in http://<mgmt>/install/sles10.2/ppc64/1/ (no patches)

If you get that then you’ll have to accept the license.

Since mine had the old SP1 in the installation source I got rid of that.  The easiest was to use zypper:

c670e2p6:~ # zypper sl
# | Enabled | Refresh | Type | Name                                  | URI
–+———+———+——+—————————————+————————————————
1 | Yes     | Yes     | YUM  | SUSE_SLES_SP2-10.2-18-20090915-023741 | http://c670ep1/install/sles10.2/ppc64/1/patches
2 | Yes     | Yes     | YaST | SUSE Linux Enterprise Server 10 SP1   | http://9.114.95.67/install/sles10.1/ppc64/1
3 | Yes     | Yes     | YaST | SUSE Linux Enterprise Server 10 SP2   | http://c670ep1/install/sles10.2/ppc64/1

I removed the #2 entry:  zypper sd 2

From there I went back into yast and did Software -> Online Update

After stumbling through install directories a few times I finally was able to update everything.  I think yast is non-optimal and I’m a much bigger fan of Yum.

xCAT common mistake #1: /etc/resolv.conf

Many times I see a cluster set up with xCAT with a split brain idea of how the /etc/resolv.conf file is to be set up on the head node.

People say:  I want the head node to connect externally, so I need to have the nameservers in that file point to the external name servers.

This is sound logic, but then the node can’t resolve the IP addresses in the internal network of the cluster.  Sometimes, I see people say the way to get around this is to put the head node in /etc/resolv.conf as well.  But this just doesn’t work quite right.

The way that works best is to do the following:

1.  In /etc/resolv.conf place ONLY the management server and the cluster domain:

search cluster.net
nameserver 10.0.0.1

Note:  Make sure that this domain ‘cluster.net’ matches what’s in your site table!!!

2.  In the site table, add the EXTERNAL name servers to the forwarders:

‘forwarders’,’9.0.2.1,9.0.3.1′

3.  Run makedns
4.  Run service named restart

Huzah!  You will now be able to resolve everywhere!