Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

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

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat