What Should We Add To Cool Stack

One of the best kept secrets at Sun is the Cool Stack project. In fact, I did a quick 3 question survey of my staff last week and 6 out of 164 who responded had not heard of Cool Stack.

Cool Stack is a collection of some of the most commonly used open source applications optimized for the Sun Solaris OS platform. By using these binaries you will enjoy the best levels of performance from your system, while also reducing your time-to-service.

Now this week's question, open to a wider audience, is, what should we add next to Cool Stack. One of the top requests has been memcache. We are working on that. Meanwhile, if you have any questions about Memcache on Solaris, check with Matt. So go ahead, comment away, and let me know what else we should be considering for Cool Stack.

Posted on: Dec 04, 2006

Posted by: marchamilton

Category: General

Tags: none

Permanent link to this entry

Comments:

I would like to memcached as well. The stack I use is lighttpd (with fastcgi over flup), django, and postgresql (over psycopg2).

Posted by newpers on December 04, 2006 at 10:15 AM PST #

[Trackback] Since Marc outted the work I've been doing with our PAE and MDE folks, I guess I'd better type up some thoughts on the goings-on. It's time to get some of it out in the wild afterall. Steve's new group, which I'm happy to be a part of, is off f...

Posted by Matt Ingenthron's Stream of Consciousness on December 04, 2006 at 10:34 AM PST #

How about python and mod_python?

Posted by James Foronda on December 04, 2006 at 10:35 AM PST #

Two issues have prevented me from looking at coolstack. The first is that it installs into /usr/local. That's reserved for my local software, so I can't install it there. It should install into /opt/coolstack or something similar. The second is that the versions are outdated or not what I need. I'm currently using apache 1.3.x or 2.2.3; mysql 5.0.27; and php 5.2.0 (with some extra modules enabled). And why not simply put the information about how to recompile the packages yourself (which you're almost certain to need to do) on the web page? Why make the customer download and install the package?

Posted by Peter Tribble on December 04, 2006 at 11:35 AM PST #

Thanks for the feedback Peter. I do know that things are moving from /usr/local to /opt in a not-to-distant release. Also, there's work going on to update all of the versions and add some of the most popular modules.

With respect to why handling things as a package and not just source code-- there are some who obviously feel the other way about that. However, I agree that we should have the build environment documented (including compiler flags and such) in case people want to take the work behind the Cool Stack testing and optimization to other versions. I'll ping the team.

Thanks for the feedback!

Posted by Matt Ingenthron on December 04, 2006 at 12:51 PM PST #

You are packaging in /usr/local/? Ouch. Not only does that violate the System V interface definition (SVID), it also won't work in sparse zones (shared out lofs, ro from the global zone). Is the SUNWpostgresql compiled with Sun Studio 11?

Posted by UX-admin on December 04, 2006 at 12:52 PM PST #

I forgot to mention, you can see Shanti's responses on some of the direction with Cool Stack here

Posted by Matt Ingenthron on December 04, 2006 at 12:56 PM PST #

There are README files in each /usr/local/<package> dir that contain the compiler options used for the build. Check http://hell.jedicoder.net/?p=85 for more info.

Posted by Derek Crudgington on December 04, 2006 at 02:04 PM PST #

Post a Comment:
Comments are closed for this entry.

This blog copyright 2009 by marchamilton