This time around, we have two release VOTEs in progress, which means that 4.1.0 is just about out the door. The CloudStack Collaboration Conference 2013 has been announced for June 23rd through 25th. You'll also want to check in on the discussions about the length of the release cycle, Chip Childers and David Nalley appearing on FLOSS Weekly, and much more.
A lot has happened since the last issue of the CloudStack Weekly News, and not just because the community's been busy – we missed getting last week's issue out. Sorry about that! If you'd like to see consistent weekly delivery, check the end of the newsletter to see how you can help.
In this section, we summarize some of the more interesting discussions taking place in the CloudStack community. While we try to pull out the discussions that are "don't miss" discussions to anyone who's involved in using or contributing to CloudStack, it's a really good idea to make sure you're subscribed to the mailing lists and follow along.
Animesh Chaturvedi started a discussion last week about the release schedule for 4.2.0, trying to nail down the specific dates for feature freeze, docs freeze, etc. That was accompanied by a question of whether we should consider a six-month cycle. Ultimately, no resolution was reached on the schedule.
Animesh has started a new thread to discuss the release cycle.
David has started a conversation on dev@ about the ease, or lack thereof, of installing CloudStack. David says, "what I want to do is get rid of sections 2-4 of the quick install guide, and replace it with - 'run this one or two lines worth of commands' (http://s.apache.org/runbook)." David describes what he'd like to see:
The all-in-one installation process I'd like to see:
Install your host OS Install an meta-RPM/Deb that either (installs everything, or alternatively configures a repo - or just installs the repo and the stuff I need to install with) Run a command that activates one of these config tools - configures the machine, installs the packages I need, and gets me to the point where I'm ready to login and go through the beautiful new user gui setup stuff.
No further comments on this so far.
Min Chin has proposed a storage backup object store plugin framework that would "allow CloudStack to systematically manage and configure various types of backup data stores from different vendors, like NFS, S3, Swift, etc." Specifically, Min says:
With this new plugin framework, we would like to achieve following functionalities:
1. Support different object store providers in a uniform and pluggable fashion.
2. Enable region wide object backup using S3-like object store.
3. Provide pluggable data motion strategies to handle data transfer from one data store to another data store.
4. Provide a scalable cache storage framework while moving data between primary storage and backup storage for certain hypervisor needs.
5. Support flexible combinations of primary storage, secondary storage and hypervisors, such as (NFS, NFS, Xen), (NF3, S3, Vmware), (ISCSI, Swift, KVM), ..., etc.
The FS is on the wiki, and Min says in a follow-up that there's a plan to "provide a sample plugin implementation" for the work.
With regards to compatibility concerns, Edison Su responds that existing APIs "can still be wired to new code" so that they continue to work, but "we can mark them as deprecated in the API document." Edison also notes that it can co-exist with the existing deployments and upgrades from pre-4.2.0 versions to 4.2.0 if the feature is accepted.
After a couple of false starts, it looks like the third time is the charm for the 4.0.2 release. Joe Brockmeier started the third voting round on Saturday 20 April, and it has quite a few +1 (binding) votes so far. Unless -1'ed by Tuesday morning, it will be ready for release.
Chip has also started the first vote for 4.1.0, which will be open for 72 hours – assuming no show-stopping defects are found, and it garners at least 3 +1 PMC votes. Note that everyone in the CloudStack community is encouraged to test out the release candidate and cast a vote, regardless of whether the vote is "binding" or not. More testing is always better, and an informed -1 from a non-PMC member isn't going to be ignored when deciding whether to release or not.
Pranav Saxena has raised a discussion about the limitations for DOMAIN admins, and wonders "why hasn't the domain -admin been given the privilege of creating sub-child domains himself? Are there any concerns/threats because of which the current architecture doesn't serve this purpose?" Alena Prokharchyk responds that there may be a feature request matching Pranav's concerns and suggests checking its status. This might be a good feature/improvement to see in 4.2.0 if there's not already work afoot.
- FLOSS Weekly Interview on Apache CloudStack: Chip and David appeared on FLOSS Weekly on April 10th. If you missed the live show, be sure to checkout the video.
- 4.0.2 Testing Procedure: Sebastien Goasguen has put together a screencast for testing the 4.0.2 release that also might be worth looking over for folks interested in testing any CloudStack release.
- Google Summer of Code with CloudStack: Sebastien has also put together a slide show about contributing to the Google Summer of Code (GSoC) with CloudStack.
- Knife CloudStack plugin 0.0.14 has been released: Sander Botman writes about the latest release of the CloudStack plugin. David has also written about the new knife-cloudstack plugin.
- To REST or not to REST: Sebastien tackles the question, "is the CloudStack API RESTful?" The short answer is "the CloudStack API is RESTlike but not RESTful since it is only based on the GET method. Being an http based API that can return JSON does not make it a RESTfull API. This should not be seen as negative criticism but just a clarification." Read the rest for the full scoop.
- Zone X is Not Ready to Launch Console Proxy Yet: Wido den Hollander writes about an odd error that he troubleshot to find an unlikely culprit.
- LinuxFest Northwest is being held in Bellingham, Washington from 27 April to 28 April.
- 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.
- Build a Cloud Day CloudCon San Francisco being held at the South San Francisco Conference Center on 15 May.
- CloudStack Collaboration Conference 2013 is being held from 23 June to 25 June in Santa Clara, CA at the Santa Clara Convention Center. See the Call for Proposals if you're interested in speaking!
If you want to to check in on events related to Apache CloudStack, see the Lanyard Page for the Apache CloudStack topic.
At the moment, bugs against 4.1.0 haven't been re-assigned to 4.1.1. This means that the bug counts for 4.1.1 are much lower than they should be. Taking into account the actual number of bugs, we're looking at one blocker bug, two critical bugs, 114 major bugs, and 25 minor.
For 4.2.0, we have:
- 5 blocker bugs for 4.2.0.
- 34 critical bugs for 4.2.0.
- 263 major bugs for 4.2.0.
- 35 minor bugs for 4.2.0.
- Bruno Demion was invited to become a committer and has accepted.
- Go Chiba was invited to become a committer and has accepted.
- Prasanna Santhanam was invited to become a PMC member and has accepted.
Please join us in congratulating all of the new committers and PMC members!
Want to keep reading the CloudStack Weekly News? Many hands make light work, but having only one editor means getting the weekly news out every week is a "best effort" activity. A healthy community publication needs several contributors to ensure weekly issues go out on time.
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 a note to the firstname.lastname@example.org mailing list with a subject including News: description of topic or email the newsletter editor directly (jzb at apache.org), 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.