On Wed, Nov 8, 2017, at 02:29 PM, Stephen Milner wrote:
> What about literally providing dkms in a container? It wouldn't > directly take care of the original request but it would give an avenue > for folks to use the dkms toolchain if they'd like to in AH without > package layering. Maybe? Are we trying to replace dkms for yum-managed systems too? I'm a bit worried about the sustainability of adding a whole other model to dkms without trying to delete one at the same time. That said, it might not be *too* hard to get a PoC here. Offhand I feel like focusing on cri-o/kube in-syscontainers is more important? Just today I saw from IRC chat: https://github.com/kubernetes/contrib/commit/9bef0bee1c4881469fbd1688b6e6c73a30ebb8d9 Yet there's no https://github.com/kubernetes-incubator/kubespray for any *AH =( (Or for that matter Fedora...I just glanced at it and it looks like it's python2, which brings us to https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-August/msg00001.html ) Though someone who's doing e.g. OpenShift-on-AH and wants to do GPGPU/ML using Nvidia GPUs in their cluster might have a different perspective!
