It sounds as though Sun is heading in the right direction. I am most interested in how we can take advantage of Open Solaris for production systems that serve very narrow, but very high visibility functions and that must meet strict service levels.
These sort of systems are typically designed so that catastrophic failures on a set of platforms do not degrade service, via design points such as logical and geographic load balancing and diverse platforms. This permits us some latitude. In a case where OpenSolaris provides a feature that addresses a specific problem (one sufficiently important) I would like to have the option of using it rather than waiting for the feature to make it into the GA Solaris release. it is easier for me to make the management team comfortable if we can expect only slightly elevated risks of defects and the confidence that Sun is prepared to help solve the problem via some "active" support mechanism. I would like to be able to call Sun and say "build 123 has this specific problem" and know that an engineer will be assigned by Sun to bring the problem to a resolution within a week or so. Since there is often significant investment in QA cycles for a platform that includes interoperability between the HW/OS/APP/Network by our own internal teams this should not include a pat response of "are you using the LATEST build?". This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org