Showing headlines posted by jzb

Apache CloudStack has graduated from the Apache Incubator! The Apache Software Foundation (ASF) board met on Wednesday (March 20) and voted in favor of the project's graduation from the incubator. The official announcement was released on Monday, March 25, 2013.

Of course, that's not all that's happened. in the past week. Work on the 4.1.0 release continues, with the first RC date slipping slightly due to the number of blocker bugs. The good news is that a lot of progress has been made on the blocker bugs in the past week, so things don't appear to be too far behind.

The board voted last week, but the announcement came out today, so it’s officially official: Apache CloudStack is now a top-level project under the Apache Software Foundation (ASF). In the grand scheme of things, this may not sound like a big deal – the ASF announces new TLPs pretty often, and Apache currently boasts more than 100 TLPs. But a fair number of projects don’t make it, and the amount of work required for a project to go from incubation to graduation isn’t trivial.

The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 150 open source projects and initiatives, announced today that Apache CloudStack has graduated from the Apache Incubator to become a Top-Level Project (TLP), signifying that the project's community and products have been well-governed under the ASF's meritocratic process and principles.

Big news this week: Apache CloudStack has passed major milestones towards graduation, major progress on bugs against 4.1.0, discussions about integrating the Palo Alto firewall with CloudStack, and getting Eclipse and Maven to play nice for developers. Some interesting posts from members of the Apache CloudStack community as well.

This week the project started the vote to determine whether the Apache CloudStack project feels ready to self-govern, discussions were held about implementing BVT (and how), and the PPMC announced its consensus for the proposed PMC chair. In addition, several technical discussions for features and processes within the project, and discussion on the -marketing list about the design of the Web site.

This week, a vote on updating the project bylaws, fixing the "Tomcat situation" after 4.1, and discussions around the support lifecycle. Some respectable progress in knocking out major and blocker bugs for 4.1.0 as well. The project also welcomes two new PPMC members and three new committers.

There’s no shortage of talks I wanted to attend at ApacheCon North America, but I was determined not to miss Kirk Kosinski’s troubleshooting talks on Tuesday. Kirk presented two talks, one on the top 10 networking issues, and another on using logs to diagnose issues with CloudStack.

This week, interesting discussions on the Java version(s) to be supported by CloudStack, updates on translation, and database changes. Also discussion on the next CloudStack Collaboration Conference, and more. Work on 4.1.0 continues, and there's much to be done before it's ready to ship.

Another busy week on -dev. This week, discussions on whether to graduate to a TLP, the whens and hows of merging, database changes for 4.1 and master, and documentation.

The Apache CloudStack project is pleased to announce the 4.0.1-incubating release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is a minor release in the 4.0.0 branch, which contains fixes for more than 30 bugs.

In the past week, the 4.0.1-incubating release passed its VOTE on the general@incubator.apache.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.

The Apache CloudStack project is pleased to announce the 4.0.0-incubating release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is the first release from within the Apache Incubator, the entry path into the Apache Software Foundation (ASF).

A configuration vulnerability has been discovered in CloudStack that could allow a malicious user to execute arbitrary CloudStack API calls, such as deleting all VMs being managed by CloudStack. John Kinsella of the Apache CloudStack PPMC announced the vulnerability on Sunday. The issue does have a workaround that can be applied immediately.

Donnie Berkholz of RedMonk has argued that the “infrastructure stack” needs an Affero LGPL to prevent the dreaded fragmentation. Do we? I’m not convinced that it’s necessary, desirable, or likely to catch on at all.

When looking to the future of technology, it’s helpful to take a look at existing technologies and see if patterns emerge – and if lessons from today’s ecosystem can be applied to tomorrow and beyond. To that end, we think that there’s no better model for open cloud to study than Linux and its ecosystem. Not just the kernel, of course, though the kernel holds many fine lessons for any student of open development and community practices. But also, the larger ecosystem of open source and vendors (notably distributions) that have formed around the kernel.

Committers can submit patches directly to the Apache CloudStack (incubating) repository, but non-committers need to follow a few more steps. Don't worry, it's easy. Here's how.

A lot has been happening since CloudStack was proposed as an project for Apache and accepted as an incubating project. Since April, a lot of work has been going on to do things “the Apache way” and prepare for the first release out of the Apache incubator. If you’re not on the developer mailing list, though, it might not be entirely clear what’s going on – or when you can expect the first release.

The Oracle v. Google trial is kind of hard to miss this week, and it's dragging out all kinds of nuggets of information. One of the best this week? Oracle's CEO unintentionally taking a jab at his own company's enterprise Linux strategy.

FUD is a lot like commodity open source software. It just keeps moving up the stack. A decade ago, the FUD was all about operating systems and database software. Now? It's migrated up to the cloud stack. FUD may be mobile, but it hasn't gotten any prettier.

If you don't like the weather in Missouri, wait 10 minutes – it'll probably change. Likewise, if you don't like the way that the Cloud industry is aligned, just give it a little time. It'll probably change, too. The latest shift? Citrix is set to propose CloudStack to the Apache Software Foundation (ASF) as an incubator project.