Neil Bothwick <neil <at> digimed.co.uk> writes:
> > Um, we can think out of the box for a new and cool installation > > semantic. Just look at blueness's posting (Gentoo Reference System) on > > www.gentoo.org as a new, and useful approach to installs for > > established gentoo admins. > That's interesting, but not an installer. It's a means to building a > standard reference system repeatedly that then needs installing. First, Anthony identifies but one popular need for gentooers with advanced skills to want (and highly desire) a robust method to install new gentoo systems. So it's not just the noobs, but devs and everybody in between that knows that this is a good idea. What do we end up with ? I'd hope several different approaches to installing real hardware as well as virtual hardware. The faster/simpler/error-free the better, imho::YMMV. Anthony's works is "alpha" so guys like yourself, with tons of experiences, could provide him ideas..... You'll find he's quite a wonderful dev to work with.... collegial is a very accurate term to describe Anthony as a dev. > I see one major problem with a pointy-clicky YaST/Ananconda type > installer: who is going to write it? Who has that particular itch bad > enough to scratch it? Rich0 said he'd modify the handbook into an experimental prose that leads to a raid-1 btrfs baseline system, if enough folks liked the ideas. I think that approach is best, because it makes all the 'die_hard" handbook fans happy and can also server as a preliminary specification to an actual automated installation, not just for noobs. Add a dose of 'snapshots' (snapper) and we'd have a much better support semantic for noobs and the rest of us too! > An automated installer is another matter, write a config file and point it > at some bare metal using something like Ansible, to allow sysadmins to > roll out systems with less fiddling. Yes, but they are inter-related issues, imho. Yes I like what you are saying. There are several needs here for automation of gentoo installs; not just for noobs, but for those of us trying to develop or stabilize other codes. HDFS, sucks as a distributed file system. HDFS is the source of many problems found in modern clustering. For me, I'm spending way too much time on trying to find an automated (semi-automated) install semantic for raid-1_btrfs. So my work on mesos [1] is very slow, ATM. Fix the installation problem, and I'll deliver (toes crossed tightly) the most 'bad ass' clustering technology currently available:: *Mesos + spark + storm + tachyon + cassandra* on gentoo (amd64). Then the stabilization work moves to arm64. Both platforms on top of btrfs/cephfs is going to be *smokin_wicked_cool*. Built from sources, gentoo will be quickly adopted by many expert linux types. The baggage/packaging problems, kernel tuning and optimization needs puts Gentoo in a unique position to dominate this space....... That's my position and I'm sticking with it.... hth, James [1] http://www.openstacksv.com/2014/09/02/make-no-small-plans/
