RE: [PROPOSAL][RFC] CloudStack for the Apache Incubator
Hi Hadrian, yes, we have been discussing this. There are a number of options today that make the system easier to develop against than it might seem. It's possible to have a single node cloud with KVM, where the CloudStack management server and KVM host are the same server. With XenServer or XCP you can work with a two node system. Or you can have a VM for the management server and a physical host for the hypervisor. There is also a XenServer API simulator available, which would allow development with XenServer with just two VMs (one for the management server and one for the XenServer simulator). CloudStack developers have used these environments for most development to date. We have also developed a software simulator. This simulator emulates hypervisor hosts under management through a single process. Although it was originally built for scalability testing, it should be possible to use it for development and functional testing as well. We have been thinking this would be the best way to enable the larger community to easily develop and test against CloudStack long term. This should work today, but there are no good docs on how to set it up, nor do we have much experience with it in this context. This is something we need to do to help the new community members engage (or we need some intrepid community members to try it and document the successful path). We have also discussed donating and/or hosting build and test infrastructure for pending commits to the project. This would be a public system test environment. Our automated test tools can take a cloud description in JSON and implement it, provided the hosts and storage are already provisioned (e.g., via PXE boot). While we have some good building blocks, we need to improve the automated system tests and implement some glue code to provide a process that can be driven from a web UI. If this is what the community needs I think we will be able to provide the hardware. In terms of timing I am more concerned about the test development and glue to make it all work than the hardware acquisition, and I believe this is a few months away. -kevin > -Original Message- > From: Hadrian Zbarcea [mailto:hzbar...@gmail.com] > Sent: Friday, April 06, 2012 6:49 PM > To: general@incubator.apache.org > Subject: Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator > > I find the proposal interesting too. I gave it a lot of though and I am > considering getting involved as well. I have a question however for the > proponents and supporters of the project. > > What makes this project different than (almost) all the other ASF projects is > that it has a high(er) barrier to entry in terms of hardware requirements. The > reality is that such a project has little chances of becoming a viable > competitor in the industry without strong support from companies like Citrix > (and I salute their commitment). Will such resources be made available to the > whole community, how was this envisioned? > > Thanks, > Hadrian > > > > On 04/04/2012 04:22 PM, Mohammad Nour El-Din wrote: > > On Wed, Apr 4, 2012 at 10:20 PM, Alex Karasulu > wrote: > > > >> On Wed, Apr 4, 2012 at 8:55 PM, Matt Hogstrom > wrote: > >> > >>> The proposal looks good. I'm excited that the community is looking > >>> to grow at the ASF. I'm working on similar technology in my day job > >>> at IBM and am interested in getting involved. Happy to mentor if > >>> you need, although, it has quite a large list now as I look at the Wiki. > >>> > >>> > >> The number of mentors should not be an issue. As stated before, in > >> other threads, the number of mentors is unbounded and AOO has 8 as an > example. > >> > >> The perspective podling should not feel that the list is too long - > >> more mentors and interest is a good thing. We have much to do, the > >> project is not small, and it would be nice to see the community > >> gracefully pass thru incubation as fast as posible in accordance with > >> incubator standards. More mentors might help in this regard. > >> > > > > Indeed > > > > > >> > >> -- > >> Best Regards, > >> -- Alex > >> > > > > > > > > -- > Hadrian Zbarcea > Principal Software Architect > Talend, Inc > http://coders.talend.com/ > http://camelbot.blogspot.com/ > > - > 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: [all] Size of releases
Christian Grobmeier wrote on Thu, Mar 29, 2012 at 00:22:19 +0200:
> On Thu, Mar 29, 2012 at 12:06 AM, Daniel Shahaf
> wrote:
> > Jukka Zitting wrote on Wed, Mar 28, 2012 at 22:34:30 +0200:
> >> Hi,
> >>
> >> On Wed, Mar 28, 2012 at 6:19 PM, Christian Grobmeier
> >> wrote:
> >> > I will try to update this document now with the recommendation from
> >> > infra:
> >> > http://incubator.apache.org/guides/releasemanagement.html#release-distribution
> >>
> >> While you're at it, can you please also (or rather instead) update the
> >> ASF-wide documentation at http://www.apache.org/dev/#releases?
> >>
> >> This isn't particularly tied to the Incubator, so the primary place
> >> for the relevant guidance shouldn't IMHO be incubator.apache.org. Most
> >> notably the IPMC shouldn't be responsible for updating this
> >> information in case the related infra policies change.
> >>
> >
> > Yes it's on infra's radar to document the "some releases are large
> > enough to need coordination with us" point. We've been busy so haven't
> > got to it yet
>
> Please let us know if you have found some time, then we can point from
> our release-docs to your document.
http://www.apache.org/dev/release#heads-up
% $svn di
Index: release.mdtext
===
--- release.mdtext (revision 1311120)
+++ release.mdtext (revision 1311121)
@@ -222,6 +222,18 @@
their dist/ dir. To transition just open a Jira ticket and specify: (1) what
mailing list commit mails should go to.
+## Do I need to talk to Infrastructure before distributing a release?
{#heads-up}
+
+Most projects can just distribute a release as described in the previous two
+questions. However, releases that are likely to strain the mirroring and
+download resources **must** be coordinated with infrastructure.
+
+Releases of more than 1GB of artifacts require a heads-up to Infrastructure in
+advance.
+
+Specific exemptions from other dist policies (such as what may or must or must
+not be distributed via the mirrors) also need to be coordinated with
Infrastructure.
+
## How Should Releases Be Announced? ## {#release-announcements}
Please ensure that you wait at least 24 hours after uploading a new release
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.9.0-incubating (RC4)
On 7 April 2012 02:59, Benjamin Hindman wrote: > Please vote on releasing the following candidate as Apache Mesos > (incubating) version 0.9.0. This will be the first incubator release for > Mesos in Apache, but the fifth release candidate. > > Vote thread on mesos-...@incubator.apache.org: > > http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201203.mbox/%3CCAFeOQnW7jk-VcTFpUP-_VonL99JCnggKeNPW%2BGx-Ozdy1U8sjg%40mail.gmail.com%3E > > The candidate for Mesos 0.9.0-incubating release is available at: > > http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz > > The tag to be voted on: > > https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4 The NOTICE file is incomplete; the product name and copyright year(s) are missing. The LICENSE file includes references to several 3rd party items. It looks like glog and utilities.cc and others may require mention in NOTICE. There's no DISCLAIMER file in SVN root. There are several 3rd party libraries in SVN under https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4/third_party/ > The MD5 checksum of the tarball can be found at: > > http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.md5 > > The signature of the tarball can be found at: > > http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.asc > > Mesos' KEYS file, containing the PGP keys used to sign the release: > http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS > > Please vote on releasing this package as Apache Mesos 0.9.0-incubating! > > The vote is open until Tuesday, April 10th at 8 pm (a bit more than 72 > hours since it's over the weekend) and passes if a majority of at least 3 > +1 IPMC votes are cast. > > [ ] +1 Release this package as Apache Mesos 0.9.0-incubating > [ ] -1 Do not release this package because ... > > To learn more about Apache Mesos, please see > http://incubator.apache.org/mesos. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Mesos 0.9.0-incubating (RC4)
Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.9.0. This will be the first incubator release for Mesos in Apache, but the fifth release candidate. Vote thread on mesos-...@incubator.apache.org: http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201203.mbox/%3CCAFeOQnW7jk-VcTFpUP-_VonL99JCnggKeNPW%2BGx-Ozdy1U8sjg%40mail.gmail.com%3E The candidate for Mesos 0.9.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.9.0-incubating-RC4 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.9.0-incubating-RC4/mesos-0.9.0-incubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.9.0-incubating! The vote is open until Tuesday, April 10th at 8 pm (a bit more than 72 hours since it's over the weekend) and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.9.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
I find the proposal interesting too. I gave it a lot of though and I am considering getting involved as well. I have a question however for the proponents and supporters of the project. What makes this project different than (almost) all the other ASF projects is that it has a high(er) barrier to entry in terms of hardware requirements. The reality is that such a project has little chances of becoming a viable competitor in the industry without strong support from companies like Citrix (and I salute their commitment). Will such resources be made available to the whole community, how was this envisioned? Thanks, Hadrian On 04/04/2012 04:22 PM, Mohammad Nour El-Din wrote: On Wed, Apr 4, 2012 at 10:20 PM, Alex Karasulu wrote: On Wed, Apr 4, 2012 at 8:55 PM, Matt Hogstrom wrote: The proposal looks good. I'm excited that the community is looking to grow at the ASF. I'm working on similar technology in my day job at IBM and am interested in getting involved. Happy to mentor if you need, although, it has quite a large list now as I look at the Wiki. The number of mentors should not be an issue. As stated before, in other threads, the number of mentors is unbounded and AOO has 8 as an example. The perspective podling should not feel that the list is too long - more mentors and interest is a good thing. We have much to do, the project is not small, and it would be nice to see the community gracefully pass thru incubation as fast as posible in accordance with incubator standards. More mentors might help in this regard. Indeed -- Best Regards, -- Alex -- Hadrian Zbarcea Principal Software Architect Talend, Inc http://coders.talend.com/ http://camelbot.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
> These touch up changes pretty much complete the proposal and we're ready to kick off a [VOTE] thread. Thoughts? +1 Cheers, Andreas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
On Apr 8, 2012 4:56 AM, "Alex Karasulu" wrote: >... > > > > I believe the proposal is now complete, pending additional feedback. > > These touch up changes pretty much complete the proposal and we're ready to > kick off a [VOTE] thread. Thoughts? +1 Discussion has been mellow. Feedback was tweaks. We're definitely past our 72 hour fence. Roll with it... Cheers, -g
Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator
On Sat, Apr 7, 2012 at 8:33 AM, Kevin Kluge wrote: > Brett, thanks for the comments. I put some responses in line. > > > -Original Message- > > From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett > Porter > > Sent: Friday, April 06, 2012 4:53 PM > > To: general@incubator.apache.org > > Cc: general@incubator.apache.org > > Subject: Re: [PROPOSAL][RFC] CloudStack for the Apache Incubator > > > > Hi Kevin, > > > > I made a couple of minor edits. > > > > A few more suggestions... > > > > I think you could drop the last sentence of the rationale. The ASF > doesn't > > have any strategic goals to cover particular technology area. > > Sure, will remove it. > > > > > Th alignment section looks fine as is, but it's not strictly necessary to > > speculate on other projects you might use. There's no requirement to > > depend on other ASF projects instead of other suitable choices. > This was actually nice to see because it showed just how many ASF projects the software depends on but as you say it's not necessary. > > The addition of the dependency and license tables is informative, but I'd > > leave the actions and remarks for a status page later - as others have > said > > these problems can be resolved in incubation. > > +1 > That's good. The presence of those columns makes the proposal a bit of a > moving target -- either we edit them as we make progress on the > unacceptable dependencies or the document becomes out of date. I will > remove them and start a separate, active document to track progress. > > > > > On that note though - I believe java mail and the server API are > available > > under compatible licenses. > > > > You've mentioned there are original contributors now less involved in the > > code. Are they likely to still be involved in other activities that are > part of the > > decision making of the project? > > Yes, Will and Sheng are both influential. Will does engineering > management at Citrix and so has input on the day-day activities of many of > the initial committers. Sheng provides input on longer term direction for > the project based on his observations across the industry. Both will have > opinions on how the project should be run. > > -kevin > > > > > > Thanks, > > Brett > > > > On 05/04/2012, at 4:03 PM, Kevin Kluge wrote: > > > > > I updated the proposal at > > http://wiki.apache.org/incubator/CloudStackProposal. I have included > the > > embedded source dependencies, binary dependencies, and contributor e- > > mail addresses. There are some open questions in the dependencies (e.g., > > treatment of dependencies that have no discernible license), but my > > impression is that these issues do not need resolution before entering > > incubation. Please correct me if that's wrong. > > > > > > I believe the proposal is now complete, pending additional feedback. > These touch up changes pretty much complete the proposal and we're ready to kick off a [VOTE] thread. Thoughts? -- Best Regards, -- Alex
