OSL

Oregon State University's Open Source Lab (OSUOSL) hosts two OSGeo machines.

OSGeo service users should file a ticket with SAC (http://trac.osgeo.org/osgeo). Under normal conditions only SAC primary administrators should file tickets with OSL. Support tickets are filed by sending emails to support at osuosl.org, please also notify SAC via a trac ticket or mailing list.

General Questions from OSGeo SAC can also be discussed on their freenode channel #osuosl .

General Information on VMs

By default the VMs allow shell access to folks in the LDAP SAC shell access group. Some VMs (ie. qgis.osgeo.org) have their own shell access.
Selected users are listed in the sudo group in /etc/group for super user access - this can be extended machine by machine as needed by those with permission.
The VMs also are preconfigured with ssh authorized keys for selected OSGeo primary admins to login directly as root (see /root/.ssh/authorized_keys), avoiding the LDAP requirement - useful if LDAP is misbehaving.
See SAC:Standard System Setup for details on how to setup a new VM.
The VMs also have an osuadmin account used by OSU OSL admins for work.
All VMs should be listed in the SAC Service Status page under osgeo3 or osgeo4.

This needs to be written up including information on:

How to get console access to VMs?
- https://ganeti.osuosl.org
- You need the password to get access to register, contact the System Admin Committee if you need access.
- Once registered one of the current System Admin Committee needs to add you to the OSGeo group.
Who has access to the physical machines
- OSUOSL - Lance is our primary contact (Ramareth on #osuosl)
Dealing with disk space issues.
Analysing performance problems.
- 1st stop is to use the munin instance.

Need to do VM reboot at OSUOSL?

Write to 'support at osuosl.org'
- don't forget to say on which physical machine the VM is (osgeoX, get that from SAC Service Status)
- Example: tracsvn.osgeo.osuosl.org is on osgeo3
if urgent, kindly ask in irc://freenode/osuosl