Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My company uses Cobbler to manager the deployment of new systems [CentOS]. I am new to the company and have been given ownership of this aspect of the IT department.
The current system work, but has a few fall backs.
Slow process. An install onto a Desktop from our installer/cobbler server hosted down the road of a 10gig direct link, takes 52mins.
This is a 6.9GB install.
The future of this system is to be used to deploy to bout 40 blades making up a render farm, so speed concerns me.
So I have been looking into SystemImager. I really like it, love how you can fine tune the image with a simple chroot. You can update the images packages every so often the same way.
The other advantage is speed. Installing from the same server to the same desktop, over the same link takes just 9mins [6.9GB in total].
So I am looking for peoples experience in this, which do you use and why? Any input appreciated.
It sounds like you've tried both, and it sounds like SystemImage - another very fine, equally well respected program - also does everything you need, and might perform considerably faster in your environment.
Just to be thorough, you might also want to look at:
Bottom line: choose whatever works best for you. If you don't need to image a bunch of hosts very often, or if it's more configurable or easier to use, then Cobbler might be the better choice - even if it happens to be much slower in your environment.
It sounds like you've tried both, and it sounds like SystemImage - another very fine, equally well respected program - also does everything you need, and might perform considerably faster in your environment.
Just to be thorough, you might also want to look at:
Bottom line: choose whatever works best for you. If you don't need to image a bunch of hosts very often, or if it's more configurable or easier to use, then Cobbler might be the better choice - even if it happens to be much slower in your environment.
'Hope that helps .. PSM
The problem with those three listed is they are "uneditable" on the server [besides maybe c but a very slow option]
Yes, we use PXE booting to fire off Cobbler/Kickstart or SystemImager.
I actually, today, incorporated SystemImager pxe boot options into Cobbler so it adds them in when a "cobbler sync" is called.
I am thinking if we can incorporate both, a CobbImager if you will and use Cobbler for new systems without a pre-captured image and SystemImager for replicating builds out. The issue is we will need to be firing up 40+ blade servers in a render farm, speed becomes important then.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.