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

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

6.4. Managing Regions and Zones

Prerequisites:

With the release of OpenShift Enterprise 2.1, you can group nodes into regions and zones. Regions and zones provide a way for brokers to manage several distinct geographies by controlling application deployments across a selected group of nodes. You can group nodes into zones, and group zones into regions. These groups can represent physical geographies, such as different countries or data centers, or can be used to provide network level separation between node environments.
Use regions when you require all application developers to use the same OpenShift Enterprise deployment, but they are separated by their geographical location. Developers can tag nodes into zones, then group the zones into regions, and their workload is placed inside the corresponding hardware, zone, and region. If you have deployed a high-availability deployment, you can use a new zone for each rack in a datacenter, and, due to gear anti-affinity, any new gears will be spread across multiple zones, ensuring availability. Configuring regions in your deployment can also help avoid latency issues. You can maximize your application performance with less latency by deploying applications geographically closer to your expected users. For example, if your application is hosted in the US, and European application users are experiencing latency, you can use regions to extend your application to European-hosted datacenters to ease the application end-users' experience.
The current implementation of regions requires the use of districts. Nodes in districts can be tagged with a region and zone, while districts themselves can span several regions or a single region. Any single application is restricted to one region at a time, while gears within an application gear group are distributed across available zones in the current region. The broker attempts to distribute new gears evenly across the available zones; if the default gear placement algorithm is not desired, a custom gear placement plug-in can be implemented.

Note

When regions are in use, gear moves are allowed using the oo-admin-move tool if the move is between districted nodes and all gears in the application remain in a single region.

See Also:

6.4.1. Creating a Region with Zones
링크 복사

Use the oo-admin-ctl-region tool to create, list, or destroy regions and add or remove zones within a given region.

Procedure 6.6. To Create a Region with Zones:

  1. Create a new region. Region names can include alphanumeric characters, underscores, hyphens, and dots: 
    # oo-admin-ctl-region -c create -r region_nameoo-admin-ctl-region -c create -r region_name
    Copy to Clipboard Toggle word wrap
  2. Add zones to the region. Zone names can include alphanumeric characters, underscores, hyphens, and dots: 
    # oo-admin-ctl-region -c add-zone -r region_name -z zone_nameoo-admin-ctl-region -c add-zone -r region_name -z zone_nameoo-admin-ctl-region -c add-zone -r region_name -z zone_nameoo-admin-ctl-region -c add-zone -r region_name -z zone_name
    Copy to Clipboard Toggle word wrap
  3. Verify the new region and zones: 
    # oo-admin-ctl-region -c list -r region_nameoo-admin-ctl-region -c list -r region_name
    Copy to Clipboard Toggle word wrap
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

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

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

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

Red Hat 소개

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

Theme

© 2025 Red Hat