Skip to main content

Linux Management

info

TYPE: TS/PVFA Operated Management Tool
STATUS: In production, June 2025
CLEAR: NOT CLEARed
BCP/DRP: N/A

This document outlines the Linux systems maintained by PVFA and the roles and responsibilities related to their configuration and use.

While core services such as security, patching, and operational oversight are provided by the Academic Operations Linux Team, this document details local PVFA IT procedures for provisioning and imaging Linux devices to ensure consistent deployment practices.

Public Documentation: https://u.tamu.edu/linux-docs
https://docs.ao.tamu.edu/

Management RACI​

PVFATSPVFATSSAS
Operating System/Infrastructure Management
  Patching/UpgradesIIR/A
  Security MonitoringIIR/A
  Baseline ConfigurationIIR/A
  Backups/RecoveryIIR/A
  Access ControlIIR/A
Application Management
  Patching/UpgradesIIR/A
  Security MonitoringIIR/A
  Baseline ConfigurationIR/AR/A
  Backups/RecoveryIIR/A
  Access ControlIR/AI

Roles and Responsibilities​

PVFA IT Responsibilities​

  • Deploy and image Linux systems according to standardized procedures.
  • Notify the Academic Operations Linux Team of newly deployed devices to ensure enrollment in enterprise management tools.
  • Report system issues or anomalies that may require further investigation, patching, or escalated support.
  • Maintain documentation on devices deployed within the unit, including hardware information and location.

Academic Operations Linux Team Responsibilities​

  • Perform regular (e.g., monthly) patching and updates of Linux systems enrolled in the central management platform.
  • Add new devices to monitoring, configuration, and compliance tools as part of standard onboarding.
  • Provide ongoing operational oversight for enrolled systems, including alerting, performance monitoring, and responding to reported issues.
  • Ensure systems remain compliant with university-wide security and update policies.
  • Coordinate with PVFA IT on any incidents, outages, or required configuration changes.
  • Configure systems for local use, including initial setup of accounts, hostname assignment, and baseline configuration.

Supported Linux Distributions​

PVFA IT supports only the latest stable releases of Ubuntu and Red Hat Enterprise Linux (RHEL) for academic, research, and administrative environments.

Currently Supported Distributions​

  • Ubuntu: Latest Long-Term Support (LTS) release
  • Red Hat Enterprise Linux (RHEL): Most recent stable version supported by Red Hat

All Linux deployments must use one of the supported distributions listed above.

Security Exception​

caution

If a device runs a distribution outside of this list, a formal security exception must be filed and approved before deployment. The exception must be submitted by the Linux System Administrator or the Associate Director.

If you are unsure of the current supported version, contact the Linux System Administrator before imaging or configuring any device.

Internal Linux Team Documentation​

To access the Academic Operations Linux Team's internal documentation:

  1. Set up a GitHub account if you do not already have one: https://github.com
  2. Link your GitHub account to Texas A&M's GitHub Enterprise:

GitHub Institution Login Screen:

  1. Once linked, you can access the internal documentation at the following link:
    https://github.com/tamu-edu/ao-public-documentation/tree/main
  2. If you have issues accessing the documentation, please contact the Linux System Administrator or Associate Director.

Patching and Updates​

All supported Linux systems are enrolled in a monthly maintenance schedule on the third Thursday of each month.

tip

Users receive an email notification one week prior with instructions on how to temporarily delay maintenance if needed.

Security and Compliance​

Linux systems deployed by PVFA IT comply with Texas A&M University (TAMU) and Texas A&M University System (TAMUS) IT policies.

Key security notes:

  1. NetID authentication is required for system login.
  2. All systems are kept current through centrally managed patching.
  3. User data is stored locally only. There are no automated backups provided by IT — users are responsible for backing up their own files.
  4. Any configuration changes affecting security or compliance must be formally approved.

Software Management​

Users have access to a self-service tool that allows installing software from approved repositories without administrator privileges.

note

Self-service installations are logged and monitored for compliance. Local .deb or .rpm packages cannot be installed with this tool.

Self-Service Tool Commands​

# View available options
self-service

# Search for a package
self-service --search <package name>

# Schedule an installation (runs within ~30 minutes)
self-service --install <package name>

# List installed packages
self-service --list_installed

# Uninstall a package (or cancel scheduled install)
self-service --uninstall <package name>