This talk focus on the Peergreen Deployment System and how we leverage the recent OSGi Resolver specification to build an efficient and extensible OSGi deployment framework.

1. OSGiTM Resolver in
action
Peergreen Deployment System
Guillaume.sauthier@peergreen.com @sauthieg

2. © 2013 Peergreen, Confidential & Proprietary
285 seconds left
What do we do in Peergreen?
I’ll talk about …

3. © 2013 Peergreen, Confidential & Proprietary
270 seconds left
We need
(for deployment at least …)
Efficiency
(multi-core architectures)
Heterogeneity
(different kind of artifacts) Ease of use

4. © 2013 Peergreen, Confidential & Proprietary
255 seconds left
Specification:
OSGi Resolver 1.0
• Part of OSGi Enterprise R5
• Build relationships
• Implemented in Apache Felix
Requirement
“I want …”
Capability
“I offer …”Resolver
Namespace + LDAP filter Namespace + attributes

5. © 2013 Peergreen, Confidential & Proprietary
240 seconds left
Resolver production
• Wire(s) (satisfied requirements)
• Or Exception (unsatisfied requirements)
Requirement CapabilityWire
Need Interpretation
(use resources, make decisions, …)

6. © 2013 Peergreen, Confidential & Proprietary
225 seconds left
Peergreen
Deployment System Goals
Efficient (multi-threading)
Resource Neutral
Plug-able architecture
Artifact Model

7. © 2013 Peergreen, Confidential & Proprietary
210 seconds left
Artifacts
Name + URI
(File, Directory, Maven, …)
Resolver Resource
(provides capabilities)

8. © 2013 Peergreen, Confidential & Proprietary
195 seconds left
Facets
Specialized View
Artifact Decoration
(Webapp, Bundle, Configadmin, …)
Dictates Lifecycle
(phase sequence)
Express Capability
(when installed)

9. © 2013 Peergreen, Confidential & Proprietary
180 seconds left
Phases
Execution Controller
Logical Steps
(read-xml, install, start, stop, …)
Resolver Client
(find compatible processors)
Pipeline / Parallel
(execution)

10. © 2013 Peergreen, Confidential & Proprietary
165 seconds left
Processors
Unit of Work
Chained Together
(Transformer, Facet producer, …)
Resolver Resource
(requirements, capabilities)

11. © 2013 Peergreen, Confidential & Proprietary
150 seconds left
High level view
Discovery Phase
• Download
• Scan
• Find
dependencies
Execution Phase
• Facet’s
lifecycle
• Concurrency

12. © 2013 Peergreen, Confidential & Proprietary
135 seconds left
@bundle
Execution phase
Concurrent Execution
(per facet lifecycle)
Multiple Artifacts
(sharing same lifecycle)
Facet Decoration
(on the fly)start
install
@webapp
start
configure
read-xml

13. © 2013 Peergreen, Confidential & Proprietary
120 seconds left
Processor Resolution
Per Phase
Resolving bound processor’s requirements
against artifact’s capabilities
Satisfied processors are executed

14. © 2013 Peergreen, Confidential & Proprietary
1 23
105 seconds left
Interpretation
Missing Capabilities
(unsatisfied processors)
B
A
DC
E ?
Requires Sorting
& Filtering
(linearize graph)
E C B

15. © 2013 Peergreen, Confidential & Proprietary
90 seconds left
Extensibility
OSGi Services
Facet addition
Facet Lifecycle
(phases definition)
New Processors

16. © 2013 Peergreen, Confidential & Proprietary
75 seconds leftExample

17. © 2013 Peergreen, Confidential & Proprietary
60 seconds left
Model
Query-able
Useful for Reporting
Introspection capabilities
(facets, processors, execution times)
Store relations
(transformations, creations, dependencies)

18. © 2013 Peergreen, Confidential & Proprietary
45 seconds left
plan
plan
web ejbjar
mvn
bundle
Artifact Tree
Report
Meta-information
(root, report, …)

19. © 2013 Peergreen, Confidential & Proprietary
30 seconds left
Benefits
Extensibility
(new requirements and capabilities)
Dynamism
(processors, facet and phases)
Ease of Use
(extension development, deployment reporting)
Efficiency
(maximize concurrency)

20. © 2013 Peergreen, Confidential & Proprietary
15 seconds left
Thanks
Follow Us
(@peergreeninfo)
Get your copy
(M1 is there, M2 soon)
www.peergreen.com