OSGi Subsystems - EclipseCon Europe 2013 |

OSGi Subsystemsfrom theory to practiceGlyn NormingtonEclipse Virgo Project LeadSpringSource/VMware

1

@glynnormingtonOSGi Subsystems

Software rots

2


modularity helps

3


but ...

4

@glynnormingtonOSGi Subsystems 5

A clean design


without enforcement


works fine for a while


then starts to decay


and soon


the rot sets in


and spreads


and worsens


until the original design


has gone.


OSGi Subsystems to the rescue

15


Subsystem: identified manageable optionally scopedgroup of bundles

16


subsystemsspec

17


subsystemsreference

implementation

18


Now some theory

19


and practice

20


followed by

21

•getting started• the future


TheorySubsystem Types

22


Feature Subsystems

Feature

bundle

bundle bundle

bundle

Scoping:•None

23


Feature Subsystems

Feature

bundle

bundle bundle

bundle

24

A depends on B

bundle Bbundle A

• bundle• package• capability• service

Notation


Feature Subsystems

Feature

bundle

bundle bundle

bundle

Scoping:•None

25


Application Subsystems

int x;{ int y;}

26



Application

bundle

bundle

bundle

bundle

Scoping:•No exports•Automatic

imports

27

{ }


Composite Subsystems

Composite

bundle

bundle bundle

bundle

Configurablescoping

28


PracticeSubsystem Types

29


Feature Subsystems

Useful for:

• Grouping dependencies

• Sharing infrastructure

• Avoiding uses constraint failures

Feature

bundle

bundle bundle

bundle

30



Useful for top layer of the system

Avoid duplicating contents

• Reduces sharing

• Complicates update

• Leads to resolution errors

Application

bundlebundle

Feature

bundlebundle

Application

bundlebundle

31


Composite SubsystemsUseful for special infrastructure

Not for general use

• Complex

• Can duplicate infrastructure

• extenders

• management bundles

Composite

bundle

bundle bundle

bundle

32


bundlespackages

capabilitiesservices

services

kernel

user region compositesubsystem


TheorySubsystem Content and

Dependencies

34


Subsystem Content• By value in a subsystem archive

or

• By reference to a repository

35


Dependencies

• Subsystem content dependencies

• Installed from repository

36


PracticeSubsystem Content and

Dependencies

37


Subsystem Content (by value)

• Easy to deploy

• Limits sharing

• Harder to update

38


Repository Content

• Convenient during development

• Avoids bloat

• Generally preferable

39


TheoryNested

Subsystems

40


Nested Subsystems• So far all subsystems have been

children of the ‘root’ subsystem

Root

Application

bundlebundle

Feature

bundlebundle

Application

bundlebundle

41


Nested Subsystems

• Unlimited nesting

• Sharing determined by the child

42


PracticeNested Subsystems

43


Nested Subsystems• Features useful for grouping other subsystems

Root

Feature

Application

bundle

bundle

bundle

Application

bundle

bundle

bundle

bundle

44


Nested Subsystems• Nested features useful for logical grouping

Root

Application

bundlebundle

Feature

bundlebundle

Root

Feature

bundlebundle

Feature

bundlebundle

45


Nested Subsystems• Nested applications useful for scoping

Root

Application

bundlebundle

Application

bundlebundle

bundle

46


More Theory

47


Subsystem States

48

installing

installed uninstalling

resolving resolved

starting stopping

active

uninstalled

install failed

install

start

start

stop

uninstall

uninstall


RegionsRegion, group of bundles:

• scoped subsystems

• root subsystem

Directed graph; arcs are filters

Region context bundle

49


Getting Started

50


Aries Subsystems

on Virgo kernel

https://github.com/glyn

51






Feature

52

Subsystem-SymbolicName: hello.feature.subsystem

Subsystem-Type: osgi.subsystem.feature

Subsystem-Content: hello


Application

53

Subsystem-SymbolicName: hello.application.subsystem

Subsystem-Type: osgi.subsystem.application

Subsystem-Content: hello


Composite

54

Subsystem-SymbolicName: hello.composite.subsystem

Subsystem-Type: osgi.subsystem.composite

Subsystem-Content: hello;version="[1,1]"

Import-Package: org.osgi.framework


Nested Subsystem

55

Subsystem-SymbolicName: hello.nested.composite.subsystem

Subsystem-Type: osgi.subsystem.composite

Subsystem-Content: hello;version="[1,1]",

hello.application.subsystem;

type="osgi.subsystem.application";

version="[0,0]"

Import-Package: org.osgi.framework


Region Digraph

56

kernel

user region

application composite nested composite

application


Alternatives

57


Technology Stack

58

Equinox region bundle

Aries Subsystems Virgo Kernel


VirgoStandard Virgo Equivalent

Feature Unscoped plan

Application Scoped plan or PAR

Composite User region

Nesting Nested plans

Repository Repository

59


Equinox Region Support• org.eclipse.equinox.region

• RegionDigraph service

• Persistence

• JMX mxbeans

60


Back to software rot

61


Subsystems

62


guide evolution

63


and discourage rot.

64


The Future

65


Future Work Items

66

Spec topics

•Extenders•Weaving and dynamic imports•Service dependency determination•Thread context class loaders•Config Admin

Tooling support


ThanksJohn Ross - Aries SubsystemsGraham Charters - Subsystems spec


OSGi R5 Enterprise Specificationhttp://www.osgi.org/Download/Release5

Arieshttp://aries.apache.org/

Aries Subsystems on Virgo Kernelhttps://github.com/glyn

Virgohttp://www.eclipse.org/virgo

Equinox Region Bundlegit://git.eclipse.org/gitroot/equinox/rt.equinox.bundles.git

68

http://www.osgi.org/Download/Release5

http://www.osgi.org/Download/Release5



http://www.eclipse.org/virgo/documentation/

http://www.eclipse.org/virgo/documentation/


Questions?

69

OSGi Subsystems - EclipseCon Europe 2013 |

Documents

Transcript of OSGi Subsystems - EclipseCon Europe 2013 |