DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Welcome back to another exciting issue of the Apache CloudStack Weekly News. This week, 4.2.0 enters code freeze, 4.1.1 gets set for release, and some it's fourth round of voting, we welcome several new committers and look at some of the major discussions on the Apache CloudStack mailing lists, and much more.
...
The fourth round of voting is now open on the 4.2 release. This release is now in code freeze as of 7/29/13. This means that only selected updates will be done on critical and blocker bugs only. This is also a time to work on documentation and preparing for the first RC on 8/19/2013. Animesh Chaturvedi detailed out the process during code freeze.
...
Given the high number of blocker and critical and that QA is still filing many defects I will follow what Chip did for 4.1 1. Up until when we cut the first RC on (2013-08-19) committers should continue to check in fixes to 4.2 branch for blocker and critical issues. Please do any fixes as cleanly as possible (i.e., squash related commits and make sure to avoid messy merge commits as much as possible).For Contributors if you have a fix that needs to go into 4.2, please email the list with the subject tag ACS42 and note the review that contains the patch. I'll pick whichever I can, but will also rely on others with commit rights to make it efficient.
I will review all commits going into that branch, and will revert anything that's outside the scope of that I outlined above (unless there is a discussion and consensus on this list to include something else).
...
full of new features, fixes and thousands of hours of work from everyone in the community. It's important to test and cast your vote on the release. Remember that all members of the community are eligible to cast a vote and note any issues that they have with the current release candidate.
Sudha Ponnaganti has throughout the 4.2 Sudha Ponnaganti put together a list of the the current blocker and critical issues that need to be reviewed. If you have issues that have been resolved please review, test, and close out please.
Second round of voting was started on 7/25 after a new cut of the RC was compiled. The release has been tested and voted on. Chip Childers put out the results. Chip will be publishing the release this week.
...
Results:+1 binding: chip, marcus, wido, alex, / non-binding: simon
-1 non-binding: ove, nicolasBased on those results, I'll move forward with publishing the release
now.-chip
As the final code products are now final, the documentation is well underway and many sections are coming available for review. Please take the time to review, comment and file doc bugs when you find issues (yes, even documents have bugs). The document team are using the DOC tag to keep everyone up to date. Here are some docs that Radhika Puthiyetath have posted for review:
*15.7. IP Reservation in Isolated Guest Networks - https://issues.apache.org/jira/browse/CLOUDSTACK-850
*15.13. Adding Multiple IP Ranges - https://issues.apache.org/jira/browse/CLOUDSTACK-847
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.
...
...
For some time now there has been discussion around a possible replacement to our current use DocBook for our primary document editor. Sebastien Goasguen started a discussion to look at Markdown by Daring Fireball. With there being concern about how to create and maintain high quality documentation, this is an important thread to participate in for anyone interested in the release documents.
After seeing lots of frustrated people with folks I decided to try something out with markdown.
I used pandoc to convert some docbook files to markdown and I used a structure for a book based on 'The little mongodb' book.
We can generate epub and pdf using latex.See: link
There are two "books" aimed at being step by step recipes. Not long, not convoluted, single OS, etc…simple step by step.
I am still sanitizing the installation one based on 4.2 .
Comments, flames ?
Aaron Delp joined in as a part of talking cloud and especially CloudStack as part of an interview with The Register and their "Speaking in Tech" podcast series.
Aaron's section on ACS is from 17:45 to 26:00 - http://www.theregister.co.uk/2013/08/01/speaking_in_tech_episode_69/
Ilya Musayev a committer of the ACS project and founder of CloudSands project has recently announced the release of a set of pre-built management server appliances available for open use based off the ACS 4.1.1 code base. There are appliances for VMware, Xen and KVM hypervisors.
Objective: Speed up the Apache CloudStack adoption by abstracting the need of going through install process and using pre-installed package instead. Especially useful for a quick POC.
vSphere:
Short URL: link
Long URL: linkKVM:
Short URL: link
Long URL: linkXEN:
Short URL: link
Full URL: linkMinimum Requirements:
1 CPU x 2 GB of RAMTesting:
Please spend few minutes on testing these out, you can import it as a template into your ACS - power on and see the details on initial start.
I've tested vSphere and KVM version. I don't have XEN instance to try.
...
...