Skip to main content

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 http://s.apache.org/BlH/. 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."

Events

New Committers and PMC Members

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

square-cloudmonkey.pngThe community is busy working on 4.2.0, and there's much to be done before the release is ready. This week, we're taking a look at some of the interesting discussions going on in the community about the next generation of Apache CloudStack, and functionality we can provide, as well as procedural changes that everyone should be aware of.

News Moving to Wednesdays

To help get information out a little more timely to key discussions and information that is going on in the community we are going to move the publishing of the weekly news to Wednesdays, starting with this issue on July 10th! If you'd like to help put the news together, please sign up for the marketing@cloudstack.apache.org mailing list and ask how you can get involved!

Major Discussions

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.

4.2 Status Update

Animesh Chaturvedi is tracking the current status of the release. Testing, bug fix work, and documentation should be targeted to complete by code freeze on 7/28. Release is still on schedule to release by 8/19.

We are now just 3 weeks from ACS 4.2 code freeze on 7/29. We have around 400 open defects with 100+ blockers and critical and I expect another 200 new defects to come in. As a community we have been fixing roughly 100 defects per 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 http://s.apache.org/BlH/. When you fix a bug in 4.2 please make sure it is also fixed in master.

<p>Given the debate on system template changes in last few days of 4.1 requiring big testing effort and potential regression, I would like to see that as community we lock down system templates for 4.2 pretty soon. If any changes are needed we should call it out now and get them resolved.</p>

<p>As for bugs here is a summary for this week:</p>
<div class='table-wrap'>
<table class='confluenceTable'><tbody>
    <tr>
        <th class='confluenceTh'>Bugs</th>
        <th class='confluenceTh'>This Week </th>
        <th class='confluenceTh'>&nbsp;</th>
        <th class='confluenceTh'>&nbsp;</th>
        <th class='confluenceTh'>&nbsp;</th>
        <th class='confluenceTh'>Last Week    </th>
        <th class='confluenceTh'>&nbsp;</th>
        <th class='confluenceTh'>&nbsp;</th>
        <th class='confluenceTh'>&nbsp;</th>
    </tr>
    <tr>
        <td class='confluenceTd'>&nbsp;</td>
        <td class='confluenceTd'>Blocker </td>
        <td class='confluenceTd'>Critical</td>
        <td class='confluenceTd'>Major </td>
        <td class='confluenceTd'>Total </td>
        <td class='confluenceTd'>Blocker </td>
        <td class='confluenceTd'>Critical </td>
        <td class='confluenceTd'>Major </td>
        <td class='confluenceTd'>Total </td>
    </tr>
    <tr>
        <td class='confluenceTd'>Incoming</td>
        <td class='confluenceTd'>8 </td>
        <td class='confluenceTd'>10 </td>
        <td class='confluenceTd'>28 </td>
        <td class='confluenceTd'>50 </td>
        <td class='confluenceTd'>11 </td>
        <td class='confluenceTd'>34 </td>
        <td class='confluenceTd'>24 </td>
        <td class='confluenceTd'>72 </td>
    </tr>
    <tr>
        <td class='confluenceTd'>Outgoing</td>
        <td class='confluenceTd'>26 </td>
        <td class='confluenceTd'>23 </td>
        <td class='confluenceTd'>34 </td>
        <td class='confluenceTd'>86 </td>
        <td class='confluenceTd'>26 </td>
        <td class='confluenceTd'>30 </td>
        <td class='confluenceTd'>40 </td>
        <td class='confluenceTd'>100 </td>
    </tr>
    <tr>
        <td class='confluenceTd'>Open Unassigned </td>
        <td class='confluenceTd'>7 </td>
        <td class='confluenceTd'>49 </td>
        <td class='confluenceTd'>129 </td>
        <td class='confluenceTd'>222 </td>
        <td class='confluenceTd'>6 </td>
        <td class='confluenceTd'>49 </td>
        <td class='confluenceTd'>119 </td>
        <td class='confluenceTd'>184 </td>
    </tr>
    <tr>
        <th class='confluenceTh'>Open Total</th>
        <td class='confluenceTd'>25 </td>
        <td class='confluenceTd'>84 </td>
        <td class='confluenceTd'>232 </td>
        <td class='confluenceTd'>403 </td>
        <td class='confluenceTd'>25 </td>
        <td class='confluenceTd'>80 </td>
        <td class='confluenceTd'>218 </td>
        <td class='confluenceTd'>385 </td>
    </tr>
</tbody></table>
</div>


<p>The status for features or improvement is depicted in table below</p>

