Difference between revisions of "OSL"

From OSGeo
Jump to navigation Jump to search
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
__toc__
 
__toc__
  
Oregon State University's Open Source Lab (OSUOSL) hosts two OSGeo machines.
+
Oregon State University's Open Source Lab (OSUOSL) hosts [[SAC_Service_Status#Servers_at_OSL|four 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.   
 
* 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.   
  
Line 11: Line 11:
 
* 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.
 
* 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.
 
* 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.
 
* 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.  
+
* All VMs should be listed in the [[SAC Service Status]] page under osgeo3 or osgeo4.
  
== How to Administer VMs with VM Manager ==
+
== How to Administer Servers ==
 +
 
 +
There are currently 7 physical servers at OSUOSL (osgeo3- osgeo9). Each has their own web interface requiring [https://wiki.osuosl.org/howtos/vpn_config.html OSUOSL OpenVPN] access to OSL network in order to access it.  osgeo3 - osgeo9 have internal private dns like osgeo3.osuosl.oob etc.
 +
 
 +
You will find credentials for this in secure container on [https://git.osgeo.org/gitea/sac/password-store OSGeo Password store] 
 +
 
 +
There is one for each server e.g. osgeo3.osgeo.osuosl.org for login details for osgeo3 server.
  
 
This needs to be written up including information on:
 
This needs to be written up including information on:
* How to get console access to VMs.
+
* For day to day use standard public console access, is sufficient as detailed in [[SAC_Service_Status#Logging_into_Physical_Machines]]
* Who has access to the physical machines
+
* Who has access to the physical machines? Only Primary Administrators have physical access and can do hard-reboots in case of major failures.
 +
Such KVM access requires an  [https://wiki.osuosl.org/howtos/vpn_config.html OSUOSL OpenVPN]  account
 +
** OSUOSL - Lance is our primary contact (Ramareth on #osuosl)
 
* Dealing with disk space issues.
 
* Dealing with disk space issues.
 
* Analysing performance problems.
 
* Analysing performance problems.
 +
** 1st stop is to use the [https://monitor.osgeo.org/ monitor] instance.
  
== Opening a ticket (VM reboot request etc) ==
+
== Opening a ticket ==
 
+
If having serious issues with hardware, like the physical host is unreachable even thru the KVM interface.
Need to do VM reboot at OSUOSL?
 
  
* Write to 'support at osuosl.org'
+
* Write to 'support at osuosl.org' - only OSGeo SysAdmins should write to support.  Other users should put in a trac.osgeo.org/osgeo for general issues
 
** don't forget to say on which physical machine the VM is (osgeoX, get that from [[SAC Service Status]])
 
** 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
+
** Example: tracsvn.osgeo.org is on osgeo7
 
* if urgent, kindly ask in irc://freenode/osuosl
 
* if urgent, kindly ask in irc://freenode/osuosl
  
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Latest revision as of 14:52, 2 November 2023

Oregon State University's Open Source Lab (OSUOSL) hosts four 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.

How to Administer Servers

There are currently 7 physical servers at OSUOSL (osgeo3- osgeo9). Each has their own web interface requiring OSUOSL OpenVPN access to OSL network in order to access it. osgeo3 - osgeo9 have internal private dns like osgeo3.osuosl.oob etc.

You will find credentials for this in secure container on OSGeo Password store

There is one for each server e.g. osgeo3.osgeo.osuosl.org for login details for osgeo3 server.

This needs to be written up including information on:

  • For day to day use standard public console access, is sufficient as detailed in SAC_Service_Status#Logging_into_Physical_Machines
  • Who has access to the physical machines? Only Primary Administrators have physical access and can do hard-reboots in case of major failures.

Such KVM access requires an OSUOSL OpenVPN account

    • OSUOSL - Lance is our primary contact (Ramareth on #osuosl)
  • Dealing with disk space issues.
  • Analysing performance problems.
    • 1st stop is to use the monitor instance.

Opening a ticket

If having serious issues with hardware, like the physical host is unreachable even thru the KVM interface.

  • Write to 'support at osuosl.org' - only OSGeo SysAdmins should write to support. Other users should put in a trac.osgeo.org/osgeo for general issues
    • don't forget to say on which physical machine the VM is (osgeoX, get that from SAC Service Status)
    • Example: tracsvn.osgeo.org is on osgeo7
  • if urgent, kindly ask in irc://freenode/osuosl