|
Replies:
30
-
Last Post:
Mar 21, 2007 12:48 AM
by: aland
|
|
|
Stefan Teleman
Stefan.Teleman@Sun.COM
|
|
|
|
Project Proposal: Next Generation Web Stack
Posted:
Mar 15, 2007 6:54 PM
|
|
Project Proposal: Next Generation Web Stack
Summary
We would like to create an OpenSolaris project to assume and enhance
the community and work originally created in Sun's CoolStack project
as part of the CoolTools project. This project will assume all of
the CoolStack components, including Apache HTTP Server, MySQL
Database Server, Perl, PHP, Ruby, Rails, Squid and others. The
existing CoolStack forums will be retired and replaced with
discussions at OpenSolaris.org.
Goals
The aim of this project is to address the OpenSolaris community needs
for a set of Next Generation Web Tier Technologies. The initial
seeding of this project will be based on the work already put into
CoolStack, but it is not intended to be tied to the set of
technologies currently in CoolStack.
The project will provide the following:
- A forum for discussion on which next generation web tier
components should be part of various Solaris distributions
- A codebase from which various packaged software can be
derived for various OpenSolaris distributions, including
build scripts and best practices for building this software
with OpenSolaris
- A forum for discussion on what kind of integration and
features users would like to see integration between
OpenSolaris and these external Open Source projects
Overview of CoolStack
In 2006, Sun introduced CoolStack - a Solaris-optimized,
full-featured open-source based Web Tier stack which includes all of
the traditional components of an AMP stack. This project proposes to
take the best of the technologies and practices delivered by
CoolStack and fully integrate them into OpenSolaris, optimized to
utilize the features within OpenSolaris such as DTrace and the
Solaris Management Facility.
Many details can be found on CoolStack and the associated forums at
http://cooltools.sunsource.net/coolstack/.
However, we would like to summarize the history and goals to clarify
how they relate to this project proposal.
CoolStack had been originally conceived to provide a set of
out-of-the-box optimized binaries for a common set of software
components on the UltraSPARC T1 based systems. By performing this
packaging for the community, the OpenSPARC project and Sun's
Performance Technologies group had a goal to make it easy for users
to quickly add packages to their existing systems to quickly obtain
optimized performance and reducing time to service.
Over time, there was sufficient demand for an equivalent set of
packages on x64, so a similar set of optimized packages and build
scripts were put together for the i386 and amd64 architectures as
appropriate.
CoolStack derives its name from the CoolTools project it is
associated with. Because the community has already gained
familiarity with the CoolStack name, there is no plan to change the
name, despite the fact it's moving away from the CoolThreads
processor and CoolTools project.
Q: Why should this project exist here instead of upstream source code
bases?
In attempting to keep the various components under this project in
step with the latest and/or most popular releases from the component
projects, core code modifications will be contributed to the upstream
projects wherever possible. However, it is expected that some
contributed items, such as build scripts, a community forum, SMF
manifests and the like, are more appropriate for an OpenSolaris
project than the codebase of the component project.
It is also anticipated that this project may have specific
discussions about packaging as it relates to various OpenSolaris
distributions and a need for there to be a forum to discuss how
OpenSolaris technologies such as DTrace and SMF integrate with these
component projects. Accordingly, this project will serve as the
source for the OpenSolaris.org discussions and community decisions.
From experience with the CoolStack project forums already, we know
there may be some overlap with questions on issues/bugs and how
things are intended to work that may be more appropriate for the
project from which the component was derived, but the members of the
OpenSolaris CoolStack project will encourage working with the
component projects wherever possible. This project is intended to
add to the communities surrounding those projects, not fragment
them.
-----
1. Public interfaces as defined in the ARC release taxonomy at
http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
--
Stefan Teleman
Sun Microsystems, Inc.
Stefan dot Teleman at Sun dot COM
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
Posts:
528
From:
CA
Registered:
12/22/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 15, 2007 7:26 PM
in response to: Stefan Teleman
|
|
On 15-Mar-07, at 6:54 PM, Stefan Teleman wrote:
> Project Proposal: Next Generation Web Stack
>
> Summary
>
> We would like to create an OpenSolaris project to assume and enhance
> the community and work originally created in Sun's CoolStack project
> as part of the CoolTools project. This project will assume all of
> the CoolStack components, including Apache HTTP Server, MySQL
> Database Server, Perl, PHP, Ruby, Rails, Squid and others. The
> existing CoolStack forums will be retired and replaced with
> discussions at OpenSolaris.org.
>
> Goals
>
> The aim of this project is to address the OpenSolaris community needs
> for a set of Next Generation Web Tier Technologies. The initial
> seeding of this project will be based on the work already put into
> CoolStack, but it is not intended to be tied to the set of
> technologies currently in CoolStack.
>
> The project will provide the following:
> - A forum for discussion on which next generation web tier
> components should be part of various Solaris distributions
> - A codebase from which various packaged software can be
> derived for various OpenSolaris distributions, including
> build scripts and best practices for building this software
> with OpenSolaris
> - A forum for discussion on what kind of integration and
> features users would like to see integration between
> OpenSolaris and these external Open Source projects
>
> Overview of CoolStack
>
> In 2006, Sun introduced CoolStack - a Solaris-optimized,
> full-featured open-source based Web Tier stack which includes all of
> the traditional components of an AMP stack. This project proposes to
> take the best of the technologies and practices delivered by
> CoolStack and fully integrate them into OpenSolaris, optimized to
> utilize the features within OpenSolaris such as DTrace and the
> Solaris Management Facility.
>
> Many details can be found on CoolStack and the associated forums at
> http://cooltools.sunsource.net/coolstack/.
>
> However, we would like to summarize the history and goals to clarify
> how they relate to this project proposal.
>
> CoolStack had been originally conceived to provide a set of
> out-of-the-box optimized binaries for a common set of software
> components on the UltraSPARC T1 based systems. By performing this
> packaging for the community, the OpenSPARC project and Sun's
> Performance Technologies group had a goal to make it easy for users
> to quickly add packages to their existing systems to quickly obtain
> optimized performance and reducing time to service.
>
> Over time, there was sufficient demand for an equivalent set of
> packages on x64, so a similar set of optimized packages and build
> scripts were put together for the i386 and amd64 architectures as
> appropriate.
>
> CoolStack derives its name from the CoolTools project it is
> associated with. Because the community has already gained
> familiarity with the CoolStack name, there is no plan to change the
> name, despite the fact it's moving away from the CoolThreads
> processor and CoolTools project.
>
> Q: Why should this project exist here instead of upstream source code
> bases?
>
> In attempting to keep the various components under this project in
> step with the latest and/or most popular releases from the component
> projects, core code modifications will be contributed to the upstream
> projects wherever possible. However, it is expected that some
> contributed items, such as build scripts, a community forum, SMF
> manifests and the like, are more appropriate for an OpenSolaris
> project than the codebase of the component project.
>
> It is also anticipated that this project may have specific
> discussions about packaging as it relates to various OpenSolaris
> distributions and a need for there to be a forum to discuss how
> OpenSolaris technologies such as DTrace and SMF integrate with these
> component projects. Accordingly, this project will serve as the
> source for the OpenSolaris.org discussions and community decisions.
>
> From experience with the CoolStack project forums already, we know
> there may be some overlap with questions on issues/bugs and how
> things are intended to work that may be more appropriate for the
> project from which the component was derived, but the members of the
> OpenSolaris CoolStack project will encourage working with the
> component projects wherever possible. This project is intended to
> add to the communities surrounding those projects, not fragment
> them.
>
> -----
> 1. Public interfaces as defined in the ARC release taxonomy at
> http://www.opensolaris.org/os/community/arc/policies/interface-
> taxonomy/
>
> --
> Stefan Teleman
> Sun Microsystems, Inc.
> Stefan dot Teleman at Sun dot COM
>
+1
--
This Message has been Digitally Signed
PGP Public Key 0x437AF1A1
Availiable on hkp://pgp.mit.edu
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
215
From:
US
Registered:
5/12/06
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 15, 2007 11:02 PM
in response to: Stefan Teleman
|
|
Stefan Teleman wrote:
> Project Proposal: Next Generation Web Stack
+1
Looking forward to getting the project going!
>
> Summary
>
> We would like to create an OpenSolaris project to assume and enhance
> the community and work originally created in Sun's CoolStack project
> as part of the CoolTools project. This project will assume all of
> the CoolStack components, including Apache HTTP Server, MySQL
> Database Server, Perl, PHP, Ruby, Rails, Squid and others. The
> existing CoolStack forums will be retired and replaced with
> discussions at OpenSolaris.org.
>
> Goals
>
> The aim of this project is to address the OpenSolaris community needs
> for a set of Next Generation Web Tier Technologies. The initial
> seeding of this project will be based on the work already put into
> CoolStack, but it is not intended to be tied to the set of
> technologies currently in CoolStack.
>
> The project will provide the following:
> - A forum for discussion on which next generation web tier
> components should be part of various Solaris distributions
> - A codebase from which various packaged software can be
> derived for various OpenSolaris distributions, including
> build scripts and best practices for building this software
> with OpenSolaris
> - A forum for discussion on what kind of integration and
> features users would like to see integration between
> OpenSolaris and these external Open Source projects
>
> Overview of CoolStack
>
> In 2006, Sun introduced CoolStack - a Solaris-optimized,
> full-featured open-source based Web Tier stack which includes all of
> the traditional components of an AMP stack. This project proposes to
> take the best of the technologies and practices delivered by
> CoolStack and fully integrate them into OpenSolaris, optimized to
> utilize the features within OpenSolaris such as DTrace and the
> Solaris Management Facility.
>
> Many details can be found on CoolStack and the associated forums at
> http://cooltools.sunsource.net/coolstack/.
>
> However, we would like to summarize the history and goals to clarify
> how they relate to this project proposal.
>
> CoolStack had been originally conceived to provide a set of
> out-of-the-box optimized binaries for a common set of software
> components on the UltraSPARC T1 based systems. By performing this
> packaging for the community, the OpenSPARC project and Sun's
> Performance Technologies group had a goal to make it easy for users
> to quickly add packages to their existing systems to quickly obtain
> optimized performance and reducing time to service.
>
> Over time, there was sufficient demand for an equivalent set of
> packages on x64, so a similar set of optimized packages and build
> scripts were put together for the i386 and amd64 architectures as
> appropriate.
>
> CoolStack derives its name from the CoolTools project it is
> associated with. Because the community has already gained
> familiarity with the CoolStack name, there is no plan to change the
> name, despite the fact it's moving away from the CoolThreads
> processor and CoolTools project.
>
> Q: Why should this project exist here instead of upstream source code
> bases?
>
> In attempting to keep the various components under this project in
> step with the latest and/or most popular releases from the component
> projects, core code modifications will be contributed to the upstream
> projects wherever possible. However, it is expected that some
> contributed items, such as build scripts, a community forum, SMF
> manifests and the like, are more appropriate for an OpenSolaris
> project than the codebase of the component project.
>
> It is also anticipated that this project may have specific
> discussions about packaging as it relates to various OpenSolaris
> distributions and a need for there to be a forum to discuss how
> OpenSolaris technologies such as DTrace and SMF integrate with these
> component projects. Accordingly, this project will serve as the
> source for the OpenSolaris.org discussions and community decisions.
>
> From experience with the CoolStack project forums already, we know
> there may be some overlap with questions on issues/bugs and how
> things are intended to work that may be more appropriate for the
> project from which the component was derived, but the members of the
> OpenSolaris CoolStack project will encourage working with the
> component projects wherever possible. This project is intended to
> add to the communities surrounding those projects, not fragment
> them.
>
> -----
> 1. Public interfaces as defined in the ARC release taxonomy at
> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
>
--
Matt Ingenthron - Web Infrastructure Solutions Architect
Sun Microsystems, Inc. - Client Solutions, Systems Practice
http://blogs.sun.com/mingenthron/
email: matt dot ingenthron at sun dot com Phone: 310-242-6439
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,674
From:
Registered:
7/15/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 16, 2007 1:30 AM
in response to: Stefan Teleman
To: OpenSolaris » discuss
|
|
> Project Proposal: Next Generation Web Stack
>
> Summary
>
> We would like to create an OpenSolaris project to
> assume and enhance
> the community and work originally created in Sun's
> CoolStack project
> as part of the CoolTools project. This project will
> assume all of
> the CoolStack components, including Apache HTTP
> Server, MySQL
> Database Server, Perl, PHP, Ruby, Rails, Squid and
> others. The
> existing CoolStack forums will be retired and
> replaced with
> discussions at OpenSolaris.org.
+1 from me, just one suggestion:
ditch the MySQL DB as fast as possible and replace it with PostgreSQL.
MySQL DB is an extremely shoddy product, besides, PostgreSQL is much easier to deploy and use.
|
|
|
|
|
Posts:
352
From:
Registered:
5/1/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 16, 2007 2:10 AM
in response to: ux-admin
To: OpenSolaris » discuss
|
|
> > Project Proposal: Next Generation Web Stack
> >
> > Summary
> >
> > We would like to create an OpenSolaris project to
> > assume and enhance
> > the community and work originally created in Sun's
> > CoolStack project
> > as part of the CoolTools project. This project
> will
> > assume all of
> > the CoolStack components, including Apache HTTP
> > Server, MySQL
> > Database Server, Perl, PHP, Ruby, Rails, Squid and
> > others. The
> > existing CoolStack forums will be retired and
> > replaced with
> > discussions at OpenSolaris.org.
>
> +1 from me, just one suggestion:
>
> ditch the MySQL DB as fast as possible and replace it
> with PostgreSQL.
> MySQL DB is an extremely shoddy product, besides,
> PostgreSQL is much easier to deploy and use.
I disagree, put both Mysql and Postgres connectors in the package. Some applications
depend on specific connectors. One could argue PHP shoddy practices but that would kill the discussion.
Still a +1. Questions though as the project will move from the gcc compiler for the Solaris x64 project to the SunStudio compilers will the project be moved from the SunSource.net site which has an issue tracker (bug database) that is much more open than b.o.o.? And/or the source repository moved from say svn to mercurial? Or will the project stay on SunSource.net?
---Bob
|
|
|
|
|
Posts:
1,674
From:
Registered:
7/15/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 16, 2007 8:37 AM
in response to: palowoda
To: OpenSolaris » discuss
|
|
> I disagree, put both Mysql and Postgres connectors
> in the package.
Actually, that's a pretty good idea.
Put both in, so those projects that explicitly depend on MySQL have "backward compatibility" and others are free to use PostgreSQL as the backend for future development.
|
|
|
|
|
Posts:
123
From:
Lodz, Poland
Registered:
3/3/07
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 16, 2007 2:11 AM
in response to: ux-admin
|
|
On Fri, Mar 16, 2007 at 01:30:59AM -0700, UNIX admin wrote:
> ditch the MySQL DB as fast as possible and replace it with PostgreSQL.
> MySQL DB is an extremely shoddy product, besides, PostgreSQL is much easier to deploy and use.
PostgreSQL is included in standard distribution and I am sure Sun's
engineers are constantly working on its optimisation. But in web
development MySQL is much more often used and IMHO the CoolStack is
for those developers who are not going (at least now) to change their
database.
I hope that moving to OpenSolaris mailing list will speed up work on
CoolStack.
Regards
przemol
----------------------------------------------------------------------
Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,695
From:
US
Registered:
4/28/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 17, 2007 3:16 PM
in response to: przemolb
|
|
Steering to OpenSolaris databases mailing-list...
http://mail.opensolaris.org/pipermail/databases-discuss/2007-March/thread.html#55
On Fri, 16 Mar 2007, przemolicc at poczta dot fm wrote:
> On Fri, Mar 16, 2007 at 01:30:59AM -0700, UNIX admin wrote:
>> ditch the MySQL DB as fast as possible and replace it with PostgreSQL.
>> MySQL DB is an extremely shoddy product, besides, PostgreSQL is much easier to deploy and use.
>
> PostgreSQL is included in standard distribution and I am sure Sun's
> engineers are constantly working on its optimisation. But in web
> development MySQL is much more often used and IMHO the CoolStack is
> for those developers who are not going (at least now) to change their
> database.
>
> I hope that moving to OpenSolaris mailing list will speed up work on
> CoolStack.
>
> Regards
> przemol
>
>
> ----------------------------------------------------------------------
> Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
>
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Jason J. W. Wil...
jasonjwwilliams@gmai...
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 10:26 AM
in response to: ux-admin
|
|
+1 from Me. Would be nice to see a Python-based framework included
(Django perhaps).
Also, the MySQL is a definite requirement. Calling MySQL a shoddy
product is pretty nasty and wrong-headed comment. I've got my own
gripes about Postgres, but lets just say I'd like to see both
included, and folks can use what works best (most reliably) for them.
-J
On 3/16/07, UNIX admin <tripivceta at hotmail dot com> wrote:
> > Project Proposal: Next Generation Web Stack
> >
> > Summary
> >
> > We would like to create an OpenSolaris project to
> > assume and enhance
> > the community and work originally created in Sun's
> > CoolStack project
> > as part of the CoolTools project. This project will
> > assume all of
> > the CoolStack components, including Apache HTTP
> > Server, MySQL
> > Database Server, Perl, PHP, Ruby, Rails, Squid and
> > others. The
> > existing CoolStack forums will be retired and
> > replaced with
> > discussions at OpenSolaris.org.
>
> +1 from me, just one suggestion:
>
> ditch the MySQL DB as fast as possible and replace it with PostgreSQL.
> MySQL DB is an extremely shoddy product, besides, PostgreSQL is much easier to deploy and use.
>
>
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
513
From:
US
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 10:52 AM
in response to: Jason J. W. Wil...
|
|
Hi,
I think this is a great idea and will help developers and shops that
depend on these tools. Of course the key issue I see is supportability.
A lot of developers like to see the latest and greatest versions of
these tools. However, that must be tempered with the requirement of
stability and security. So QA testing will be paramount to making this
a realistic project.
FYI, I noticed that postgres is now under /usr/postgres. It would be
great to see mysql follow the same rule. Having /usr/apache,
/usr/perl5, /usr/postgres, /usr/java, /usr/gnu, etc. are great for
keeping things organized. So I hope we would do the same for other
things such as Ruby, PHP, etc.
Octave
--- "Jason J. W. Williams" <jasonjwwilliams at gmail dot com> wrote:
> +1 from Me. Would be nice to see a Python-based framework included
> (Django perhaps).
>
> Also, the MySQL is a definite requirement. Calling MySQL a shoddy
> product is pretty nasty and wrong-headed comment. I've got my own
> gripes about Postgres, but lets just say I'd like to see both
> included, and folks can use what works best (most reliably) for them.
>
> -J
>
> On 3/16/07, UNIX admin <tripivceta at hotmail dot com> wrote:
> > > Project Proposal: Next Generation Web Stack
> > >
> > > Summary
> > >
> > > We would like to create an OpenSolaris project to
> > > assume and enhance
> > > the community and work originally created in Sun's
> > > CoolStack project
> > > as part of the CoolTools project. This project will
> > > assume all of
> > > the CoolStack components, including Apache HTTP
> > > Server, MySQL
> > > Database Server, Perl, PHP, Ruby, Rails, Squid and
> > > others. The
> > > existing CoolStack forums will be retired and
> > > replaced with
> > > discussions at OpenSolaris.org.
> >
> > +1 from me, just one suggestion:
> >
> > ditch the MySQL DB as fast as possible and replace it with
> PostgreSQL.
> > MySQL DB is an extremely shoddy product, besides, PostgreSQL is
> much easier to deploy and use.
> >
> >
> > This message posted from opensolaris.org
> > _______________________________________________
> > opensolaris-discuss mailing list
> > opensolaris-discuss at opensolaris dot org
> >
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo dot com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
_____________________________________________________________________________ _______
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
John Mark Walker
johnmark@hyperic.com
|
|
|
|
Re: Re: Project Proposal: Next Generation Web
Stack
Posted:
Mar 19, 2007 11:01 AM
in response to: oorgeron
|
|
Hi,
I would like to point out that manageability should be part of any web
stack discussion - ask any ops guys who have had to actually deploy this
stuff. Managing it usually requires a great deal of customization as
current software does a poor job of dealing with it - except for ours,
of course :)
Obviously, I would like Hyperic HQ to be part of any web stack
management discussion, but I would settle for a documented set of best
practice information.
I also notice that all the great J2EE-based app servers were left out of
the discussion. I don't see how anyone can have a web tools discussion
these days without including app servers in the mix.
Thanks,
John Mark Walker
Community Outreach
Hyperic, Inc.
Octave Orgeron wrote:
> Hi,
>
> I think this is a great idea and will help developers and shops that
> depend on these tools. Of course the key issue I see is supportability.
> A lot of developers like to see the latest and greatest versions of
> these tools. However, that must be tempered with the requirement of
> stability and security. So QA testing will be paramount to making this
> a realistic project.
>
> FYI, I noticed that postgres is now under /usr/postgres. It would be
> great to see mysql follow the same rule. Having /usr/apache,
> /usr/perl5, /usr/postgres, /usr/java, /usr/gnu, etc. are great for
> keeping things organized. So I hope we would do the same for other
> things such as Ruby, PHP, etc.
>
> Octave
>
> --- "Jason J. W. Williams" <jasonjwwilliams at gmail dot com> wrote:
>
>
>> +1 from Me. Would be nice to see a Python-based framework included
>> (Django perhaps).
>>
>> Also, the MySQL is a definite requirement. Calling MySQL a shoddy
>> product is pretty nasty and wrong-headed comment. I've got my own
>> gripes about Postgres, but lets just say I'd like to see both
>> included, and folks can use what works best (most reliably) for them.
>>
>> -J
>>
>> On 3/16/07, UNIX admin <tripivceta at hotmail dot com> wrote:
>>
>>>> Project Proposal: Next Generation Web Stack
>>>>
>>>> Summary
>>>>
>>>> We would like to create an OpenSolaris project to
>>>> assume and enhance
>>>> the community and work originally created in Sun's
>>>> CoolStack project
>>>> as part of the CoolTools project. This project will
>>>> assume all of
>>>> the CoolStack components, including Apache HTTP
>>>> Server, MySQL
>>>> Database Server, Perl, PHP, Ruby, Rails, Squid and
>>>> others. The
>>>> existing CoolStack forums will be retired and
>>>> replaced with
>>>> discussions at OpenSolaris.org.
>>>>
>>> +1 from me, just one suggestion:
>>>
>>> ditch the MySQL DB as fast as possible and replace it with
>>>
>> PostgreSQL.
>>
>>> MySQL DB is an extremely shoddy product, besides, PostgreSQL is
>>>
>> much easier to deploy and use.
>>
>>> This message posted from opensolaris.org
>>> _______________________________________________
>>> opensolaris-discuss mailing list
>>> opensolaris-discuss at opensolaris dot org
>>>
>>>
>> _______________________________________________
>> opensolaris-discuss mailing list
>> opensolaris-discuss at opensolaris dot org
>>
>>
>
>
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> Octave J. Orgeron
> Solaris Systems Engineer
> http://www.opensolaris.org/os/community/sysadmin/
> http://unixconsole.blogspot.com
> unixconsole at yahoo dot com
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>
>
>
> _______________________________________________________________________________ _____
> TV dinner still cooling?
> Check out "Tonight's Picks" on Yahoo! TV.
> http://tv.yahoo.com/
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
315
From:
US
Registered:
4/27/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 7:37 PM
in response to: oorgeron
|
|
On Monday 19 March 2007 13:52, Octave Orgeron wrote:
> Hi,
>
> I think this is a great idea and will help developers and shops
> that depend on these tools. Of course the key issue I see is
> supportability. A lot of developers like to see the latest and
> greatest versions of these tools. However, that must be tempered
> with the requirement of stability and security.
http://www.php-security.org/
--Stefan
--
Stefan Teleman 'Nobody Expects the Spanish Inquisition'
KDE e.V. -Monty Python
stefan dot teleman at gmail dot com
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,109
From:
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 11:07 PM
in response to: steleman
|
|
On Monday 19 March 2007 07:37 pm, Stefan Teleman wrote:
> http://www.php-security.org/
This is scary...I think I'll go get a cold shower...;-)
I have to wonder, much of the online forum software is written in PHP, and as
such seems to be vulnerable. How do people deal with sites that are based on
that? I mean, you have to patch this stuff constantly, so no matter what is
delivered will be changing shortly it would seem.
Truely the only way to deal with that is to be tracking the nightly code from
PHP, or is there another way?
Seems we'll need to update this regularly as a community. Not pointing the
finger at you specific Stefan, it's an issue that needs to be worked out
within the community.
It's scary to think that much of the forum software is written with it...
--
Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at Sun - hire people that care about our company!
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
315
From:
US
Registered:
4/27/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 12:24 AM
in response to: aland
|
|
On Tuesday 20 March 2007 02:07, Alan DuBoff wrote:
> On Monday 19 March 2007 07:37 pm, Stefan Teleman wrote:
> > http://www.php-security.org/
>
> This is scary...I think I'll go get a cold shower...;-)
>
> I have to wonder, much of the online forum software is written in
> PHP, and as such seems to be vulnerable. How do people deal with
> sites that are based on that?
Numerous sites are written in PHP. Many of them run the suhosin
security extension, but many others don't. Those who don't are doing
so at their own peril.
php-security writes the suhosin PHP security extension, which is very
useful (imho it would be insanely risky to run any PHP site open to
the Internet without suhosin enabled). The constant problem
php-security is facing is that they update their security extension
depending on the latest vulnerabilities they have uncovered. So it
ends up being a game of a catch-up: PHP releases a new version,
php-security has to update the suhosin extension to this latest
version.
> I mean, you have to patch this stuff constantly, so no matter what
> is delivered will be changing shortly it would seem.
Essentially, yes. It looks like there will always be two parallel
patch tracks: security patches for the currently released PHP, and
security patches for the next-to-be-released PHP version.
All this is compounded by the fact that PHP releases aren't
necessarily compatible with each other.
> Truely the only way to deal with that is to be tracking the nightly
> code from PHP, or is there another way?
The fundamental problems stems from the fact that a PHP vulnerability
can exist either in the PHP code, or in the PHP application.
Uncovering vulnerabilities in the PHP code can be very tricky:
vulnerabilities might only occur on infrequent code paths, or in
infrequent combinations of code paths + PHP extensions being used.
Vulnerabilities in the PHP application depend exclusively on how the
application is written.
I'm thinking that the nightly code would be even more dangerous. It's
also a moving target. It seems to me that the efficient approach is
to track official PHP releases. The official (numbered) PHP releases
are the only ones which might have a release of suhosin.
What i believe we should do: we should audit the PHP codebase with
Coverity (http://www.coverity.com/). From looking at the
htp://scan.coverity.com/ page, it doesn't look like PHP is currently
being audited by Coverity. The only information i could find about a
PHP Coverity audit was here:
http://www.internetnews.com/dev-news/article.php/3589361
"Perl had a defect density of only 0.186. In comparison Python had a
defect density of 0.372 and PHP was actually above both the baseline
and LAMP averages at 0.474."
[defect density == number of code defects per 1000 lines of code]
I believe we should also Purify PHP. The problem is that Purify
probably won't work on Nevada, but we could build PHP on a release of
S10 they support, and it will still catch buffer overflows, ABR/ABW,
UMR, stack corruption, double deletion, etc. We could then publish
the results of the Coverity audit and of the Purify output, and we
could forward them to php-security.org, along with patches. This
would give the PHP community an objective base for requesting bug and
security fixes.
> Seems we'll need to update this regularly as a community. Not
> pointing the finger at you specific Stefan, it's an issue that
> needs to be worked out within the community.
The most important aspect, for me, is to identify these
vulnerabilities and to have bugs and security fixes accepted upstream
by the PHP Group.
--Stefan
--
Stefan Teleman 'Nobody Expects the Spanish Inquisition'
KDE e.V. -Monty Python
stefan dot teleman at gmail dot com
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
215
From:
US
Registered:
5/12/06
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 9:45 AM
in response to: steleman
|
|
Stefan Teleman wrote:
(snip...)
>
> I believe we should also Purify PHP. The problem is that Purify
> probably won't work on Nevada, but we could build PHP on a release of
> S10 they support, and it will still catch buffer overflows, ABR/ABW,
> UMR, stack corruption, double deletion, etc. We could then publish
> the results of the Coverity audit and of the Purify output, and we
> could forward them to php-security.org, along with patches. This
> would give the PHP community an objective base for requesting bug and
> security fixes.
>
>
While Nevada may not run Purify, it is possible to get a subset of this
with umem debugging, which is in nevada and as Open Source has been
ported to Linux by an ISV. This sounds like an excellent thing to get
going under the new OpenSolaris project! The upstream projects can take
it into their codebases as well if they'd like to do so.
Speaking of which, we haven't been set up yet, have we?
It may also be interesting to see what, if anything, can be done about
reducing privilege sets for this OpenSolaris Apache/PHP stack to at
least reduce the possibility of nefarious activities if (when?) there is
a vulnerability. My colleague Alec Muffet may be able to lend some
thoughts there.
- Matt
--
Matt Ingenthron - Web Infrastructure Solutions Architect
Sun Microsystems, Inc. - Client Solutions, Systems Practice
http://blogs.sun.com/mingenthron/
email: matt dot ingenthron at sun dot com Phone: 310-242-6439
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
513
From:
US
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 10:02 AM
in response to: ingenthr
|
|
Hi,
I support the idea of adding reduced privs to this stack to help
customers reduce the security issues that these tools expose by nature.
It's these kind of "value adds" that will differentiate our web stack.
Another aspect would be management. It would be nice to a tool to
manage a data center full of servers running this web stack that could
be easily managed.
Octave
--- Matt Ingenthron <Matt dot Ingenthron at Sun dot COM> wrote:
> Stefan Teleman wrote:
>
> (snip...)
> >
> > I believe we should also Purify PHP. The problem is that Purify
> > probably won't work on Nevada, but we could build PHP on a release
> of
> > S10 they support, and it will still catch buffer overflows,
> ABR/ABW,
> > UMR, stack corruption, double deletion, etc. We could then publish
> > the results of the Coverity audit and of the Purify output, and we
> > could forward them to php-security.org, along with patches. This
> > would give the PHP community an objective base for requesting bug
> and
> > security fixes.
> >
> >
>
> While Nevada may not run Purify, it is possible to get a subset of
> this
> with umem debugging, which is in nevada and as Open Source has been
> ported to Linux by an ISV. This sounds like an excellent thing to
> get
> going under the new OpenSolaris project! The upstream projects can
> take
> it into their codebases as well if they'd like to do so.
>
> Speaking of which, we haven't been set up yet, have we?
>
> It may also be interesting to see what, if anything, can be done
> about
> reducing privilege sets for this OpenSolaris Apache/PHP stack to at
> least reduce the possibility of nefarious activities if (when?) there
> is
> a vulnerability. My colleague Alec Muffet may be able to lend some
> thoughts there.
>
> - Matt
>
> --
> Matt Ingenthron - Web Infrastructure Solutions Architect
> Sun Microsystems, Inc. - Client Solutions, Systems Practice
> http://blogs.sun.com/mingenthron/
> email: matt dot ingenthron at sun dot com Phone: 310-242-6439
>
>
>
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo dot com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
_____________________________________________________________________________ _______
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,793
From:
GB
Registered:
3/9/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 10:03 AM
in response to: ingenthr
|
|
Matt Ingenthron wrote:
> It may also be interesting to see what, if anything, can be done about
> reducing privilege sets for this OpenSolaris Apache/PHP stack to at
> least reduce the possibility of nefarious activities if (when?) there is
> a vulnerability. My colleague Alec Muffet may be able to lend some
> thoughts there.
Start with the sun.com/blueprints articles by Glenn Brunette and I,
where we cover using Apache as an example service. We didn't include
PHP and that might add an additional wrinkle to what privileges are
needed but since I know nothing about PHP I can't be sure.
Oh and BTW it is Muffett (two 't's in Alec's name one in mine :-)).
--
Darren J Moffat
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,109
From:
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 10:40 AM
in response to: ingenthr
|
|
On Tuesday 20 March 2007 09:45 am, Matt Ingenthron wrote:
> It may also be interesting to see what, if anything, can be done about
> reducing privilege sets for this OpenSolaris Apache/PHP stack to at
> least reduce the possibility of nefarious activities if (when?) there is
> a vulnerability. My colleague Alec Muffet may be able to lend some
> thoughts there.
I'll watch to see what Alec might have to say, but in general this is going to
be one very high maintenance package, any way we look at it. We do need the
software, it just has a lot of strings attached from any perspective we look
at it, unless the software is just left vulnerable.
--
Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at Sun - hire people that care about our company!
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
215
From:
US
Registered:
5/12/06
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 11:11 AM
in response to: aland
|
|
Alan DuBoff wrote:
>
> I'll watch to see what Alec might have to say, but in general this is going to
> be one very high maintenance package, any way we look at it. We do need the
> software, it just has a lot of strings attached from any perspective we look
> at it, unless the software is just left vulnerable.
>
>
Agreed, and at some level or another, this project will just be
packaging what the community around the given component develops, bug
for bug complete. I suspect users will understand that already, though
it doesn't obviate the need to communicate it.
It'll be a tough balance to strike, since not only is it the version
that Zend/MySQL and others ship that the project will need to track, but
it may also need to track what's in popular consumption and/or in other
packaging projects (i.e. distributions). I will say it's my opinion
that while there are many things we *could* do, we should be very
judicious about the steps taken so it won't be too much effort to keep
up with how the other projects evolve.
This is all the more reason the OpenSolaris project community input is
important.
- Matt
--
Matt Ingenthron - Web Infrastructure Solutions Architect
Sun Microsystems, Inc. - Client Solutions, Systems Practice
http://blogs.sun.com/mingenthron/
email: matt dot ingenthron at sun dot com Phone: 310-242-6439
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,109
From:
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 21, 2007 12:48 AM
in response to: ingenthr
|
|
On Tuesday 20 March 2007 11:11 am, Matt Ingenthron wrote:
> Agreed, and at some level or another, this project will just be
> packaging what the community around the given component develops, bug
> for bug complete. I suspect users will understand that already, though
> it doesn't obviate the need to communicate it.
You would think so, but don't ever underestimate the ignorance of the user,
they will always astound you!<g>
> This is all the more reason the OpenSolaris project community input is
> important.
Absolutely. I feel we need this type of software, yet at the same time see it
as a double edge sword. I was considering running some PHP software on a
public site, but now I'm not sure.
Anyone in the community that really works with PHP on a regular basis and can
comment on how they handle the security issues and/or updates?
It is my understanding that many modules will not compile on different
releases of PHP. Not sure how much of a problem it is to update though.
--
Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at Sun - hire people that care about our company!
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
5,504
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 10:09 AM
in response to: steleman
|
|
Stefan Teleman wrote:
> I believe we should also Purify PHP. The problem is that Purify
> probably won't work on Nevada, but we could build PHP on a release of
> S10 they support, and it will still catch buffer overflows, ABR/ABW,
> UMR, stack corruption, double deletion, etc.
Sun Studio's dbx check -all will give you a large subset of that on
Nevada, though in Studio 11, much of it is only fully functional on
SPARC, not x64. (I believe that's being resolved in Studio 12.)
--
-Alan Coopersmith- alan dot coopersmith at sun dot com
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,695
From:
US
Registered:
4/28/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 11:09 AM
in response to: steleman
|
|
The sfwnv-discuss list might be a better venue for this discussion. Some of
the people subscribed there might not be subscribed here.
Eric
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
513
From:
US
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 6:16 AM
in response to: aland
|
|
Hi,
Perl and PHP are often targeted on the internet. It's sad and
unfortunate, but it's the reality of things. When I use to work for a
web hosting company, we'd constantly have to deal with crackers and
script kiddies hijacking customer websites. In many cases, poorly
written perl or php code was to blame. The worst part is that most of
the code people use comes from other sites that have pre-packaged
forums, ordering systems, mailing list etc. So I think we'll be
upgrading and patching(once 11 comes out) the web stack on a regular
basis. But at the same time, it would provide a lot of value to
customers in the web space.
Octave
--- Alan DuBoff <Alan dot DuBoff at Sun dot Com> wrote:
> On Monday 19 March 2007 07:37 pm, Stefan Teleman wrote:
> > http://www.php-security.org/
>
> This is scary...I think I'll go get a cold shower...;-)
>
> I have to wonder, much of the online forum software is written in
> PHP, and as
> such seems to be vulnerable. How do people deal with sites that are
> based on
> that? I mean, you have to patch this stuff constantly, so no matter
> what is
> delivered will be changing shortly it would seem.
>
> Truely the only way to deal with that is to be tracking the nightly
> code from
> PHP, or is there another way?
>
> Seems we'll need to update this regularly as a community. Not
> pointing the
> finger at you specific Stefan, it's an issue that needs to be worked
> out
> within the community.
>
> It's scary to think that much of the forum software is written with
> it...
>
> --
>
> Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
> Advocate of insourcing at Sun - hire people that care about our
> company!
>
>
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo dot com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
_____________________________________________________________________________ _______
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.
http://farechase.yahoo.com/promo-generic-14795097
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,109
From:
Registered:
6/14/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 10:26 AM
in response to: oorgeron
|
|
On Tuesday 20 March 2007 06:16 am, Octave Orgeron wrote:
> Perl and PHP are often targeted on the internet. It's sad and
> unfortunate, but it's the reality of things. When I use to work for a
> web hosting company, we'd constantly have to deal with crackers and
> script kiddies hijacking customer websites. In many cases, poorly
> written perl or php code was to blame. The worst part is that most of
> the code people use comes from other sites that have pre-packaged
> forums, ordering systems, mailing list etc. So I think we'll be
> upgrading and patching(once 11 comes out) the web stack on a regular
> basis. But at the same time, it would provide a lot of value to
> customers in the web space.
When you say, "So I think we'll be upgrading and patching(once 11 comes out)
the web stack on a regular basis.", so you mean the community will need to
keep upgrading the package(s)? I'm not sure who "we'll" refers to.
Yes, the packages will need to be updates, and most likely we won't be able to
get things updated quick enough for folks that are running this stuff in
production, they'll need to be tracking that themself, IMO.
At least the way the current system works, it takes some work to build, test,
and package the software up. If this needs to be done everytime a security
module is released, that will cause a lot of work.
If we had an online repository that could update over the net, that would be
easier, but it would still be work to build, test, and package.
I'd be curious to hear if Blastwave is able to keep up with security patches
on PHP, they would be in the same situation, but less as they probably don't
do as much testing as Sun has done in packaging up the software themself.
Maybe Dennis can comment on that and/or how the users of Blastwave PHP keep
themself secure from attacks.
OTOH, maybe Blastwave has figured out a way to get updates for PHP in place on
in a timely fashion that that isn't a problem. Regardless, someone will need
to track these security problems on a daily basis.
--
Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group
Advocate of insourcing at Sun - hire people that care about our company!
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
315
From:
US
Registered:
4/27/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 20, 2007 12:07 PM
in response to: aland
|
|
On 3/20/07, Alan DuBoff <Alan dot DuBoff at sun dot com> wrote:
> When you say, "So I think we'll be upgrading and patching(once 11 comes out)
> the web stack on a regular basis.", so you mean the community will need to
> keep upgrading the package(s)? I'm not sure who "we'll" refers to.
In this particular case "we" referes to yours truly. I was using the
Royal "We". :-)
Yes, maintaining security patches for PHP is an extremely high maintenance job.
--Stefan
--
Stefan Teleman
KDE e.V.
stefan dot teleman at gmail dot com
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,674
From:
Registered:
7/15/05
|
|
|
|
Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 12:10 PM
in response to: Jason J. W. Wil...
To: OpenSolaris » discuss
|
|
> Also, the MySQL is a definite requirement. Calling
> MySQL a shoddy
> product is pretty nasty and wrong-headed comment.
Take that however you please, but I stand behind what I wrote.
Any product that is incapable of doing a cold DB dump and reimport back into another instance of the product (same revision) is shoddy, and to make matters worse, this happened while following the MySQL AB's documentation. Anything like that does not deserve to be called production quality, let alone have applications that might be mission critical depend on it.
I wrote it, you read it here from me, and I stand behind it any day of the week.
Message was edited by:
ux-admin
|
|
|
|
|
John Mark Walker
johnmark@hyperic.com
|
|
|
|
Re: Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 12:14 PM
in response to: ux-admin
|
|
UNIX admin wrote:
> Any product that is incapable of doing a cold DB dump and reimport back into another instance of the product (same revision) is shoddy, and to make matters worse, this happened while following the MySQL AB's documentation. Anything like that does not deserve to be called production quality, let alone have applications that might be mission critical depend on it.
> I wrote it, you read it here from me, and I stand behind it any day of the week.
>
All fine and well, but I suspect a few million web site operators and
other IT operations staff would disagree with you. I'm a fan of Postgres
myself, but any proposed "web stack" that leaves out MySQL is kind of
missing the point by not serving the users who would, you know, actually
stand to benefit.
-JM
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,674
From:
Registered:
7/15/05
|
|
|
|
Re: Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 12:30 PM
in response to: John Mark Walker
To: OpenSolaris » discuss
|
|
> All fine and well, but I suspect a few million web
> site operators and
> other IT operations staff would disagree with you.
> I'm a fan of Postgres
> myself, but any proposed "web stack" that leaves out
> MySQL is kind of
> missing the point by not serving the users who would,
> you know, actually
> stand to benefit.
...Which is why I a wrote earlier that including both in the CoolStack would be beneficial for everyone. At least then one could pick and choose between one or the other RDBMS, both optimized for Solaris. Applications that had a hard dependency on MySQL would continue to work. Everybody wins.
|
|
|
|
|
Jason J. W. Wil...
jasonjwwilliams@gmai...
|
|
|
|
Re: Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 1:38 PM
in response to: ux-admin
|
|
Hey there,
We run a few hundred millions rows of data in multiple MySQL clusters
and have not had the same issue...having done it many times a week.
Sounds like operator error.
-J
On 3/19/07, UNIX admin <tripivceta at hotmail dot com> wrote:
> > Also, the MySQL is a definite requirement. Calling
> > MySQL a shoddy
> > product is pretty nasty and wrong-headed comment.
>
> Take that however you please, but I stand behind what I wrote.
>
> Any product that is incapable of doing a cold DB dump and reimport back into another instance of the product (same revision) is shoddy, and to make matters worse, this happened while following the MySQL AB's documentation. Anything like that does not deserve to be called production quality, let alone have applications that might be mission critical depend on it.
> I wrote it, you read it here from me, and I stand behind it any day of the week.
>
> Message was edited by:
> ux-admin
>
>
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
1,674
From:
Registered:
7/15/05
|
|
|
|
Re: Re: Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 2:11 PM
in response to: Jason J. W. Wil...
To: OpenSolaris » discuss
|
|
> Hey there,
>
> We run a few hundred millions rows of data in
> multiple MySQL clusters
> and have not had the same issue...having done it many
> times a week.
> Sounds like operator error.
Hmmm, no such error in PostgreSQL... or in Oracle. Strange, don't you think? I wouldn't call that a coincidence.
|
|
|
|
|
Posts:
1,695
From:
US
Registered:
4/28/05
|
|
|
|
Re: Project Proposal: Next Generation Web Stack
Posted:
Mar 19, 2007 9:29 AM
in response to: Stefan Teleman
|
|
Thanks, Stefan. You have seconds. I'll contact you offline to
get you set up.
On Thu, 15 Mar 2007, Stefan Teleman wrote:
> Project Proposal: Next Generation Web Stack
>
> Summary
>
> We would like to create an OpenSolaris project to assume and enhance
> the community and work originally created in Sun's CoolStack project
> as part of the CoolTools project. This project will assume all of
> the CoolStack components, including Apache HTTP Server, MySQL
> Database Server, Perl, PHP, Ruby, Rails, Squid and others. The
> existing CoolStack forums will be retired and replaced with
> discussions at OpenSolaris.org.
>
> Goals
>
> The aim of this project is to address the OpenSolaris community needs
> for a set of Next Generation Web Tier Technologies. The initial
> seeding of this project will be based on the work already put into
> CoolStack, but it is not intended to be tied to the set of
> technologies currently in CoolStack.
>
> The project will provide the following:
> - A forum for discussion on which next generation web tier
> components should be part of various Solaris distributions
> - A codebase from which various packaged software can be
> derived for various OpenSolaris distributions, including
> build scripts and best practices for building this software
> with OpenSolaris
> - A forum for discussion on what kind of integration and
> features users would like to see integration between
> OpenSolaris and these external Open Source projects
>
> Overview of CoolStack
>
> In 2006, Sun introduced CoolStack - a Solaris-optimized,
> full-featured open-source based Web Tier stack which includes all of
> the traditional components of an AMP stack. This project proposes to
> take the best of the technologies and practices delivered by
> CoolStack and fully integrate them into OpenSolaris, optimized to
> utilize the features within OpenSolaris such as DTrace and the
> Solaris Management Facility.
>
> Many details can be found on CoolStack and the associated forums at
> http://cooltools.sunsource.net/coolstack/.
>
> However, we would like to summarize the history and goals to clarify
> how they relate to this project proposal.
>
> CoolStack had been originally conceived to provide a set of
> out-of-the-box optimized binaries for a common set of software
> components on the UltraSPARC T1 based systems. By performing this
> packaging for the community, the OpenSPARC project and Sun's
> Performance Technologies group had a goal to make it easy for users
> to quickly add packages to their existing systems to quickly obtain
> optimized performance and reducing time to service.
>
> Over time, there was sufficient demand for an equivalent set of
> packages on x64, so a similar set of optimized packages and build
> scripts were put together for the i386 and amd64 architectures as
> appropriate.
>
> CoolStack derives its name from the CoolTools project it is
> associated with. Because the community has already gained
> familiarity with the CoolStack name, there is no plan to change the
> name, despite the fact it's moving away from the CoolThreads
> processor and CoolTools project.
>
> Q: Why should this project exist here instead of upstream source code
> bases?
>
> In attempting to keep the various components under this project in
> step with the latest and/or most popular releases from the component
> projects, core code modifications will be contributed to the upstream
> projects wherever possible. However, it is expected that some
> contributed items, such as build scripts, a community forum, SMF
> manifests and the like, are more appropriate for an OpenSolaris
> project than the codebase of the component project.
>
> It is also anticipated that this project may have specific
> discussions about packaging as it relates to various OpenSolaris
> distributions and a need for there to be a forum to discuss how
> OpenSolaris technologies such as DTrace and SMF integrate with these
> component projects. Accordingly, this project will serve as the
> source for the OpenSolaris.org discussions and community decisions.
>
> From experience with the CoolStack project forums already, we know
> there may be some overlap with questions on issues/bugs and how
> things are intended to work that may be more appropriate for the
> project from which the component was derived, but the members of the
> OpenSolaris CoolStack project will encourage working with the
> component projects wherever possible. This project is intended to
> add to the communities surrounding those projects, not fragment
> them.
>
> -----
> 1. Public interfaces as defined in the ARC release taxonomy at
> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
>
> --
> Stefan Teleman
> Sun Microsystems, Inc.
> Stefan dot Teleman at Sun dot COM
>
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss at opensolaris dot org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
