[Savannah-cvs] [833] updates and elaborations

[ineiev]

Revision: 833
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=833
Author:   ineiev
Date:     2025-06-07 06:14:24 -0400 (Sat, 07 Jun 2025)
Log Message:
-----------
updates and elaborations

Modified Paths:
--------------
    trunk/sviki/SavannahArchitecture.mdwn

Modified: trunk/sviki/SavannahArchitecture.mdwn
===================================================================
--- trunk/sviki/SavannahArchitecture.mdwn       2025-06-07 10:01:47 UTC (rev 
832)
+++ trunk/sviki/SavannahArchitecture.mdwn       2025-06-07 10:14:24 UTC (rev 
833)
@@ -29,18 +29,32 @@
 
 ## Xen/KVM architecture
 
-Savannah operates with five critical Xen/KVM VMs.
+Savannah operates with five groups of critical Xen/KVM VMs.
 
--   mgt0.savannah.gnu.org
--   internal0.savannah.gnu.org
--   frontend0.savannah.gnu.org
--   vcs0.savannah.gnu.org
--   download0.savannah.gnu.org
+-   mgt<var>?</var>.savannah.gnu.org
+-   internal<var>?</var>.savannah.gnu.org
+-   frontend<var>?</var>.savannah.gnu.org
+-   vcs<var>?</var>.savannah.gnu.org
+-   download<var>?</var>.savannah.gnu.org
 
-## mgt0.savannah.gnu.org
+Where <var>?</var> is a digit.
 
-This is the management VM, where maintenance scripts can be run and
-software can be built for the other four VMs.  Also runs bind (for the
+For mgt, internal, frontend, download,
+two VMs exist, one of them ('current') provides Savannah services
+and the other ('previous') was used before OS upgrade
+on the 'current', and will likely become 'current' after the next
+OS upgrade.  The 'current' VM can be accessed without the digit,
+like download.savannah.gnu.org.
+
+For vcs, different VMs provide different services, for example,
+vcs1 runs CVS.
+
+## mgt<var>?</var>.savannah.gnu.org
+
+These are the management VMs, where maintenance scripts can be run and
+software can be built for the other four VMs.  As of 2025-05, mgt1
+is the primary management VM, its /root/ChangeLog is used to record
+changes in all Savannah VMs.   mgt0 still runs bind (for the
 *.savannah.gnu.org/*.savannah.nongnu.org domains).
 
 Scripts may be found in the /root/maintenance directory.
@@ -49,12 +63,12 @@
 running/creating/maintaining maintenance scripts and for other
 administrative functions.
 
-From the mgt VM, the other VM's are accessible via ssh.
+From the mgt VM, the other VMs are accessible via SSH.
 
--   ssh root@download0
--   ssh root@vcs0
--   ssh root@frontend0
--   ssh root@internal0
+-   ssh root@download<var>?</var>
+-   ssh root@vcs<var>?</var>
+-   ssh root@frontend<var>?</var>
+-   ssh root@internal<var>?</var>
 
 SSH keys may be synced to the savannah virtual machines using the
 /root/maintenance/authorized\_keys\_replicate.sh script, which copies
@@ -66,34 +80,43 @@
 management vm on the other vm's without actually being in the mgt vm's
 authorized\_keys file.
 
-## internal0.savannah.gnu.org
+## internal.savannah.gnu.org
 
-The internal0 VM runs mysql.
+The internal VM runs MariaDB.
 
-## frontend0.savannah.gnu.org
+## frontend.savannah.gnu.org
 
-The frontend VM runs the web server instances for Savannah.
+The frontend VM runs the web server for Savannah.
 
 The frontend Savane repository pulls from administration/savane.git
 
-## vcs0.savannah.gnu.org
+## vcs<var>?</var>.savannah.gnu.org
 
-This is the version control system virtual machine. It runs
-cvs/git/bzr/etc as well as webservers for repository viewing.
+These are the version control system virtual machines:
 
-Alone among the Savannah hosts, it allows ssh from everywhere since that
-is part of VC access, and has a custom sshd_config directive
-`AuthorizedKeysCommand` to look up ssh keys in the mysql database.
+* vcs0 runs CVS
+* vcs2 runs Git
+* vcs3 provides RSYNC acess to Git
+* vcs1 runs other systems: bzr, svn, hg, arch
 
-Users themselves are authenticated in `/etc/nsswitch.conf` with a
-`mysql` module (`libnss-mysql`), also directly against the mysql
-database on internal0.
+Before 2025-06, they run webservers for repository viewing as well.
 
-## download0.savannah.gnu.org
+These machines allow SSH from everywhere since that
+is part of VCS access, and have a custom sshd_config directive
+`AuthorizedKeysCommand` to look up SSH keys in the mysql database.
 
-This is the "download" vm, it runs a webserver and stores the released
+Users are authenticated in `/etc/nsswitch.conf` with a
+`mysql` module (`libnss-mysql`), also directly against the
+database on internal.
+
+## download.savannah.gnu.org
+
+This is the "download" VM, it runs a webserver and stores the released
 packages from Savannah.
 
+Like for VCS hosts, the users have SSH access to this for uploading
+the releases.
+
 ## High load
 
 If a DomU is experiencing heavy load, running these commands will
@@ -112,9 +135,6 @@
 * https://savannah.gnu.org/
 * https://savannah.gnu.org/maintenance/FrontPage/
 
-The mirrors redirection is handled by Apache2::Geo::Mirror, normally
-installed via cpan.
-
 See also [[SavannahServices]] for list of publically accessible services.
 
 ## Misc