[CentOS-devel] kickstart extra minimal

Mon Jan 5 20:07:27 UTC 2015
Manuel Wolfshant <wolfy at nobugconsulting.ro>

On 01/05/2015 07:30 PM, PatrickD Garvey wrote:
> On Mon, Jan 5, 2015 at 8:24 AM, Manuel Wolfshant
> <wolfy at nobugconsulting.ro> wrote:
>> On 01/05/2015 06:19 PM, Marcos Carraro wrote:
>>
>> Hay Group, happy new year !!
>>
>>
>> I am looking to make a very small kickstart to try to leave the installation
>> of very light hundreds. Both for use of RAM and also to disk.
>>
>> Follow my kickstart for hundreds 6.6 x64, any suggestions?
>>
>> look for minimal below https://nazar.karan.org/tree/bluecain and adjust as
>> needed for your use case
> Please excuse my remediable ignorance, but according to
> http://wiki.centos.org/TipsAndTricks/KickStart,
> "At https://nazar.karan.org/summary/bluecain.git you can find a
> collection of ready-made kickstart files. Their primary goal is for
> testing the CentOS deployment process but they can of course be used
> for any other purpose."
emphasis on "any other purpose"

>
> And now I find the person who last modified that page offering
> https://nazar.karan.org/summary/bluecain.git as a source for a
> solution for a request for help.
FWIW, those minimal-*.cfg files were written by me and I actively use 
them (adapted when/were needed) for deployments for the clients I work 
for. I am old fashioned and when I do not have the possibility (or the 
need ) to use a larger config management / deployment solution, I start 
from those minimal kickstarts and then install (using ansible) whatever 
is needed for that specific use case.



> If that resource is more than "a git repo for some of the things that
> I'm working on" as stated on http://wiki.centos.org/KaranbirSingh and,
> in fact, has been used by several members of the CentOS project as a
> significant resource for the quality of the deployment process of
> CentOS and for solutions to support requests, why is it maintained
> outside the CentOS.org domain?
THAT is a good question. I guess that the priority of  transferring them 
somewhere below git.c.o is pretty low.