<div class='table-wrap'>
<table class='confluenceTable'><tbody>
    <tr>
        <th class='confluenceTh'>New Features / Improvements </th>
        <th class='confluenceTh'>Today     </th>
        <th class='confluenceTh'>Last Week </th>
    </tr>
    <tr>
        <td class='confluenceTd'>Closed</td>
        <td class='confluenceTd'>10</td>
        <td class='confluenceTd'>10</td>
    </tr>
    <tr>
        <td class='confluenceTd'>Resolved</td>
        <td class='confluenceTd'>59</td>
        <td class='confluenceTd'>57</td>
    </tr>
    <tr>
        <td class='confluenceTd'>In Progress</td>
        <td class='confluenceTd'>11</td>
        <td class='confluenceTd'>13</td>
    </tr>
    <tr>
        <td class='confluenceTd'>Reopened</td>
        <td class='confluenceTd'>1</td>
        <td class='confluenceTd'>1</td>
    </tr>
    <tr>
        <td class='confluenceTd'>Ready To Review</td>
        <td class='confluenceTd'>1</td>
        <td class='confluenceTd'>1</td>
    </tr>
    <tr>
        <td class='confluenceTd'>Open</td>
        <td class='confluenceTd'>20</td>
        <td class='confluenceTd'>20</td>
    </tr>
    <tr>
        <th class='confluenceTh'>Total</th>
        <td class='confluenceTd'>102</td>
        <td class='confluenceTd'>102</td>
    </tr>
</tbody></table>
</div>
Swift Support in 4.2

On July 3rd, Edison Su reported that support for Swift is broken due to the object store refactor. There's been a fair amount of discussion on how an extant feature could be broken without being exposed via testing, and what should be done about it at this stage.

David Nalley says that "unplanned/unannounced deprecation of a feature is a blocker IMO. It engenders a bad relationship with our users, and strands them on previous versions with no good migration/upgrade path." Chip Childers says that "I believe that this was an honest mistake, but we need to figure out what to do. I'm -1 on us saying 'we'll drop Swift support'. If necessary, I'd say that we need to roll back the object-store branch merge... I don't want to see that happen, though. That's why I'm asking about the effort to fix it."

Chip opened CLOUDSTACK-3400 as a blocker against 4.2 until Swift support is fixed. Discussion about the bug continues.

Closing 4.2 Resolved Defects

Sudha Ponnaganti posted a list of 543 defects that are in resolved state that need to re-validated, reopened or closed. Please look through this list and check to see if you're assigned to any of these defects.

There are 543 defects in Resolved state and not closed. Please make sure that you validate and close the defect if you are satisfied with the fix. If there are issues with the fix, pl reopen the defect. Pl note that these need to be validated in 4.2 branch as all are fixed in 4.2 ( should be applicable for master as well). You can prioritize these based on the blocker, critical, major etc. As team is already done with the features, this is good time to close these...

Coding Convention Reminder

As open source projects mature and add new participants, it's occasionally necessary to send a gentle reminder of accepted conventions in the community. For example, Alex Huang opened a discussion about the CloudStack coding conventions on July 2nd, saying "Our coding conventions have been going all over the place recently. Please take a look."

He also proposed extending the 120 column limit to 180 columns.

I recently was reading the following code. If it followed even our current coding conventions, this would have been 11 lines but it ends up to be 23 lines,
more than doubled. The whole file was like this. Just thinking about all the extra scrolling I have to do makes my cts act up. We are in the 21st century
and using wide screen lcd monitors. Let's not format our code to fit 80 column amber text screens please!

<p>What's worse is I've found that some people are actively breaking existing source code to 80 columns, causing a bunch of unnecessary merge activities. </p>

For those folks who use Eclipse Alex has checked in his Eclipse profile to tools/eclipse/eclipse.epf. It will help with a number of issues, such as removing trailing white space, reformats edited portions of the file using the current formatting rules, and more.

Changing Bug Severity

Prasanna Santhanam noted that some bugs have changed severity without any reason given. Any time a change of this sort of significance is made in Jira, some reason should be given so that other users can have some idea why the change was made without having to track down the person responsible and ask.

Prasanna asks:

Can the bug reporters please mention the
reason as to how something :

<p>a) blocks movement on the feature/installation/cloudstack in general<br/>
b) affects deployment and does not have workarounds via the API<br/>
c) troubleshooting done with respect to a and b.</p>

<p>Here's some light reading on how to have bugs resolved faster:
<a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" class="external-link" rel="nofollow">http://www.chiark.greenend.org.uk/~sgtatham/bugs.html</a></p>

Chip replied:

+1 with an added "d)":

<p>d) needs to be considered a release blocker for a legal, security or<br/>
trademark reason</p>
Name space

Dharmesh Kakadia one of our Google Summer of Code participants has started a discussion on changing the future namespace convention for Apache CloudStack. The current namespace has been in place since the original Cloud.com implementation. As Dharmesh states, this is a big change, please join the discussion on how we can make this a successful switchover.

