Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of uthaiyashankar@gmail.com
 designates 209.85.212.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=oWwLg2ik4cKV/W3ydBMfWv4ckSIDrUG8zpbTXAQpn6Urp7ct0fXFUy3Xt9TCaQur+Q
         iZ+OATfEr2Rp+z28eeiGF6bjbmnp7dzO5wp+NqBIIZNXTLy6pK/H+6MfmrjHsvjWAmTA
         OXvxHxmlv+uc/SbwC4b+t6uiZDauJKVJEq1ZM=
MIME-Version: 1.0
In-Reply-To: <1273174879.7253.99.camel@avon.watzmann.net>
References: <1273174879.7253.99.camel@avon.watzmann.net>
Date: Tue, 11 May 2010 10:42:24 +0530
Message-ID: <AANLkTinysT-8taIBGBNnFzVBA0_cCPTaVC-8gE3yf7El@mail.gmail.com>
Subject: Re: [PROPOSAL] Deltacloud Project
From: Selvaratnam Uthaiyashankar <uthaiyashankar@gmail.com>
To: general@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I would like to contribute. Please add me as an initial committer.
(shankar AT apache DOT org) .

regards,
Shankar

On Fri, May 7, 2010 at 1:11 AM, David Lutterkort <lutter@redhat.com> wrote:
> Hi,
>
> I would like to propose the Deltacloud API[1] for addition to the Apache
> incubator.
>
> I have added the initial proposal to the Wiki[2]; it is also included
> below for convenience.
>
> There are a few additional people that have expressed interest in
> becoming initial committers; I am waiting for their express consent to
> list them as committers, and will add them to the Wiki as I get that.
>
> We are looking forward to any and all feedback and/or questions on the
> proposal. We already have two mentors, but would very much welcome
> additional volunteers to help steer Deltacloud through the incubation
> process.
>
> David
>
> [1] http://deltacloud.org/
> [2] http://wiki.apache.org/incubator/DeltacloudProposal
>
>
> Deltacloud, a cross-cloud web service API
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Abstract
> --------
>
> Deltacloud defines a web service API for interacting with cloud service
> providers and resources in those clouds in a unified manner. In addition,
> it consists of a number of implementations of this API for the most popul=
ar
> clouds.
>
> Proposal
> --------
>
> =A0* Define a REST-based API for managing and manipulating cloud resource=
s
> =A0 =A0in a manner that isolates the API client as much as possible from =
the
> =A0 =A0particulars of specific cloud API's
> =A0* Provide an open API definition for cloud providers for their IaaS
> =A0 =A0clouds and a basis on which PaaS providers can layer their offerin=
g
> =A0* Provide image management and directory capabilities as part of the A=
PI
> =A0* The current implementation allows instance lifecycle management
> =A0 =A0(create, start, stop, destroy, reboot), and querying of related
> =A0 =A0resources like available images, instance sizes, and allowed insta=
nce
> =A0 =A0actions for a number of public and private clouds
> =A0* Currently supported are Amazon EC2, Eucalyptus, Rackspace, RimuHosti=
ng,
> =A0 =A0GoGrid, OpenNebula, and RHEV-M
> =A0* Future enhancements should broaden the scope of the API to include
> =A0 =A0networking, firewalling, authentication, accounting, and image
> =A0 =A0management
>
> Background
> ----------
>
> An important issue for cloud users is that of avoiding lock-in to a
> specific cloud. By providing a cross-cloud API for
> infrastructure-as-a-service (IaaS) clouds, Deltacloud addresses this
> concern and strives to provide the best possible API for writing
> cloud-management applications that can target multiple clouds.
>
> There are also no efforts currently to define a truly open-source cloud
> API, one for which there is a proper upstream, independent of any specifi=
c
> cloud provider. Deltacloud API strives to create a community around
> building an open-source cloud API in a manner that fully allows for
> tried-and-true open source mechanisms such as user-driven innovation.
>
> By providing a web-service API, Deltacloud is language agnostic, and one =
of
> its subordinated goals is to provide a practical vocabulary for talking
> about IaaS cloud resources and operations on them.
>
> Rationale
> ---------
>
> IaaS clouds provide numerous advantages to their users, for example,
> making provisioning new servers more agile. If users directly use the
> 'native' cloud API's, they risk locking themselves in to the API of a
> specific cloud provider.
>
> There is therefore a strong need for an API that can be used across a wid=
e
> range of public and private clouds, and that can serve as the basis for
> developing cloud management applications; in contrast to several existing
> language-specific efforts in this direction, Deltacloud is conceived as a
> web service.
>
> This will allow the project to attract a broad community of users of the
> API and cloud providers interested in offering a truly open-source API,
> with a proper upstream community.
>
> We strongly believe that the best way to drive such an API effort is by
> developing the API and open-source implementations of the API side-by-sid=
e.
>
> Initial Goals
> -------------
>
> Deltacloud is an existing open source project; initially started by Red
> Hat, it has attracted a number of outside contributors. We look at moving
> this project to the ASF as the next step to broaden the community, and pu=
t
> the project on solid footing since the ASF governance model is well suite=
d
> for the Deltacloud project goals. The ASF is a great location for
> Deltacloud to build a community and will benefit from ASL licensing.
>
> Current Status
> --------------
>
> Deltacloud API is licensed under the LGPL:
>
> =A0* Deltacloud Website (http://deltacloud.org) There are two projects ho=
sted there: the API under consideration here and the Aggregator (not part o=
f this proposal, though also open source)
> =A0* Deltacloud git repository (http://git.fedorahosted.org/git/?p=3Ddelt=
acloud/core.git;a=3Dsummary)
> =A0* Deltacloud mailing lists
> =A0 =A0- users (https://fedorahosted.org/mailman/listinfo/deltacloud-user=
s)
> =A0 =A0- developers (https://fedorahosted.org/mailman/listinfo/deltacloud=
-devel)
>
> Transition to Apache
> --------------------
>
> All current contributors have consented to relicensing the Deltacloud API
> code under the Apache Software License 2.0; the code will be relicensed t=
o
> ASL 2.0 on acceptance into the Incubator.
>
> Meritocracy
> -----------
>
> Deltacloud API accepts patches from anybody, based solely on technical
> merit, and will give commit rights to contributors with a proven technica=
l
> track record. Communication is done through an IRC channel on freenode an=
d
> the two mailing lists above. The mailing lists will be migrated to the AS=
F
> project list on acceptance into the Incubator.
>
> Community
> ---------
>
> Because it was started by Red Hat, the majority of the initial contributi=
on
> is from Red Hat employees, though we have received and accepted a number =
of
> patches from outside sources, particularly, from a number of cloud
> providers. We expect that the project will greatly increase in contributi=
on
> base, and this is one aspect the project will monitor in becoming ready f=
or
> graduation.
>
> API Developers
> --------------
>
> =A0* Bob McWhirter (initial developer)
> =A0* David Lutterkort (current maintainer)
> =A0* Michal Fojtik
> =A0* Ivan Meredith
> =A0* Daniel Molina Aranda
>
> Alignment
> ---------
>
> Currently, there are no other Apache projects concerned with building a
> cross-cloud API as a web service. =A0However, we feel it will be a strong
> complement to the set of Apache projects, and provide any other Apache
> project an API for interacting with any cloud provider.
>
> Known Risks
> -----------
>
> =A0- Orphaned Products
>
> =A0 =A0Deltacloud API is actively used by other Red Hat projects. I have
> =A0 =A0received interest in Deltacloud API both from some cloud providers=
 and
> =A0 =A0other organizations in joining the project. We feel that it is
> =A0 =A0importatant to put formal governance in place both for the project=
 and
> =A0 =A0the contributors as the project expands. We feel the ASF is the be=
st
> =A0 =A0location for this.
>
> =A0- Inexperience with Open Source
>
> =A0 =A0I have been involved with Open Source Software for over a decade; =
I
> =A0 =A0have actively contributed to puppet (http://www.puppetlabs.com/), =
where
> =A0 =A0I was one of the earliest contributors, libvirt (http://libvirt.or=
g/),
> =A0 =A0virt-manager (http://virt-manager.et.redhat.com/), and a number of
> =A0 =A0other projects. I started and maintain two projects, Augeas
> =A0 =A0(http://augeas.net/) and netcf (https://fedorahosted.org/netcf/)
> =A0 =A0related to systems management.
>
> =A0 - Homogenous Developers
>
> =A0 While much of the initial code base has been written by Red Hat, seve=
ral
> =A0 of the backend drivers and some important aspects of the API design h=
ave
> =A0 been heavily influenced by outside contributors.
>
> =A0 - Reliance on Salaried Developers
>
> =A0 Currently the project has mostly salaried developers. Expanding the
> =A0 diversity of the project's developers is one of the areas we will
> =A0 actively work on in the Incubator, and will be a crucial factor in
> =A0 making Deltacloud a successful project.
>
> =A0 - Relationships with Other Apache Products
>
> =A0 Currently there are not really any stong relationships with other Apa=
che
> =A0 projects. There is a certain amount of overlap with libcloud
> =A0 (http://incubator.apache.org/libcloud/), though the projects differ i=
n
> =A0 scope and goals. At its most basic, libcloud is a Python in-process A=
PI,
> =A0 whereas Deltacloud is a web service written in Ruby.
>
> =A0 - An Excessive Fascination with the Apache Brand
>
> =A0 We seek to build a lasting community around Deltacloud API; the most
> =A0 important reason for proposing this project for the incubator is to
> =A0 clarify project governance to other parties, to allow them more easil=
y
> =A0 to join and contribute to the project, and for the project to be mana=
ged
> =A0 and governed independently.
>
> Documentation
> -------------
>
> =A0* API definition (http://deltacloud.org/api.html)
> =A0* Supported drivers (http://deltacloud.org/drivers.html)
> =A0* Ruby Client (http://deltacloud.org/client-ruby.html)
> =A0* Writing new drivers (http://deltacloud.org/framework.html)
>
> Documentation is maintained in a separate, public git repository
> (http://git.fedorahosted.org/git/?p=3Ddeltacloud/docs.git;a=3Dshortlog;h=
=3Drefs/heads/next)
>
> Initial Source
> --------------
>
> All sources can be found in the git repositories mentioned above.
>
> External Dependencies
> ---------------------
>
> Deltacloud is written in Ruby; there are a number of Ruby libraries that
> the code depends on, most importantly:
>
> =A0* Ruby
> =A0* Sinatra (http://www.sinatrarb.com/)
> =A0* HAML (http://haml-lang.com/)
> =A0* thin (http://code.macournoyer.com/thin/)
>
> A complete list of dependencies can be found in the deltacloud-core.gemsp=
ec
> in the core repository. All dependencies are licensed under either the Ru=
by
> License or the MIT License.
>
> Cryptography
> ------------
>
> Uses standard Ruby APIs for SSL/HTTPS
>
> Required Resources
> ------------------
>
> =A0* Mailing lists
>
> =A0 =A0* deltacloud-devel
> =A0 =A0* deltacloud-commits
> =A0 =A0* deltacloud-private
>
> =A0* Subversion
>
> =A0 =A0* https://svn.apache.org/repos/asf/incubator/deltacloud
>
> =A0* Issue Tracking
>
> =A0 =A0* Bugzilla (deltacloud)
>
> Initial Committers
> ------------------
>
> =A0* David Lutterkort <lutter@redhat.com>
> =A0* Michal Fojtik <mfojtik@redhat.com>
> =A0* Marios Andreou <mandreou@redhat.com>
> =A0* Andrew N Cadel <cadel_a@jpmorgan.com>
>
> Sponsors
> --------
>
> =A0Champion
> =A0 =A0Carl Trieloff =A0 <cctrieloff@redhat.com>
>
> =A0Nominated Mentors
> =A0 =A0Carl Trieloff =A0 <cctrieloff@redhat.com>
> =A0 =A0Craig L Russell <Craig.Russell@sun.com>
>
> =A0Sponsoring Entity
> =A0 =A0Incubator PMC
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


--=20
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org