Support for deploying to CentOS #119
Comments
|
This is coming up now but not quite working yet. ZFS Is running on my CentOS host: And a StorageClass is set up for the SaturnPool storage pool. However, after creating a PVC and a Pod like so: The Which indicates to me that it is still encountering some errors:
|
|
|
Centos Version: Linux Version: ZFS Version: |
|
I have added this to our Roadmap (https://github.com/orgs/openebs/projects/10). Will work on it to add the support for centOS in next release (v0.6). However I need one help from you if you can, I tried to install ZFS 0.8 on our in-house CentOS7.7 machine by following https://github.com/openzfs/zfs/wiki/RHEL-and-CentOS, but I could not succeed. Could you help us with the steps you used to install it on your machine. |
|
@pawanpraka1 here is an Ansible role to do so on CentOS 7.7. https://github.com/zimmertr/Bare_Metal_Kubeadm/blob/master/ansible/roles/prepare_zfs/tasks/main.yml |
|
See if this modified yaml with local image is working for you https://raw.githubusercontent.com/pawanpraka1/zfs-localpv/centos/deploy/zfs-operator.yaml This yaml is using image from my docker hub pawanpraka1/zfs-driver:centos I have changed the docker file(buildscripts/zfs-driver/Dockerfile) and compiled and push the image to my own docker hub |
|
Hi, thank you for the quick turnaround! Everything provisions as expected and I can confirm that the ZFS Volumes are created on my Pool. However, OpenEBS appears to fail to format the filesystem on the volume. These logs are produced: |
|
Can you try this storage class. Modify the pool name accordingly. |
|
Hi, looks like things are working! Thank you for your help. |
|
Reopening it, will close it once we have changes in production. |
|
I am also facing issue on CentOS 8 nodes with this driver. |
|
Please use the manifests and image described in this comment by @pawanpraka1 until this has been resolved upstream. |
|
I have used that image and the also the SC yaml that is also mentioned. |
|
finally worked this out, the image is CentOS7 based... I can update the docker image but I need to know how to run the make file to get the zfs-driver alternatively can I just copy that out of the existing container and into the the new one ? |
|
@jlcox1970 sorry, we couldn't prioritize this in to our release. Clone this repo https://github.com/pawanpraka1/zfs-localpv and go to the CentOS branch. then Just change the image to centos8 in the docker file https://github.com/pawanpraka1/zfs-localpv/blob/centos/buildscripts/zfs-driver/Dockerfile. To create the image, you just have to do |
|
@pawanpraka1 thats ok and i am happy to help as this is my cluster at home :) as for the make, I have never used go before and so I have a whole lot of errors that come up |
pawanpraka1
added
the
Need community involvement
|
@jlcox1970 here is the developer setup doc : https://github.com/openebs/zfs-localpv/blob/master/docs/developer-setup.md. You can follow this to setup go : https://www.tecmint.com/install-go-in-linux/ (use golang version 1.12.5). I have pushed the centos8 image also and updated the operator file with that. You can try this yaml which is using centos8 image : https://raw.githubusercontent.com/pawanpraka1/zfs-localpv/centos/deploy/zfs-operator.yaml |
|
@pawanpraka1 that fixed it nicely :) |
|
Sure @jlcox1970 . Just to confirm, you are able to provision the volume using the latest yaml? |
|
can you also provide the below details :
|
|
yes the volume is provisioned linux-vdso.so.1 (0x00007fff74dcb000) CentOS Linux release 8.1.1911 (Core) |
|
@zimmertr, @jlcox1970 I am working on a change(pawanpraka1@6c567bd) which can work for both ubuntu and centos. I have tested it on ubuntu, and it seems to be working. I need one help/favor from you guys, if you can test this on centos7 and centos8 and if it is working then I will upstream this change. https://raw.githubusercontent.com/pawanpraka1/zfs-localpv/lib/deploy/zfs-operator.yaml |
|
I have actually moved away from CentOS 7 to Flatcar Linux since making this post and do not have a server available to test anymore. If @jlcox1970 is unable to as well, I could probably spin something up in a VM though. It just won't resemble a production environment any longer. I haven't yet tested this with Flatcar. Is that distro supported? |
|
@zimmertr thanks. Flatcar will also be supported if the libraries required for zfs is in /lib or /lib64 and binary is installed at /sbin/zfs or /usr/sbin/zfs. If that is the case then same yaml will work, otherwise we have to make little modification to the yaml and it should just work.
|
|
sorry on the delay on this but work......
got to testing and found that the openebs-zfs-plug keeps failing and
the only thing in the logs are
*** stack smashing detected ***: <unknown> terminated
Jason
…On Tue, 2020-05-26 at 04:54 -0700, Pawan Prakash Sharma wrote:
@zimmertr, @jlcox1970 I am working on a ***@***.***)
which can work for both ubuntu and centos. I have tested it on
ubuntu, and it seems to be working. I need one help/favor from you
guys, if you can test this on centos7 and centos8 and if it is
working then I will upstream this change.
https://raw.githubusercontent.com/pawanpraka1/zfs-localpv/lib/deploy/zfs-operator.yaml
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@jlcox1970 thanks for helping me with the testing. It seems like there is more work needs to be done in this. I should probably restrict the host libraries to zfs binary only. Currently the whole pod is exposed to the host libraries and that is probably causing the issue. Let me fix that. Thanks again @jlcox1970 . |
|
@jlcox1970, sorry for the delay, Please see if the below yaml works for you for CentOS7 => CentOS8 => |
|
We have upstreamed the centos7 and centos8 yaml here |
|
We have merged a PR #204 to make the ZFS operator yaml not agnostic to the underlying Operation system. In 1.0 and onward releases we can use the same Operator yaml (https://github.com/openebs/zfs-localpv/blob/master/deploy/zfs-operator.yaml) of all the Operating systems. |
Description
The
zfs-Operatormanifest is incompatible with ZFS. After deployment some hostPath references to libraries fail.Context
I use CentOS/RHEL in production not Ubuntu.
Possible Solution
This manifest with modified libraries was sent to me via Slack and is deploying successfully.
The text was updated successfully, but these errors were encountered: