OSL - Revision history

Robe: /* How to Administer Servers */

2023-11-02T22:52:30Z

How to Administer Servers

2020-12-09T22:11:47Z

Opening a ticket (VM reboot request etc)

2020-12-09T22:09:17Z

How to Administer VMs with VM Manager

2017-09-08T09:33:24Z

link back to service status

2012-01-10T21:35:10Z

How to Administer VMs with VM Manager

2012-01-10T21:22:31Z

How to Administer VMs with VM Manager

2011-09-28T05:30:11Z

General Information on VMs

2011-09-27T21:09:40Z

Opening a ticket (VM reboot request etc)

2011-09-24T10:49:37Z

+toc

2011-09-24T10:48:10Z

ticket procedure added

@@ Line 17: / Line 17: @@
 == How to Administer Servers ==
-There are currently 4 physical servers at OSUOSL. Each has their own web interface requiring OpenVPN access to OSL network in order to access it.
+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 OSGeo 7 in root/access folder.
 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:
-* 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.
 ** OSUOSL - Lance is our primary contact (Ramareth on #osuosl)
 * Dealing with disk space issues.

@@ Line 30: / Line 30: @@
 ** 1st stop is to use the [https://monitor.osgeo.org/ monitor] instance.
-== Opening a ticket (VM reboot request etc) ==
+== Opening a ticket ==
-Need to do VM reboot at OSUOSL?
+* 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.osuosl.org is on osgeo3
+** Example: tracsvn.osgeo.org is on osgeo7
 * if urgent, kindly ask in irc://freenode/osuosl
 [[Category:Infrastructure]]

@@ Line 15: / Line 15: @@
 * 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 ==
 This needs to be written up including information on:
 * How to get console access to VMs?
-** https://ganeti.osuosl.org
+* 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 [http://webextra.osgeo.osuosl.org/munin munin] instance.
+** 1st stop is to use the [https://monitor.osgeo.org/ monitor] instance.
 == Opening a ticket (VM reboot request etc) ==

@@ Line 1: / Line 1: @@
 __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.

@@ Line 20: / Line 20: @@
 * How to get console access to VMs?
 ** https://ganeti.osuosl.org
-** You need the password to get access register.
+** You need the password to get access to register, contact the System Admin Committee if you need access.
-** Once register contact the System Admin Committee to be added to the OSGeo group.
+** Once registered one of the current System Admin Committee needs to add you to the OSGeo group.
 * Who has access to the physical machines
 * Dealing with disk space issues.
 * Analysing performance problems.
 == Opening a ticket (VM reboot request etc) ==

@@ 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.
 * 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 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 VMs with VM Manager ==

← Older revision		Revision as of 10:48, 24 September 2011
Line 20:		Line 20:
	* Dealing with disk space issues.		* Dealing with disk space issues.
	* Analysing performance problems.		* Analysing performance problems.
		+
		+	= Opening a ticket (VM reboot request etc) =
		+
		+	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]])
		+	* if urgent, kindly ask in irc://freenode/osuosl