Since the CloudStack project has moved to ASF, the suggestion is to move from com.cloud packages to org.apache java packages.(https://issues.apache.org/jira/browse/CLOUDSTACK-212)

<p>As you might be realize, this is pretty big change. And merging this changes with a continuously updating master is non-trivial. So, here is the planned strategy after discussion over IRC. I am starting this thread to inform and know everyone's opinions.</p>

<p>1. I will be pushing code with new packages on branch "namespacechanges" and will notify on this thread as each refactored module is pushed.</p>

<p>2. There will be a freeze on master branch commits for some time in which "namespacechanges" will be applied to master. I suggest the date to be 20th July.</p>

<p>3. All the branch-owner updates their branch for reflect new packages. It was suggested that branch owners can look into the "namespacechanges" branch as it grows and start doing the package changes early, although it depends on branch-owners.</p>
In-Development Release Naming

While we are still hard at work at getting 4.2 out the ready and out to the world, John Burwell has proposed moving to release naming until a release has gotten to feature freeze and it can be judged on what the semantic version number change should be. There's been a lot of discussion on this topic. We would probably look to start this in the next release if it can come to a vote.

Since we have adopted Semantic Versioning [1], it seems odd that we designate a release version before the final set of enhancements/fixes has been identified. For example, the release proceeding 4.2 may contain no backwards compatible API changes to be 4.3. Conversely, we may decide during the development cycle, as a community, to accept a non-backwards compatible change which would bump the version to 5.0.0. As such, it is difficult to know in advance what the proper semantic version number will be at when the work is released. We run the risk of confusing our users if we start calling a pending release say 4.3.0, and accept a change mid-cycle that will bump it to 5.0.0. To address this potential issue, I proposed that we refer to releases by a codename until feature freeze when we understand the complete scope of change and can apply the correct semantic version number. I further propose we codename the release directly proceeding 4.2 "Gamma Rays" or "Gamma Rays Gonna Get Ya".

CloudStack Planet

What's going on in the CloudStack community? While all the discussion happens on the mailing lists, we also encourage members of the CloudStack community to share what they're working on their blogs. In this section, you'll find posts by Apache CloudStack community members and interesting news that's relevant to Apache CloudStack.

CloudStack European User Group Summary

The ShapeBlue blog has a summary of the most recent meeting, by Giles Sirett.

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."

In Case You're Not Already Sold on DevOps

Joe Brockmeier talks a bit about Gene Kim's keynote at the CloudStack Collaboration Conference, "Why Every Company Needs DevOps Now."

Hackathon Storage Group Puts Out Discussion and Proposal

John Burwell who led the storage discussion group during the CloudStack Collaboration Conference Hackathon put out the first group discussion on the future needs and a proposal on how to better define storage for future versions of CloudStack. Read the and participate in the discussion and weigh-in on the proposal.

Interview with The Cloudcast (.net)

Chip Childers and David Nalley sit down with Aaron Delp for the Cloudcast podcast. Be sure to give it a listen!

New Videos Coming Soon From Our Summer Video Project

Gregg Witkin and Jessica Tomechak are working together on videos this summer. Gregg hit the ground running by bringing his cameras to the Collab Conference June 24-25 in Santa Clara. He is editing that footage into short clips to help promote the November CloudStack Collaboration Conference in Amsterdam.

These short videos will be posted as soon as the conference organizers approve them. Meanwhile, check out these videos Gregg did with CloudStack just last year. Link 1, Link 2

Events

New Committers and PMC Members

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

square-cloudmonkey.pngWe are half way through the year and a lot of work is done, and lot more is yet to be done. This week we look back at some of the CloudStack Collaboration Conference, 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. There's a by-laws vote underway to look at how and where we decide non-technical issues, and some discussion on the best way to discuss and do code reviews.

News Moving to Wednesdays

To help get information out a little more timely to key discussions and information that is going on in the community we are going to move the publishing of the weekly news to Wednesdays starting July 10th!

Major Discussions

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.

Feature Freeze in Affect for the 4.2 Release

Code Freeze in now in effect starting 6/28 and the 4.2 branch was created on 6/29. There is currently no motion in the community to extend the freeze date, and Animesh Chaturvedi is keep the release on schedule. If the feature or merge you are working on was unable to make it in, please start to move it to your JIRA tickets and additional documentation to 4.3 scheduled to release sometime in December.

Currently Animesh is handling the release management for 4.2 has listed out our current state. He put together an e-mail on the current status of the release. If we don't quickly get these resolved further delays in the release and jeopardize future releases.

We are now just two days away from feature freeze, but still there are many open tickets. If the feature or improvement is unlikely to be wrapped up by 6/28 it should be moved out of 4.2

As for bugs here is a summary for this week:

BugsThis Week    Two Week Ago    
  Blocker Critical Major Total Blocker Critical Major Total
Incoming 4 19 37 68 8 20 29 60
Outgoing 19 42 34 102 18 10 42 76
Open Unassigned 4 27 116 184 7 35 93 166
Open Total 17 62 223 365 19 74 192 345
Progress on 4.1.1 Release

With 4.1 now released we are already beginning work on the 4.1.1 patch update. Ilya Musayev is the release manager for the 4.1.x branch, and has asked work all merges to be completed. Once that is done, he will call for a VOTE.

Large Merge / Release Work

As we seen in the past and now again in 4.2, it's important to focus on merging your features early and often. By breaking up large merge and code review requests it is possible to help keep releases on schedule, get features in before the freeze and avoid Veto votes. Alex Huang and Kelven Yang worked really hard on a new and large VMSync feature that many users need. Because it came in so close to freeze and was a large merge request with less than a week before freeze it immediately received Veto votes blocking the merge. Even with the help of several other committers the review couldn't be done in a timely fashion and miss the 4.2 cutoff.

When late requests come in like this it also puts undo stress on the testing of the release as well. Read through the merge thread to follow the discussion on how we can improve this in the future.

BVT Automation Testing Breaks

After complaints that the BVT environment was broken, Alex Huang did some investigating to identify the root cause and raise a suggest on how BVT testing should be dealt with in the future.

After Dave's complain in the vmsync MERGE thread about BVT in horrible shape on master, I went around to figure out what exactly happened. The best I can figure is that after a certain merge (I will leave out which merge as that's not important), BVT no longer runs automatically. It was promised to be fixed and there are people who are actively fixing it but it's been in this way for about two weeks. People running BVTs are working around the problem but it's not automated anymore and so it's no longer running on master. I understand people are nice and tried to be accommodating to other people by working around the problem but sometimes we just have to be an arse. So let me be that arse...

