Omer, Tzafrir great input.thank you both. I like Tzafrir's approach of doing it ground up from the distro - it solves a lot of problems - I've checked mysql licensing and we should have no problem there, and of crs we should use dynamic php modules etc.. I am also thinking of an advanced stack - that would enable Lamp to work in a f/o cluster out of the box - this is becoming increasingly a must have for many customers.
I totally agree with Omer's assessment of hard work of specification. I believe that we need to baseline against business applications like MamboCMS, phpbb, osCommerce etc..and i'm tending towards offering preset default configurations as well as an advanced diy. Good input from Tzafrir that a well packaged distro can make sure that config files are in the same place; having said that - for the busy admin - there is nothing like a GUI to save time, enforce consistency and ensure valid parameter values - look how cryptic sendmail can be. I am also placing great importance on automated testing for certifying that the damn thing actually works well under load - Another idea that has come up the past few days - is taking it even further up the food chain and making a Lamp or LamJ hardware appliance. I'm not sure - as an ex-Intel guy - i think that the hardware is moving even faster than the kernel - been seeing Intel mobo's recently on RH3 that dont detect Intel Pro 1000 nics ;-) ----- Original Message ----- From: "Omer Zak" <[EMAIL PROTECTED]> To: "linux ILUG" <[EMAIL PROTECTED]> Sent: Thursday, December 09, 2004 5:01 PM Subject: Re: Stacks > > On Thu, 9 Dec 2004, Tzafrir Cohen wrote below how to actually implement > it, and how easy it is with today's state of the art tools. > > In general, today's application software development scene is > characterized by powerful tools, which make it easy to do exactly what you > want to do. > > However, they do not eliminate the hard work of specifying exactly what > you want to do. > > So all the hard work that Danny Lieberman and his cohorts need to do would > consist of specifying. What packages are to be part of the standard LAMP? > What officially sanctioned extensions are to be there? How would the > default configuration look like? What frequently-occurring configuration > modifications are likely to be and which will be supported out of the box? > > Not to mention all the certification testing, which Danny Lieberman wants > to accomplish. > > > On Thu, Dec 09, 2004 at 03:45:06PM +0200, Omer Zak wrote: > > > > > > On Thu, 9 Dec 2004, Tzafrir Cohen wrote: > > > > > > > On Thu, Dec 09, 2004 at 12:59:13PM +0200, Danny Lieberman wrote: > > > > > open question to the list: > > > > > > > > > > I'm considering starting acommunity project that would create ready-to-install "stacks" for Lamp, LamJ and Webapp clustering > > > > > the idea is a stack forend user customers which : > > > > > > > > > > 1. is certified (and/or bundled) for a particular distro(rh 3 or caos) > > > > > > > > Whynot provide the whole distro? > > > > > > The original distro already has all packages. > > > What is missing is: > > > 1. Selection of the packages needed for a particular application. > > > For example, in Debian you may want to define a 'lamp' meta-package, > > > which when selected, will cause all required LAMP packages to be > > > installed). > > > Maybe also in urpmi and in the gentoo what-is-its-name there are > > > similar capabilities. > > > > This is something extermely easy: create a custom yum/apt source. Init > > put a simple package that has no contents but requires all the other > > relevant packages. Now all the user has to do is to add your apt/yum > > source and install your package. apt/yum will do the rest. > > > > > 2. Default configuration suitable for the busyadmin. > > > > Repackage badly-packages ones. Or find other non-intrusive methods to > > change the default configuration. Those methods should be resiliant to > > software upgrades through apt/yum. > > > > > 3. Customization tools which are friendly to the busy admin. > > > > This is a package you write yourself or integrate from an existing > > package. > --- Omer > My opinions, as expressed in this E-mail message, are mine alone. > They do not represent the official policy of any organization with which > I may be affiliated in any way. > WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
