Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 2. Environment Requirements and Assumptions

In order to enable Instance HA, your Red Hat OpenStack Platform overcloud must meet the following requirements:

  • The environment was deployed using Red Hat OpenStack Platform director. See Director Installation and Usage for details.
  • Fencing has already manually been enabled on the control plane.

  • The following packages are installed on all nodes:

    • fence-agents-4.0.11-66.el7_4.3 (or greater)
    • pacemaker-1.1.16-12.el7.x86_64 (or greater)
    • resource-agents-3.9.5-105.el7.x86_64 (or greater)
  • The environment can tolerate a full outage of both Compute and Control planes.
  • Shared storage is enabled within the environment for ephemeral and block storage. See Section 2.1, “Exceptions for Shared Storage” for related information.

  • The Message Broker (AMQP) recognizes each Compute node’s hostname as valid. To check the hostname of a Compute node: 

    heat-admin@compute-n $ sudo crudini --get /etc/nova/nova.conf DEFAULT host
    Copy to Clipboard Toggle word wrap

  • Each Compute node should be able to reach the endpoint set in $OS_AUTH_URL. In addition, this environment variable must be set to either:

    • The overcloud’s authentication service (which requires access to the external network), or
    • The internal authentication URL.
Warning

When Instance HA is enabled, overcloud upgrade or scale-up operations are not possible. Any attempts to do so will fail. This includes both minor and major upgrades.

Before upgrading or scaling your overcloud, disable Instance HA first. For instructions, see Chapter 5, Rollback.

2.1. Exceptions for Shared Storage
링크 복사

Typically, enabling Instance HA requires shared storage. If you attempt to use the no-shared-storage option, you are likely to receive an InvalidSharedStorage error during evacuation, and instances will not power up on the other node. However, if all your instances are configured to boot up from a Block Storage (cinder) volume, then you will not need shared storage to store the disk image of instances; you will be able to evacuate all instances using the no-shared-storage option.

During evacuation, if your instances are configured to boot from a Block Storage volume, any evacuated instances can be expected to boot up from the same volume, but on another Compute node. As a result, the evacuated instances can immediately restart their jobs, as the OS image and application data are kept on the Block Storage volume.

Note

The ansible-based deployment procedure in this guide supports installation with no-shared-storage option.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat맨 위로 이동