New Rule....
If BVT or automated regression tests break on master or any release branch, we revert all commits that broke it. It doesn't matter if they promise to fix it within the next hour. If it's broken, the release manager will revert the commits and developers must resubmit. It sounds mean but it's the only way this problem can be fixed.

To avoid having a bunch of reverts and resubmits, the developers should be able to request that BVT run on their branch and don't merge until BVT on their branch is at 100%. We will work on figuring out how to do that.

CloudMonkey and PyPI Releases

On June 9th, Rohit Yadav asked about a problem with the 4.1.0-0 CloudMonkey release on PyPI lacking the fail safe API cache. Starting a discussion about the future of how to treat CloudMonkey and Marvin.

Follow-up - Rohit and David Nalley have since moved CloudStack CloudMonkey out to its own Git Repository and version based off the continuing conversation through last week. No decisions have been made yet in regards to Marvin and if community members have an opinion are encouraged to join the discussion.

A Vote on final adoption of the move of CloudMonkey is now underway. Please join in the Vote thread.

Java and Tomcat version upgrades

As we continue to work on improving CloudStack, there are additional upgrades to the tools that we use to bring CloudStack to life. Hugo Trippaers started the discussion on support for Java 1.7 and Tomcat 7. Please join in the discussion as it will have affect development of future versions of CloudStack.

Vote starts to determine where non-technical matters are decided on

In previous discussion about publishing books about CloudStack on the CloudStack.Apache.Org page, Sebastien Goasguen 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).
...

Based off this, Noah Slater has proposed new language to the by-laws to help improve our ability to manage such decisions.

...
Summary of changes:

  • Addition of "3.4.2. Non-Technical Decisions" section. This specifies that
    non-technical decisions can be made on any appropriate list (i.e. marketing@)
    and also allows us to vote on them with lazy 2/3 majority.
  • Changed "The vote must occur on a project development mailing list." to
    "The vote must occur on the project development mailing list." in several
    places. This makes it explicit that these decisions must be made on
    the dev@list.
  • Minor rewordings, typographical changes, corrections, section
    renumbering, etc.
    ...

CloudStack Planet

Google Summer of Code Update
  • Google Summer of Code (GSOC) has been headed up by Sebastien Goasguen, bringing 5 young developers and their projects to the CloudStack community.The Community Bonding period was to help introduce them to the community and their ideas and help them get acquainted with procedures and systems.

We now enter the work period and get going on these proposals. Please help them as they try to help improve Apache CloudStack.

CloudStack Community Survey Underway

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.

CloudStack Community Votes to Publish CloudStack Book List

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.

A Videographer is Working with CloudStack to Create Videos for the Project

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

Events

CloudStack Collaboration Conference 2013

