Guillaume Coré
2018-01-26 2d30da9a4e68887d52a5f714270d5d466ea66150
refs
author Guillaume Coré <gucore@redhat.com>
Friday, January 26, 2018 15:32 +0100
committer Guillaume Coré <gucore@redhat.com>
Friday, January 26, 2018 15:39 +0100
commit2d30da9a4e68887d52a5f714270d5d466ea66150
tree 848fbbf46d28d4ea4d7b9c4d855f2b580ed80c62 tree | zip | gz
parent adb0e61d4e95464337e2c3ecc1a34e27f16ef495 view | diff
ocp 3.7: fix elasticsearch and cassandra on NFS

2 scenarii here:

1. without glusterfs

This set of variable works for 3.7 to keep ES and cassandra on NFS

see https://bugzilla.redhat.com/show_bug.cgi?id=1538995

2. with glusterfs

The idea is not to put ES and cassandra on glusterfs (not supported), instead
try to keep them on NFS. Currently this does not work, PVC for both will still
use default storageClass. It requires manual steps on PVC after the installation.
To do things properly, a new class glusterblock should be created by the
openshift-ansible playbook. This glusterblock storageclass then to be used for ES
and cassandra PVC. This is not yet possible, see:

https://bugzilla.redhat.com/show_bug.cgi?id=1534750
1 files modified
55 ■■■■■ changed files
ansible/configs/ocp-workshop/files/hosts_template.j2 55 ●●●●● diff | view | raw | blame | history