Hi Nicholas,
Thanks for the proposal, I have a few questions:
1) Is it necessary that you have the community group setup before your
source code is available/published? I only ask because I'm not entirely
comfortable with the idea of giving governance representation and voting
grants to a community that doesn't yet have open code or open development.
2) What will the community's initial content be? Will it be entirely
Sun Cluster focused, or will it be more generalised as the community
name suggests?
3) Similar to #2, but more generally: will your community
endorse/sponsor community work/projects focused on HA Clusters, but
involving non-Sun Cluster code?
4) Do you have a plan for involving non-Sun employees (i.e.:
documentation, tutorials, code walk-throughs, etc.) to help bring them
up to speed with your development process and source code?
I think those are all the questions I have for now, if anymore come to
mind - I'll let you know. :) Thanks!
cheers,
steve
Nicholas Solter wrote:
> Following is a proposal for an HA Clusters community on opensolaris.org.
>
> Name:
>
> ?HA Clusters?
>
> Background:
>
> High-Availability (HA) Clusters are a class of tightly-coupled
> distributed systems that provide high availability of services through
> hardware and software monitoring and hardware redundancy. HA Clusters
> are often closely associated with the underlying operating system, and
> in many cases can be considered extensions of the OS. For example,
> approximately one half of the Solaris Cluster code runs in the Solaris
> kernel.
>
> Focus and Scope:
>
> The scope of the community will be implementations, ideas, innovations,
> and research around high-availability clusters on the OpenSolaris
> platform. This scope includes, but is not limited to, such areas as core
> technologies (eg. heartbeats, quorum, filesystems), APIs, system
> administration, application support code (agents), and test frameworks.
> Although the focus is on clusters for high-availability, as opposed to
> HPC clusters, grids, or other cluster technologies, we recognize that
> there is often overlap between the technologies for different kinds of
> clusters, and will not discourage fruitful conversations and projects as
> long as they relate to high availability.
>
> Initial Contributions:
>
> Sun Microsystems will contribute to the community the source code for
> Solaris Cluster, Sun's commercial HA Cluster product group, under the
> name ?Open High Availability Cluster.? This contribution will start at
> the time of community formation with the Sun Cluster Agents source for a
> wide portfolio of applications. A Sun Cluster Agent provides the ?glue?
> to allow an off-the-shelf application to run with high-availability on
> Sun Cluster software.
>
> Nominating Members:
>
> Bonnie Corwin
> Sara Dornsife
> Mike Kupfer
> Liane Praza
>
> Initial Contributors (all from Sun Microsystems):
>
> Nicholas Solter
> Suraj Verma
> Jonathan Mellors
> Prasad Dharmavaram
> Swathi Devulapalli
> Madhan Kumar Balasubramian
> Venkat Chennuru
> Subhadeep Sinha
> Lisa Shepherd
> Thelan Nguyen
> Lingling Chyu
> Sekhar Lakkapragada
> Meenakshi Kaul-Basu
> Thorsten Frueauf
> Neil Garthwaite
> Jatin Jhala
> Tim Read
> Detlef Ulherr
> Bob Bart
> Ashutosh Tripathi
> Hemachandran Namachivayam
>
>
> Initial Facilitator:
>
> Nicholas Solter
>
> Thanks,
> Nick
> _______________________________________________
> ogb-discuss mailing list
> ogb-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/ogb-discuss
--
stephen lau // stevel at sun.com | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
