Skip to main content

Apache CloudStack Weekly News - 24 July 2013

Welcome back to another exciting issue of the Apache CloudStack Weekly News. This week, we take a look at the progress towards 4.2.0, major discussions on the Apache CloudStack mailing lists, and much more.

Major Discussions

4.2 Release Coding Starting to Wrap-up

With a less than a week left before code freeze for the 4.2 release on 7/29, there is a lot of work still to be done and a lot of bugs that need to be worked out. With this major release many new and existing features need the blocker and critical bugs cleared out as soon as possible. There's been great teamwork in the community. Animesh Chaturvedi points out the work that still needs to be done:

...For the days remaining to code freeze, lets prioritize fixing blockers and critical over majors. As from last week in order to clear up our backlog I request you to help out on aggressively fixing the issues. The unassigned issue list is available at When you fix a bug in 4.2 please make sure it is also fixed in master.

The outstanding resolved issues now stand at 492 with 250 blockers and critical still to be verified. As with fixing issues now we need to focus on blockers and critical first.

The detailed bug status is captured below.

BugsThis Week    Last Week    
  Blocker Critical Major Total Blocker Critical Major Total
Incoming 29 48 64 144 31 40 46 120
Outgoing 37 68 51 159 33 38 65 140
Open Unassigned 6 13 149 208 6 46 120 226
Open Total 24 68 239 392 30 84 213 388

The status for features or improvement is depicted in table below

New Features / Improvements Today Last Week
Closed 13 12
Resolved 60 59
In Progress 9 10
Reopened 2 2
Ready To Review 0 0
Open 18 19
Total 102 102
4.1.1 Release Candidate Vote is Now Open

4.1.1 patch release has been in the works for a while now and has quite a few fixes in it since the release of 4.1.0 on June 5th. The release candidate was cut on Monday and the Vote is now open until Saturday. Please provide your testing results and vote.

Bylaws change for Committer and PMC Member Nomination

To make the process of allowing for nomination of Committers and PMC members into the CloudStack community, Chip Childers has started a discussion on changing the bylaws to change the voting process of the PMC Group from a lazy consensus to a majority process. Join in the discussion.

As it stands now, we currently use a "Lazy Consensus" model (yes Noah, I know we didn't define that term correctly as of now, but I think that's a different discussion). We currently have that term defined as:

Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no binding -1 votes.

I'd like to propose that we change the PMC and Committer voting rule to use the Lazy 2/3 Majority approach defined as:

Lazy 2/3 majority votes requires at least 3 binding votes and twice as many binding +1 votes as binding -1 votes.

Possibly Ending the IRC Chats

After low attendance in weekly IRC chats, Joe Brockmeier has raised the question about the need for regular IRC chats. IRC chats have been in place for a long time with the community. Make sure to stay involved with the discussion and let your voice be heard.

How Your Coding May Affect Others

Brian Federle noticed when working on the GUI code in Master recently that the tab style had changed. This started a large rebase and merge of the UI code of other developers in the community. While the original commit had the best intention and was committed correctly for 4.3, the review and commit were done within a short time frame and didn't give the community much time to see it and understand the impact. Make sure to communicate and be aware of what impacts your code might have on others working on the same objects as you.

Chip Childers pointed out:

...that sweeping changes like this (or architectural changes as well) are best done early in a release cycle. The challenge we've run into here is that while 4.2 work is proceeding, master is open for 4.3 changes (and there is a preference that if something big is going to come in, nows the time to do it).

New Components in JIRA

To help clarify better on what a bug is all about, and to get it to the right visibility on it, Prasanna Santhanam and Animesh Chaturvedi have added several new component fields in JIRA to help with bug distinction. The new components:

  • Infra - Infrastructure managed by the project - CloudStack - (jenkins, builds, repos, mirrors)
  • SystemVM - SystemVM appliances, images, scripts, ssvm, cpvm
  • Virtual Router - Anything related to the Virtual Router appliance
  • XCP - Xen Cloud Platform
  • UCS - Cisco UCS System
  • Upgrade - Upgrade scripts, process, database

CloudStack Planet

Do You Have One of the Coolest CloudStack Clouds?

Gregg Watkins is doing a video on the Coolest Clouds and is looking for participants. Gregg has already spent most of the summer working with the project putting together videos on CloudStack, the CloudStack Collaboration Conference and is now looking to show case some of the best clouds in the world ran on Apache CloudStack. If you would like to participate please reach out to Gregg on the Dev or User lists.

The last video I plan on making this summer is a short video featuring some
of the coolest clouds and I am hoping you all will help me since we are all
so spread out.

Here is what I am needing to make this project a success: A webcam
interview of you (questions below) and screen casts/capture of your cloud
in action.

Because my fellowship ends August 9th I will need this information by no
later than the 29th of July.

While I appreciate how busy all of you are, I am hoping you can carve a few
moments out of a day this week and complete the questions and capture some
of your cloud. If you need any assistance in either capturing video
interviews or screens please let me know and I can help you.

This project is a great way to get your project some more visibility and I
thank you in advance for any help you can provide. Please let me know if
you have any questions or concerns.

Apache Whirr and CloudStack for Big Data in the Clouds

Sebastien Goasguen has a tutorial on his blog about using Apache Whirr with CloudStack. "In this tutorial we introduce Apache Whirr, an application that can be used to define, provision and configure big data solutions on CloudStack based clouds. Whirr automatically starts instances in the cloud and boostrapps hadoop on them. It can also add packages such as Hive, Hbase and Yarn for map-reduce jobs."


New Committers and PMC Members

No new committers or PMC members have been announced in the last newsletter period.