Another busy week in Apache CloudStack land! Javelin has been merged with master, the 4.1 branch has been created, and the 4.0.1-incubating release has passed its second round vote to go on to the IPMC vote.
The Javelin branch has been merged into master by Kelven Yang. Kelven has noted that developers should increase the amount of memory available to the JVM if running the management server under Maven:
For linux/Mac users
For Windows users
Add similar settings to windows environment settings (via Windows control panel)
Following the Javelin merge, Chip Childers has created the 4.1 branch, and has asked committers "to respect the feature and improvement freeze in that branch. Bug fixes, doc updates and other release stabilization activities are obviously expected." Chip also says that committers should continue committing directly to the 4.1 branch until code freeze. (Code freeze, excepting fixes for blocker bugs and so forth, is on February 28th.)
If you're a non-committer and wish to send in a patch against 4.1.0, send in a patch built against the 4.1 branch. Chip says:
Committers taking these fixes should also consider applying them to master. If there are conflicts in master (which may happen, as there were a
couple of code-base refactoring activities, like switching packages from com.cloud to org.apache.cloudstack), apply the fix into 4.1 anyway, and inform the submitter that the patch has conflicts with master to get that sorted out (or you can fix it yourself).
The 4.0.1-incubating release has passed the vote on cloudstack-dev, and is now in the 72-hour IPMC vote. Going into the vote on firstname.lastname@example.org, the release artifacts already have 3 +1 mentor votes, so it should pass barring any -1 votes.
With the feature freeze in place, it's time to get docs into shape and start getting things ready for translations. Sebastien Goasguen has created a new /pot directory with the .pot (portable object templates).
Sebastien notes that contributors need to remember the 50-character limit for XML filenames, as Transifex doesn't support longer file names. Contributors will also need to run publican update_pot when updating doc files and/or creating new files.
Hugo Trippaers sent out an update about the discussion on packaging for 4.1. Hugo says the main goal for redoing the current way of packaging CloudStack is to get "rid of ant and waf completely." The secondary goal "is to create a reference set of packages which in itself should be enough to get anyone going with CloudStack, but will hardly depend on the underlying distro. Real distro specific stuff should be handled by packagers from those distros. We just aim to provide a reference implementation."
Hugo also says that the plan is to rename the packages "to make it perfectly clear what somebody is installing." That's going to change the location of a number of files, but Hugo says "we intend to include symlinks for backwards compatibility."
The planned packages for now are cloudstack-management, cloudstack-agent, cloudstack-common, cloudstack-cli, cloudstack-docs, cloudstack-awsapi and
cloudstack-usage. You might already have seen these names in some of the checkins.
One of the side-effects of the new packaging plan is that CloudMonkey may not be installed with the RPMs, but instead require that admins use PIP to grab CloudMonkey.
Mice Xia proposed merging the VM Snapshot branch to master ahead of the 4.1 branching/feature freeze on January 28th. However, there were a number of questions about the feature's implementation and consensus was not reached in time for the 4.1 branch's creation.
On the plus side, this is why we have time-based releases. While it will delay inclusion into CloudStack slightly, the feature will be well-poised to go into 4.2 and the additional attention that the discussion has raised will likely make it that much better a feature when merged to master. It also means that a single feature won't delay the 4.1 release, which already has quite a lot of improvements and new features that CloudStack users will want to have ready when it's scheduled for release.
Rohit Yadav has proposed deprecating CloudStack's non-RESTful APIs and API server over a reasonable timeline. The reaction has been positive, and Min Chen has offered to share an architecture design that's in-progress, when it's ready.
David Nalley has sent out a request for help reviewing his runbook, which is an opinionated guide to setting up a simple CloudStack install on a single CentOS 6.3 server using KVM. Other CloudStack users and contributors have expressed interest in creating similar runbooks for Ubuntu-based systems.
- India User Group Meet-up: Citrix, ShapeBlue, and CloudByte are combinedly organizing a CloudStack India User Group Meetup in Bangalore (5 February, 2013).
- Build a Cloud Day (BACD): Full day BACD at SCALE on Friday (22 February 2013).
- CloudStack Booth at SCALE: Meet with CloudStack folks at SCALE (23-24 February 2013), also Joe Brockmeier is speaking about CloudStack at SCALE.
Be sure to check the list of 4.1.0 bugs to see if there are any open issues assigned to you, or any unassigned issues that you could take on.
The Apache CloudStack project is pleased to welcome Koushik Das as a committer this week. Well done, Koushik!