Linux/Unix/Windows integration project Information Page

This page was last updated on 08-2-2006

 

 

 

WHAT WE HAD BEFORE THE PROJECT:

OUR GOAL:

WHAT WE HAVE DONE SO FAR:

SOFTWARE INSTALLED:

WHERE WE ARE NOW:

RECENT PROBLEMS ENCOUNTERED:

WHAT IS LEFT:

STATEMENT:

LINUX FAQ:

 

 

WHAT WE HAD:

(TOP)

 

The OLD UNIX system consisted of an NFS server that had 22 exports on 17 disks of varying sizes from 2 Gig to 72 Gig. These drives were single drives with no redundancy and most were out of warranty. When any drive had a problem the whole SCSI bus would hang and lock up the server, which would stop all UNIX machines from working because /usr/local is an export from the NFS server.  These drives contained all of the UNIX home directories and group storage for the UNIX research platform. The UNIX system also included Hypatia that maintained the samba shares, Tesla which is the font server and print server, and  Sunfire1 and Sunfire2 which were the general application machines running apps like pine, Netscape, mathematica, etc. Most of the apps are old and out of date. Sunfire1 is also the ssh entry point machine for the UNIX system. We also had three or four Solaris desktops left but over time most of the groups have added Linux machines to their research environment. We had two separate Linux machines that acted as servers for user accounts to two different groups of Linux research machines.  Many of the Linux machines maintained local user accounts which had to be synchronized with the UNIX system. We were up to 34 Linux research machines and 10 Linux desktops, not counting the HEP group that has their own Linux setup with a server and about 10 more desktops. Each group of Linux machines was set up by a different UNIX administrator so not everything was done the same on each system, like printing and access to common or scratch space, which made administration difficult.

 

Add in the Windows accounts, and password synchronization or user account synchronization became very difficult. Adding a new user may have meant making the same user on up to 5 machines (and not all of them were made correctly). Users may have had to change their password in up to three or more places just for physics.

 

 

 

OUR GOAL:

 (TOP)

 

The goal of the new system is to provide a useful, easy to use, and stable research platform that does not take a lot of time to administer. The Physics department purchased a 5 terabyte SANS (storage Area Network) so all of the data in the department would be on redundant disks and be in one place. We also have purchased Vintela Authentication Services (VAS) software for the UNIX/Linux system that allows Linux machines (which are based on Redhat) and Solaris machines to authenticate against Windows Active Directory. With this system we will only have to make a user once on the Windows system and they will be able to log into any machine they have permissions on with the same username and password. Also, changing a password can be done from any OS. All of the data will be in one place on the SANS making it easier to backup.

 

 

WHAT WE HAVE DONE:

(TOP)

 

For the last year we have been working on moving away from the old UNIX system to a newer system based on Linux.

 

What we have done so far:

  1. Settled on Scientific Linux as our research platform.  Scientific Linux is based on RedHat enterprise edition OS and is maintained by CERN and FERMI Labs. It is free and has installs for x86, x64, and ia64 hardware.
  2. Tested VAS software with active directory.
  3. Tested VAS software with Scientific Linux.
  4. Tested VAS software with Solaris.

a.                Determined that our UNIX system was very old and did not have PAM (Pluggable Authentication Module) support installed on most of the authentication methods.

b.                Installed SSH with PAM support on the UNIX system.

c.                Tested SSH with VAS on the UNIX system and determined that it does work.

d.                Determined that XDMCP (eXceed's method of authentication) did not have PAM support and that it was very difficult to install on all of the UNIX machines. So all UNIX machines will have SSH access only using VAS.

 

  1. Decided to put the Linux home directory as a sub directory of the Windows home directory that way the files stayed separate from each other but where easy to access from either system.
  2. Installed the SANS and a Cluster of three nodes. The cluster will provide the NFS shares to the Linux machines as well as the Windows shares. By having the NFS server on a cluster we have redundancy and uptime benefits.
  3. Created a new entry point machine named linux1. This machine is to replace sunfire1 as the ssh entry point machine.
  4. Setup a CUPS print server that sends all print jobs through our print monitoring software so we can keep track of the printing on the Windows and Linux system.
  5. Created a Scientific Linux system image with all the software that was requested installed. These include:

a.                Mathematica 5.2 (Still needs font server update to work from Windows)

b.                Ghostview

c.                Povray

d.                Intel Fortran 9.0 with mkl

e.                Intel C++ 9.0 (Soon)

f.                Gnuplot

g.                Acrobat reader 7.0

h.                Xdpf

i.                Xmgr

j.                Xmgrace

k.                Mozilla

l.                Open Office

m.                Latex

n.                VMD

o.                Xview

p.                Sm (soon)

q.                Mplayer

r.                Plus all of the standard software and browser plug-ins

 

 

  1. Installed VAS client software on all Linux machines and     Sunfire2.
  2. Set up active directory OU’s and group policies to limit access to research machines and to automatically provide access to common storage space.
  3. Started moving users to the new system which requires copying all their data from their UNIX home directory and sometimes multiple Linux home directories to their Windows home directory under the linux sub folder. (O:\linux\) Activated their new account in Windows and remove their account on the old system. Then we set the correct permissions on the home directory and test the account.
  4. Built a new font server.
  5. Made Xwindows work on the Terminal server.
  6. All known UNIX have been moved.

 

 

 

 

WHERE WE ARE:

(TOP)

 

AS of the 1st of June we have moved 52 users and have created 7 special use users. We have moved approximately 220GB of data with an estimate of about 0GB more to move. There are approximately 0 users left to move from the old system (Not counting integrating the HEP Linux system).

We have also added 6 new Linux research machines (with 3 more on the way) and 3 Linux desktops used for data collection. 

 

 

 

RECENT PROBLEMS ENCOUNTERED:

(TOP)

 

When moving the first few users there was a problem with the file permissions on the old server so the script did not copy all of their files. Since then, we have modified the script to check the disk usage after the copy to verify that all files were copied.

 

We had an issue with being able to remove the x bit from files in the new home directory. A solution was found and by the 16th of June all home directories should be updated.

 

One of the nodes in the cluster had a problem with authentication of the NFS shares.  This caused a “permission denied error” to randomly occur. The problem node has been taken out of production to be rebuilt. The mapping service has been linked to the failover setting so if it happens again the service will automatically move to a functioning node.

 

 

Other problems people have reported are that the printer names have changed and that the home directory location is different. A few scripts may need to be changed to reflect the new location which is  now /lhome/username/linux/  .

 

 

 

 

 

 

WHAT IS LEFT:

(TOP)

 

  1. Integrate HEP Linux users and machines.
  2. Reimage all the research machines so they all have the same OS and software.
  3. Data needs to be moved around. We have currently moved all of the UNIX home directories into the Windows home directories no matter how large they were. In a few weeks we will need people to reduce there home directory space to under 2GB because the home space is to be divided up evenly within the department. The extra data will need to be moved to the group’s common space which is 100GB each. I will explain this later when we are ready for that to happen.

 

 

STATEMENT:

(TOP)

 

The move process is very individualized, so if you have any problems or suggestions let me know and I will be glad to help call Larry 785-532-6810.

I also have a list of the Frequently Asked Questions at Linux FAQ.