If you're not able to join, all sessions are being recorded and will be available after the conference for viewing.

  • The Hack Day was a great success with several tables opening up and a lot of conversations flowing. There were large conversations in storage, mindshare/marketing, documentation and several others. Each group is encouraged to share their collaborations with the rest of the community.
  • Chip Childers kicked off the conference on Monday, June 24th, 2013 with a state of a strong and busy community. He talked about how much we have accomplished in the time that we have been in the Apache Foundation and the great work that is upcoming. Chip's presentation is up on slideshare
  • Gene Kim's keynote gave us an insight into Devops and the ability of IT to work in a different way and more function ways.Aaron Delp wrote a blog on the opening keynotes. Read it here
  • Adrian Cockcroft’s delivered a great keynote closing the conference talking about “Dystopia as a Service” on Tuesday.
  • There were so many amazing presentations! They were all recorded and will be available shortly on the BuildACloud.org website. We will let you know when it's available.
  • The tweeters were busy during the conference! Check out the #CCC13 Tag for a lot of info from the conference.
  • Want to win $10,000? That's right, Citrix has offered a $10,000 bounty for the first person to get Netflix OSS Tool to work on CloudStack! Mark Hinkle made the announcement during the closing keynote.
  • Here's some links to many of the pictures taken: link, link, link, link, link
More Events

New Committers and PMC Members

  • Mike Tutkowski has been invited by the PMC to become a committer and has accepted.

square-cloudmonkey.pngIt'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.

Major Discussions

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.

Progress on 4.1.1 Release

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.

CloudMonkey and PyPI Releases

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.

CloudStack Community Survey Underway

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.

CloudStack Community Votes to Publish CloudStack Book List

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
...

Google Summer of Code Update
  • Google Summer of Code (GSOC) has been headed up by Sebastien Goasguen, bringing 5 young developers and their projects to the CloudStack community.The Community Bonding period was to help introduce them to the community and their ideas and help them get acquainted with procedures and systems.

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:

A Videographer is Working with CloudStack to Create Videos for the Project

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

CloudStack Planet

CloudStack PMC members asked to join ASF membership

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.

JCSUG presents at LinuxCon / CloudOpen Japan

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.

Upcoming Events

CloudStack Collaboration Conference 2013 - Only 1 week away!

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.

  • Registration opens on Sunday, June 25th at 4:30pm right before the Welcome Cocktail Reception.
  • Joe Brockmeier has already started planning discussion for the Hack Day. Topics like Storage Architecture with John Burwell, Documentation with Joe Brockmeier, and Apache Project integrations with Sebastien Goasguen. Check out the sessions on the wiki
  • Gene Kim & Chip Childers will be kicking off the conference with keynotes on Monday, June 24th, 2013.
  • Gene Kim will be doing book signings during the morning and afternoon breaks. The first 250 attendees to get registered for their badges at the conference will get a copy of The Phoenix Project.
  • Adrian Cockcroft’s keynote has been announced. He will be closing the conference with his keynote, “Dystopia as a Service” on Tuesday, June 25th.
  • Remember to sign up for the evening events – the CloudStack Roller Coaster Party requires a ticket.
  • If you have not booked your hotel room yet – simply make your reservation here!
More Events

New Committers and PMC Members

  • Jayapal Reddy Uradi has been invited by the PMC to become a committer and has accepted.

square-cloudmonkey.pngThis week, we take a look at the 4.2.0 feature freeze pushback, the Apache CloudStack user survey, and new committers and PMC members for Apache CloudStack.

Major Discussions

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.

4.1 Releases

The first major release of Apache CloudStack since it became a top level project was released on June 5, 2013 and is available. For more information, please see the official announcement.

4.2 Feature Freeze Push Back

Due to the delays in releasing 4.1 release, it was requested by many in the community to push back the freeze date. Chip Childers called for a Vote on 5/31 to move the Feature Freeze back from 5/31 to 6/28 (Updated Schedule). The push back was approved with 19 +1 votes (full results).

CloudStack Community Survey Underway

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.

CloudStack Planet

  • CloudStack University by Sebastien Goasguen: At Apache CloudStack we recently started an initiative to organize our content into learning modules. We call this initiative CloudStack University. Everyone is invited to participate by contributing content (slides and screencasts), suggesting new learning modules that are needed and even creating exercises and assignments. School fun ! As we were discussing the initiative on the mailing list we started by looking at our existing content: slideshares, youtube videos and thought about organizing them into a CloudStack 101 course. This is still a work in progress that requires everyones participation to make it a great resource.
  • Videographer is working with CloudStack to create videos for the project. Is your cloud one of the "Top 10 Coolest CloudStack Deployments"? Videographer Gregg Witkin and writer 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 welcome your 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

Upcoming Events

Don't miss the CloudStack Collaboration Conference, which is coming up June 23 through June 25.

  • Just announced that Adrian Cockcroft (Director of Architecture for the Cloud Systems team at Netflix) will deliver the closing keynote at the conference with, "Dystopia as a Service" on June 25th, 2013. Adrian will discuss the new challenges and demands of living in this dystopian world of cloud-based services along with an overview of the Netflix open source cloud platform. For more info click here

