Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
documentation.suse.com › SUSE Linux Enterprise High Availability Extension Documentation › Geo Clustering Guide › Preface
ContentsContents
Geo Clustering Guide
  1. Preface
  2. 1 Challenges for Geo clusters
  3. 2 Conceptual overview
  4. 3 Requirements
  5. 4 Setting up the booth services
  6. 5 Synchronizing configuration files across all sites and arbitrators
  7. 6 Configuring cluster resources and constraints
  8. 7 Setting up IP relocation via DNS update
  9. 8 Managing Geo clusters
  10. 9 Troubleshooting
  11. 10 Upgrading to the latest product version
  12. 11 For more information
  13. A GNU licenses
Navigation←→
documentation.suse.com › SUSE Linux Enterprise High Availability Extension Documentation › Geo Clustering Guide › Preface
Top
←→
Applies to SUSE Linux Enterprise High Availability Extension 15 SP3

Preface Edit source

Available documentation
Improving the documentation
Documentation conventions
Support

1 Available documentation Edit source

Online documentation

The online documentation for this product is available at https://documentation.suse.com/#sle-ha. Browse or download the documentation in various formats.

Find the online documentation for other products at https://documentation.suse.com/.

Note
Note: Latest updates

The latest documentation updates are usually available in the English version of the documentation.

Release notes

For release notes, see https://www.suse.com/releasenotes/.

In your system

For offline use, find documentation in your installed system under /usr/share/doc. Many commands are also described in detail in their manual pages. To view them, run man, followed by a specific command name. If the man command is not installed on your system, install it with sudo zypper install man.

2 Improving the documentation Edit source

Your feedback and contributions to this documentation are welcome. The following channels for giving feedback are available:

Service requests and support

For services and support options available for your product, see https://www.suse.com/support/.

To open a service request, you need a SUSE subscription registered at SUSE Customer Center. Go to https://scc.suse.com/support/requests, log in, and click Create New.

Bug reports

Report issues with the documentation at https://bugzilla.suse.com/. To simplify this process, you can use the Report Documentation Bug links next to headlines in the HTML version of this document. These preselect the right product and category in Bugzilla and add a link to the current section. You can start typing your bug report right away. A Bugzilla account is required.

Contributions

To contribute to this documentation, use the Edit Source links next to headlines in the HTML version of this document. They take you to the source code on GitHub, where you can open a pull request. A GitHub account is required.

Note
Note: Edit Source only available for English

The Edit Source links are only available for the English version of each document. For all other languages, use the Report Documentation Bug links instead.

For more information about the documentation environment used for this documentation, see the repository's README https://github.com/SUSE/doc-sleha/blob/main/README.adoc.

Mail

You can also report errors and send feedback concerning the documentation to <>. Include the document title, the product version, and the publication date of the document. Additionally, include the relevant section number and title (or provide the URL) and provide a concise description of the problem.

3 Documentation conventions Edit source

The following notices and typographical conventions are used in this documentation: 

  • tux > command

    Commands that can be run by any user, including the root user. 

  • root # command

    Commands that must be run with root privileges. Often you can also prefix these commands with the sudo command to run them. 

  • crm(live)#

    Commands executed in the interactive crm shell. For details, see Chapter 8, Configuring and managing cluster resources (command line).

  • /etc/passwd: directory names and file names

  • PLACEHOLDER: replace PLACEHOLDER with the actual value

  • PATH: the environment variable PATH

  • ls, --help: commands, options, and parameters

  • user: users or groups

  • packagename: name of a package

  • Alt, Alt–F1: a key to press or a key combination; keys are shown in uppercase as on a keyboard

  • File, File › Save As: menu items, buttons

  • amd64, em64t, ipf This paragraph is only relevant for the architectures amd64, em64t, and ipf. The arrows mark the beginning and the end of the text block.

  • Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in another manual.

  • Notices

    Warning
    Warning

    Vital information you must be aware of before proceeding. Warns you about security issues, potential loss of data, damage to hardware, or physical hazards.

    Important
    Important

    Important information you should be aware of before proceeding.

    Note
    Note

    Additional information, for example about differences in software versions.

    Tip
    Tip

    Helpful information, like a guideline or a piece of practical advice.

For an overview of naming conventions with regard to cluster nodes and names, resources, and constraints, see Appendix B, Naming conventions.

4 Support Edit source

Find the support statement for SUSE Linux Enterprise High Availability Extension and general information about technology previews below. For details about the product lifecycle, see the Upgrade Guide for SUSE Linux Enterprise Server 15 SP3.

If you are entitled to support, find details on how to collect information for a support ticket in the Administration Guide for SUSE Linux Enterprise Server 15 SP3.

4.1 Support statement for SUSE Linux Enterprise High Availability Extension Edit source

To receive support, you need an appropriate subscription with SUSE. To view the specific support offerings available to you, go to https://www.suse.com/support/ and select your product.

The support levels are defined as follows:

L1

Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.

L2

Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.

L3

Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.

For contracted customers and partners, SUSE Linux Enterprise High Availability Extension is delivered with L3 support for all packages, except for the following:

  • Technology previews.

  • Sound, graphics, fonts, and artwork.

  • Packages that require an additional customer contract.

  • Some packages shipped as part of the module Workstation Extension are L2-supported only.

  • Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.

SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.

4.2 Technology previews Edit source

Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. The previews are included for your convenience to give you the chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, please contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.

However, technology previews come with the following limitations:

  • Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.

  • Technology previews are not supported.

  • Technology previews may only be available for specific hardware architectures.

  • Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.

  • Technology previews can be dropped at any time. For example, if SUSE discovers that a preview does not meet the customer or market needs, or does not prove to comply with enterprise standards. SUSE does not commit to providing a supported version of such technologies in the future.

For an overview of technology previews shipped with your product, see the release notes at https://www.suse.com/releasenotes/.

→Chapter 1 Challenges for Geo clusters←Geo Clustering Guide
Print this page

© 2022 SUSE