generic: get rid of outdated &hasi; entity (#356)

* generic: get rid of outdated &hasi; entity - the following preparations where needed before we can fix the value of &productname; via doc-kit: * replace '[T,t]he &hasi;' with &productname; where appropriate * replace '[T,t]he &hasi;' with '&ha; (software)' where appropriate * update product-entities.ent * Apply suggestions from code review Co-authored-by: Tahlia Richardson <[email protected]> --------- Co-authored-by: Tahlia Richardson <[email protected]>
SUSE · Nov 8, 2023 · 4b3feb3 · 4b3feb3
1 parent e3db436
commit 4b3feb3
Show file tree

Hide file tree

Showing 25 changed files with 217 additions and 219 deletions.
diff --git a/xml/article_geo_clustering.xml b/xml/article_geo_clustering.xml
@@ -239,7 +239,7 @@
    patterns. These patterns are only available after the &productname; is installed.
   </para>
   <para>
-   You can register to the &scc; and install the &hasi; while installing &sles;,
+   You can register to the &scc; and install &productname; while installing &sles;,
    or after installation. For more information, see
    <link xlink:href="https://documentation.suse.com/sles/html/SLES-all/cha-register-sle.html">
    &deploy;</link> for &sles;.
@@ -259,7 +259,7 @@
     <note>
      <title>Installing software packages on all nodes</title>
      <para>
-      For an automated installation of &sls; &productnumber; and the &hasi;,
+      For an automated installation of &sls; &productnumber; and &productname; &productnumber;,
       use &ay; to clone existing nodes. For more
       information, see <xref linkend="sec-ha-installation-autoyast"/>.
      </para>

diff --git a/xml/article_installation.xml b/xml/article_installation.xml
@@ -306,8 +306,8 @@
       This pattern is only available after the &productname; is installed.
     </para>
     <para>
-     You can register to the &scc; and install the &hasi; while installing &sles;,
-     or after installation. For more information, see the
+      You can register to the &scc; and install &productname; while installing &sles;,
+      or after installation. For more information, see the
      <link xlink:href="https://documentation.suse.com/sles/html/SLES-all/cha-register-sle.html">
      &deploy;</link> for &sles;.
     </para>
@@ -326,8 +326,8 @@
        <note>
         <title>Installing software packages on all nodes</title>
         <para>
-         For an automated installation of &sls; &productnumber; and the &hasi;,
-         use &ay; to clone existing nodes. For more
+          For an automated installation of &sls; &productnumber; and &productname; &productnumber;,
+          use &ay; to clone existing nodes. For more
          information, see <xref linkend="sec-ha-installation-autoyast"/>.
         </para>
        </note>
@@ -340,7 +340,7 @@
    <para>
     Before you can configure SBD with the bootstrap script, you must enable a watchdog
     on each node. &sls; ships with several kernel modules that provide hardware-specific
-    watchdog drivers. The &hasi; uses the SBD daemon as the software component
+    watchdog drivers. &productname; uses the SBD daemon as the software component
     that <quote>feeds</quote> the watchdog.
    </para>
    <para>

diff --git a/xml/ha_concepts.xml b/xml/ha_concepts.xml
@@ -24,8 +24,8 @@
     (load balancing) of individually managed cluster resources).
    </para>
    <para>
-    This chapter introduces the main product features and benefits of the
-    &hasi;. Inside you will find several example clusters and learn about
+    This chapter introduces the main product features and benefits of &productname;.
+    Inside you will find several example clusters and learn about
     the components making up a cluster. The last section provides an
     overview of the architecture, describing the individual architecture
     layers and processes within the cluster.
@@ -47,10 +47,11 @@
       </dm:docmanager>
     </info>
     <sect1 xml:id="sec-ha-availability">
-  <title>Availability as extension</title>
+  <title>Availability as a module or extension</title>
 
   <para>
-   The &hasi; is available as an extension to &sls; &productnumber;.
+   &ha; is available as a module or extension for several products. For details, see
+   <link xlink:href="https://documentation.suse.com/sles/html/SLES-all/article-modules.html#art-modules-high-availability"></link>.
   </para>
  </sect1>
  <sect1 xml:id="sec-ha-features">
@@ -65,7 +66,7 @@
   <sect2 xml:id="sec-ha-features-scenarios">
    <title>Wide range of clustering scenarios</title>
    <para>
-    The &hasi; supports the following scenarios:
+    &productname; supports the following scenarios:
    </para>
    <itemizedlist>
     <listitem>
@@ -123,11 +124,11 @@
   <sect2 xml:id="sec-ha-features-flexibility">
    <title>Flexibility</title>
    <para>
-    The &hasi; ships with &corosync; messaging and membership layer
+    &productname; ships with &corosync; messaging and membership layer
     and Pacemaker Cluster Resource Manager. Using Pacemaker, administrators
     can continually monitor the health and status of their resources, and manage
     dependencies. They can automatically stop and start services based on highly
-    configurable rules and policies. The &hasi; allows you to tailor a
+    configurable rules and policies. &productname; allows you to tailor a
     cluster to the specific applications and hardware infrastructure that
     fit your organization. Time-dependent configuration enables services to
     automatically migrate back to repaired nodes at specified times.
@@ -137,7 +138,7 @@
   <sect2 xml:id="sec-ha-features-storage">
    <title>Storage and data replication</title>
    <para>