New Committers and PMC Members

  • John Burwell has been invited to join the CloudStack PMC, and has accepted
  • Sailaja Mada has been invited to become a CloudStack committer, and has accepted
  • Venkata Swamy has been invited to become a CloudStack committer, and has accepted
  • Wei Zhou has been invited to become a CloudStack committer, and has accepted
  • Sangeetha Hariharan has been invited to become a CloudStack committer, and has accepted

square-cloudmonkey.png The Apache CloudStack project is pleased to announce the 4.1.0 release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is the first major release from Apache CloudStack since its graduation from the Apache Incubator on March 20th.

Apache CloudStack is an integrated software platform that allows users to build a feature-rich IaaS. CloudStack includes an intuitive user interface and rich API for managing the compute, networking, accounting, and storage resources for private, hybrid, or public clouds.

The 4.1.0 release represents more than five months of development effort by the Apache CloudStack community. The release includes many new features and bugfixes from the 4.0.x cycle. The 4.1.0 release also marks major changes in the codebase to make CloudStack easier for developers, a new structure for creating RPM/Debian packages, and completes the changeover to using Maven as a build tool.

New Features​

Some of the notable new features in Apache CloudStack 4.1.0 include:

  • An API discovery service that allows an end point to list its supported APIs and their details.
  • Added an Events Framework to CloudStack to provide an “event bus” with publish, subscribe, and unsubscribe semantics. Includes a RabbitMQ plugin that can interact with AMQP servers. Introduces the notion of a state change event.
  • Implement L3 router functionality in the Nicira NVP plugin, and including support for KVM (previously Xen-only).
  • API request throttling to prevent attacks via frequent API requests.
  • AWS-style regions.
  • Egress firewall rules for guest networks.
  • Resizing root and data volumes.
  • Reset SSH key to access VMs.
  • Support for EC2 Query API.
  • Autoscaling support in conjunction with load balancing devices such as NetScaler.

Downloads​

The official source is available from:

http://cloudstack.apache.org/downloads.html

In addition to the official source code release, individual contributors also make convenience binaries available. 4.1.0 convenience binaries should be available within a day or so of the release announcement.

Note that there is a known issue with 4.1.0 and a recent Tomcat release. This has been addressed in the convenience binaries, but is still present in 4.1.0 source release. We will be working on a 4.1.1 release that will contain that fix shortly.

CloudStack Collaboration Conference​

The CloudStack community will be gathering for its second conference this month in Santa Clara, CA. The event will start on June 23rd with a hackathon, then formal programming on June 24th and 25th. This year we’ve gotten some fantastic keynotes, including DevOps legend Gene Kim (author of “The Phoenix Project”). You can find all the details at http://www.cloudstackcollab.org/, and the schedule at http://www.cloudstackcollab.org/schedule/.

About Apache CloudStack​

Apache CloudStack is a complete software suite for creating Infrastructure-as-a-Service (IaaS) clouds. Target environments include service providers and enterprises. It is used by many service providers to set up an on-demand, elastic cloud computing services and by enterprises to set up a private cloud for use by their own employees. Apache CloudStack is also available to individuals and organizations that wish to study and implement an IaaS for personal, educational, and/or production use.

Further information on Apache CloudStack can be found at cloudstack.apache.org.

square-cloudmonkey.pngThe Apache CloudStack is very near to the 4.1.0 release, and as a result we’re conducting a vote on artifacts for the 4.1.0 release right now. Because we want to make sure we have the best possible release, we’d like to invite anyone who’s interested in CloudStack to take the current release candidate for a test drive.

Chip Childers started the vote on May 28th and it will run for a minimum of 72 hours, barring any blockers. Note that a VOTE requires at least three +1 votes from PMC members to pass, but anyone can vote, and we welcome input from all members of the community - positive votes mean that a wider community has taken a look at the release and helped vet it before we make it official. And if there are technical issues that might be a –1 on the release, we’ll take a look at those regardless of whether a person is a PMC member or a member of the community speaking up for the first time.

The source release is available on dist.apache.org: https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/, and the list of CHANGES is available via our git repository.

Full testing instructions are available on the CloudStack wiki.

Please be sure to send any feedback via the VOTE thread on dev@cloudstack.apache.org. We’re looking forward to getting the 4.1.0 release out the door, come and give us a hand!

square-cloudmonkey.pngWhat's new in Apache CloudStack? This issue, we take a look at progress towards the 4.1.0 release, major discussions in the community, and the upcoming CloudStack Collaboration Conference. We also welcome three new committers to the Apache CloudStack project, Clayton Weise, Isaac Chiang, and Phong Nguyen.

