B. Finishing Atomic overlay support; making hardware enablement an overlay
This could be highly useful for supporting things that need to be added for support of the base daemon set of an Atomic host, e.g. gluster clients and fuse for GlusterFS persistent storage support. But I think we'd need to clone Colin to make this faster... The idea of a containerized version of k8s that shipped all the relevant needed packages for all the k8s specific support.
Alternatively, if we think that having glusterfs / ceph / etc available as a "native" storage method, then I guess that would be a feature add.
C. Getting all this stuff to work properly in SPCs
There is a "tools" (fedora/tools) SPC that starts down this road. I'm sure that could use some more eyes and work on what needs to be added and how things work. I'm not sure what tools would need to be taught in order to use the /host mount or to change how the underlying host gets represented up. Maybe we can get a thread going around updates to the tools SPC?
- Matt M
On Tue, Dec 15, 2015 at 9:08 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Mon, Dec 14, 2015 at 03:11:04PM -0700, Chris Murphy wrote:
> Should I just file bugs like that for each one of these other missing
> components, and set them to block a tracker bug for things to include
> on the ISO? In my view a baremetal installation is first a server, so
> it should have basic server tools.
The hardware enablement and configuration stuff needs to be available,
I agree. Unfortunately, after all of these years, hardware is still
terrible.* But I'm not sure stuffing every possible tool into Atomic is
the way to go. Options I can see are:
A. Separate hardware/virt trees; have the installer ISO point at the
hardware one by default (but also have the option of virt)
B. Finishing Atomic overlay support; making hardware enablement an overlay
C. Getting all this stuff to work properly in SPCs
D. Something else?
* so is software. *sigh*
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
