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?
install
text
reboot
cdrom // Caso a instalação vai ser por CD/DVD Descomente esta linha;
lang en_US.UTF-8 // Eu utilizo a linguagem Ingles, caso deseja alterar use pt_BR.UTF-8
keyboard br-abnt2 // Já o teclado utilizo abt2
skipx
network --device eth0 --bootproto dhcp
rootpw a12345 // Senha Default do ROOT
firewall --disabled // Firewall já desativado
selinux --disabled // SElinux desativado
authconfig --enableshadow --enablemd5
timezone UTC
bootloader --pasword=abc123 --location=MBR --append="crashkernel=auto rhgb quiet"
%packages --nobase
#use the next line instead of the previous one if you do not care about the doc files
#%packages --nobase --excludedocs
coreutils
yum
rpm
e2fsprogs
lvm2
grub
openssh-server
openssh-clients
dhclient
-anacron
-autofs
-yum-updatesd
-wireless-tools
-irda-utils
-nfs-utils
-NetworkManager
-atmel-firmware
-b43-openfwwf
-cronie
-cronie-anacron
-crontabs
-cyrus-sasl
-info
-sudo
-sysstat
-yum-utils
-ipw2100-firmware
-ipw2200-firmware
-ivtv-firmware
-iwl1000-firmware
-iwl3945-firmware
-iwl4965-firmware
-iwl5000-firmware
-iwl5150-firmware
-iwl6000-firmware
-iwl6050-firmware
-libertas-usb8388-firmware
-rt61pci-firmware
-rt73usb-firmware
-mysql-libs
-zd1211-firmware
// Programas Extras
tar
vim-enhanced
vim-common
%end
%post --log=/root/my-post-log
exec < /dev/tty3 > /dev/tty3
chvt 3
echo
echo "##################################"
echo "# Aplicando configuração Pós Instalação #"
echo "##################################"
yum update –y
chvt 1
%end
*--* Att Marcos Carraro about.me/marcoscarraro
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
On Mon, Jan 5, 2015 at 8:24 AM, Manuel Wolfshant wolfy@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
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
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."
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.
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?
On 01/05/2015 07:30 PM, PatrickD Garvey wrote:
On Mon, Jan 5, 2015 at 8:24 AM, Manuel Wolfshant wolfy@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.
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
I understand git.centos.org is a result of the Red Hat + CentOS Announcement and nazar.karan.org/summary/bluecain.git is a chronologically older resource, I'm just looking for a statement of direction for future work and, perhaps, an increase in the organization of CentOS repositories. Otherwise, I anticipate more confusion like that documented in http://wiki.centos.org/AdditionalResources/Repositories.
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
On 01/10/2015 01:36 AM, Karanbir Singh wrote:
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
On Fri, Jan 9, 2015 at 3:48 PM, Manuel Wolfshant wolfy@nobugconsulting.ro wrote:
On 01/10/2015 01:36 AM, Karanbir Singh wrote:
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
That would be the short version of what I just posted.
On 01/09/2015 11:48 PM, Manuel Wolfshant wrote:
On 01/10/2015 01:36 AM, Karanbir Singh wrote:
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
I get that, the bit that I dont get is the assumption that there is no content outside of the centos project that might be consumed by folks using CentOS Linux.
I can turn those sites off to the world, and just keep doing fluff myself - but i think its best to share and lots of awesome people have contributed over the years into some of those resources.
On Fri, Jan 9, 2015 at 3:55 PM, Karanbir Singh mail-lists@karan.org wrote:
On 01/09/2015 11:48 PM, Manuel Wolfshant wrote:
On 01/10/2015 01:36 AM, Karanbir Singh wrote:
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
I get that, the bit that I dont get is the assumption that there is no content outside of the centos project that might be consumed by folks using CentOS Linux.
I can turn those sites off to the world, and just keep doing fluff myself - but i think its best to share and lots of awesome people have contributed over the years into some of those resources.
-- Karanbir Singh
Are those kickstart files part of the tools used in the regular QA flow of the CentOS project? (That's probably the crux of my confusion.) If yes, then they are no longer JUST your personal files; they are critical to the continuing, regular process flow of the CentOS project. As such, at least a copy should be on a CentOS asset.
On 01/09/2015 05:48 PM, Manuel Wolfshant wrote:
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
So, perhaps there's a secondary question worth asking here.
Would a repository of community contributed kickstarts be valuable under the CentOS namespace on github and/or mirrored with git.centos.org?
If so, how would we as a distribution validate them prior to accepting the pull request, and what format/code style would be required/recommended.
We're already publishing kickstarts for docker, as well as some others in https://github.com/CentOS/sig-cloud-instance-build
Perhaps we look at restructuring/expanding that scope?
On 01/10/2015 02:16 AM, Jim Perrin wrote:
On 01/09/2015 05:48 PM, Manuel Wolfshant wrote:
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
So, perhaps there's a secondary question worth asking here.
Would a repository of community contributed kickstarts be valuable under the CentOS namespace on github and/or mirrored with git.centos.org?
yes, it would. and we could start by transferring the content sitting now below bluecain.git
If so, how would we as a distribution validate them prior to accepting the pull request, and what format/code style would be required/recommended.
peer review, as always ?
We're already publishing kickstarts for docker, as well as some others in https://github.com/CentOS/sig-cloud-instance-build
Perhaps we look at restructuring/expanding that scope?
why not putting ALL available kickstarts below the same git repo ?
On 01/10/2015 12:16 AM, Jim Perrin wrote:
On 01/09/2015 05:48 PM, Manuel Wolfshant wrote:
I assume the confusion is triggered by us ( me ) recommending something from your personal web site rather than from one "fully blessed " by CentOS ( whatever that would mean )
So, perhaps there's a secondary question worth asking here.
Would a repository of community contributed kickstarts be valuable under the CentOS namespace on github and/or mirrored with git.centos.org?
this question was largely unanswered at the time we did the repo the way it is now..
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
We're already publishing kickstarts for docker, as well as some others in https://github.com/CentOS/sig-cloud-instance-build
Perhaps we look at restructuring/expanding that scope?
I dont think we should do that, content metadata for specific roles should stay within those roles. Otherwise were just looking towards running a single svn ( or cvs?) repo with absolutely everything and the kitchen sink in there.
On 01/09/2015 06:27 PM, Karanbir Singh wrote:
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
That sounds reasonable. Who from the community would like to lead this effort?
On Sat, Jan 10, 2015 at 4:18 PM, Jim Perrin jperrin@centos.org wrote:
On 01/09/2015 06:27 PM, Karanbir Singh wrote:
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
That sounds reasonable. Who from the community would like to lead this effort?
Hello,
I would like to help with this. Editing & testing kickstart files can be time consuming trial and error and some nice samples for various setups could be very useful for quite some people I think.
Kind regards, Dries
On Wed, Jan 14, 2015 at 9:27 AM, Dries Verachtert dries.verachtert@dries.eu wrote:
On Sat, Jan 10, 2015 at 4:18 PM, Jim Perrin jperrin@centos.org wrote:
On 01/09/2015 06:27 PM, Karanbir Singh wrote:
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
That sounds reasonable. Who from the community would like to lead this effort?
Hello,
I would like to help with this. Editing & testing kickstart files can be time consuming trial and error and some nice samples for various setups could be very useful for quite some people I think.
Kind regards, Dries
If you're going this route, can I beg you to put in this? I've asked the anaconda developers for this before, and it's invaluable for getting your actual ks.cfg saved for reference, rather than that wildly distinct and script discarding 'anaconda-ks.cfg'.
%post --nochroot cp -a /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/14/2015 04:28 PM, Nico Kadel-Garcia wrote:
On Wed, Jan 14, 2015 at 9:27 AM, Dries Verachtert dries.verachtert@dries.eu wrote:
On Sat, Jan 10, 2015 at 4:18 PM, Jim Perrin jperrin@centos.org wrote:
On 01/09/2015 06:27 PM, Karanbir Singh wrote:
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
That sounds reasonable. Who from the community would like to lead this effort?
Hello,
I would like to help with this. Editing & testing kickstart files can be time consuming trial and error and some nice samples for various setups could be very useful for quite some people I think.
Kind regards, Dries
If you're going this route, can I beg you to put in this? I've asked the anaconda developers for this before, and it's invaluable for getting your actual ks.cfg saved for reference, rather than that wildly distinct and script discarding 'anaconda-ks.cfg'.
%post --nochroot cp -a /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end
This kind of thing makes me think, metadata around each kickstart is crucial to this. We can't just have a raw .ks file, unless it's as well documented (#commented) as a Tom Callaway tutorial example.
What I mean is, we need a way to track your comment about why that bit is invaluable for which situations, and how/where it's useful in what sort of kickstart files.
- - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/14/2015 11:29 PM, Karsten Wade wrote:
If you're going this route, can I beg you to put in this? I've asked the anaconda developers for this before, and it's invaluable for getting your actual ks.cfg saved for reference, rather than that wildly distinct and script discarding 'anaconda-ks.cfg'.
%post --nochroot cp -a /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end
This kind of thing makes me think, metadata around each kickstart is crucial to this. We can't just have a raw .ks file, unless it's as well documented (#commented) as a Tom Callaway tutorial example.
That's pretty much what I'd like the repo to be.
What I mean is, we need a way to track your comment about why that bit is invaluable for which situations, and how/where it's useful in what sort of kickstart files.
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
- -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
On 01/15/2015 01:08 PM, Jim Perrin wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
its likely trivial to implement a template system around this and service it out on demand. Maybe something to look at if/when this gets traction.
Dries, great to see you back in the loop!
Regards
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
Awesome, thanks!
-Jeff
On 01/15/2015 08:26 AM, Jeff Sheltren wrote:
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
Hopefully folks will tidy up some of the kickstarts already there, and contribute some new ones for centos7, since there are some significant changes.
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
Jim Perrin
Please forgive the intrusion, but why https://github.com/CentOS/Community-Kickstarts and not https://git.CentOS.org/Community-Kickstarts ?
On 01/15/2015 01:38 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
Jim Perrin
Please forgive the intrusion, but why https://github.com/CentOS/Community-Kickstarts and not https://git.CentOS.org/Community-Kickstarts ?
Because more people have github accounts than git.centos accounts. I'll look into mirroring between them.
On Thu, Jan 15, 2015 at 1:14 PM, Jim Perrin jperrin@centos.org wrote:
On 01/15/2015 01:38 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
Jim Perrin
Please forgive the intrusion, but why https://github.com/CentOS/Community-Kickstarts and not https://git.CentOS.org/Community-Kickstarts ?
Because more people have github accounts than git.centos accounts. I'll look into mirroring between them.
-- Jim Perrin
Thank you.
I think I'll wait to ask more penetrating questions until after I've made use of git for a while. I just have some ideas based on sketchy information about git that duplicate files in the two have no added value.
Once again, thank you. -- PatrickD
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/15/2015 01:27 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 1:14 PM, Jim Perrin jperrin@centos.org wrote:
On 01/15/2015 01:38 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
- -- Jim Perrin
Please forgive the intrusion, but why https://github.com/CentOS/Community-Kickstarts and not https://git.CentOS.org/Community-Kickstarts ?
Because more people have github accounts than git.centos accounts. I'll look into mirroring between them.
-- Jim Perrin
Thank you.
I think I'll wait to ask more penetrating questions until after I've made use of git for a while. I just have some ideas based on sketchy information about git that duplicate files in the two have no added value.
Git (and other DVCS systems) takes a bit of a different mental approach than a traditional hub-and-spoke model. Each Git repo contains a complete history of all changes from each other repo, so the changes and history are distributed rather than centralized. In that case, it's all duplicates, from my local git checkout to each other checkout. Where we say e.g. git.centos.org is a central repository, that is more a convention we choose rather than a limitation (feature) of the Git software.
The reason for using GitHub is that it has become something akin to "social coding". It is now a normal behavior to fork a GitHub repo, make changes, and offer them back via a pull request. It's a very low barrier for people interested in offering subtle-to-big code changes, documentation changes, etc. (vs joining a mailing list to submit a patch.)
However, there is a risk to an open source project to put all the code in a closed source application as the central repository, e.g. putting all ones eggs in one basket. For this reason, the recommendation is to have the project's git repository be primary (canonical), and use GitHub for the ease-of-use, by mirroring changes back-and-forth between the two git repos.
http://bit.ly/TOSWOpenTooling [1]
... I've been pondering putting in a specific guideline that speaks to GitHub, but I prefer to keep the guidelines more generic than specific where possible.
Regards,
- - Karsten
[1] Long URL:
http://www.theopensourceway.org/wiki/How_to_loosely_organize_a_community#Use...
- -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
On Thu, Jan 15, 2015 at 8:34 PM, Karsten Wade kwade@redhat.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- On 01/15/2015 01:27 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 1:14 PM, Jim Perrin jperrin@centos.org wrote:
On 01/15/2015 01:38 PM, PatrickD Garvey wrote:
On Thu, Jan 15, 2015 at 5:08 AM, Jim Perrin jperrin@centos.org wrote:
The repository has been cloned to github for community use/improvement. If I made a couple minor changes and updated the README (along with wolfy) so please feel free to review/contribute to https://github.com/CentOS/Community-Kickstarts
- -- Jim Perrin
Please forgive the intrusion, but why https://github.com/CentOS/Community-Kickstarts and not https://git.CentOS.org/Community-Kickstarts ?
Because more people have github accounts than git.centos accounts. I'll look into mirroring between them.
-- Jim Perrin
Thank you.
I think I'll wait to ask more penetrating questions until after I've made use of git for a while. I just have some ideas based on sketchy information about git that duplicate files in the two have no added value.
Git (and other DVCS systems) takes a bit of a different mental approach than a traditional hub-and-spoke model. Each Git repo contains a complete history of all changes from each other repo, so the changes and history are distributed rather than centralized. In that case, it's all duplicates, from my local git checkout to each other checkout. Where we say e.g. git.centos.org is a central repository, that is more a convention we choose rather than a limitation (feature) of the Git software.
I think that paragraph confirms my suspicion that I need never move code from one git to another, but there is some mechanism by which the people using each notify their git about the other and code is shared across the gap semi-automatically. This is where I expect experience to inform me better than generous attempts to explain it ahead of time.
The reason for using GitHub is that it has become something akin to "social coding". It is now a normal behavior to fork a GitHub repo, make changes, and offer them back via a pull request. It's a very low barrier for people interested in offering subtle-to-big code changes, documentation changes, etc. (vs joining a mailing list to submit a patch.)
This seems to indicate there is some human-to-human communication cost to sharing across two git domain names. Again, I look to my future experience for a deeper understanding.
However, there is a risk to an open source project to put all the code in a closed source application as the central repository, e.g. putting all ones eggs in one basket. For this reason, the recommendation is to have the project's git repository be primary (canonical), and use GitHub for the ease-of-use, by mirroring changes back-and-forth between the two git repos.
I've seen indications there are some objections to using GitHub from some quarters. Are you saying GitHub is closed source? I had meant to investigate the rumblings for enlightenment. One only has so much time to learn the basic knowledge and I often defer the cultural knowledge investigations.
If there are legitimate concerns about using a tool outside the CentOS.org domain, it seems to me, the project needs to find a way to bridge the gap. I understand the reluctance to lose contributions from people outside the domain. I also understand the comfort levels generated by using what one has used successfully, especially mental models about how tools work behind the scenes.
Thank you, Karsten, for your time. I hope it has been beneficial to the CentOS project also.
http://bit.ly/TOSWOpenTooling [1]
... I've been pondering putting in a specific guideline that speaks to GitHub, but I prefer to keep the guidelines more generic than specific where possible.
Regards,
- Karsten
[1] Long URL:
http://www.theopensourceway.org/wiki/How_to_loosely_organize_a_community#Use...
Karsten 'quaid' Wade .^\ CentOS Doer of Stuff
On Fri, Jan 16, 2015 at 10:56 AM, PatrickD Garvey patrickdgarveyt@gmail.com wrote:
On Thu, Jan 15, 2015 at 8:34 PM, Karsten Wade kwade@redhat.com wrote:
Git (and other DVCS systems) takes a bit of a different mental approach than a traditional hub-and-spoke model. Each Git repo contains a complete history of all changes from each other repo, so the changes and history are distributed rather than centralized. In that case, it's all duplicates, from my local git checkout to each other checkout. Where we say e.g. git.centos.org is a central repository, that is more a convention we choose rather than a limitation (feature) of the Git software.
I think that paragraph confirms my suspicion that I need never move code from one git to another, but there is some mechanism by which the people using each notify their git about the other and code is shared across the gap semi-automatically. This is where I expect experience to inform me better than generous attempts to explain it ahead of time.
Tastes, and workflow, vary tremendously. It's not usually feasible to keep track of *all* the forks, because remote developers can make forks of each other forks, with no record of what the other forks are. And it's not usually a "push" mechanism to transimit code to other repositories: usually it's a "notify the other user, and give them a target to pull from at their leisure".
The reason for using GitHub is that it has become something akin to "social coding". It is now a normal behavior to fork a GitHub repo, make changes, and offer them back via a pull request. It's a very low barrier for people interested in offering subtle-to-big code changes, documentation changes, etc. (vs joining a mailing list to submit a patch.)
This seems to indicate there is some human-to-human communication cost to sharing across two git domain names. Again, I look to my future experience for a deeper understanding.
It can be automated, but that can be.... adventuresome of both are considered "writable" repositories for non-automated procedures.
I've seen indications there are some objections to using GitHub from some quarters. Are you saying GitHub is closed source? I had meant to investigate the rumblings for enlightenment. One only has so much time to learn the basic knowledge and I often defer the cultural knowledge investigations.
Github is my friend for many projects. What it lacks is free "private group" repositories, like "bitbucket" has.
On Fri, Jan 16, 2015 at 4:04 PM, Nico Kadel-Garcia nkadel@gmail.com wrote:
On Fri, Jan 16, 2015 at 10:56 AM, PatrickD Garvey patrickdgarveyt@gmail.com wrote:
On Thu, Jan 15, 2015 at 8:34 PM, Karsten Wade kwade@redhat.com wrote:
Git (and other DVCS systems) takes a bit of a different mental approach than a traditional hub-and-spoke model. Each Git repo contains a complete history of all changes from each other repo, so the changes and history are distributed rather than centralized. In that case, it's all duplicates, from my local git checkout to each other checkout. Where we say e.g. git.centos.org is a central repository, that is more a convention we choose rather than a limitation (feature) of the Git software.
I think that paragraph confirms my suspicion that I need never move code from one git to another, but there is some mechanism by which the people using each notify their git about the other and code is shared across the gap semi-automatically. This is where I expect experience to inform me better than generous attempts to explain it ahead of time.
Tastes, and workflow, vary tremendously. It's not usually feasible to keep track of *all* the forks, because remote developers can make forks of each other forks, with no record of what the other forks are. And it's not usually a "push" mechanism to transimit code to other repositories: usually it's a "notify the other user, and give them a target to pull from at their leisure".
The reason for using GitHub is that it has become something akin to "social coding". It is now a normal behavior to fork a GitHub repo, make changes, and offer them back via a pull request. It's a very low barrier for people interested in offering subtle-to-big code changes, documentation changes, etc. (vs joining a mailing list to submit a patch.)
This seems to indicate there is some human-to-human communication cost to sharing across two git domain names. Again, I look to my future experience for a deeper understanding.
It can be automated, but that can be.... adventuresome of both are considered "writable" repositories for non-automated procedures.
I've seen indications there are some objections to using GitHub from some quarters. Are you saying GitHub is closed source? I had meant to investigate the rumblings for enlightenment. One only has so much time to learn the basic knowledge and I often defer the cultural knowledge investigations.
Github is my friend for many projects. What it lacks is free "private group" repositories, like "bitbucket" has.
Thanks, Nico.
It definitely sounds like I need to actually use git to come to a full understanding of how it can be used and how I will endeavor to use it.
There is no kickstart file for which this is not useful. Reviewing anaconda-ks.cfg are like examining the corpse *after* the cannibals ate it. You learn more about the cannibal than about how their dinner lived.
Nico Kadel-Garcia Email: nkadel@gmail.com Sent from iPhone
On Jan 15, 2015, at 0:29, Karsten Wade kwade@redhat.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/14/2015 04:28 PM, Nico Kadel-Garcia wrote: On Wed, Jan 14, 2015 at 9:27 AM, Dries Verachtert dries.verachtert@dries.eu wrote:
On Sat, Jan 10, 2015 at 4:18 PM, Jim Perrin jperrin@centos.org wrote:
On 01/09/2015 06:27 PM, Karanbir Singh wrote:
the problem is - the scope of this would be large enough that anyone can manage it, and everyone can get involved. But I dont want to do this as a part of the Core effort, that closes too many doors. But the SIGs are too specialised in their outlook to curate something of this nature.
The only group in a suiteable place to perhaps take ownership of a resource like that would be the docs group - so we do a community contributed setup there, and the build services retail their own metadata ( which is what the atomic / docker / cloud stuff is ) as and when and where they need it.
That sounds reasonable. Who from the community would like to lead this effort?
Hello,
I would like to help with this. Editing & testing kickstart files can be time consuming trial and error and some nice samples for various setups could be very useful for quite some people I think.
Kind regards, Dries
If you're going this route, can I beg you to put in this? I've asked the anaconda developers for this before, and it's invaluable for getting your actual ks.cfg saved for reference, rather than that wildly distinct and script discarding 'anaconda-ks.cfg'.
%post --nochroot cp -a /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end
This kind of thing makes me think, metadata around each kickstart is crucial to this. We can't just have a raw .ks file, unless it's as well documented (#commented) as a Tom Callaway tutorial example.
What I mean is, we need a way to track your comment about why that bit is invaluable for which situations, and how/where it's useful in what sort of kickstart files.
- Karsten
Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iEYEARECAAYFAlS3UE8ACgkQ2ZIOBq0ODEF+RACdH6162DNIY779KJ81/kw2x95j 7IcAoMEPNvQZrURRgpxU2DfuCMrfaOaP =Yhb8 -----END PGP SIGNATURE----- _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Fri, Jan 9, 2015 at 3:36 PM, Karanbir Singh mail-lists@karan.org wrote:
On 01/09/2015 10:50 PM, PatrickD Garvey wrote:
On Tue, Jan 6, 2015 at 3:01 AM, Karanbir Singh mail-lists@karan.org wrote:
On 01/05/2015 05:30 PM, PatrickD Garvey wrote:
CentOS and for solutions to support requests, why is it maintained outside the CentOS.org domain?
I guess you could extend that to github.com and then most of the stuff going on there would be wrong according to you as well right ?
-- Karanbir Singh
Sorry for the slow response when you're answering my question.
According to the FAQ < http://community.redhat.com/centos-faq/#_git_centos_org >, "git.centos.org ... is the canonical repository for the CentOS Project, and for SIGs working on variants." So, yes, I would expect anything that is regularly used in building CentOS or proposed as support items for CentOS' use by the community to be readily available on git.centos.org.
nothing on nazar should be consider centos 'project' assets. its my personal stuff, just like everything else karan.org would be. I am struggling to see why you might be confused by that.
-- Karanbir Singh
Manuel Wolfshant offered https://nazar.karan.org/summary/bluecain.git to Marcos Carraro as a source for a kickstart on which to begin building a kickstart for Marcos' purposes.
And http://wiki.centos.org/TipsAndTricks/KickStart says, "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." which, to me, indicates this collection is regularly used to test a key CentOS process.
If these kickstart files are part of the tools used in the regular QA flow of the CentOS project, should they not be on a identifiably CentOS project asset?
-
Dries Verachtert -
Jeff Sheltren -
Jim Perrin -
Karanbir Singh -
Karsten Wade -
Manuel Wolfshant -
Marcos Carraro -
Nico Kadel-Garcia -
PatrickD Garvey