In the past week, the 4.0.1-incubating release passed its VOTE on the firstname.lastname@example.org list, work continued on 4.1.0, and there were active discussions on using Gerrit, cloud-init, and whether memory usage has increased following the adoption of the Spring framework.
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!
Alex Huang kicked off a discussion about using Gerrit. David Nalley pointed out that many of the problems Alex looks to solve with Gerrit are "social/cultural problems" that a technical solution alone won't fix.
Hugo Trippaers also voiced concerns about implementing Gerrit, saying that "a formal process like Gerrit" isn't necessary.
The committer status is granted based on the trust we put in a certain individuals to take care of the CloudStack project, for me that included taking the responsibility that any contributions are up to spec. I want to trust my fellow committers that they know what they are doing and i don't feel the need to second guess that by wanting to look over their code before they can commit it.
David Nalley raised a question from the Ghent Build-a-Cloud-Day about "whether or not to package the SSH key reset and password reset utilities, or whether we should focus our PW/SSH efforts on cloud-init."
Wido den Hollander voiced support for cloud-init, saying "We want CloudStack to be accepted by more and more users and they probably want to use cloud-init. cloud-init has cool Puppet and Chef plugins as well which make it very
easy to get it all up and running."
Chiradeep Vittal says he likes cloud-init, but worried that adopting cloud-init would be "hurting the investment of existing CloudStack users who have built hundreds of templates with the extant scripts."
Wido says that "the scripts should keep working" but preferred to avoid packaging the homegrown scripts and encouraging new users/new setups to go with cloud-init.
Chip says that "I'm in agreement that the existing scripts would need to remain as a supported option for quite some time. I consider things like that to actually be related to our semver version numbering, although it's not specifically our CS query API, it's a similar interface expectation."
Abhinandan Prateek forwarded a note from Bharat Kumar about changes to the way capacity is calculated in CloudStack.
I have made changes to the way capacity is calculated in Cloudstack ,
please review and comment.
I will illustrate this with an example.
let us say we have a host with
Actual Total capacity=4GB ram,
and the overcommit ratio be 2.
Total capacity= 4*2= 8GB.
Values after deploying 4 VMs with 1GB in service offering.
Allocated per vm =1GB.
now if we decrease the overcommit ratio to 1
Total Capacity = 4*1=4GB.
used Capacity = 4GB.
Available = 4-4=0. (implies 100% usage. can also go to more than 100%)
The latest master is consuming nearly 900MB of memory, according to Koushik Das.
There's some discussion as to the cause of this, and CLOUDSTACK-1168 ("Memory usage is very high") has been created. If you're testing master/4.1 and run into this problem, it'd be helpful to update the ticket with your experience and the environment you're seeeing the issue in.
Sudha Ponnaganti brought up a couple of issues on February 8th that are blocking automated testing. CLOUDSTACK-1216 has been fixed, CLOUDSTACK-1200 (Unknown column 'vm_instance.disk_offering_id' in table vm_instance, db exception shown in MS log) is still unresolved.
Joe Brockmeier announced on Friday that the first point release from the CloudStack 4.0 branch has passed its vote on email@example.com with +1 votes from Jim Jagielski, Olivier Lamy, and Alex Karasulu. No -1 or +0 votes were cast.
The release has been pushed to the mirrors and will be announced on Tuesday, February 12.
Chip Childers sent out a reminder about the release schedule for CloudStack 4.1.0 on Monday.
2013-02-28 is the end of our test phase, and should be the end of the doc finalization for the release.
We'll shift into a mode where the 4.1 branch should only be updated by me after that date (after you ask for a cherry-pick for a critical bug or translation update).
Chip also noted that there are 15 features/improvements listed as "open" for 4.1, and asked that the reporter/assignee update to "In Progress" or move the target release to 4.2 or Future, as appropriate.
John Kinsella has announced the first Bay Area CloudStack Meetup to be held in San Jose on February 20th.
- Build a Cloud Day (BACD): Full day BACD at SCALE on Friday (22 February 2013).
- SCALE 11x: Meet with CloudStack folks at SCALE (23-24 February 2013). The CloudStack project will have a booth at the event, plus a number of talks on the schedule:
- Taking the Cloud to 11 with CloudStack - Joe Brockmeier
- ApacheCon North America: ApacheCon NA is in Portland, Oregon from 26 February to 28 February. Cloud is a hot topic at ApacheCon North America and you'll find quite a bit of CloudStack content on the schedule:
- Apache CloudStack's Plugin Model: Balancing the Cathedral with a Bazaar - Donal Lafferty
- Top 10 Network Issues in Apache CloudStack - Kirk Kosinski
- Advanced CloudStack Troubleshooting using Log Analysis - Kirk Kosinski
- Scalable Object Storage with Apache CloudStack and Apache Hadoop - Chiradeep Vittal
- Getting to Know Apache CloudStack - Joe Brockmeier
- DevCloud: A CloudStack Sandbox - Sebastien Goasguen
- Powering CloudStack with Ceph RDB - Patrick McGarry
- Software Defined Networking in Apache CloudStack - Chiradeep Vittal
Status for 4.1 as of Monday, 11 February - by priority:
Of the remaining bugs for 4.1.0, 103 are currently unassigned.
No new committers or PPMC members were announced this week.
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.