Editing Production Cluster Configuration

These packages form the basic functionality of the production cluster.  

Scripts & config files are checked into gitlab under the Kubernetes group project listed.

{| class="wikitable"
|-
! activity !! gitlab !! script/procedures/config !! IP !! hostname(s)
|-
| [[Ceph Storage Cluster]] || k8s-admin || || ||
|-
| [[Rook Storage for Kubernetes|Rook Storage]] || k8s-admin || || || (StorageClass)<br/>rook-ceph-hdd<br/>rook-ceph-nvme
|-
| gitlab registry secrets || || gitlab-registry-kube-system.yaml <br /> gitlab-registry-secret.yaml || ||
|-
| wordpress (dredwilliams.com) || k8s/dredwilliams || || || dredwilliams.williams-net.org
|-
| mediawiki || mediawiki || || 10.0.0.116 || wiki.williams.localnet <br />wiki.williams-net.org
|-
| [[MariaDB]] || mariadb || || 10.0.0.117 || database.williams.localnet
|}

=== Storage ===
The production cluster depends on the '''/shared''' filesystem for its persistent storage as provided by the production Ceph cluster.  The Ceph is configured as shown here:
{| class="wikitable"
|-
! system !! function !! storage !! size
|-
| caspian || master || NVMe<br/>HDD || 1TB<br/>1TB
|-
| uvilas || node || NVMe<br/>HDD<br/>HDD || 1TB<br/>1TB<br/>1TB
|-
| belisar || node || NVMe<br/>HDD || 1TB<br/>250GB
|}

The work filesystem can be mounted via NFS:

 10.0.0.75:/work /work nfs4 soft 0 0

=== Backups ===

In addition to the normal backups configured in the basic OS installation steps, the databases in the production cluster must be backed up daily using the 'mysqldump' command:

 TBD

These commands should be inserted into the /etc/cron.daily/backup file on one of the cluster nodes (telmar is a good choice).  The first does a complete database dump of the MediaWiki database server, the second dumps just the mediawiki database itself, and the third dumps the general purpose database server.  Additional dump commands should be inserted for additional significant databases, as parsing individual databases out of a system dump can be tedious.