2、在任意一台服务器上配置
gluster volume create gv0 replica server2:/data/brick1/gv0 #创建卷
gluster volume start gv0 gluster volume info
#启动卷 #查看卷信息
2
server1:/data/brick1/gv0
3.6 测试GlusterFS卷
在此处,我们选择一个服务器同时做为客户端进行测试
mount -t glusterfs server1:/gv0 /mnt #挂载卷
for i in `seq -w 1 100`; #向卷写入数据
do cp -rp /var/log/messages /mnt/copy-test-$i; done
石家庄众毅信息技术有限公司共47页第25页
第4章 建议物理安装环境
1、 确保DNS 和NTP正常工作
2、 10GBE 或InfiniBand是最佳的后端存储网络, 但是即使 1GBE 也可以让你得到大部分
的功能. 确保您要使用的接口也在 dns 中, 因为我们将在部署 gluster 时使用主机名 3、 说到磁盘, 越多越好。尽管在技术上可以用单个磁盘来伪造, 但一旦您尝试在服务器上
执行任何实际工作, 就会出现性能问题
石家庄众毅信息技术有限公司共47页第26页
第5章 Did you know?
This document is an attempt to describe less-documented behaviours and features of GlusterFS that an admin always wanted to know but was too shy or busy to ask.
这份文件试图描述 GlusterFS 的行为和特征, 管理员总是想知道, 但过于害羞或繁忙的要求。
Trusted Volfiles信任 volfiles
Observant admins would have wondered why there are two similar volume files for every volume, namely trusted--fuse.vol and -fuse.vol. To appreciate this one needs to know about the IP address/hostname based access restriction schemes available in GlusterFS. They are \and \The \and \options take a comma separated list of IP addresses/hostnames as value. \allows access only to clients running on machines whose IP address/hostname are on this list. It is highly likely for an admin to configure the \option without including the list of nodes in the cluster. One would expect this to work. Previously, in this configuration (internal) clients such as gluster-nfs, glustershd etc., running in the trusted storage pool, would be denied access to the volume. This is undesirable and counter-intuitive. The work around was to add the IP address/hostnames of all the nodes in the trusted storage pool to the \fix this, an alternate authentication mechanism for nodes in the storage pool was introduced. Following is a brief explanation of how this works.
细心的管理员会想知道为什么每卷都有两个类似的卷文件, 即可trusted--fuse.vol 和-fuse.vol。要理解这一点, 需要了解 GlusterFS 中可用的基于 ip 地址/主机名的访问限制方案。它们是 \授权许可\和 \认证-拒绝\。\授权允许\和 \授权拒绝\选项以逗号分隔的 ip 地址/主机名列表作为值。\授权允许\仅允许在其 ip 地址/主机名所在的计算机上运行的客户端访问此列表。管理员极有可能配置 \授权允许\选项, 而不包括群集中的节点列表。人们希望这能奏效。以前, 在受信任存储池中运行的此配置 (内部) 客户端 (如 gluster nfs、glustershd 等) 将被拒绝访问该卷。这是不可取的和反直觉的。周围的工作是将受信任存储池中所有节点的 ip 地址/主机名添加到 \授权允许\列表中。这对于数量相当大的节点来说是不好的。为解决此问题, 引入了一个用于存储池中节点的备用身份验证机制。下面是对如何工作的简要说明。
The volume file with trusted prefix in its name (i.e trusted-volfile) has a username and password option in the client xlator. The trusted-volfile is used only by mount processes running in the trusted storage pool (hence the name). The username and password, when present, allow \(and other glusterfs) processes to access the brick processes even if the node they are running on is not explicitly added in \on nodes outside the trusted storage pool, use the non-trusted-volfile. The important thing to note is that \
在其名称中具有受信任前缀的卷文件 (i. e trusted--fuse.vol) 在客户端 xlator 中有一个用户名和密码选项。受信任的 volfile 仅由在受信任的存储池中运行的挂载进程 (因此名称) 使用。用户名和密码, 当出现时, 允许 \装载\和其他 glusterfs) 进程访问砖块进程, 即使他们正在运行的节点没有显式添加到 \授权允许\地址。\常规\挂载进程在受信任的存储池石家庄众毅信息技术有限公司共47页第27页
外的节点上运行, 使用信任-volfile。需要注意的重要一点是, 在此上下文中, \受信任\仅隐含属于受信任的存储池。
石家庄众毅信息技术有限公司共47页第28页
第6章 为RHEL/CentOS编译rpm安装包
RPMS can be compiled on at least the following OS's: Red Hat Enterprise Linux 5, 6 (& 7 when available) CentOS 5, 6 (& 7 when available) Fedora 16-20
Specific instructions for compiling are below. If you're using:
Fedora 16-20 - Follow the Fedora steps, then do all of the Common steps. CentOS 5.x - Follow the CentOS 5.x steps, then do all of the Common steps CentOS 6.x - Follow the CentOS 6.x steps, then do all of the Common steps.
RHEL 6.x - Follow the RHEL 6.x steps, then do all of the Common steps.
6.1 准备
6.1.1 Preparation steps for Fedora 16-20 (only)
Install gcc, the python development headers, and python setuptools: $ sudo yum -y install gcc python-devel python-setuptools
If you're compiling GlusterFS version 3.4, then install python-swiftclient. Other GlusterFS versions don't need it:
$ sudo easy_install simplejson python-swiftclient
6.1.2 Preparation steps for CentOS 5.x (only)
Install EPEL first:
$
curl
-OL
`[`http://download.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm`](http://download.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm)
$ sudo yum -y install epel-release-5-4.noarch.rpm --nogpgcheck
Install the packages required only on CentOS 5.x:
$ sudo yum -y install buildsys-macros gcc ncurses-devel python-ctypes python-sphinx10 \\
6.1.3 Preparation steps for CentOS 6.x (only)
Install EPEL first:
$yum
-y
install
`[`http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm`](http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm)
石家庄众毅信息技术有限公司共47页第29页
百度搜索“77cn”或“免费范文网”即可找到本站免费阅读全部范文。收藏本站方便下次阅读,免费范文网,提供经典小说综合文库GlusterFS学习笔记(翻译by 张文超)(6)在线全文阅读。
相关推荐: