You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

We are into deep work on 4.2.0 and need your help in making the grade. There's a lot of interesting discussions going on into the community about the next generation of CloudStack and functionality we can provide as well as some procedural adjustments 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!

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.

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.

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|https://cwiki.apache.org/confluence/display/CLOUDSTACK/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!

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.

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 :

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

Here's some light reading on how to have bugs resolved faster: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Chip replied:

+1 with an added "d)":

d) needs to be considered a release blocker for a legal, security or
trademark reason

4.2 Release
Progress on 4.1.1 Release

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

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.

  • No labels