It's been another busy week for the Apache CloudStack project. This week we welcome another new committer, work continues on 4.1.1 and 4.2.0, and we have some interesting discussions on how we should release the CloudMonkey and Marvin tools used with CloudStack. We've also seen a few interesting marketing discussions, and the community is gearing up for the second CloudStack Collaboration Conference taking place 23 June through 25 June in Santa Clara, CA.
In this section we look at major discussions that have happened on the CloudStack mailing lists. This is by no means a full summary of all discussions on the lists, but we try to hit the highlights that are relevant to the larger CloudStack community.
With 4.1 now released we are already beginning work on the 4.1.1 patch update. Ilya Musayev is release manager for the 4.1.x branch, but Chip Childers will handle the 4.1.1 release as Ilya is unavailable during the timeframe we expect to finish 4.1.1 and call for a VOTE.
On June 9th, Rohit Yadav asked about a problem with the 4.1.0-0 CloudMonkey release on PyPI lacking the failsafe API cache:
When I install it I don't get any api commands. The autodiscovery using sync is useful but only with the ApiDiscovery plugin which works only for 4.2 and later. For 4.1 and below I think we should, in that case, bundle the cache for all the apis. Or maybe
just oss components/plugins?
David replied that "this is exactly why I've been suggesting that we break CloudMonkey (and Marvin) out of the main repo" and give them their own lifecycle. "It's far easier/faster to iterate cloudmonkey than all of CloudStack and tying it to the slower lifecycle of ACS will continue to trouble it IMO."
Rohit replied that "we should do it then." Prasanna Santhanam replied, "I haven't given breaking out the project much thought. But it's certainly a possibility." However, Prasanna notes that "parts of the codebase" depend on Marvin, and it would require an "easier way to update Marvin across CloudStack providers to enable auto-updating Marvin's libraries like CloudMonkey can."
No final decisions have been made, but the discussion is still open for anyone that has a stake in how releases happen for Marvin and CloudMonkey.
Please let your voice and your organization be heard in this short survey. We would like to have both users of the Apache CloudStack source and Commercial derivatives, "We will be using the data in aggregate to get to know more about how it's being deployed out there." Chip Childers commented. Click Here to take the short survey.
In a heavily discussed topic throughout the community to allow the publishing of outside books about CloudStack on the CloudStack.Apache.Org website or wiki, it was finally voted on and decided to allow outside publications to be published. Right now Sebastien Goasguen has setup a wiki page and will work on where to have the permanent placement for this page. Sebastien posted the full results on June 12, but noted that there's a question about voting on a list that isn't dev@:
...
Our bylaws (1) do not cover votes on non-technical matters, so while we have
lazy majority on this vote it seems that this situation is not covered by the
bylaws. Moreover section 3.1.1 of bylaws says that decisions on the project
happen on dev@, so it seems that votes even on marketing@ are not allowed
(unsure about this).I propose the following:
1-To move forward without having to re-cast a vote, I propose to list
immediately the books on the Wiki, and inform Packt. I just created the page (2)
2- If people agree that we have a bylaw "loophole", we need to modify the bylaws
to allow votes on marketing@ and agree on using Lazy majority or Lazy 2/3
majority.Once we agree, I will inform users@ and dev@ and invite folks who participated
in this vote to join marketing@3- We could then re-cast a vote to list on the website
(1) http://cloudstack.apache.org/bylaws.html
(2) https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Books
...
We now enter the work period and get going on these proposals. Please help them as they try to help improve Apache CloudStack.
Get to know these 5 young talents:
Gregg Witkin and Jessica Tomechak are working together on videos this summer, including one that aims to show some of the most interesting real-world applications of CloudStack. They're asking for participation on this video, and suggestions for other videos you'd like to see. Check out these videos Gregg did with CloudStack just last year. Link 1, Link 2
Chip Childers and David Nalley were invited to be members of the Apache Software Foundation. An honor given to those, "Committers who demonstrate merit in the Foundation’s growth, evolution, and progress are nominated for ASF Membership by existing members.". Congratulations to both Chip and David.
On May 29-31 the Japanese CloudStack User Group participated in the LinuxCon / CloudOpen 2013 in Tokyo. 20 volunteers helped with the CloudStack and Xen booth at the conference. During the conference there was also several sessions on building clouds with CloudStack, Cloudstack networking, and participation in a discussion panel with Google, Rackspace, NTT and Red Hat. Here are pictures of the event.
The CloudStack Collaboration Conference 2013 (CCC13) hasn't even begun yet and the collaboration, excitement and participation for the event is already in full swing. Here are some of the highlights and notes to remember for attendees.