As you may have noticed, we skipped the newsletter last week. Apologies about that! This week's newsletter catches up from the beginning of May.

CloudStack North America Collaboration Conference 2013!

The Apache CloudStack community is going to have its second conference in late June. If you missed the first one, or couldn't wait to do it again, you'll want to hurry up and make plans to be there!

  • CloudStack Collaboration Conference 2013 is being held from 23 June to 25 June in Santa Clara, CA at the Santa Clara Convention Center.
  • Register now as spots are limited! It's important to join in our yearly conference to learn and truly collaborate with the community in person. This year we are including a "Hack Day", where collaboration will be happening in a real time!
  • Are you ready to share your CloudStack vision? See the Call for Proposals if you're interested in speaking. Proposals close on May 19th.
  • We are still looking for Conference Sponsors! Have your company be part of this great event. Contact Nancy Asche at (407) 601-6228 or nancy.asche@conferencedirect.com for more details on how to get involved.

Major Discussions

Several major discussions this week, summarized below. Note that this is only a fraction of the activity in the project. For a full overview of project activity, you may want to subscribe to dev@cloudstack.apache.org.

4.1.0 Update

Chip Childers sent out an update on the latest blockers on Monday, May 13th.

Security Mailing List

To better help communicate about security related matters, announce security concerns, and determine additional security needs for CloudStack, a new mailing list security@cloudstack.apache.org is being set up and run similarly to security@apache.org. The list is only open to members of the security team, but anyone can email the list with security issues.

Network Guru Refactoring

Daan Hoogland has proposed refactoring the network guru. Chiradeep Vittal points out that, for major changes, we should have a functional specification (FS) in addition to an email bringing the topic up on dev@. Daan has agreed to provide one, which should help spark an intelligent discussion about the proposed feature.

Test Plan Review for Better VM Sync

Suresh Sadhu has asked for review of a QA Test Plan for "Better VM Sync" and for comments on the plan.

Feature Freeze for 4.2.0 is Coming

Animesh Chaturvedi has posted a reminder about the 4.2.0 feature freeze, along with the dashboard for tracking 4.2.0 progress.

Change Status when Features are Merged to Master

Sudha Ponnaganti reminds contributors to change the status in Jira. It's important to help folks doing QA to pick up the feature for validation.

CloudStack Planet - Posts from the CloudStack Community

Upcoming Events

If you have an event you wanted added here, please send to the marketing@cloudstack.apache.org or see how to contribute to the news below.

New Committers and PMC Members

Clayton Weise has been invited to become a committer and has accepted.

Phong Nguyen has been invited to become a committer and has accepted.

Isaac Chiang has been invited to become a committer and has accepted.

Contributing to the Weekly News

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 marketing@cloudstack.apache.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.

square-cloudmonkey.pngAre you using, supporting, or helping develop Apache CloudStack? Doing interesting work around Apache CloudStack? If so, you should be speaking at the second CloudStack Collaboration Conference this June in Santa Clara. The deadline for submissions is Sunday, May 12th. You can submit talks at http://www.cloudstackcollab.com/CfP/.

The Collaboration Conference will feature tracks for users, developers, and integrators of Apache CloudStack. We’re looking for presentations that provide insight into best practices in deploying and developing Apache CloudStack. This includes supporting technologies like configuration management tools, monitoring solutions, and more.

This will be an outstanding opportunity for developers to collaborate, exchange ideas, and get work done face-to-face with other Apache CloudStack contributors to improve Apache CloudStack.

Proposals​

The program committee will be looking for presentations and workshops related to working with and developing Apache CloudStack. This includes everything from running CloudStack at scale, best practices for working with IaaS clouds, discussions about CloudStack’s architecture, proposals for feature development, and more. We’re also open to talks that go hand-in-hand with managing Apache CloudStack, like configuration management and monitoring tools.

In short, if it’s relevant to Apache CloudStack development, deployment, and integration, we’re interested in what you might have to say. For an example of what we’re looking for, check out some of the videos from last year’s event.

To submit your talk, just go to http://www.cloudstackcollab.com/CfP/ and follow the steps there.

Timeline and Deadlines​

There’s no time like the present to submit a proposal. We recommend getting your proposal in early, and feel free to ask questions about talk ideas on marketing@cloudstack.apache.org if you want tips for success! You can reach the CfP committee at planning@cloudstackcollab.org.

Dates for proposals are as follows:

  • Call for Proposals is open on April 22nd.
  • Call for Proposals closes on May 12th.
  • Notifications will go out on May 17th.
  • Confirmations will be due by May 22nd.

Travel Sponsorships​

Not sure if you can afford the airfare and lodging to attend the Collaboration Conference? Please don’t let that stop you from submitting your best proposal. We may be making a number of travel sponsorships available for speakers who have useful information to share with the Apache CloudStack community.

Code of Conduct​

