Happy birthday Apache Karaf

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:

http://icodebythesea.blogspot.com/2011/06/apache-karaf-year-one-in-review.html

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.

Karaf Future

We also share our vision about the Karaf future.

We identified the following topics:

  1. 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.
  2. 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).
  3. 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.
  4. 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.
  5. Related to the previous topic, provisioning is a must have. Apache ACE and Apache Karaf will work together to provide an enterprise provisioning solution.
  6. 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:

https://cwiki.apache.org/confluence/display/KARAF/Apache+Karaf+First+Birthday+Meeting+%282011-06-16%29

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.

Comments

Post a Comment

Popular posts from this blog

Quarkus and "meta" extension

Quarkus is a great Java framework with a large ecosystem thanks to the extensions . Basically, if using Maven, your pom.xml contains the list of the extensions you want to use, meaning something like this: ... <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-grpc</artifactId> </dependency> <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-opentelemetry</artifactId> </dependency> ... It can quickly become large, and sometime you can have "conflict" between extensions (for example if you mix in the same dependencies set reactive and non reactive extensions). Quarkus "meta" extension To simplify the dependencies for the extensions you want to use (especially if it's basically the same extensions in all your services), you can create your own "meta" extension. This extension doesn't contain actual code, it "wraps" other exten
Read more

Getting started with Apache Karaf Minho

Image
Apache Karaf Minho Apache Karaf Minho is a new runtime, completely created from scratch. The objectives are: super easy to use and run ligtning fast, including GraalVM support Kubernetes compliant to be easily used on the cloud helping to optimize cloud costs by supporting applications colocation providing turnkey services allowing you to create Minho applications in a minute Minho is composed by: minho-boot is the core of Minho. It contains the runtime launcher and the core services (service registry, lifecycle service, configuration service, ...). minho-* services provided additional functionnalities in the runtime. You can use these services to create your own services, it's also where you will find the services managing sepcific kind of applications, allowing colocation. minho-tooling optionally provide convenient tools to create your own runtime. It includes minho-maven-plugin for instance. In this blog post, we will take a quick tour on A
Read more

Apache Karaf Minho and OpenTelemetry

Image
Telemetry is an important part of a software stack, especially on distributed system (where services call each others). OpenTelemetry is a CNCF project coming from OpenTracing and OpenCensus. It provides API to easily instrument your code and tools to collect and export telemetry data (metrics, logs and traces). Before going into how to use OpenTelemetry with Minho, we have to understand some key concepts: Span is a single building block representing an operation or some unit of work that you want to capture. They are capable of standing on their own, referencing (or following) from other spans, storing metadata, tags, etc. Trace is a visualisation of the life of a request (or series of other operations) that is made up of one or more spans. This collection of spans work together to paint a picture of the overall request, allowing you to easily reconstruct what happened within each span, etc. SpanContext is a wrapper of key values pairs that associates a trace to one or mor
Read more