{"action":"opened","issue":{"url":"https://api.github.com/repos/openshift/openshift-ansible/issues/9799","repository_url":"https://api.github.com/repos/openshift/openshift-ansible","labels_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/9799/labels{/name}","comments_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/9799/comments","events_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/9799/events","html_url":"https://github.com/openshift/openshift-ansible/issues/9799","id":354765455,"node_id":"MDU6SXNzdWUzNTQ3NjU0NTU=","number":9799,"title":"Question: using a single glusterfs for appdata and registry","user":{"login":"Klaas-","id":3710192,"node_id":"MDQ6VXNlcjM3MTAxOTI=","avatar_url":"https://avatars0.githubusercontent.com/u/3710192?v=4","gravatar_id":"","url":"https://api.github.com/users/Klaas-","html_url":"https://github.com/Klaas-","followers_url":"https://api.github.com/users/Klaas-/followers","following_url":"https://api.github.com/users/Klaas-/following{/other_user}","gists_url":"https://api.github.com/users/Klaas-/gists{/gist_id}","starred_url":"https://api.github.com/users/Klaas-/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Klaas-/subscriptions","organizations_url":"https://api.github.com/users/Klaas-/orgs","repos_url":"https://api.github.com/users/Klaas-/repos","events_url":"https://api.github.com/users/Klaas-/events{/privacy}","received_events_url":"https://api.github.com/users/Klaas-/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-28T14:45:53Z","updated_at":"2018-08-28T14:45:53Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"#### Description\r\n\r\nQuestion: can I deploy a registry into a single glusterfs or does it need a seperate glusterfs_registry?\r\n\r\nThe examples all deal with two glusterfs, one for registry one for appdata. Can I use one for both?\r\n\r\n##### Version\r\n\r\n```\r\n# ansible --version\r\nansible 2.4.6.0\r\n  config file = /root/ansible-environment/ansible.cfg\r\n  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']\r\n  ansible python module location = /usr/lib/python2.7/site-packages/ansible\r\n  executable location = /usr/bin/ansible\r\n  python version = 2.7.5 (default, May 31 2018, 09:41:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]\r\n\r\n\r\n# rpm -q openshift-ansible\r\nopenshift-ansible-3.10.21-1.git.0.6446011.el7.noarch\r\n```\r\n\r\n\r\n##### Additional Information\r\n\r\nProvide any additional information which may help us diagnose the\r\nissue.\r\n\r\n* Current RHEL 7.5\r\n\r\nInventory (currently not running, this is just my idea of how the inventory should look like)\r\n\r\n```\r\n[OSEv3:children]\r\nmasters\r\nnodes\r\netcd\r\nglusterfs\r\nlb\r\n\r\n[OSEv3:vars]\r\n# use root\r\nansible_ssh_user=root\r\n\r\nopenshift_deployment_type=openshift-enterprise\r\nopenshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'true', 'challenge': 'true', 'kind': 'HTPasswdPasswordIdentityProvider'}]\r\n# Use containers\r\ncontainerized=true\r\n# Use network isolation\r\nos_sdn_network_plugin_name=redhat/openshift-ovs-multitenant\r\n\r\n# Use firewalld instead of iptables\r\nos_firewall_use_firewalld=True\r\n\r\n# Wildcard Domain\r\nopenshift_master_default_subdomain=openshift.domain.tld\r\nopenshift_master_cluster_method=native\r\nopenshift_master_cluster_hostname=masterlb-openshift.domain.tld\r\n\r\n# registry gluster\r\nopenshift_hosted_registry_storage_kind=glusterfs\r\nopenshift_hosted_registry_storage_volume_size=5Gi\r\nopenshift_hosted_registry_selector='node-role.kubernetes.io/infra=true'\r\n\r\n# use metrics\r\nopenshift_metrics_install_metrics=true\r\nopenshift_metrics_cassandra_storage_type=dynamic\r\n\r\n# use logging\r\nopenshift_logging_install_logging=true\r\nopenshift_logging_es_pvc_dynamic=true\r\n\r\n## Gluster\r\nopenshift_storage_glusterfs_namespace=app-storage\r\nopenshift_storage_glusterfs_storageclass=true\r\nopenshift_storage_glusterfs_storageclass_default=true\r\nopenshift_storage_glusterfs_block_deploy=true\r\nopenshift_storage_glusterfs_block_host_vol_size=100\r\nopenshift_storage_glusterfs_block_storageclass=true\r\nopenshift_storage_glusterfs_block_storageclass_default=false\r\n\r\n[masters]\r\nmaster1.domain.tld\r\nmaster2.domain.tld\r\nmaster3.domain.tld\r\n\r\n[etcd]\r\nmaster1.domain.tld\r\nmaster2.domain.tld\r\nmaster3.domain.tld\r\n\r\n[lb]\r\nlb.domain.tld\r\n\r\n[nodes]\r\nmaster1.domain.tld openshift_node_group_name='node-config-master'\r\nmaster2.domain.tld openshift_node_group_name='node-config-master'\r\nmaster3.domain.tld openshift_node_group_name='node-config-master'\r\ninfra1.domain.tld openshift_node_group_name='node-config-infra'\r\ninfra2.domain.tld openshift_node_group_name='node-config-infra'\r\ninfra3.domain.tld openshift_node_group_name='node-config-infra'\r\nnode1.domain.tld openshift_node_group_name='node-config-compute'\r\nnode2.domain.tld openshift_node_group_name='node-config-compute'\r\n\r\n[glusterfs]\r\ninfra1.domain.tld glusterfs_devices='[ \"/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:2\" ]'\r\ninfra2.domain.tld glusterfs_devices='[ \"/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:2\" ]'\r\ninfra3.domain.tld glusterfs_devices='[ \"/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:2\" ]'\r\n```\r\n"}}
{"actor":{"display_login":"Klaas-"}}