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

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

Chapter 7. Manual Post-Deployment Tasks

The Puppet module attempts to automate as many tasks as it reasonably can. However, it is constrained to setting up only a single host at a time. In an assumed multi-host setup, you must perform the following manual post-deployment tasks after the module has completed.
  1. Set up DNS entries for hosts. If you installed BIND using the Puppet module, then any other components installed with the module on the same host received DNS entries. Other hosts must all be defined manually, including at least your node hosts. The oo-register-dns command on a broker host may prove useful for this.
  2. Copy the rsync public key to enable moving gears. The broker rsync public key must go on nodes, but it is difficult to script the task generically. Nodes should not have password-less access to brokers to copy the .pub key, so this must be performed manually on each node host: 
    # scp root@broker:/etc/openshift/rsync_id_rsa.pub /root/.ssh/
(The above step will ask for the root password of the broker machine.)
# cat /root/.ssh/rsync_id_rsa.pub >> /root/.ssh/authorized_keys
# rm /root/.ssh/rsync_id_rsa.pub
    Copy to Clipboard Toggle word wrap
    If you skip this step, each gear move requires typing root passwords for each of the node hosts involved.
  3. Copy SSH host keys between the node hosts. All node hosts must identify with the same host keys, so that when gears are moved between hosts, ssh, and git do not give developers spurious warnings about the host keys changing. Copy /etc/ssh/ssh_* from one node host to all of the rest. Alternatively, if using the same image for all hosts, keep the keys from the image.
  4. Create districts. Nodes must belong to a district in order to work properly. Adding a node to a district after the node already has hosted applications running on it is very difficult, so it is important to do during the initial deployment. For a discussion of what districts are, see the OpenShift Enterprise Administration Guide [12].
    On a broker host, run the following command to define a new district: 
    # oo-admin-ctl-district -c create -n District_Name -p Gear_Profileoo-admin-ctl-district -c create -n District_Name -p Gear_Profileoo-admin-ctl-district -c create -n District_Name -p Gear_Profileoo-admin-ctl-district -c create -n District_Name -p Gear_Profile
    Copy to Clipboard Toggle word wrap
    To perform a blank assignment of all nodes to a district, run: 
    # oo-admin-ctl-district -c add-node -n District_Name -aoo-admin-ctl-district -c add-node -n District_Name -aoo-admin-ctl-district -c add-node -n District_Name -a
    Copy to Clipboard Toggle word wrap
    Otherwise add nodes one at a time with: 
    # oo-admin-ctl-district -c add-node -n District_Name -i Node_Hostnameoo-admin-ctl-district -c add-node -n District_Name -i Node_Hostnameoo-admin-ctl-district -c add-node -n District_Name -i Node_Hostnameoo-admin-ctl-district -c add-node -n District_Name -i Node_Hostname
    Copy to Clipboard Toggle word wrap
  5. Import cartridge manfiests. Run the following command on a broker host to import the cartridge manifests for all cartridges installed on nodes: 
    # oo-admin-ctl-cartridge -c import-profile --activate --obsolete
    Copy to Clipboard Toggle word wrap
    This registers the cartridges with the broker and makes them available to developers for new hosted applications.

Note

For further information on administering an OpenShift Enterprise deployment, see the OpenShift Enterprise Administration Guide [13].

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

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

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

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

Red Hat 소개

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

Theme

© 2025 Red Hat