The Apache CloudStack Blog
Apache CloudStack Weekly News - 8 April 2013
The Apache CloudStack community has been heads-down for the last week working out the remaining bugs for the 4.1.0 release. Chatter on the dev@ mailing list has been a little muted, comparatively, but there's still plenty of interest in this week's roundup of major discussions and CloudStack community activity.
This week, we look at the outstanding issues for 4.1.0, a discussion about allowing multiple API names for the same API Cmd object, how to deal with tests that expect no database, and how ticket assignment should work.
Outstanding Work for the 4.1.0 Release
4.1.0 is getting close, but we're not quite there yet. Chip Childers sent out a list of outstanding work required for 4.1.0. Several of the issues are already in progress, but Chip also pointed out CLOUDSTACK-1941: Cannot delete users in the default admin account within the UI as unassigned. This is a critical issue that will need to be addressed before an RC or release can be cut.
API Name Alias
Kishan Kavala has raised a discussion about an API name alias. Kishan has a plan to enhance the name parameter "to support comma separated values. This will allow multiple API names for the same API Cmd object." John Burwell recommended using an array rather than a comma separated value, but there's been some discussion as to whether that's the best arrangement for the current code.
So far, the discussion has not come to a resolution. Folks who have an understanding of the impact or wish to comment on the feature should jump into the discussion on dev@.
Database Tests and Hitting Master
While the project works on finalizing 4.1.0, work continues on 4.2.0 and later releases in the master branch. This week there was another breakage in master, and a discussion following about database access during tests. One proposal was to disable the database before running tests, but this has been challenged as being overly complicated for developers who may be running CloudStack on their test machines and find it inconvenient to disable the db when running tests.
Preparing the Board Report
As an Incubating project, Apache CloudStack prepared a board report every three months, which would be reviewed by the IPMC and (if approved) sent up to the board as part of the Apache Incubator report.
Now that Apache CloudStack is a top-level project (TLP), it prepares its own report for the board. Chip Childers started the discussion on the mailing list with a draft of the report.
Noah Slater raised an issue about ticket assignments:
Right now, we have people who are regularly going through JIRA and triaging tickets. This is totally fantastic, and a very valuable activity for the project. (So thank you!) But I also notice that specific individuals are being assigned to the tickets in the process.
This is a form of "cookie licking". The analogy is that if you fancy a cookie, but you're too hungry right now, you take a lick of it so nobody else can touch it. This is an anti-pattern and we should try to avoid it.
As a result, Noah suggested that we change the way that ticket assignments are handled so that people are taking tickets as they get a chance to work on them, rather than taking tickets that they plan to work on.
CloudStack Planet - Posts from the CloudStack Community
- Chip Childers: "Apache CloudStack Graduation News Roundup" Chip rounds up some of the reports on the Apache CloudStack graduation.
- Open Cloud Challenges at the Data Center Expo, Paris, April 10th Open Cloud.
- Cloud Computing at the University of British Columbia (Robson Campus), Vancouver, Canada, April 9th.
- CloudStack Introduction and Basics - The inaugural meeting of the CloudStack NYC User Group will be Wednesday, April 10th in New York City. Sign up on Meetup.com.
- UK/European CloudStack user group meet-up will be April 11th in London.
- Storage in Apache CloudStack being held by the CloudStack SF Bay Area Users Group on April 30, 2013 @ Citrix Conference Center, sign up on the Meetup.com Website.
- CloudStack Bangalore Meetup Sometime in April, date not yet announced. Watch the Meetup page for details.
- Last week: 2 blocker bugs. This week: 2 blocker bugs, only one of which is truly a bug. (The other is a task that must be completed before release.)
- Last week: 6 critical bugs. This week: 6 critical bugs
- Last week: 122 major bugs. This week: 118 major bugs
- Last week: 23 minor bugs. This week: 23 minor bugs
New Committers and PMC Members
No new committers or PMC members were announced this week. To see all current committers and PMC members, see the Who We Are page on the Apache CloudStack website.