This week, a vote on updating the project bylaws, fixing the "Tomcat situation" after 4.1, and discussions around the support lifecycle. Some respectable progress in knocking out major and blocker bugs for 4.1.0 as well. The project also welcomes two new PPMC members and three new committers.
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!
Chip Childers kicked off a thread about why it matters where and how development happens, based on a discussion that had taken place on cloudstack-private:
It's largely a re-hash of things that have already been discussed, but we wanted to get this summary moved into the dev list so that the points are available for reference. We should probably distill this into a wiki page somewhere, but that's not done quite yet (volunteer?). Keep in mind
that I've tried to pull the important parts of the conversation into this email... it was a fairly long thread of discussion and debate.
I'd suggest reading it all the way to the end to form your own understanding of why we have to be careful about how we work as a community.
The TL;DR version:
The issue that we ran into with several features being developed "outside the community" for 4.1 was a major deal, and it had several
implications. First, doing that effectively hurts our community. The other issue is related to the legal right of the project to accept the
code developed elsewhere.
Rather than summarizing it here, I'd recommend that readers spend the time to read Chip's initial email and the replies in the thread.
There is one catch though, VirtualBox exports VHD appliance which is said to be compliant with HyperV. I thought we may need to do something for Xen separately, so I followed and found a way. The "way" is to export a raw disk image and convert it to a VHD 1 but the problem is the VHD created from that "way" fails when vhd-util tries to scan for any dependent VHDs (parents etc.), I don't know what's the reason.
Read the rest of the thread if you have an interest in creating custom system VMs for CloudStack.
Noa Resare has admitted being intensely frustrate with "the current tomcat situation" when working on packaging CloudStack. The current setup, says Noa, has many problems. In response, Noa has started a proof-of-concept "of a replacement for this whole mess yesterday, a few tens of lines of code setting up an embedded jetty web container. A few lines of code to parse a config file, set up logging and spawn an embedded servlet container."
Chip kicked off a VOTE thread last week to modify the project bylaws slightly:
The text was clarified slightly during the vote. The vote remains open until March 5.
With the 4.1 release getting closer, David Nalley raised the topic of the support lifetime for releases. Chip proposed a model that would consist of only bug fix releases for:
- The latest feature release of our active major version number (i.e.: 4.x)
- The latest feature release of our last major version number (doesn't exist today, but will be 4.x when / if we bump to 5.0)
Joe Brockmeier replied with a +1, saying that with the current level of participation in the bug-fix releases "this is the most realistic approach that's good for the community."
David asked whether an end of support means an end to bug fixes and security fixes at the same time. "Wearing your enterprise software consumer hat - does a supportlifetime of approximately 12 months make sense?" Instead, David proposed "we should add a month (so that EOL is one month after 4.n+2 releases, with the understanding that 4.n is likely to only receive security fixes if any during that extra one month window.)"
The discussion continues, so developers and users that have a vested interest in the support lifetime for ACS releases would do well to follow and respond to the discussion.
Parth Jagirdar has started a discuss thread about API throttling. "API throttling number can be set to anything at this point. Suggestions here is to have this number set to a value that is 'greater than' number of API that can be fired by any potential action on UI." (Note, Parth then sent out a follow-up email to correct the initial subject line from [DISCUSS} to DISCUSS, but all relevant discussion has happened in the original thread. It's probably not necessary to send a follow-up in those situations and may fragment the conversation.)
Sudha Ponnaganti posted a report to the -dev mailing list about branch stability for QA testing:
*Xen and VMWare are blocked with the following two issues. KVM is working fine (agent issue-1469 has been fixed by Hugo).
Failed to download default template in VMware
Xen - unhandled exception executing api command: deployVirtualMachine
There are no blockers now on Master / 4.2. Below are the only blockers and you
can continue to use older templates to make progress on master till new one gets
Used Master Branch System VM Template: Volume of System VM Failed to Create on
the XenServer due to IOError
The ASFBot shot a summary of the weekly IRC meeting to the -dev mailing list. If you missed it or need a reminder of what happened, check it out.
Joe sent out a short report about the doc sprint that took place on Friday, March 1st. Another is planned for Friday, March 8th.
Joe Brockmeier wrote a report on two talks at ApacheCon North America by Kirk Kosinski on troubleshooting CloudStack. The talks covered common networking issues and how to use log files to troubleshoot CloudStack.
Mark Hinkle has put up a post about Cloud talks at ApacheCon North America with links to presentations.
- CloudStack India, Bangalore Chapter: March Meetup - Cloud Storage & Monitoring - Koramangala, Bangalore, Thursday March 7, 2013.
- Doc Sprint (IRC): The doc team is running another sprint on Friday, March 8th from 16:00 to 23:00 UTC (that's 08:00 to 15:00 Pacific time, 11:00 to 18:00 Eastern in the USA) in #cloudstack-dev. All CloudStack contributors who have an interest in making the docs awesome are encouraged to attend and help out. See the wiki for more info.
- New York City Cloud Computing Group: Deploying Apache CloudStack from API to UI - New York City, Wednesday March 13, 2013.
- NYLUG Meetup: Open Source Private Clouds with CloudStack, Eucalyptus and OpenStack - New York City, Thursday March 14, 2013. RSVPs open on February 28th at 6:15 p.m. Eastern.
Big bug-fixing week for Apache CloudStack! The community knocked out 5 blocker bugs, 3 critical bugs, 9 major bugs, and 3 minor bugs. Still plenty of work left to do before 4.1.0 is ready for prime-time, though.
- Last week: 9 blocker bugs. This week: 4 blocker bugs
- Last week: 21 critical bugs. This week: 18 critical bugs
- Last week: 200 major bugs. This week: 191 major bugs
- Last week: 33 minor bugs. This week: 30 minor bugs
It's worth noting that the doc sprint helped quite a bit, bringing the total number of docs bugs for 4.1.0 to 44 (down from 64 just two weeks ago). Of the remaining bugs for 4.1.0, 80 are currently unassigned, down from 99 last week.
A big week for new committers and PPMC members.
- Marcus Sorenson has been invited to join the PPMC and has accepted.
- Sebastien Goasguen has been invited to join the PPMC and has accepted.
- Radhika Puthiyetath has been invited to become a committer and has accepted
- Sateesh Chodapuneedi has been invited to become a committer and has accepted
- Noa Resare has been invited to become a committer and has accepted.
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 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.