The Apache CloudStack community is open to everyone. As such, we are committed to providing a friendly, safe, and welcoming environment for all - regardless of gender, sexual orientation, disability, ethnicity, or religion. We respect and encourage diversity at our conference.

By agreeing to present at the conference, you are agreeing to abide by the code of conduct. We expect all speakers and attendees to have read and understood the code of conduct, and that all presentations will meet this standard.

Questions?​

If you have questions or concerns, please don’t hesitate to reach out to the conference planning committee by sending an email to planning@cloudstackcollab.org.

This week, we had discussions about the release cycle and whether a six-month cycle may be more appropriate. Work continued on the 4.1.0 release, and Apache CloudStack 4.0.2 was released.

Major Discussions

Several major discussions this week, summarized below. Note that this is only a fraction of the activity in the project. For a full overview of project activity, you may want to subscribe to dev@cloudstack.apache.org.

Release Cycle: Four Months, or Six?

Animesh Chaturvedi started new thread for a discussion that cropped up in the timeline thread about the four-month vs. six-month release cycle ideas. After much discussion, Animesh summed up the discussion saying:

I still see there is difference of opinion and not a clear consensus with 12 out
of 21 ( approx. 60%) preferring 6 months. But going by the argument of not
having given proper shot to 4 month cycle I will say we can keep 4.2 as a 4
month cycle and pull in all effort to make it successful. If it turns out that
we can work with 4 month schedule that's well and good otherwise we can bring
this topic again based on the results of running 4 month cycle.

4.1.0 Approaches

After clearing out a number of last-minute blockers, it looks like 4.1.0 may be just about ready to roll. Chip Childers posted on Friday that he was waiting on confirmation on CLOUDSTACK-528 and CLOUDSTACK-2194 being fixed. If those are fixed, Chip says he will "proceed with starting the VOTE thread" Monday morning, Eastern time.

Apache CloudStack 4.0.2 Released

Joe Brockmeier announced the 4.0.2 release on 24 April, along with security fixes for two security vulnerabilities.

Security Vulnerabilities in CloudStack 4.0.x

John Kinsella sent out an announcement detailing two security vulnerabilities on 24 April:

Description:
The CloudStack PMC was notified of two issues found in Apache CloudStack:

1) An attacker with knowledge of CloudStack source code could gain
unauthorized access to the console of another tenant's VM.

2) Insecure hash values may lead to information disclosure. URLs
generated by Apache CloudStack to provide console access to virtual
machines contained a hash of a predictable sequence, the hash of
which was generated with a weak algorithm. While not easy to leverage,
this may allow a malicious user to gain unauthorized console access.

Mitigation:
Updating to Apache CloudStack versions 4.0.2 or higher will mitigate
these vulnerabilities.

Credit:
These issues were identified by Wolfram Schlich and Mathijs Schmittmann
to the Citrix security team, who in turn notified the Apache
CloudStack PMC.

Exposing APIs that carry POST data

Prasanna Santhanam raised a discussion about adding the ability to send user data as POST to commands.

I'm guessing we'll have to put in additional annotations on our APIs
that support POST so that API discovery can print the methods
supported (GET/POST). Right now it's only the deployVMCmd (AFAIK). But
I expect this will need to be done for others soon.

I've included POST support for every command in marvin but that's
just brute-force. To make it more intelligent I think we should apply
it to only apis that make sense as POST (causing side-effects). But
that needs to be exposed by the api endpoint.

Enabling GitHub Pull Request Notification

A discussion was brought up on dev@ this weekend about enabling notifications for pull requests made via GitHub. David Nalley remarked that in his opinion, "there really isn't an option - if we are going to have a GitHub mirror, we also need to be able to deal with the pull requests there. Ignoring folks that submit pull requests is inappropriate."

Chip questioned the need for a GitHub mirror at all. "Not sure the value, when you consider the confusion it causes WRT the canonical source repo."

CloudStack Planet - Posts from the CloudStack Community

  • More Fun with the CloudStack API - Kirk Jantzer writes about playing with the CloudStack API and writing a tool "in an effort to make deployment of a mass amount of servers with as little effort as possible."
  • Thanks to the Apache CloudStack community! - Shane Curcuru writes about the Apache CloudStack graduation and its incubation. "The desire to get things 'right' at Apache was clear in everything the CloudStack community did, and the end result looks to be an incredibly strong project that’s quickly gathering developers from a wide variety of vendors and users. Part of this growth is about the great technology; but a lot is due to the helpful and welcoming face that the CloudStack committers put on their project."

Upcoming Events

Jira

Checking in on the upcoming 4.2.0 release, we have added a few bugs over the past week:

New Committers and PMC Members

No new committers or PMC members announced this week.

Contributing to the Weekly News

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 marketing@cloudstack.apache.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.