Hello, we'd like to start Server spin. I've already created a spin page[1] and I'd appreciate any feedback from Spins SIG.
The spin doesn't exactly follow the rules, since we use a script to generate the kickstart file[2].
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
thanks, - daniel
[1] https://fedoraproject.org/wiki/Server_Spin [2] http://dmach.fedorapeople.org/server-spin/
On Fri, 2010-11-12 at 16:14 +0100, Daniel Mach wrote:
Hello, we'd like to start Server spin. I've already created a spin page[1] and I'd appreciate any feedback from Spins SIG.
The spin doesn't exactly follow the rules, since we use a script to generate the kickstart file[2].
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
I think the last time this came up there was the following question:
What is a server spin if NOT a simple kickstart of minimal?
I don't mean this sarcastically at all - I just don't know what is being shown off in a server spin that you can't get from a network ks of fedora minimal.
-sv
Dne 12.11.2010 16:44, seth vidal napsal(a):
On Fri, 2010-11-12 at 16:14 +0100, Daniel Mach wrote:
Hello, we'd like to start Server spin. I've already created a spin page[1] and I'd appreciate any feedback from Spins SIG.
The spin doesn't exactly follow the rules, since we use a script to generate the kickstart file[2].
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
I think the last time this came up there was the following question:
What is a server spin if NOT a simple kickstart of minimal?
I don't mean this sarcastically at all - I just don't know what is being shown off in a server spin that you can't get from a network ks of fedora minimal.
-sv
You can say this about any spin.
I see additional value in this spin - there will be something to test, we can watch deps more easily so we can ask for package splits and have generally better control over server packages in Fedora.
- daniel
On Fri, 2010-11-12 at 17:36 +0100, Daniel Mach wrote:
You can say this about any spin.
Sort of - most other spins have a livecd to demo things out - I'm not sure what a demo of a server spin would _do_
I see additional value in this spin - there will be something to test, we can watch deps more easily so we can ask for package splits and have generally better control over server packages in Fedora.
that's fair enough.
I can see the virtue in that.
-sv
On Fri, Nov 12, 2010 at 16:14:44 +0100, Daniel Mach dmach@redhat.com wrote:
Hello, we'd like to start Server spin. I've already created a spin page[1] and I'd appreciate any feedback from Spins SIG.
We'll see what happens at Tempe, but I expect in the future each spin will be handled by its own SIG. But either way, you'd want a page to describe what you are doing.
The spin doesn't exactly follow the rules, since we use a script to generate the kickstart file[2].
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
If you don't want a published ISO we can include the tool to build the kickstart file in one of the spins-kickstart packages. It might be a good idea to think about other potential uses for a script that generates kickstart files. Maybe you can make some aspects more general than needed for just handling servers.
On 11/12/10 7:14 AM, Daniel Mach wrote:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
To answer your question, kickstart group syntax allows options, such as --optional.
http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_3._Package_Selectio...
This way you can do:
%packages @foo --optional
Jesse Keating (jkeating@redhat.com) said:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
... I'm confused why you'd do this as well. How many people install their servers from *media*? (That being said, it would be interesting to benchmark an image-based installation of @core, but given that anaconda won't run on that...)
Bill
On Mon, 2010-11-15 at 20:34 -0500, Bill Nottingham wrote:
Jesse Keating (jkeating@redhat.com) said:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
... I'm confused why you'd do this as well. How many people install their servers from *media*? (That being said, it would be interesting to benchmark an image-based installation of @core, but given that anaconda won't run on that...)
I always install my own servers from "media". Often it's an ISO given to a VM, but it is always from an ISO. Never a pre-packaged image, etc.
Jon.
On Mon, 2010-11-15 at 20:54 -0500, Jon Masters wrote:
On Mon, 2010-11-15 at 20:34 -0500, Bill Nottingham wrote:
Jesse Keating (jkeating@redhat.com) said:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
... I'm confused why you'd do this as well. How many people install their servers from *media*? (That being said, it would be interesting to benchmark an image-based installation of @core, but given that anaconda won't run on that...)
I always install my own servers from "media". Often it's an ISO given to a VM, but it is always from an ISO. Never a pre-packaged image, etc.
No - I think he meant a network install.
-sv
On Mon, 2010-11-15 at 23:22 -0500, seth vidal wrote:
On Mon, 2010-11-15 at 20:54 -0500, Jon Masters wrote:
On Mon, 2010-11-15 at 20:34 -0500, Bill Nottingham wrote:
Jesse Keating (jkeating@redhat.com) said:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
... I'm confused why you'd do this as well. How many people install their servers from *media*? (That being said, it would be interesting to benchmark an image-based installation of @core, but given that anaconda won't run on that...)
I always install my own servers from "media". Often it's an ISO given to a VM, but it is always from an ISO. Never a pre-packaged image, etc.
No - I think he meant a network install.
Actually, I still mostly do non-network installs (even on virtual machines). I don't think I'm alone, especially in the Fedora space. I *do* think it's far more common to do network installs the larger you get, but for e.g. a home VM host box or a few build boxes like I have at home, I generally download the media and do it from that. That also has the advantage of not requiring another box to serve the install images that is local (Fedora installs over the public Internet is painful, better than it used to be, but still fails too often in my usage).
Cases where I don't do local installs are:
1). Poking with creating virt. instances for e.g. distcc use. 2). Testing anaconda or install-time stuff with boot.iso.
Jon.
On 11/16/2010 02:54 AM, Jon Masters wrote:
On Mon, 2010-11-15 at 20:34 -0500, Bill Nottingham wrote:
Jesse Keating (jkeating@redhat.com) said:
Do you think it's appropriate to keep it this way or should I change it? The reason why I do it this way is, that pungi doesn't pull optional comps packages in the media kit. Any idea how to work this around without having an extra script?
To date, all spins have been either live media, or a virt image that is quite similar. However you mention using pungi, which means you're making a more traditional install media, as opposed to live media. Basically you're just adjusting what packages are or are not on the DVD media we generate as part of a Fedora release?
... I'm confused why you'd do this as well. How many people install their servers from *media*? (That being said, it would be interesting to benchmark an image-based installation of @core, but given that anaconda won't run on that...)
I always install my own servers from "media". Often it's an ISO given to a VM, but it is always from an ISO. Never a pre-packaged image, etc.
Jon.
I also prefer media (or ISO). I suppose there will be still lot of people using media. We can see that after releasing spin from number of downloads.
Marcela Mašláňová (mmaslano@redhat.com) said:
I also prefer media (or ISO). I suppose there will be still lot of people using media. We can see that after releasing spin from number of downloads.
My concern is, unlike a desktop OS, there's such a large variety of things that a server could do that I wonder if it's practical to place it all on the image... a server could want the entire PHP stack, or the entire Python and Django/Turbogears stack, or rails, or just bind and ftp, or...
Bill
On Tue, 2010-11-16 at 10:52 -0500, Bill Nottingham wrote:
Marcela Mašláňová (mmaslano@redhat.com) said:
I also prefer media (or ISO). I suppose there will be still lot of people using media. We can see that after releasing spin from number of downloads.
My concern is, unlike a desktop OS, there's such a large variety of things that a server could do that I wonder if it's practical to place it all on the image... a server could want the entire PHP stack, or the entire Python and Django/Turbogears stack, or rails, or just bind and ftp, or...
Of course, but nevertheless Red Hat is able to ship Red Hat Enterprise Linux Server isos. :) There will just have to be done some choice and cutoff to fit the packages into a Fedora Server spin DVD.
server@lists.fedoraproject.org