Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create LVMCluster resource on crc start #4097

Closed
3 tasks
anjannath opened this issue Apr 3, 2024 · 3 comments
Closed
3 tasks

create LVMCluster resource on crc start #4097

anjannath opened this issue Apr 3, 2024 · 3 comments

Comments

@anjannath
Copy link
Member

after crc-org/snc#867 openshift bundles will have the LVMS operator installed in the cluster, to make use of it we need to create the LVMCluster crd resource provided by the operator to have the necessary storage class, CSI drivers setup to handle dynamic provisioning of the PVCs

to create the LVMCluster resource we also need to provide the disk to be used for creating the lvm volumes, so we need to also create a second disk image for the vm.

apiVersion: lvm.topolvm.io/v1alpha1
kind: LVMCluster
metadata:
  name: my-lvmcluster
spec:
  storage:
    deviceClasses:
    - name: vg1
      fstype: ext4 
      default: true
      deviceSelector: 
        paths:
        - /dev/disk/by-path/pci-0000:87:00.0-nvme-1
        - /dev/disk/by-path/pci-0000:88:00.0-nvme-1
        forceWipeDevicesAndDestroyAllData: true
      thinPoolConfig:
        name: thin-pool-1
        sizePercent: 90 
        overprovisionRatio: 10

Todo

  • add creation of second disk image in drivers (vfkit, libvirt and hyper-v drivers)
  • add a config option to enable users to choose if they want to use LVMS operator
  • create disk and LVMCluster resource during crc start
@cfergeau
Copy link
Contributor

cfergeau commented Apr 3, 2024

add a config option to enable users to choose if they want to use LVMS operator

why a config option?

@anjannath
Copy link
Member Author

add a config option to enable users to choose if they want to use LVMS operator

why a config option?

initially, i thought of having a config option to enable/disable the topolvm, and also keep the hostpath-provisioner that we have currently, but it doesn't have any usefulness for users, it was just a thought to be able to test quickly the new topolvm without removing the hostpath-provisioner

@anjannath
Copy link
Member Author

this is not needed anymore, installation of the operator is now handled in snc, by crc-org/snc#877

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants