Hi I hope this is the appropriate forum for my question. I am recompiling a F20 kernel as part of preparing a custom image for use on Google Cloud. I wish to build a minimal nginx+node.js+mondodb server image. I am attempting to compile an image in accordance with Google's recommendations here: https://developers.google.com/compute/docs/building-image#providedkernel
Apart from Google's recommendations, there seem to be a large number of other features that could/should be disabled. Is there an existing guide anywhere as to how much useless stuff can be safely disabled in the kernel in this use case?
Thanks
Mike
----- Original Message -----
From: "Michael Hall" mike@mjhall.org To: cloud@lists.fedoraproject.org Sent: Tuesday, January 14, 2014 9:08:55 AM Subject: F20 Kernel recompile for Google Cloud
Hi I hope this is the appropriate forum for my question. I am recompiling a F20 kernel as part of preparing a custom image for use on Google Cloud. I wish to build a minimal nginx+node.js+mondodb server image. I am attempting to compile an image in accordance with Google's recommendations here: https://developers.google.com/compute/docs/building-image#providedkernel
Apart from Google's recommendations, there seem to be a large number of other features that could/should be disabled. Is there an existing guide anywhere as to how much useless stuff can be safely disabled in the kernel in this use case?
I think this could be what you need now: https://fedoraproject.org/wiki/Building_a_custom_kernel
Kind regards, Tuan
Thanks Truong, I am using that page. What I would like to know is how much I can safely disable in the kernel. Does anyone have a list of what most VM images don't need? For example, it seems that most hardware support can go, and most filesystem support that isn't needed. I would like to build a s small a kernel as possible that will still function securely.
Thanks Mike
On Tue, Jan 14, 2014 at 11:44 AM, Truong Anh. Tuan tuanta@iwayvietnam.comwrote:
----- Original Message -----
From: "Michael Hall" mike@mjhall.org To: cloud@lists.fedoraproject.org Sent: Tuesday, January 14, 2014 9:08:55 AM Subject: F20 Kernel recompile for Google Cloud
Hi I hope this is the appropriate forum for my question. I am recompiling a F20 kernel as part of preparing a custom image for
use on
Google Cloud. I wish to build a minimal nginx+node.js+mondodb server image. I am attempting to compile an image in accordance with Google's recommendations here: https://developers.google.com/compute/docs/building-image#providedkernel
Apart from Google's recommendations, there seem to be a large number of
other
features that could/should be disabled. Is there an existing guide anywhere as to how much useless stuff can be safely disabled in the kernel in this use case?
I think this could be what you need now: https://fedoraproject.org/wiki/Building_a_custom_kernel
Kind regards, Tuan _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Mon, Jan 13, 2014 at 9:30 PM, Michael Hall mike@mjhall.org wrote:
Thanks Truong, I am using that page. What I would like to know is how much I can safely disable in the kernel. Does anyone have a list of what most VM images don't need? For example, it seems that most hardware support can go, and most filesystem support that isn't needed. I would like to build a s small a kernel as possible that will still function securely.
Your question is timely. The Fedora kernel team has been told that the Cloud people would like a smaller kernel package, but nobody has actually come forward with what that means. So I'm interested in seeing what the Cloud experts reply with, because we're already doing work on the kernel to split it up to make it smaller. The mechanics of that are somewhat simple, but the content is the part we're blocking on.
(NOTE: This is for Fedora.next, not F20 so whatever you're doing is likely unaffected.)
josh
OK, well I'll continue experimenting anyway. If anyone has any tips or advice it is certainly welcome. I'm also assuming that if the kernel can be gotten small enough it may as well be monolithic?
Mike
On Tue, Jan 14, 2014 at 10:03 PM, Josh Boyer jwboyer@fedoraproject.orgwrote:
On Mon, Jan 13, 2014 at 9:30 PM, Michael Hall mike@mjhall.org wrote:
Thanks Truong, I am using that page. What I would like to know is how much I can safely disable in the kernel. Does anyone have a list of what most VM images don't need? For example, it seems that most hardware support can go, and most
filesystem
support that isn't needed. I would like to build a s small a kernel as possible that will still function securely.
Your question is timely. The Fedora kernel team has been told that the Cloud people would like a smaller kernel package, but nobody has actually come forward with what that means. So I'm interested in seeing what the Cloud experts reply with, because we're already doing work on the kernel to split it up to make it smaller. The mechanics of that are somewhat simple, but the content is the part we're blocking on.
(NOTE: This is for Fedora.next, not F20 so whatever you're doing is likely unaffected.)
josh _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-
Josh Boyer -
Michael Hall -
Truong Anh Tuan