-    With the &hasi; you can dynamically assign and reassign server
+    With &productname; you can dynamically assign and reassign server
     storage as needed. It supports Fibre Channel or iSCSI storage area
     networks (SANs). Shared disk systems are also supported, but they are
     not a requirement. &productname; also comes with a cluster-aware file
@@ -156,8 +157,8 @@
     virtual Linux servers. &sls; &productnumber; ships with &xen;,
     an open source virtualization hypervisor, and with &kvm; (Kernel-based
     Virtual Machine). &kvm; is a virtualization software for Linux which is based on
-    hardware virtualization extensions. The cluster resource manager in the
-    &hasi; can recognize, monitor, and manage services running within
+    hardware virtualization extensions. The cluster resource manager in &productname;
+    can recognize, monitor, and manage services running within
     virtual servers and services running in physical servers. Guest
     systems can be managed as services by the cluster.
    </para>
@@ -270,7 +271,7 @@
   <sect2 xml:id="sec-ha-features-tools">
    <title>User-friendly administration tools</title>
    <para>
-    The &hasi; ships with a set of powerful tools. Use them for basic installation
+    &productname; ships with a set of powerful tools. Use them for basic installation
     and setup of your cluster and for effective configuration and
     administration:
    </para>
@@ -280,7 +281,7 @@
      <listitem>
       <para>
        A graphical user interface for general system installation and
-       administration. Use it to install the &hasi; on top of &sls; as
+       administration. Use it to install &productname; on top of &sls; as
        described in the &haquick;. &yast;
        also provides the following modules in the &ha; category to help
        configure your cluster or individual components:
@@ -337,17 +338,17 @@
   <title>Benefits</title>
 
   <para>
-   The &hasi; allows you to configure up to 32 Linux servers into a
+   &productname; allows you to configure up to 32 Linux servers into a
    high-availability cluster (HA cluster). Resources can be
    dynamically switched or moved to any node in the cluster. Resources can
    be configured to automatically migrate if a node fails, or they can be
    moved manually to troubleshoot hardware or balance the workload.
   </para>
 
   <para>
-   The &hasi; provides high availability from commodity components. Lower
+   &productname; provides high availability from commodity components. Lower
    costs are obtained through the consolidation of applications and
-   operations onto a cluster. The &hasi; also allows you to centrally
+   operations onto a cluster. &productname; also allows you to centrally
    manage the complete cluster. You can adjust resources to meet changing
    workload requirements (thus, manually <quote>load balance</quote> the
    cluster). Allowing clusters of more than two nodes also provides savings
@@ -413,7 +414,7 @@
   </para>
 
   <para>
-   The following scenario illustrates some benefits the &hasi; can
+   The following scenario illustrates some benefits &productname; can
    provide.
   </para>
 
@@ -480,7 +481,7 @@
   </para>
 
   <para>
-   When Web Server 1 failed, the &hasi; software did the following:
+   When Web Server 1 failed, the &ha; software did the following:
   </para>
 
   <itemizedlist>
@@ -523,13 +524,13 @@
    either automatically fail back (move back) to Web Server 1, or they can
    stay where they are. This depends on how you configured the resources for
    them. Migrating the services back to Web Server 1 will incur some
-   down-time. Therefore the &hasi; also allows you to defer the migration until
+   down-time. Therefore &productname; also allows you to defer the migration until
    a period when it will cause little or no service interruption. There are
    advantages and disadvantages to both alternatives.
   </para>
 
   <para>
-   The &hasi; also provides resource migration capabilities. You can move
+   &productname; also provides resource migration capabilities. You can move
    applications, Web sites, etc. to other servers in your cluster as
    required for system management.
   </para>
@@ -545,7 +546,7 @@
   <title>Cluster configurations: storage</title>
 
   <para>
-   Cluster configurations with the &hasi; might or might not include a
+   Cluster configurations with &productname; might or might not include a
    shared disk subsystem. The shared disk subsystem can be connected via
    high-speed Fibre Channel cards, cables, and switches, or it can be
    configured to use iSCSI. If a node fails, another designated node in
@@ -627,15 +628,15 @@
   <title>Architecture</title>
 
   <para>
-   This section provides a brief overview of the &hasi; architecture. It
+   This section provides a brief overview of &productname; architecture. It
    identifies and provides information on the architectural components, and
    describes how those components interoperate.
   </para>
 
   <sect2 xml:id="sec-ha-architecture-layers">
    <title>Architecture layers</title>
    <para>
-    The &hasi; has a layered architecture.
+    &productname; has a layered architecture.
     <xref linkend="fig-ha-architecture" xrefstyle="FigureXRef"/> illustrates
     the different layers and their associated components.
    </para>

diff --git a/xml/ha_config_basics.xml b/xml/ha_config_basics.xml
@@ -21,7 +21,7 @@
     This chapter introduces some basic concepts you need to know
     when administering your cluster. The following
     chapters show you how to execute the main configuration and
-    administration tasks with each of the management tools the &hasi;
+    administration tasks with each of the management tools &productname;
     provides.
    </para>
       </abstract>
@@ -407,8 +407,8 @@ C = number of cluster nodes</screen>
     </term>
     <listitem>
      <para>
-      Home page of Pacemaker, the cluster resource manager shipped with the
-      &hasi;.
+      Home page of Pacemaker, the cluster resource manager shipped with
+      &productname;.
      </para>
     </listitem>
    </varlistentry>