Project

General

Profile

Configurations for Virtual Machines

We are beginning to set up some experiment specific virtual machines (VM). As a pilot project each experiment will receive one VM. Each VM is actually half of a physical 8 core machine.The list below includes the proposed configuration for each VM.

The admins think that these VM's will have more flexibility running older os versions, so SLF4.7 is an option.

There will be no batch jobs running on these VM's, so their configuration and maintenance is simpler than current nodes. You will (eventually) be able to submit to the (common) batch, or grid via these nodes.

The current thinking is the VM names will be <exp>gpcfNN or <exp>gpNN. This may get long, so if you have a preferred <exp> abbreviation let me know.

Notes:
1. mounts are bluearc or /pnfs mounts
2. local-acct's are local accounts with /home/<acct> areas
3. need , in .k5login of local accounts

Groups:

1. minerva: gid=9555(e938)
2. nova: gid=9553(nova)
3. argoneut: gid=9874(t-962)
4. uboone: gid=9937(microboone)
5. mu2e: gid=9915(mu2e)
6. lbne: gid=9960(lbne)
7. minos: gid=5111(e875)
8. jdem: gid=9934(jdem)
9. mboone: gid=5468(e898)

Int. login vm's

1. minerva
os: SLF4.7
user-home:/afs
user-accts:same as if01
mount1: /minerva/data (noexe)
mount2:/minerva/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
mount5:/pnfs/minerva
local-acct1:minervadat
local-acct2:minervapro
local-acct3:minervaana
local-acct4:mnvonline

2. nova
os: SLF5.n
user-home:/afs
user-accts:same as gpsn01
mount1: /nova/data (noexe)
mount2:/nova/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
mount5:/pnfs/nova
local-acct1:nova
local-acct2:novadata
local-acct3:novapro
local-acct4:novaana
local-acct4:novacal

3. argoneut
os: SLF5.n
user-home:/afs
user-accts:new list
mount1: /argoneut/data (noexe)
mount2:/argoneut/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
mount5:/pnfs/argoneut
local-acct1:argoneut
local-acct2:argoneutana
local-acct3:argoneutpro
local-acct4:argoneutcal

4. uboone
os: SLF5.n
user-home:/afs
user-accts:new list
mount1: /argoneut/data (noexe)
mount2:/argoneut/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
mount5:/pnfs/argoneut
(added mount):/lbne/data
(added mount):/lbne/app
local-acct1: (no uids available yet)
local-acct2:
local-acct3:
local-acct4:

5. mu2e
os: SLF4.7
user-home:/afs
user-accts:new list
mount1: /mu2e/data (noexe)
mount2:/mu2e/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
mount5:/pnfs/mu2e
local-acct1:mu2e
local-acct2:mu2eana
local-acct3:mu2ecal
local-acct4:mu2epro

6. lbne
os: SLF5.n
user-home:/afs
user-accts:same as gpcf026
mount1: /lbne/data (noexe)
mount2:/lbne/app
mount3:/grid/data (noexe)
mount4:/grid/fermiapp
local-acct1:lbne
local-acct2:lbnedata
local-acct3:lbnepro
local-acct4:lbneana
local-acct5:lbnecal

7. minos
requested-name:minos-slf5 (Glenn says to avoid "-" however)
os: SLF5.n
user-home:/afs
user-accts:same as minos cluster
mounts: same as minos cluster
local-accts: same as minos cluster

8. jdem
as per Stu's advice

9. mboone
tbd
(is mboone interested in this?)

Mounts

minosgpvm01.fnal.gov
minos-nas-0.fnal.gov:/minos/scratch /minos/scratch
blue2:/minos/data /minos/data2
minos-nas-0.fnal.gov:/minos/data /minos/data

argoneutgpvm01.fnal.gov
blue3:/argoneut/data /argoneut/data
blue3:/argoneut/app /argoneut/app

gm2gpvm01.fnal.gov
blue3:/gm2/data /gm2/data
blue3:/gm2/app /gm2/app

lbnegpvm01.fnal.gov
blue3:/lbnewc/app /lbne/app
blue3:/lbnewc/data /lbne/data

minervagpvm01.fnal.gov
blue3:/minerva/app /minerva/app
blue3:/minerva/data /minerva/data

mu2egpvm01.fnal.gov
blue3:/mu2e/data /mu2e/data
blue3:/mu2e/app /mu2e/app

novagpvm01.fnal.gov
blue3:/nova/data /nova/data
blue3:/nova/app /nova/app