Yesterday was the first birthday of Apache Karaf.
We made a conference call between all Karaf developer. It was funny to put a voice on a name 🙂
It was very interesting even if unfortunately some key players were not available such as Guillaume or Achim.
Past Year Review
First, we made a review about this past year. Jamie had prepared a very complete review:
We can note that the Karaf downloads increased a lot with the 2.2.0 release. It was a really expected release and it has been included in a lot of projects both open-source (ServiceMix, CXF, Camel, Geronimo, …) and enterprise (Talend, Fuse, …).
We can conclude that the Karaf visibility and adoption have quickly increase and Karaf is now a important container in the OSGi eco-system.
We also share our vision about the Karaf future.
We identified the following topics:
- Our first focus will be the Karaf 3.0.0 release. It means that Karaf 2.1.x branch will turn in EOL (End Of Life), the Karaf 2.2.x branch will be in maintenance mode. This release will be a major release as it includes a lot of new features and enchancements.
- Create custom Karaf distribution is not really easy right now and some projects have to change low level configuration files. We are going to work on Karaf dsitributions and profiles, by providing tooling (such as maven plugin).
- Add a premium OSGi container, Karaf should provide a complete and “sexy” web console. The current web console (powered by Felix console) will be maintained and suported, but we are going to work on a new one, highly extendible (by a plugin mechanism) and supporting branding. We are going to use a modern component-oriented framework such as Wicket.
- We moved forward in the clustering area with Karaf Cellar sub-project. It’s clear that clustering, clouding, and farming are features expected by the enterprises. We are going to work on this topic by extending Cellar.
- Related to the previous topic, provisioning is a must have. Apache ACE and Apache Karaf will work together to provide an enterprise provisioning solution.
- Cellar was the first Karaf sub-project. Related to provisioning, Karaf Cave OBR could be a new Karaf sub-project. The purpose is to provide an OBR server implementations including advanced features (P2P, REST interface, multi-repositories, etc).
I wrote down the concall minute notes:
It’s clear that we should schedule this kind of concall every two or three months. It allows us to make a kind of checkpoint and drive the Karaf roadmap.