10525fa19d32a5ad9e4067a2436d0d4d.ppt
- Количество слайдов: 10
Site Report Royal Holloway Sukhbir Johal Simon George Barry Green RHUL 1
Hardware ~30 Desktop PC’s ranging from 300 MHz K 6 to XP 2400+ Athlon mostly RH 7. 3, few Win. XP ~12 Desktop PC’s 450 K 6 – 1700 Athlon for ATLAS test bed RH 7. 3 ~24 Laptops both personal and department-owned RH 7. 3, 9, Fedora and Win. XP ~6 PC servers RH 7. 3 (one RH 6. 0) – mostly Athlon XP 2000 -3000 NFS, NIS, Firewall, Web Server, etc. 1 PC server RH 7. 3 with 64 bit kernel on a Athlon 64! as yet unsuccessful with Fedora 64 bit ~2 PC servers Windows 2000 Native Active Directory Terminal server (Citrix/ICA), Office, VB RHUL 2
Hardware continued. . 3 Raid servers 2. 0 TB array running RH 8 (2 will become SE’s for new Farm) user scratch volume, home backup 1 Sun E 450 Solaris 8 Home (NFS) 1 Sun E 250 Solaris 8 Babar 1 Sun. Blade 100 Solaris 8 Mentor (CAD) RHUL 3
Compusys Farm 75 nodes 2 x Intel Xeon Processors 3 Ghz 80 GB HDD, 1 GB RAM RH 7. 3 1 Master node 2 x Intel Xeon Processors 3 Ghz 2 x 80 GB HDD, 2 GB RAM RH 7. 3 Failover master node, 1 AIT 2 tape unit HP gigabit ethernet throughout Console switches Good experience with Compusys RHUL Grid: 1 LCFG install server 1 CE pbs interfaces with pbs on master node of farm 2 SE 2. 0 TB each (to be installed next week) RHUL 4
Network • Mostly Switched 100 Base. T to desktops, 1000 Base. T to servers • Connected to college 2 Gb ring via 1 Gb switch on VLAN • We are not firewalled by the college. • Our firewall is a default DENY setup • Laptops on 11 Mb wireless network and 100 Mb ethernet • Currently experimenting with a gateway/router for a private wireless subnet for laptops Network security • College suffers badly from worm epidemics • Mainly due to badly managed staff machines at home: • connecting via VPN from home or infected laptops brought in to work • We haven’t had an incident (yet) on the HEP network, but if the campus network is overrun we still suffer the consequences RHUL 5
Issues: • Hardware Specification Laptop/desktop - Linux compatibility • Laptop updates - use of Microsoft SUS for Win OS’s and Yum for RH • Laptop backup strategy • Security - physical and network • Linux releases RHUL 6
Projects: • Replacing aging desktop PCs • Replace 15 machines at once to get economies of scale • Buy pre-built to our spec • 5 x PCI slots, 1 x AGP slot • We decided on the following spec: • Supports AMD Athlon XP K 7 VTA 3 (full ATX motherboard) CPUs up to 3000+ • 333 MHz FSB 1. 44 MB Floppy • on board 10/100 Mbps LAN AMD Athlon. XP 2400+ CPU • on board audio 256 MB DDRR PC 2700 RAM • 6 USB 2. 0 Ports (4 at rear, 2 at front) 40 GB HDD 7200 rpm • 2 DIMM Slots (max. 2 GB) 16 x DVD ROM DDR PC 2700 Radeon 7000 AGP 32 MB graphics card • 1 x Serial Port, 1 x Parallel • Competitive quotes from companies like: Port Midland, BBN, Savastore, Nsysonline, Aligatortech, Pentathlon • Cost <£ 200 each RHUL 7
Projects: • Remote windows update management: • Critical security issue for group laptops • Tried MS SUS 1 (too buggy) and MBSA (useless and discontinued) • Waiting for Microsoft SUS release 2 which seems to have a lot more features and is more stable for laptop updates. • Looking at Microsoft Services for Unix (SFU 3. 5) Provides interoperability of Active Directory and NIS NFS Alternative to Samba? RHUL 8
Linux versions • Red. Hat 7. 3 • updates from Fedora and CERN seem to work well • looks ok for the rest of this year • RHEL 3 • cost still an issue, even though the lowest price has come down (workstation + educational price + no support) • admin effort of having to deal with paid licensing at all • concern that future CERN deal might not have the right pricing for us • Scientific Linux (SLC) • one test workstation set up, so far so good • seems like a perfect HEP solution • planning to use this on new desktop machines this summer (hardware support for new machines in Red. Hat 7. 3 is now a problem) RHUL 9
RHUL 10
10525fa19d32a5ad9e4067a2436d0d4d.ppt