Some general cleanup for 5.1.0

Author: arlake228

conf.py

@@ -53,9 +53,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = '5.0.7'
+version = '5.1.0'
 # The full version, including alpha/beta/rc tags.
-release = '5.0.7'
+release = '5.1.0 Beta 1'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

images/intro_about-arch.png

@@ -35,7 +35,6 @@ Installation
    install_quick_start
    install_config_first_time
    install_el
-   install_centos
    install_debian
    install_docker
    install_ansible
@@ -80,7 +79,6 @@ Running Measurements with pScheduler
    pscheduler_ref_tests_tools
    pscheduler_ref_archivers
    pscheduler_ref_contexts
-   pscheduler_ref_bwctl
    pscheduler_disk_to_disk
 
 Managing Multiple Hosts with pSConfig

index.rst

@@ -72,11 +72,10 @@ perfSONAR hosts are just like any other host and need to be actively managed to
   * An important aspect of security is to stay informed. Multiple system administrators from your site should be subscribed to the perfsonar security `announcement list <https://lists.internet2.edu/sympa/subscribe/perfsonar-announce>`_. This mailing list keeps users up-to-date on actions that need to be taken when critical security updates for both perfSONAR and third-party packages are released. 
   * Always follow best common security practices when it comes to creating user accounts and choosing passwords. Normal precautions should be taken to protect the root password as it can be used to make changes to the system. For example, safe password practices would recommend a password that contains a mixture of letters of different case, numbers, symbols, and a length greater than 8.  It is also not recommend to re-use passwords on multiple machines, in the event of a system breach.
   * If you have enabled SSH on the system, consider restricting access to specific subnets to the SSH port via IPTables, or implement a *jump host* that allows only logins from one location.  
-  * Consider configuring rsyslog to send logs to other locations for aggregation and analysis
+  * Consider configuring syslog to send logs to other locations for aggregation and analysis
   * If email has been enabled on the host, forward email from root to a central location
   * If applicable, use a management network on a spare networking interface to further restrict the access profile for users and system data.  
-  * If your site uses any form of automated management (CFEngine, Puppet, Forman, etc.), integrate the perfSONAR node into this procedure.  
-  * If you run `Nagios <http://www.nagios.org>`_, add your perfSONAR host to your monitoring infrastructure. Consider running some of the nagios `security plugins <http://exchange.nagios.org/directory/Plugins/Security#/>`_ such as `check_yum <http://exchange.nagios.org/directory/Plugins/Operating-Systems/Linux/check_yum/details>`_
+  * If your site uses any form of automated management (e.g. Ansible), integrate the perfSONAR node into this procedure.  
   * Automatic updates are enabled by default on all perfSONAR Toolkit hosts. In order to understand how to update your Toolkit and if automatic updates are right for your system, see :doc:`manage_update`
   * The perfSONAR Toolkit ships with a default iptables rule-set and intrusion detection system (IDS) software. In order to learn more about these components and how to do things like add custom firewall rules see :doc:`manage_security`
 

install_centos.rst

@@ -1,17 +1,14 @@
 ************************************************************
 Bundle Installation on RedHat Enterprise Linux Variants 
 ************************************************************
- 
-note:: For older CentOS 7 installation see :doc:`install_centos`
-
 
 perfSONAR combines various sets of measurement tools and services bundled in different useful ways. RPMs are available that install the bundles described in :doc:`install_options`. The steps in the remaining sections of this document detail the steps required for installing these bundles.
 
 System Requirements 
 ==================== 
 * **Operating System:**
 
-  * **Alma 8, Alma 9, Rocky 8 or Rocky 9** x86_64 installations are supported. Other RedHat-based operating systems may work, but are not officially supported at this time.
+  * **Alma 9 or Rocky 9** x86_64 installations are supported. Other RedHat-based operating systems based on EL9 may work, but are not officially supported at this time.
   * See :doc:`install_hardware` for hardware requirements and more.
 
 .. note:: Installing a graphical/desktop environment with perfSONAR is not supported.  These environments generally come with a Network Manager that conflicts with the way that perfSONAR is tuning the network interface parameters.  We recommend doing only server grade OS installs.
@@ -25,29 +22,19 @@ Installation
 
 Step 1: Configure DNF 
 ---------------------- 
-.. note:: If your system is using dnf/yum priorities make sure that repositories required for perfSONAR are higher priority than anything else to avoid conflicts with older versions. Please note that yum maintainers do not recommend using priorities.
+.. note:: If your system is using dnf priorities make sure that repositories required for perfSONAR are higher priority than anything else to avoid conflicts with older versions. Please note that dnf maintainers do not recommend using priorities.
 
 The process configures dnf to point at the necessary repositories to get packages needed for perfSONAR. **You will need to follow the steps below as privileged user**:
 
-.. note:: All commands work on both EL8 and EL9 based operating systems unless otherwise indicated
-
 #. Install the EPEL RPM::
 
     dnf install epel-release
 
-#. **EL8-only** Enable the PowerTools repository on an EL8 system::
-
-    dnf config-manager --set-enabled powertools
-
-#. **EL9-only** Enable the CBR repository on an EL9 system::
+#. Enable the CBR repository::
 
     dnf config-manager --set-enabled crb
 
-#. **EL8-only** Install the perfsonar-repo RPM for EL8::
-
-    dnf install http://software.internet2.edu/rpms/el8/x86_64/latest/packages/perfsonar-repo-0.11-1.noarch.rpm
-
-#. **EL9-only** Install the perfsonar-repo RPM for EL9::
+#. Install the perfsonar-repo RPM for EL9::
 
     dnf install http://software.internet2.edu/rpms/el9/x86_64/latest/packages/perfsonar-repo-0.11-1.noarch.rpm
 
@@ -145,29 +132,17 @@ You can also enable dnf ‘auto updates’ to ensure you always have the most cu
 
 .. _install_el_step6:
 
-Step 6: Service Watcher
-------------------------
-The ``perfsonar-toolkit-servicewatcher`` installs scripts that check if important processes are running and restarts if they have stopped unexpectedly. 
-
-The install automatically configures cron to run the service_watcher regularly.
-
-To run the script manually, run::
-
-  /usr/lib/perfsonar/scripts/service_watcher
-
-.. _install_el_step7:
-
-Step 7: Register your services 
+Step 6: Register your services 
 ------------------------------- 
 
 Note: this step can be done through the web interface if the perfsonar-toolkit bundle was installed. 
 See :doc:`manage_admin_info`.
 
 No actual configuration is required but filling fields such as administrator_email, site_name, city, country, latitude, longitude, etc. are **highly recommended**. You can add these by removing the leading `#` of any property and filling it out with a proper value for your host. Changes will be picked-up automatically without need for any restarts.
 
-.. _install_el_step8:
+.. _install_el_step7:
 
-Step 8: Starting your services 
+Step 7: Starting your services 
 ------------------------------- 
 All services should be started after install. Additionally, you can start all the services by rebooting the host since all are configured to run by default. In order to check services status issue the following commands::