Difference between revisions of "Roentgen"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
Line 15: Line 15:
 
Check with "virsh dumpxml roentgen.unh.edu" on the machine running roentgen!
 
Check with "virsh dumpxml roentgen.unh.edu" on the machine running roentgen!
  
*Memory: 1.5 GB
+
*Memory: 8 GB
*Hard Disk: 50 GB
+
*Hard Disk: 60 GB
*Swap Disk: 2 GB
+
*CPU: 4 Virtual CPUs
 +
*Swap Disk: 23 GB
 
*Network 1 (eth0): Farm-Bridge
 
*Network 1 (eth0): Farm-Bridge
 
*Network 2 (eth1): UNH-Bridge
 
*Network 2 (eth1): UNH-Bridge
*SCSI Controller: LSI Logic
 
  
Look at the scripts!
+
The system has eth1 and eth1:1 to server roentgen.unh.edu and nuclear.unh.edu
  
 
== Backup Configuration ==
 
== Backup Configuration ==

Revision as of 17:11, 5 September 2018

General Information

Roentgen runs an Apache webserver, with wiki on top of it and shows you these pages. SO, if there are troubles with roentgen, you couldn't read this. Roentgen also hosts the MySQL server and the wiki. THIS wiki.

Hostnames: roentgen.unh.edu, roentgen.farm.physics.unh.edu
Alias: physics.farm.physics.unh.edu nuclear.farm.physics.unh.edu

Virtual Machine

Roentgen is a virtual machine. See Kvm It used to run on Taro, and was moved to Gourd on April 1, 2015. No joke. Previous attempts at moving roentgen had failed, apparently, so here is the recipe that worked: Moving A Virtual Machine

Virtual Hardware

Check with "virsh dumpxml roentgen.unh.edu" on the machine running roentgen!

  • Memory: 8 GB
  • Hard Disk: 60 GB
  • CPU: 4 Virtual CPUs
  • Swap Disk: 23 GB
  • Network 1 (eth0): Farm-Bridge
  • Network 2 (eth1): UNH-Bridge

The system has eth1 and eth1:1 to server roentgen.unh.edu and nuclear.unh.edu

Backup Configuration

/etc/rsync-backup.conf

# Backups are 'pull' only.  Too bad there isn't a better way to enforce this.
read only       = yes

# Oh for the ability to retain CAP_DAC_READ_SEARCH, and no other.  
uid             = root

# There's not much point in putting the superuser in a chroot jail
# use chroot    = no

# This isn't really an effective "lock" per se, since the value is per-module,
# but there really ought never be more than one, and it would at least 
# ensure serialized backups.
max connections = 1

[var]
        path    = /var
        comment = user and system storage
        filter  = - /lib/bind/proc

[srv]
        path    = /srv
        comment = published content

[usr_local]
        path    = /usr/local
        comment = unpackaged software

[opt]
        path    = /opt
        comment = unpackaged software

[etc]
        path    = /etc
        comment = conf files

[wheel]
        path    = /wheel
        comment = admin files
        filter  =               \
                : .rsync-filter \
                + /             \
                + /kickstart    \
                + /custom       \
                + /docs         \
                + /gpg-pubkey   \
                + /scripts      \
                - /*            \