Notes from the workshop (taken by BJ Hargrave)

Attendees

Peter Kriens <>
Benjamin Reed <>
Dimitar Valtchev <>
Andreas Oberhack <>
Peter Neubauer <>
Wolfgang Gehner <>
Tim Diekmann <>
Dieter Hemkemeyer <>
Klaus Jank <>
Adam Harris <>
Thomas Odenwald <>
Jay Indurkar <>
Jon Bork <
Anurag Gupta <>
Leigh Williamson <>
Eric Jönsson <>
Jim Colson <>
Seth White <>
Olivier Caudron <>
Hal Hildebrand <>
Eric Newcomer <>
Ryutaro Kawamura <>
Andreas Kraft <>
Jon Bostrom <>
BJ Hargrave <>
Vic Magnotti <>

Introductions

Peter Kriens starts the meeting at 0900.

We go around the room and the attendees introduce themselves and their interest in participating in the workshop.

Position Statements

Several attendees present a position statement on their interest/goals for OSGi technology in the enterprise space.

SAP

• Lifecycle management - complete
  • device profiling
  • service profiling
• Support
  • remote: management, debug, monitoring, etc.
• Extensibility
• Network connected awareness
• Data sync/persistence
• Internationalization
• Connectivity - web services, REST
• Security - security, bundle certification
• User context awareness
• UI integration - w/o specifying a UI API

Andreas Oberhack

• distributed container model
• load balancing
• transparent fail over
• distributed registry management
• context awareness
• RAS
• security - who is calling which service when
• provisioning/versioning
• application lifecycle management (development)
• common services
  • scheduling
  • date/time
  • sequencing
• protocol bindings (like JBI)
• aspects

Siemens

• extension of OSGi service model
• multiple containers in one logical container
• QOS - performance framework
• enhanced security
  • authentication
  • authorization
  • inter and intra container
• large scale deployment support
  • multi node
  • update/patch support
• SCA and OSGi
  • OSGi bindings
  • OSGi implementation type
  • OSGi-based SCA container
• Whats missing
  • SCA based component model
    e.g.remote services vs. components
  • improved lifecyle and dependency management
  • inter conatiner communications

Oracle - SCA as a topology between containers

• Daidalos project
  • inter container communications API
  • concepts and API for dependability mechanism
  • generic service discovery concept

Peter Neubauer

• development lifecycle
  • building systems, tools
• repository of components
  • licenses
  • services
  • QOS
  • discovery
• testing dependencies
• "life cycle outside of core runtime"
• aspects
• fluid computing
  • transfer of state and bundle(code)
  • for failover
• IoC choices
  • best practices

SAP - best practices for different domains
Nokia - decouple UI from services
BJ - CC/PP target platform details

IBM

• Need to establish enterprise EG to have a forum for this work
• distributed frameworks
• multi process
• "ESB"
• symmetry important
• dont bloat
• non functional requirements
• integration
  • legacy components
  • other languages - multi-lingual
• scope
  • servers
  • desktop - e.g. Eclipse RCP
  • both??

Peter Neubauer - grouped bundles at runtime
BJ - service scopes?
Intel - legacy coexistence is key
Intel - dependencies on lower level things: os drivers, os patches
Peter Neubauer - need a standard, clean way to deploy an OSGi runtime on a system
IONA - SCA and OSGi?
Oracle - SCA takes all the dynamic discovery out of SOA -> development time discovery
Nokia - Mentions OSGi has permission to create java api specifications but OSGi is not limited to Java language

<break>

Spring OSGi work overview

Hal Hildebrand gives an overview of the Spring OSGi? work.

Position Statements (cont)

Yahoo

• Grid computing/utility computing
• batch jobs
• failure isolation

Brainstorming Discussion

Intel - descriptive metadata to allow bundles to state platform dependencies

IONA - asks about JavaME as a limit to what OSGi can specify

BJ - OSGi tries to specify API to work in JavaME but that is not a fixed rule and can be deviated from

Oracle - asks for more information on distributed services ideas previously discussed

BJ - Need to add a new primitive mechanism to OSGi service model:

• around advice for publish and find and bind
• allow services to be easily provided by
  • other OSGi frameworks
  • other languages
  • web services
  • ...
• Can be used to inject interceptors around arbitrary services

Oracle - JNLP integration

Nokia - wants to see OSGi define a replacement for the applet model - browser based

Oracle - JVM/JRE - OSGi interaction/integration

• bootstrap pain, start up etc.
• what would be differenct if you knew the JVM would be running OSGi?

<lunch>

Organizing and Prioriting

Peter Kriens reviews ideas collected from the morning's discussion.

Grouped ideas into related groups.

Discussed the grouping and refined the grouping

Within each group, the attendees voted for their top 2 items. This yielded a ranking within each group.

Then the attendees voted for their top three groups.

<break>

The results of the organization and prioritization can be found here.

OSGi organization overview

BJ presented on overview of the OSGi organization and the technical process uses to develop specifications, reference implementations and test suites.

Draft Charter

A draft charter for an enterprise expert group was presented and discussed. More work is need on the technical scope based upon the prioritized requirements. This would be done after the workshop.

Next Steps

It was agreed to create a mailing list and a wiki to continue disussion and finalization of the expert group charter leading up formation of the expert group within OSGi.

Attendees who were not currently OSGi members were encouraged to begin efforts to join OSGi to participate in the expert group once formed.