Re: [libcloud] [VOTE] Release Apache Libcloud 0.3.1

2010-05-10 Thread Jeremy Orem 
+1

-Jeremy

On Thu, May 6, 2010 at 4:09 PM, Paul Querna  wrote:
> Test tarballs for Apache Libcloud 0.3.1 are available at:
>  
>
> Please test and place your votes please;
>
>  +/- 1
>  [  ]  Release Apache Libcloud 0.3.1
>
> Vote closes on Monday May 10, 2010 at 1pm PST.
>
> This release fixes several issues related to the license blocks,
> NOTICE file, and test cases that were noticed in the scrubbed 0.3.0
> release.
>
> It is based upon this tag:
> 
>
> Thanks,
>
> Paul
>

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

Re: [VOTE] Accept Whirr for Incubation

2010-05-10 Thread Donald Woods 
> [X] +1 Accept Whirr for incubation


-Donald


On 5/5/10 2:06 PM, Tom White wrote:
> We've added three mentors since starting the proposal thread, so I
> would like to start the vote to accept Whirr into the Apache
> Incubator.
> 
> The proposal is included below and is also at:
> http://wiki.apache.org/incubator/WhirrProposal
> 
> Please cast your votes:
> 
> [ ] +1 Accept Whirr for incubation
> [ ] +0 Don't care
> [ ] -1 Reject for the following reason:
> 
> Thanks,
> 
> Tom
> 
> = Whirr, a library of cloud services =
> 
> == Abstract ==
> Whirr will be a set of libraries for running cloud services.
> 
> == Proposal ==
> Whirr will provide code for running a variety of software services on
> cloud infrastructure. It will provide bindings in several languages
> (e.g. Python and Java) for popular cloud providers to make it easy to
> start and stop services like Hadoop clusters. The project will not be
> limited to a particular set of services, rather it will be expected
> that a range of services are developed, as determined by the project
> contributors. Possible services include Hadoop, HBase, !ZooKeeper,
> Cassandra.
> 
> == Background ==
> The ability to run services on cloud providers is very useful,
> particularly for proofs of concept, testing, and also ad hoc
> production work. Bringing up clusters in the cloud is non-trivial,
> since careful choreography is required. (Designing an interface that
> is convenient as well as secure is also a challenge in a cloud
> context.)  Making services that runs on a variety of cloud providers
> is harder, even with the availability of libraries like libcloud and
> jclouds, since each platform's quirks and extra features must be
> considered (and either worked around, or possibly taken advantage of,
> as appropriate) . Whirr will facilitate sharing of best practices,
> both for a particular service (such as Hadoop configuration on a
> particular provider), and for common cloud operations (such as
> installation of dependencies across cloud providers). It will provide
> a space to share good configurations and will encode service-specific
> knowledge.
> 
> == Rationale ==
> There are already scripts in the Hadoop project that allow users to
> run Hadoop clusters on Amazon EC2 and other cloud providers. While
> users have found these scripts useful, their current home as a Hadoop
> Common contrib project has the following limitations:
>  * Tying the scripts' release cycle to Hadoop's means that it is
> difficult to distribute updates to the scripts which are changing fast
> (new features and bugfixes).
>  * The scripts support multiple versions of Hadoop, so it makes more
> sense to distribute them separately from Hadoop itself.
>  * They are general: people want to contribute code for non-Hadoop
> services like Cassandra (for example:
> http://github.com/johanoskarsson/cassandra-ec2).
>  * Having a uniform approach to running services in the cloud, hosted
> in one project, makes launching sets of complementary services easier
> for the user. Today, the scripts and libraries hosted within each
> project (e.g. in Hadoop, HBase, Cassandra) have slightly different
> conventions and semantics, and are likely to diverge over time.
> Building a community around cloud infrastructure services will help
> enforce a common approach to running services in the cloud.
> 
> == Initial Goals ==
>  * Provide a new home for the existing Hadoop cloud scripts.
>  * Add more services (e.g. HBase)
>  * Develop Java libraries for Hadoop clusters
>  * Add new cloud providers by taking advantage of libcloud and jclouds.
>  * (Future) Run on own hardware, so users can take advantage of the
> same interface to control services running locally or in the cloud.
> 
> == Current Status ==
> === Meritocracy ===
> The Hadoop scripts were originally created by Tom White, and have had
> a substantial number of contributions from members of the Hadoop
> community. By becoming its own project, significant contributors to
> Whirr would become committers, and allow the project to grow.
> 
> === Community ===
> The community interested in cloud service infrastructure is currently
> spread across many smaller projects, and one of the main goals of this
> project is to build a vibrant community to share best practices and
> build common infrastructure. For example, this project would provide a
> home to facilitate collaboration between the groups of Hadoop and
> HBase developers who are building cloud services.
> 
> === Core developers ===
> Tom White wrote most of the original code and is familiar with open
> source and Apache-style development, being a Hadoop committer and an
> ASF member. There have been a number of contributors who have provided
> patches to these scripts over time. Andrew Purtell who created the
> HBase cloud scripts is a HBase committer. Johan Oskarsson (Hadoop and
> Cassandra committer) ported the scripts to Cassandra.
> 
> === Alignment ===
> Whirr complements libcloud, current

Re: [PROPOSAL] Deltacloud Project

2010-05-10 Thread David Lutterkort 
On Sat, 2010-05-08 at 11:16 +0530, Sanjiva Weerawarana wrote:
> David, +1 for this project. We've been doing something similar in WSO2
> (called Ozone) and are happy to jump to this. Have you looked at OpenNebula
> (http://opennebula.org/)

Yes, they actually wrote a Deltacloud driver, so you can use Deltacloud
to talk to your ON instance. But having more people with an interest in
ON help out will definitely be good.

>  - we were heading towards using that (and adding
> some Web service APIs etc.). Looks like they decided to form a business a
> few days ago: http://opennebula.ulitzer.com/node/1382814.

Interesting, I hadn't seen that.

David



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

[VOTE] Approval to release Apache Aries (Incubating) version 0.1-incubating

2010-05-10 Thread Jeremy Hughes 
The Aries community has voted on its first release. From the Aries home page:

"The Aries project is delivering a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes."

Aries is a multi-module project. The vote thread on aries-dev for RC5:

http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201005.mbox/%3cl2wadbf02b11005050801hdb720bfse0dd3f748f81a...@mail.gmail.com%3e

concluded with 14 votes, all of them +1, four of which were binding
Incubator PMC votes from Jarek Gawor, Kevan Miller, Guillaume Nodet &
Davanum Srinivas.

The following Aries top level modules are staged and tagged in
https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision
941288.

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-009/

parent
eba-maven-plugin
testsupport
util
blueprint
jndi
transaction
web
jmx

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-004/

jpa
samples

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-010/

application

The RAT and IANAL build checks passed.

The KEYS file located here:

https://svn.apache.org/repos/asf/incubator/aries/KEYS

contains the code signing key for myself, Jeremy Hughes, the release
manager for this release.

We already have 4 binding +1 IPMC votes on the aries-dev list, and I'm
opening up this thread for 72 hours for any further feedback on the
staged artifacts for release.

Thank you,
Jeremy

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

Re: [PROPOSAL] Deltacloud Project - next steps

2010-05-10 Thread David Lutterkort 
On Thu, 2010-05-06 at 12:41 -0700, David Lutterkort wrote:
> 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.

Thanks to everybody on this thread for the very positive reception of
Deltacloud. For next steps, I'd like to leave the discussion open until
Wednesday 5/12, 5pm PDT and start the formal vote at that time on a
separate thread.

David



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

Re: [VOTE] Approval to release Apache Aries (Incubating) version 0.1-incubating

2010-05-10 Thread Jean-Baptiste Onofré 

+1

I made a quick review on blueprint, jndi and jta and it seems very good 
for me (deployed on karaf).


Regards
JB

On 05/10/2010 08:31 PM, Jeremy Hughes wrote:

The Aries community has voted on its first release. From the Aries home page:

"The Aries project is delivering a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes."

Aries is a multi-module project. The vote thread on aries-dev for RC5:

http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201005.mbox/%3cl2wadbf02b11005050801hdb720bfse0dd3f748f81a...@mail.gmail.com%3e

concluded with 14 votes, all of them +1, four of which were binding
Incubator PMC votes from Jarek Gawor, Kevan Miller, Guillaume Nodet&
Davanum Srinivas.

The following Aries top level modules are staged and tagged in
https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision
941288.

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-009/

parent
eba-maven-plugin
testsupport
util
blueprint
jndi
transaction
web
jmx

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-004/

jpa
samples

Modules staged at

https://repository.apache.org/content/repositories/orgapachearies-010/

application

The RAT and IANAL build checks passed.

The KEYS file located here:

https://svn.apache.org/repos/asf/incubator/aries/KEYS

contains the code signing key for myself, Jeremy Hughes, the release
manager for this release.

We already have 4 binding +1 IPMC votes on the aries-dev list, and I'm
opening up this thread for 72 hours for any further feedback on the
staged artifacts for release.

Thank you,
Jeremy

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



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

Re: [VOTE] Release Apache Libcloud 0.3.1

2010-05-10 Thread Paul Querna 
Vote has ended:
ipmc binding +1 from: ant, matt hogstorm, pquerna, gavin
other +1s from: oremj, polvi, cicero, tdavis, eric woods,
non-binding -1 from sebb

The vote passes. Apache Libcloud 0.3.1 is released. I'm pushing it out
to the dist website now, and will post the announcement email in about
a day once the mirrors sync.

Thanks Everyone,

Paul


On Thu, May 6, 2010 at 4:09 PM, Paul Querna  wrote:
> Test tarballs for Apache Libcloud 0.3.1 are available at:
>  
>
> Please test and place your votes please;
>
>  +/- 1
>  [  ]  Release Apache Libcloud 0.3.1
>
> Vote closes on Monday May 10, 2010 at 1pm PST.
>
> This release fixes several issues related to the license blocks,
> NOTICE file, and test cases that were noticed in the scrubbed 0.3.0
> release.
>
> It is based upon this tag:
> 
>
> Thanks,
>
> Paul
>

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

Re: [PROPOSAL] Deltacloud Project

2010-05-10 Thread Chintana Wilamuna 
On Fri, May 7, 2010 at 1:11 AM, David Lutterkort  wrote:

[snip]

As Sanjiva mentioned we've been involved with a similar kind of effort
as well. May be we can consolidate our efforts. I would also like to
contribute to this project.

Bye,

-Chintana

-- 
blog: http://engwar.com/
photos: http://flickr.com/photos/chintana
linkedin: http://www.linkedin.com/in/engwar

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

Re: [PROPOSAL] Deltacloud Project

2010-05-10 Thread Selvaratnam Uthaiyashankar 
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  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
> =
>
> 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 popular
> clouds.
>
> Proposal
> 
>
>  * Define a REST-based API for managing and manipulating cloud resources
>    in a manner that isolates the API client as much as possible from the
>    particulars of specific cloud API's
>  * Provide an open API definition for cloud providers for their IaaS
>    clouds and a basis on which PaaS providers can layer their offering
>  * Provide image management and directory capabilities as part of the API
>  * The current implementation allows instance lifecycle management
>    (create, start, stop, destroy, reboot), and querying of related
>    resources like available images, instance sizes, and allowed instance
>    actions for a number of public and private clouds
>  * Currently supported are Amazon EC2, Eucalyptus, Rackspace, RimuHosting,
>    GoGrid, OpenNebula, and RHEV-M
>  * Future enhancements should broaden the scope of the API to include
>    networking, firewalling, authentication, accounting, and image
>    management
>
> 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 specific
> 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 wide
> 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-side.
>
> 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 put
> the project on solid footing since the ASF governance model is well suited
> 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:
>
>  * Deltacloud Website (http://deltacloud.org) There are two projects hosted 
> there: the API under consideration here and the Aggregator (not part of this 
> proposal, though also open source)
>  * Deltacloud git repository 
> (http://git.fedorahosted.org/git/?p=deltacloud/core.git;a=summary)
>  * Deltacloud mailing lists
>    - use

Re: [VOTE] Approval to release Apache Aries (Incubating) version 0.1-incubating

2010-05-10 Thread ant elder 
On Mon, May 10, 2010 at 7:31 PM, Jeremy Hughes  wrote:
> The Aries community has voted on its first release. From the Aries home page:
>
> "The Aries project is delivering a set of pluggable Java components
> enabling an enterprise OSGi application programming model. This
> includes implementations and extensions of application-focused
> specifications defined by the OSGi Alliance Enterprise Expert Group
> (EEG) and an assembly format for multi-bundle applications, for
> deployment to a variety of OSGi based runtimes."
>
> Aries is a multi-module project. The vote thread on aries-dev for RC5:
>
> http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201005.mbox/%3cl2wadbf02b11005050801hdb720bfse0dd3f748f81a...@mail.gmail.com%3e
>
> concluded with 14 votes, all of them +1, four of which were binding
> Incubator PMC votes from Jarek Gawor, Kevan Miller, Guillaume Nodet &
> Davanum Srinivas.
>
> The following Aries top level modules are staged and tagged in
> https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision
> 941288.
>
> Modules staged at
>
> https://repository.apache.org/content/repositories/orgapachearies-009/
>
> parent
> eba-maven-plugin
> testsupport
> util
> blueprint
> jndi
> transaction
> web
> jmx
>
> Modules staged at
>
> https://repository.apache.org/content/repositories/orgapachearies-004/
>
> jpa
> samples
>
> Modules staged at
>
> https://repository.apache.org/content/repositories/orgapachearies-010/
>
> application
>
> The RAT and IANAL build checks passed.
>
> The KEYS file located here:
>
> https://svn.apache.org/repos/asf/incubator/aries/KEYS
>
> contains the code signing key for myself, Jeremy Hughes, the release
> manager for this release.
>
> We already have 4 binding +1 IPMC votes on the aries-dev list, and I'm
> opening up this thread for 72 hours for any further feedback on the
> staged artifacts for release.
>
> Thank you,
> Jeremy
>

Its a slightly unusual release structure so apologies if I'm missing
it but where is the source release? If i'm not missing some other link
then something may have gone wrong in the release build,  as an
example, in the folder:

https://repository.apache.org/content/repositories/orgapachearies-009/org/apache/aries/blueprint/org.apache.aries.blueprint/0.1-incubating/

the source jar org.apache.aries.blueprint-0.1-incubating-sources.jar
is mostly empty and doesn't contain the source of
org.apache.aries.blueprint-0.1-incubating.jar.

   ...ant

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