Skip to content

Commit

Permalink
generic: get rid of outdated &hasi; entity (#356)
Browse files Browse the repository at this point in the history
* 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

* Further changes required for version 12

Co-authored-by: Tahlia Richardson <[email protected]>

---------

Co-authored-by: Tahlia Richardson <[email protected]>
  • Loading branch information
taroth21 and tahliar committed Nov 8, 2023
1 parent efdd20e commit 11bcc16
Show file tree
Hide file tree
Showing 29 changed files with 167 additions and 172 deletions.
2 changes: 1 addition & 1 deletion xml/art_sle_ha_geo_quick.xml
Original file line number Diff line number Diff line change
Expand Up @@ -337,7 +337,7 @@
information in the &haguide; for &productname;
&productnumber;, available from
<link xlink:href="http://www.suse.com/documentation/"/>. Refer to the
chapter <citetitle>Installing the &hasi;</citetitle>, section
chapter <citetitle>Installing &productname;</citetitle>, section
<citetitle>Mass Installation and Deployment with &ay;</citetitle>.
</para>
<para>
Expand Down
13 changes: 6 additions & 7 deletions xml/art_sle_ha_install_quick.xml
Original file line number Diff line number Diff line change
Expand Up @@ -292,8 +292,8 @@
<sect1 xml:id="sec-ha-inst-quick-installation">
<title>Installing &sls; and &ha; Extension</title>
<para>
The packages for configuring and managing a cluster with the
&hasi; are included in the <literal>&ha;</literal> installation
The packages for configuring and managing a cluster with &productname;
are included in the <literal>&ha;</literal> installation
pattern. This pattern is only available after &productname; has been
installed as an extension to &slsreg;.
</para>
Expand Down Expand Up @@ -337,10 +337,9 @@
<note>
<title>Installing Software Packages on All Parties</title>
<para>
For an automated installation of &sls; &productnumber; and &productname;
&productnumber;, use &ay; to clone existing nodes. For more information,
see <link
xlink:href="https://www.suse.com/documentation/sle-ha-12/book_sleha/data/sec_ha_installation_autoyast.html"/>.
For an automated installation of &sls; &productnumber; and &productname; &productnumber;,
use &ay; to clone existing nodes. For more
information, see <link xlink:href="https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-all/cha-ha-install.html#sec-ha-installation-autoyast"/>.
</para>
</note>
</step>
Expand Down Expand Up @@ -432,7 +431,7 @@
<para>
In &sls;, watchdog support in the kernel is enabled by default: It 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>
Expand Down
4 changes: 2 additions & 2 deletions xml/geo_install_i.xml
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
</info>

<para>
For using the &hasi; and &hageo;, you need the packages included in the
For using &productname; and &hageo;, you need the packages included in the
following installation patterns:
</para>

Expand Down Expand Up @@ -119,7 +119,7 @@
information in the <citetitle>&haguide;</citetitle> for &productname;
&productnumber;, available from
<link xlink:href="http://www.suse.com/documentation/"/>. Refer to the
chapter <citetitle>Installation the &hasi;</citetitle>, section
chapter <citetitle>Installing &productname;</citetitle>, section
<citetitle>Mass Installation and Deployment with &ay;</citetitle>.
</para>
<para>
Expand Down
75 changes: 37 additions & 38 deletions xml/ha_concepts.xml
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@
management functionality (supporting failover, failback, and migration
(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
<para>
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.
Expand All @@ -47,12 +47,12 @@
</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;.
Support for &geo.dispersed; clusters (&geo; clusters) is available
as a separate extension to the &hasi;, called &hageo;.
&ha; is available for several products. Support for &geo.dispersed; clusters
(&geo; clusters) is available as a separate extension called &hageo;. For details, see
<link xlink:href="https://documentation.suse.com/sles/12-SP5/html/SLES-all/cha-add-ons.html#sec-add-ons-extensions"/>.
</para>
</sect1>
<sect1 xml:id="sec-ha-features">
Expand All @@ -67,7 +67,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>
Expand Down Expand Up @@ -126,11 +126,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, manage
dependencies, and 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.
Expand All @@ -140,16 +140,15 @@
<sect2 xml:id="sec-ha-features-storage">
<title>Storage and Data Replication</title>
<para>
With the &hasi; you can dynamically assign and reassign server
storage as needed. It supports Fibre Channel storage area networks (SAN)
and iSCSI storage on networks. Thus, shared disk systems are supported,
but they are not a requirement.
&productname; also comes with a cluster-aware file
system and volume manager (OCFS2) and the clustered Logical Volume
Manager (cLVM). For replication of your data, you can use DRBD* to
mirror the data of a &ha; service from the active node of a cluster
to its standby node. Furthermore, &productname; also supports CTDB
(Clustered Trivial Database), a technology for Samba clustering.
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
system (OCFS2) and the cluster Logical Volume Manager (&clvm;).
For replication of your data, use DRBD* to mirror the data of
a &ha; service from the active node of a cluster to its standby node.
Furthermore, &productname; also supports CTDB (Cluster Trivial Database),
a technology for Samba clustering.
</para>
</sect2>

Expand All @@ -169,7 +168,7 @@
<para>
&productname; has been extended to support different geographical
scenarios. Support for &geo.dispersed; clusters (&geo; clusters)
is available as a separate extension to &hasi;, called &hageo;.
is available as a separate extension called &hageo;.
</para>
<variablelist>
<varlistentry>
Expand Down Expand Up @@ -242,8 +241,8 @@
<sect2 xml:id="sec-ha-features-tools">
<title>User-friendly Administration Tools</title>
<para>
The &hasi; ships with a set of powerful tools for basic installation
and setup of your cluster, effective configuration and
&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>
<variablelist>
Expand All @@ -252,7 +251,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:
Expand Down Expand Up @@ -310,18 +309,18 @@
<title>Benefits</title>

<para>
The &hasi; allows you to configure up to 32 Linux servers into a
high-availability cluster (HA cluster), where resources can be
dynamically switched or moved to any server in the cluster. Resources can
be configured to automatically migrate if a server fails, or they can be
&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
manage the complete cluster and to adjust resources to meet changing
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
by allowing several nodes to share a <quote>hot spare</quote>.
Expand Down Expand Up @@ -386,7 +385,7 @@
</para>

<para>
The following scenario illustrates some benefits the &hasi; can
The following scenario illustrates some benefits &productname; can
provide.
</para>

Expand Down Expand Up @@ -453,7 +452,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>
Expand Down Expand Up @@ -496,13 +495,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, so 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>
Expand All @@ -518,7 +517,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 server fails, another designated server in
Expand Down Expand Up @@ -588,15 +587,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>
Expand Down
Loading

0 comments on commit 11bcc16

Please sign in to comment.