savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [752] update for partial mgt0 to mgt1 migration


From: ineiev
Subject: [Savannah-cvs] [752] update for partial mgt0 to mgt1 migration
Date: Mon, 15 Jan 2024 03:03:28 -0500 (EST)

Revision: 752
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=752
Author:   ineiev
Date:     2024-01-15 03:03:27 -0500 (Mon, 15 Jan 2024)
Log Message:
-----------
update for partial mgt0 to mgt1 migration

Modified Paths:
--------------
    trunk/sviki/NonGnuToGnuSysadmin.mdwn
    trunk/sviki/SavannahHosts.mdwn
    trunk/sviki/ShellAccess.mdwn
    trunk/sviki/SqlQueries.mdwn
    trunk/sviki/UserAuthentication.mdwn

Modified: trunk/sviki/NonGnuToGnuSysadmin.mdwn
===================================================================
--- trunk/sviki/NonGnuToGnuSysadmin.mdwn        2024-01-15 07:47:43 UTC (rev 
751)
+++ trunk/sviki/NonGnuToGnuSysadmin.mdwn        2024-01-15 08:03:27 UTC (rev 
752)
@@ -24,7 +24,7 @@
     ordinarily shouldn't use it.
 
 -   Launch a curl to update www.gnu.org/software/GROUP -- the
-    appropriate command from mgt0:/opt/administration/curl.txt.
+    appropriate command from mgt1:/opt/administration/curl.txt.
 
     This will also automatically create a redirection from
     www.nongnu.org/GROUP to www.gnu.org/software/GROUP. It works via

Modified: trunk/sviki/SavannahHosts.mdwn
===================================================================
--- trunk/sviki/SavannahHosts.mdwn      2024-01-15 07:47:43 UTC (rev 751)
+++ trunk/sviki/SavannahHosts.mdwn      2024-01-15 08:03:27 UTC (rev 752)
@@ -408,7 +408,7 @@
 
 Ideally every host will have two IP addresses.  One will be a stable
 RFC1918 private LAN address.  The other will be a floating public IP
-address used for public services.  This allows the IP addres to float
+address used for public services.  This allows the IP address to float
 to a new node if needed.  At the present time this does not exist but
 I am working on getting this available for our use.
 

Modified: trunk/sviki/ShellAccess.mdwn
===================================================================
--- trunk/sviki/ShellAccess.mdwn        2024-01-15 07:47:43 UTC (rev 751)
+++ trunk/sviki/ShellAccess.mdwn        2024-01-15 08:03:27 UTC (rev 752)
@@ -37,7 +37,7 @@
 have that already, see [GNU accounts
 README](//www.gnu.org/software/README.accounts.html).  After that, an
 existing Savannah worker can enable your access to Savannah.  (By adding
-the key to `mgt0:/root/.ssh/authorized_keys` (in the right section,
+the key to `mgt1:/root/.ssh/authorized_keys` (in the right section,
 please).  See comments in those files.)
 
 You may find it convenient to automatically proxy ssh through fencepost,
@@ -51,10 +51,6 @@
 result, though.  Understand what you're doing.  [[SavannahArchitecture]]
 lists the various hosts.
 
-FYI, you can also log in to lists.gnu.org (as user list) from
-root@mgt0.savannah.gnu.org; see [[ListServer]] for tasks that this is
-needed for.
-
 ## As separate user, for Savannah workers
 
 Some sv workers like to have personal accounts on the servers.  The best
@@ -74,7 +70,7 @@
 This number is different from the user_id field which shows up in the
 Savannah profile as the "Id:" <https://savannah.gnu.org/users/luca>.
 
-0. On mgt0, add the obvious passwd entry using that uid.  It's not
+0. On mgt1, add the obvious passwd entry using that uid.  It's not
 technically necessary that the uid's match, but it seems cleaner to
 avoid possible conflicts.
 

Modified: trunk/sviki/SqlQueries.mdwn
===================================================================
--- trunk/sviki/SqlQueries.mdwn 2024-01-15 07:47:43 UTC (rev 751)
+++ trunk/sviki/SqlQueries.mdwn 2024-01-15 08:03:27 UTC (rev 752)
@@ -14,7 +14,7 @@
 with the forum_id column in news_bytes.  Set display type of news
 comments to flat or replies-to-comments will not be displayed.
 
-On the mgt0 host, in /opt/administration/bin are some scripts:
+On the mgt1 host, in /opt/administration/bin are some scripts:
   forum-remove-by-id, items-list-by-id, items-remove-by-id
 The first silently removes all forum posts for ids listed on the cmdline.
 The second lists all posts in all trackers, plus forum posts, for the given id,

Modified: trunk/sviki/UserAuthentication.mdwn
===================================================================
--- trunk/sviki/UserAuthentication.mdwn 2024-01-15 07:47:43 UTC (rev 751)
+++ trunk/sviki/UserAuthentication.mdwn 2024-01-15 08:03:27 UTC (rev 752)
@@ -136,7 +136,7 @@
 When a new user is registerd on Savannah, the `user_id` will be
 unique, but the `uidNumber` will be *NULL*.
 
-A cron job (`mgt0:/etc/cron.d/savannah`) calls a script (sv_assign_uid_gid)
+A cron job (`mgt1:/etc/cron.d/savannah`) calls a script (sv_assign_uid_gid)
 which scans the new users in the database, and creates unix user IDs and
 group IDs if needed (if users are not part of any group, they won't need
 ssh access and thus won't need user ID).
@@ -143,7 +143,7 @@
 
 Search for `sv_assign_uid_gid` in [[SavannahInternals]] to see
 how it is called (but note that the page is outdated: the script now
-runs as a cron job on `mgt0`, not `internal0`).
+runs as a cron job on `mgt1`, not `internal0`).
 
 ### ssh authentication
 
@@ -194,15 +194,15 @@
 
 ### mgt and root access
 
-`mgt0.savannah.gnu.org` is the management server (see [[SavannahArchitecture]] 
for
+`mgt1.savannah.gnu.org` is the management server (see [[SavannahArchitecture]] 
for
 more details).
 
-root access to `mgt0` (and from there to the other Savannah servers) is
-controlled by `mgt0:/root/.ssh/authorized_keys`. This file is updated
+root access to `mgt1` (and from there to the other Savannah servers) is
+controlled by `mgt1:/root/.ssh/authorized_keys`. This file is updated
 **manually** by existing Savannah administrators, adding ssh public keys
 of authorized Savannah hackers.
 
-ssh access to `mgt0` is only possible from `fencepost` (and other
+ssh access to `mgt1` is only possible from `fencepost` (and other
 internal FSF machines to which no one outside the FSF has access).
 ssh access to vcs0 and download0 is open to all as required by their
 respective functions.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]