Skip to main content

Apache CloudStack Weekly News - 18 February 2013

Another busy week on -dev. This week, discussions on whether to graduate to a TLP, the whens and hows of merging, database changes for 4.1 and master, and documentation.

Also worth noting, we now have a marketing mailing list. To sign up and participate in promoting Apache CloudStack, please subscribe to the mailing list ( and help out!

Major Discussions and Issues

Some of the major discussions and issues that have taken place on cloudstack-dev and cloudstack-users in the past week. This is by no means exhaustive, if you need to be up-to-date on all development issues in the project, you'll definitely want to be subscribed to the mailing lists!

QA Scrum Meeting Minutes

The QA Scrum meeting minutes for 12 February 2013 sent to the mailing list.

IRC Meeting Minutes

Summary of the weekly IRC Meeting for 13 February 2013.

Note that last week's meeting went in reverse alpha-order, but it was largely agreed during the meeting that we should have an agenda for the meeting. Please submit agenda items by Wednesday at 16:00 UTC.

Graduation to a Top-Level Project (TLP)?

Is Apache CloudStack ready to leave the incubator? Chip Childers raised the discussion on the -dev list on February 13th.

My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences.

Marcus Sorensen agreed that there are rough edges but, "the incubation process itself may not teach us anything further about these things, and they're just things we need to iron out over time."

David Nalley wrote:

I don't see us actively receiving any benefit from continuing in incubation. We are far from perfect, but the project seems to be policing itself. So I am not seeing a huge incentive to staying.

There are also some downsides to remaining in incubation. First there's the label 'incubation' that follows almost everything we do, and is potentially off-putting to potential community members. Second as a community there are a number of things we can't do for ourselves, and thus have to ask permission or for help - this includes votes on releases, creating new user accounts, etc. I think of this as the overhead of being in the incubator.

Discussion on Database Changes and Merges

Rohit Yadav put out the word that there were database changes ahead for the 4.1 branch and master.

Rohit also brought up a merge for database schemas for 4.1.0 and pointed to the current differences in the database schema for 4.1 over 4.0.

Documentation for 4.1

Sebastien Goasguen started a thread on documentation for 4.1, which is a must-read for anyone working on docs.

How to Treat Broken Builds

David Nalley expressed some frustration with the community's reaction to broken builds.

In general it seems we don't care, and this makes it more difficult to fix problems. Jenkins reporting a broken build (be it a broken run of RAT, failure to compile, failure of a unit test, building docs, etc.) should be our Andon cord. We should all stop commits that aren't fixing the broken build. To illustrate why this is a problem, RAT failures started occurring recently, this keeps us from testing whether CloudStack builds, because each build is conditioned on the successful completion of the test before it. That in turn keeps apidocs from building, which keeps marvin from building, which keeps documentation from building. We essentially are blind until it gets fixed.

Marcus Sorensen asked if there was a Jenkins report committers could subscribe to in order to avoid the problem. David replied, "Yes there are - the commits mailing list receives the notifications from both jenkins.cs.o and builds.a.o. ... You can subscribe by sending an email to"

Wait Before you Merge!

How long should you wait until you merge into master or a branch? Chip Childers brought this up in response to a merge that was announced on February 12th and then committed on February 13th. This discussion raised the fact that there's not a formal merge process documented. Chip volunteered to take a crack at the document and asked for help "in getting it in shape to reflect consensus on the topic."

Android and iOS CloudStack Clients

Abhinandan Prateek asked about the utility of a Android and/or iOS client for CloudStack. David pointed out that an Android client called Cumulus exists that is "pretty useful as an end-user, but less so as an admin."

Pranav Saxena replied that there was already some work underway off-list on a client using PhoneGap, and it might be possible to collaborate. (Ed. Note: This is why you should bring ideas to the list sooner rather than later, so there's not a wasted effort when two or more community members have the same idea and try to implement it separately.)

New Dependency on OWASP ESAPI for Java

Likitha Shetty announced a new dependency on the OWASP ESAPI for Java in master.

Upcoming Events


Bug count for 4.1.0 hasn't significantly decreased since last week, though major bugs have dropped slightly while there's been an increase of blocker and critical bugs.

Of the remaining bugs for 4.1.0, 95 are currently unassigned. Doc bugs are by far the largest component needing help, with 64 bugs remaining.

New Committers and PPMC Members

David Nalley announced that Likitha Shetty has been asked to become a committer, and Likitha has accepted. Please join us in congratulating Likitha!

Contributing to the Apache CloudStack Weekly News

If you have an event, discussion, or other item to contribute to the Weekly News, you can add it directly to the wiki by editing the issue you want your item to appear in. (The next week's issue is created before the current issue is published - so at any time there should be at least one issue ready to edit.) Alternatively, you can send to the cloudstack-dev mailing list with a subject including News: description of topic or email the newsletter editor directly (jzb at, again with the subject News: description of topic. Please include a link to the discussion in the mailing list archive or Web page with details of the event, etc.