The document presents an overview of the Apache Software Foundation (ASF) and its structure, emphasizing its non-profit, collaborative nature designed to foster open-source software development. It explores the OSGi (Open Services Gateway Initiative) technology, its architecture, and its integration within ASF projects like Apache Karaf and others. Additionally, it discusses project management, roles, the incubator process for new projects, and highlights the dynamic capabilities of OSGi for modular applications.

1. Apache, OSGi,
Blueprint and Karaf
Guillaume Nodet
April 12, 2011

2. Your presenter:
Guillaume Nodet
FuseSource http://fusesource.com
Apache Software Foundation Member, VP
Apache Karaf, PMC Member of ActiveMQ,
Aries, Camel, CXF, Felix, Geronimo,
Karaf, Mina, Ode, ServiceMix
Co-creator of ServiceMix, Karaf, Mina
SSHD
Member of the OSGi EEG

3. Overall agenda
The Apache Software Foundation
OSGi overview
OSGi at the ASF
Quick Blueprint intro
Apache Karaf

4. The Apache Software
Foundation
What it is and how it works...

5. Schedule
What is the
Apache Software Project
Foundation Management
A bit of The Foundation
history infrastructure
Meritocracy Other
foundation
The Foundation entities
structure
Conclusion
Roles

6. What is the Apache
Software Foundation?
Non-profit organization
Open, collaborative software
development
Independent legal entity for
donations
Means for individuals to be
sheltered from legal suits
Protect the ‘Apache’ brand

7. History
HTTPD web server from the NCSA
Community to support it
Developers called themselves the
“Apache Group”
ASF created in 1999

8. Meritocracy
Not initiated by a single person
More people attracted and started
contributing
When a person “earned” the merit,
access to the repository was granted
Scales well as newcomers are
volunteers and no power to steal

9. Foundation structure
Projects are delegated authority and
are self-governing
Board of Directors
Project Management Committees

10. Board of Directors
Manage and oversee the corporation,
its assets and resources
Technical authority assigned to PMC
Nine individuals (members), elected
every year

11. Project Management
Committees
Established and terminated by
resolution of the Board
One officer (VP) appointed by the
Board (PMC chair). Establish rules,
report to the board, perform
administrative tasks
PMC oversee legal aspects and
community health

12. Officers
Oversee the day-to-day affairs
Elected by the Board

13. Roles
user
developer
committer
PMC member
PMC chair
ASF member

14. Project Management
Collaborative and consensus-based
pocess
No single set of rules between PMCs

15. Project Management
(cont)
Communication Operation
Documentation Individuals
Decision making Confidentiality
Philosophy vs public

16. The Incubator
fitering (non technical) proposals of
new projects
help creation / infrastrucure
mentor the incubated community to
become open and meritocratic
evaluate the maturity for graduation

17. The Incubator
(cont.)
working code base
copyright donation
sponsoring member
increase diversity (long term
stability, variety of technical
visions)

18. Other entities
Infrastructure team
Attic, Labs, Legal Affairs, Public
Relations, Conferences ...

20. OSGi

21. OSGi Alliance
Formerly known as the Open Services
Gateway Initiative
Industry consortium
Defines OSGi Service Platform
Serveral expert groups

22. OSGi Architecture
Overview

23. OSGi Framework
Component oriented
Service oriented architecture
Run multiple applications
Single VM
Separate class loader per bundle
Dynamic

24. OSGi Framework
layers

25. OSGi momentum
OSGi technology has moved beyond
original target domain
Initial success story was Eclipse RCP
More recent success stories in
enterprise scenarios

26. OSGi Specifications
OSGi R4.2 released in Sept/09
Blueprint, Remote Services, Web
Applications, JNDI, JTA, JDBC, JPA
Next Core release in Q1 2011
Next Enterprise release in Q1 2012
Subsystems, OBR ...

27. Modularity Layer

28. Standard Java
Modularity Limitations
Limited scoping mechanism
Simplitic version handling
Implicit dependencies
Split packages by default
Low-level support for dynamics
Unsophisticated consitency model
Missing module concept

29. OSGi Framework
modularity support
Resolves nearly all deficiencies
OSGi bundles as a boundary for a
module
Bundle metadata explicitly declares
versioned dependencies
Framework automatically manages
bundle code dependencies
Framework enforces sophisticated
consistency rules for class loading

30. Bundle Lifecycle

32. OSGi at the ASF
Overview of the various projects

33. 88 Top Level Projects
More then 40 incubating projects

34. Classification
Non Java
Non OSGi aware
OSGi aware (provide OSGi bundles)
OSGi based

35. OSGi Based
Aries
Felix Incubator
Karaf Ace
ServiceMix Celix
Sling Clerezza
Geronimo (i.p.)

36. OSGi Aware
Abdera Directory (i.p.)
ActiveMQ Harmony
Axis HttpComponents
Camel Mina
Commons OpenEJB
CXF OpenJPA
DB Synapse

38. Blueprint
DI brought to OSGi

39. Overview
Dependency injection / IOC
Handle legacy code
Handle OSGi dynamics
Hide the OSGi API

40. Configuration
Extender pattern
XML resources
Metadata
Blueprint Bundle Metadata
XML
Blueprint Extender

41. Simple example
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0”>
<service interface=“org.poitoucharentesjug.User”>
<bean class=“org.poitoucharentesjug.impl.UserImpl”>
<argument value=“gnodet” />
</bean>
</service>
</blueprint>

42. Managers
manager
bean service-reference service
reference reference-list

45. Overview
Apache Karaf is a small OSGi based
runtime which provides a
lightweight container onto which
various components and
applications can be deployed.

46. Karaf Console
Poweful command line shell
Highly extensible
SSH access

47. Logging
Support multiple APIs
OSGi, JCL, JUL, Log4j, Slf4j
Uses a single back-end
Dynamic reconfiguration through
ConfigAdmin
Shell integration

48. Deployer

49. Provisionning
Features concept
Maven integration (plugin, url handler)
Drives OSGi SubSystems specification

50. Other
OS integration
Instances management
JAAS based security

52. gnodet@gmail.com