我从一个节点的Openshift集群开始,它成功地部署了主/节点和gluster卷。现在我扩展了Openshift集群,它成功了。
但在扩展glusterfs体积时
[glusterfs]
10.1.1.1 glusterfs_devices='[ "/dev/vdb" ]'
10.1.1.2 glusterfs_devices='[ "/dev/vdb" ]' openshift_node_labels="type=upgrade"
ansible-playbook -i inventory2.ini /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/config.yml -e openshift_upgrade_nodes_label="type=upgrade"
它只添加了10.1.1.2作为对等,但卷仍然只有一块砖
完成以下定制以从1节点{--none}开始部署gluster
openshift-ansible/roles/openshift_storage_glusterfs/tasks/heketi_init_db.yml
- name: Create heketi DB volume
command: "{{ glusterfs_heketi_client }} setup-openshift-heketi-storage --image {{ glusterfs_heketi_image }} --listfile /tmp/heketi-storage.json **--durability none**"
register: setup_storage
>gluster peer status
Number of Peers: 1
Hostname: 10.1.1.2
Uuid: 1b8159e4-99e2-4f4d-ad95-e97bc8655d32
State: Peer in Cluster (Connected)
gluster volume info
Volume Name: heketidbstorage
Type: Distribute
Volume ID: 769419b9-d28f-4cdd-a8f3-708b6b738f65
Status: Started
Snapshot Count: 0
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.1.1.1:/var/lib/heketi/mounts/vg_4187bfa3eb090ceffea9c53b156ddbd4/brick_80401b43be8c3c8a74417b18ad574524/brick
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
预期/期望的行为
我希望在添加每个新节点时,它也会创建新的砖块
有关如何复制的详细信息(最小和精确)
Add nodes in gluster cluster with below commands
ansible-playbook -i inventory2.ini /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/config.yml -e openshift_upgrade_nodes_label="type=upgrade"
有关环境的信息:
-
OpenShift 3.10
-
使用的操作系统:
森托斯
-
Heketi从源代码处编译,作为包(rpm/deb)或容器:
容器
-
如果是容器,请选择哪个容器图像:
docker.io/heketi/heketi:最新版本
-
使用kubernetes、openshift或直接安装:
-
如果是kubernetes/openshift,gluster是在kubernetes/openshift内部运行还是在外部运行:
外部
-
openshift-ansible
