Bug 1471718
Summary: | [RFE] Allow to create storageclass at installation time | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eduardo Minguez <eminguez> |
Component: | Installer | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.5.0 | CC: | aos-bugs, bleanhar, eminguez, gpei, jokerman, mmccomas, tatanaka |
Target Milestone: | --- | ||
Target Release: | 3.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
You may now configure an arbitrary storage class at installation time. In order to do so set variables like the following in your inventory.
openshift_storageclass_name=test-1
openshift_storageclass_provisioner=rbd
openshift_storageclass_parameters={'fstype': 'ext4', 'iopsPerGB': '10', 'foo': 'bar'}
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-30 19:08:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eduardo Minguez
2017-07-17 10:13:57 UTC
Eduardo what cloud provider are you using? Hi Scott, I think this should be "cross provider" because if you want to deploy logging at installation time with a custom storageclass, you should do it no matter what provider you are using. I think the idea will be to have an ansible variable with the storageclass definition and create it just after the installation and before creating the router, registry, logging, etc. so you can use it "out of the box" for the registry, logging, metrics, etc. Thanks! Yeah, we do that today for GCE and AWS. But I believe there's no way to define a generic default storage class that works across all providers, am I mistaken? Not generic, but to be able to allow users to create them at installation time. I'm thinking in something like this (just an example) * default_storageclass_name = whatever * default_storageclass_provisioner = kubernetes.io/rbd (or any other) * default_storageclass_parameters = [{'fstype': 'ext4', 'iopsPerGB': '10', 'foo': 'bar'}] Sorry, pressed enter too soon... Or something like the ldap authentication stuff: * default_storage_class = [{'name': 'whatever', 'provisioner': 'kubernetes.io/rbd', 'fstype': 'ext4', 'iopsPerGB': '10', 'foo': 'bar'}] Default storage classes should be created in 3.9 and later. Verify this bug with openshift-ansible-3.10.0-0.22.0.git.0.b6ec617.el7.noarch.rpm With the following options setting in inventory file, start installation. openshift_storageclass_name=test-1 openshift_storageclass_provisioner=rbd openshift_storageclass_parameters={'fstype': 'ext4', 'iopsPerGB': '10', 'foo': 'bar'} After installation finished, check the default storageclass [root@qe-gpei-310test2master-etcd-1 ~]# oc get storageclass NAME PROVISIONER AGE test-1 (default) kubernetes.io/rbd 1h [root@qe-gpei-310test2master-etcd-1 ~]# oc describe storageclass test-1 Name: test-1 IsDefaultClass: Yes Annotations: storageclass.beta.kubernetes.io/is-default-class=true Provisioner: kubernetes.io/rbd Parameters: foo=bar,fstype=ext4,iopsPerGB=10 AllowVolumeExpansion: <unset> MountOptions: <none> ReclaimPolicy: Delete VolumeBindingMode: Immediate Events: <none> Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1816 |