Re: specifying storage class for metrics and logging
openshift_logging_elasticsearch_pvc_dynamic is a deprecated variable that defined the alpha feature of PV->PVC associations prior to the introduction of storage classes On Tue, Apr 17, 2018 at 6:26 AM, Per Carlson wrote: > Hi. > > On 17 April 2018 at 12:17, Tim Dudgeon wrote: > >> So if you are using dynamic provisioning the only option for logging is >> for the default StorageClass to be set to what is needed? >> >> On 17/04/18 11:12, Per Carlson wrote: >> >> This holds at least for 3.7: >> >> For metrics you can use "openshift_metrics_cassanda_pvc_storage_class_name" >> (https://github.com/openshift/openshift-ansible/blob/release >> -3.7/roles/openshift_metrics/tasks/generate_cassandra_pvcs.yaml#L44). >> >> Using a StorageClass for logging (ElasticSearch) is more confusing. The >> variable is "openshift_logging_elasticsearch_pvc_storage_class_name" ( >> https://github.com/openshift/openshift-ansible/blob/release >> -3.7/roles/openshift_logging_elasticsearch/defaults/main.yml#L34). But, >> it is only used for non-dynamic PVCs (https://github.com/openshift/ >> openshift-ansible/blob/release-3.7/roles/openshift_logging_ >> elasticsearch/tasks/main.yaml#L368-L370). >> >> >> -- >> Pelle >> >> Research is what I'm doing when I don't know what I'm doing. >> - Wernher von Braun >> >> >> > > No, I think you can use a StorageClass by keeping > "openshift_logging_elasticsearch_pvc_dynamic" > is false. Not sure if that has any side effects though. > > -- > Pelle > > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > -- -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering OpenShift Integration Services Red Hat, Inc. *Office*: 703-748-4420 | 866-546-8970 ext. 8162420 jcant...@redhat.com http://www.redhat.com ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: specifying storage class for metrics and logging
Hi. On 17 April 2018 at 12:17, Tim Dudgeon wrote: > So if you are using dynamic provisioning the only option for logging is > for the default StorageClass to be set to what is needed? > > On 17/04/18 11:12, Per Carlson wrote: > > This holds at least for 3.7: > > For metrics you can use "openshift_metrics_cassanda_pvc_storage_class_name" > (https://github.com/openshift/openshift-ansible/blob/ > release-3.7/roles/openshift_metrics/tasks/generate_cassandra_pvcs.yaml#L44 > ). > > Using a StorageClass for logging (ElasticSearch) is more confusing. The > variable is "openshift_logging_elasticsearch_pvc_storage_class_name" ( > https://github.com/openshift/openshift-ansible/blob/ > release-3.7/roles/openshift_logging_elasticsearch/defaults/main.yml#L34). > But, it is only used for non-dynamic PVCs (https://github.com/openshift/ > openshift-ansible/blob/release-3.7/roles/openshift_ > logging_elasticsearch/tasks/main.yaml#L368-L370). > > > -- > Pelle > > Research is what I'm doing when I don't know what I'm doing. > - Wernher von Braun > > > No, I think you can use a StorageClass by keeping "openshift_logging_elasticsearch_pvc_dynamic" is false. Not sure if that has any side effects though. -- Pelle ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: specifying storage class for metrics and logging
So if you are using dynamic provisioning the only option for logging is for the default StorageClass to be set to what is needed? On 17/04/18 11:12, Per Carlson wrote: This holds at least for 3.7: For metrics you can use "openshift_metrics_cassanda_pvc_storage_class_name" (https://github.com/openshift/openshift-ansible/blob/release-3.7/roles/openshift_metrics/tasks/generate_cassandra_pvcs.yaml#L44). Using a StorageClass for logging (ElasticSearch) is more confusing. The variable is "openshift_logging_elasticsearch_pvc_storage_class_name" (https://github.com/openshift/openshift-ansible/blob/release-3.7/roles/openshift_logging_elasticsearch/defaults/main.yml#L34). But, it is only used for non-dynamic PVCs (https://github.com/openshift/openshift-ansible/blob/release-3.7/roles/openshift_logging_elasticsearch/tasks/main.yaml#L368-L370). -- Pelle Research is what I'm doing when I don't know what I'm doing. - Wernher von Braun ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
specifying storage class for metrics and logging
If using dynamic provisioning for metrics and logging e.g. your inventory file contains: openshift_metrics_cassandra_storage_type=dynamic How does one go about specifying the StorageClass to uses? Without this the default storage class would be used which is not what you might want. Tim ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
