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

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

9.3. Configuring Network Encryption for an existing Trusted Storage Pool

You can configure network encryption for an existing Red Hat Gluster Storage Trusted Storage Pool for both I/O encryption and management encryption.

9.3.1. Enabling I/O encryption for a Volume
링크 복사

Enable the I/O encryption between the servers and clients:
  1. Unmount the volume on all the clients. 
    # umount mount-point# umount mount-point
    Copy to Clipboard Toggle word wrap
  2. Stop the volume. 
    # gluster volume stop VOLNAME# gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Set the list of common names for clients allowed to access the volume. Be sure to include the common names of all the servers. 
    # gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'# gluster volume set VOLNAME auth.ssl-allow 'server1,server2,server3,client1,client2,client3'
    Copy to Clipboard Toggle word wrap
  4. Enable client.ssl and server.ssl on the volume. 
    # gluster volume set VOLNAME client.ssl on
# gluster volume set VOLNAME server.ssl on
    Copy to Clipboard Toggle word wrap
  5. Start the volume. 
    # gluster volume start VOLNAME# gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  6. Mount the volume from the new clients. For example, to manually mount a volume and access data using Native client, use the following command: 
    # mount -t glusterfs server1:/test-volume /mnt/glusterfs
    Copy to Clipboard Toggle word wrap

9.3.2. Enabling Management Encryption
링크 복사

Though, Red Hat Gluster Storage can be configured only for I/O encryption without using management encryption, management encryption is recommended. On an existing installation, with running servers and clients, schedule a downtime of volumes, applications, clients, and other end-users to enable management encryption.
You cannot currently change between unencrypted and encrypted connections dynamically. Bricks and other local services on the servers and clients do not receive notifications from glusterd if they are running when the switch to management encryption is made.
  1. Unmount the volume on all the clients. 
    # umount mount-point# umount mount-point
    Copy to Clipboard Toggle word wrap
  2. Stop all the volumes. 
    # gluster volume stop VOLNAME# gluster volume stop VOLNAME
    Copy to Clipboard Toggle word wrap
  3. Stop glusterd on all servers. 
    # service glusterd stop
    Copy to Clipboard Toggle word wrap
  4. Stop all gluster-related processes on all servers. 
    # pkill glusterfs
    Copy to Clipboard Toggle word wrap
  5. Create the /var/lib/glusterd/secure-access file on all servers and clients. 
    # touch /var/lib/glusterd/secure-access
    Copy to Clipboard Toggle word wrap
  6. Start glusterd on all the servers. 
    # service glusterd start
    Copy to Clipboard Toggle word wrap
  7. Start all the volumes 
    # gluster volume start VOLNAME# gluster volume start VOLNAME
    Copy to Clipboard Toggle word wrap
  8. Mount the volume on all the clients. For example, to manually mount a volume and access data using Native client, use the following command: 
    # mount -t glusterfs server1:/test-volume /mnt/glusterfs
    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