Eclipse Cyclone

Basics
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project: 
Background: 

Acceptance of Eclipse Cyclone as a recognized (data-sharing) standard in the Industrial Internet of Things (IIoT) (see http://www.iiconsortium.org/IIRA.htm and http://www.iiconsortium.org/IICF.htm for a detailed assessment of this) really calls for an opensource-based solution and we feel that Eclipse IoT can provide the thriving ecosystem that will make this project a huge success

In the scope of this project we (ADLINK) will contribute our proven DDS solution as a starting point for a true open-source DDS offering with applicability in a wide range of existing and upcoming IoT applications.

Scope: 

This project implements the OMG Data Distribution Service (DDS) specification (see http://www.omg.org/spec/DDS/ ) and the related specifications for interoperability (see http://www.omg.org/spec/DDSI-RTPS/ )

 

Description: 

With 'DATA' being 'the currency of the IOT', having a proper data-sharing technology will be a key-asset in any IOT-platform. The OMG DDS standard is recognized as a highly applicable standard for reliable and robust data-sharing in business- and mission-critical environments (see http://www.iiconsortium.org/IIRA.htm and http://www.iiconsortium.org/IICF.htm ) and with that a great fit with the Eclipse-IOT ecosystem.

 

Why Here?: 

Eclipse Cyclone offers unique data-sharing capabilities compared to the already existing Eclipse solutions (i.e. for messaging).

Its data-centric architecture (where data has RDBMS-like structure and relations rather than 'blobs' as typically used in lower level messaging products) combined with the capability to 'annotate' the data(-models) with fine-grained QoS properties (for reliability, urgency, persistency etc.) provide unrivalled functional and non-functional propoerties for time- and mission/business-critical IOT-systems.

With a history of proven applicability in the military C4I domain (that are not so much unlike upcoming large-scale IOT-systems where you can also distinguish between planning-, awareness- and execution-grids that all impose specific requirements w.r.t. interoperabillity, high-volume data-sharing and deterministic/real-time data-access) we are confident that  starting from day-1 this offering can significantly reduce the complexity of many IOT-systems and with that reduce their integration efforts and risks. 

Furthermore we are confident that the Eclipse-IOT ecosystem will benefit even more by active participation in the evolution of this technology and the (OMG-)standard its based upon.

Project Scheduling: 

Initial contribution: immediate after project-acceptance to allow IP-review by the IP-team: A 3rd party software list will be provided immediately, code can be expected within 1 month of project acceptance

Future Work: 

The following functionality will be added in the next 12 to 18 months:

  • support for the extensible data-types specification (OMG DDS-Xtypes rev 1.2)
  • support for the interoperable DDS security specification (OMG DDS-Security rev 1.0)

​Furthermore we foresee a flow of tools and additional-features and integrations from our commercial offering towards opensource as the need for them grows by the community and its uptake of DDS. Concrete examples of this are our evolving 'Vortex Insight' tooling for monitoring DDS-based systems and prototyped integrations with 3rd party tools such as apache-spark/storm, node-red and freeboard (see http://prismtech.github.io/ which will be transferred to Eclipse too)

From our experience of IOT projects, we foresee webinars to the community and use case stories, as well as sponsoring events and presenting at them. We would also like to contribute plugins to other eclipse IOT projects to enable users to benefit from DDS

People
Committers: 
Mentors: 
Source Code
Initial Contribution: 

The initial contribution will exist of the Vortex OpenSplice code-base (v6.8): a polyglot DDS implementation covering all DCPS-profiles and related QoS-policies​

Apart from some third-party libraries, all code is currently owned by ADLINK and there currently exists a modest (1000+ members) community around its Community Edition (based on the v6.7 codebase, see http://www.prismtech.com/dds-community) which obviously will migrate to Eclipse too.

Source Repository Type: