Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "IoT/IoTServerPlatform/Meetings"

(May 20, 2015)
 
Line 1: Line 1:
 +
 +
= June 4, 2015 =
 +
 +
Time: 3pm CEST / 9am EDT / 6am PDT
 +
 +
== Dial-in details ==
 +
 +
Google Hangouts:
 +
* Join the video/audio call [https://plus.google.com/hangouts/_/calendar/a2FydGJlbkBnbWFpbC5jb20.ga22lodv6ruul8krdkegfcalec?authuser=0 here]
 +
* [https://www.google.com/calendar/event?action=TEMPLATE&tmeid=Z2EyMmxvZHY2cnV1bDhrcmRrZWdmY2FsZWMga2FydGJlbkBt&tmsrc=kartben%40gmail.com Add the event to your calendar]
 +
 +
 +
 +
= May 20, 2015 =
 +
 +
Time: 3pm CEST / 9am EDT / 6am PDT
 +
 +
== Dial-in details ==
 +
 +
* North America 1-866-569-4992
 +
* Germany 49-692-2224-6059
 +
* France 33-(0)-17-070-8535
 +
* UK 0800-033-7806
 +
* Switzerland 41-44-580-2115
 +
* Sweden 46-85-063-8386
 +
* Italy 003-902-3604-8268
 +
Participant conference extension: 713, then enter pin 68764
 +
 +
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
 +
 +
== Agenda ==
 +
 +
* Review architecture draft
 +
* Map components to existing open source projects and identify what needs to be developped
 +
 +
== Participants ==
 +
 +
* Benjamin Cabé
 +
* Ian Skerrett
 +
* James Kirkland
 +
* Kai Hudalla
 +
* Steffen Evers
 +
* Julien Vermillard
 +
* Andrea Ceiner
 +
 +
 +
== Methodology ==
 +
 +
* Drafting business and technical context
 +
* What are the surrounding systems?
 +
 +
* ARC42
 +
** Contextual views
 +
** Then building blocks
 +
*** White box view
 +
*** Underlying components as black boxes
 +
 +
* Other initiatives to look at: OneM2M, Open Interconnect Consortium (OIC)
 +
 +
* Two goals:
 +
** Gap Analysis
 +
** Recommendations to integrate with existing open source stacks
 +
 +
== Misc topics / Questions ==
 +
 +
* Are there different business applications we are targeting?
 +
* Next meeting over Google Hangouts
 +
 +
== Next steps ==
 +
 +
* Add next level of details (ie building blocks) for the "IoT Server Platform"
 +
* Andrea to add SIM Management details
 +
* Plan a meeting at EclipseCon France (Benjamin)
 +
 +
 
= May 7, 2015 =  
 
= May 7, 2015 =  
  
Line 79: Line 154:
 
* Kai Hudalla has volunteered to help sketch a high level architecture of the server solution
 
* Kai Hudalla has volunteered to help sketch a high level architecture of the server solution
 
* Next meeting: May 20, 3pm CEST / 9am ET / 6am PT
 
* Next meeting: May 20, 3pm CEST / 9am ET / 6am PT
 
= May 20, 2015 =
 
 
Time: 3pm CEST / 9am EDT / 6am PDT
 
 
== Dial-in details ==
 
 
* North America 1-866-569-4992
 
* Germany 49-692-2224-6059
 
* France 33-(0)-17-070-8535
 
* UK 0800-033-7806
 
* Switzerland 41-44-580-2115
 
* Sweden 46-85-063-8386
 
* Italy 003-902-3604-8268
 
Participant conference extension: 713, then enter pin 68764
 
 
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
 
 
== Agenda ==
 
 
* Review architecture draft
 
* Map components to existing open source projects and identify what needs to be developped
 
 
== Participants ==
 
 
* Benjamin Cabé
 
* Ian Skerrett
 
* James Kirkland
 
* Kai Hudalla
 
* Steffen Evers
 
* Julien Vermillard
 
* Andrea Ceiner
 
 
 
== Methodology ==
 
 
* Drafting business and technical context
 
* What are the surrounding systems?
 
 
* ARC42
 
** Contextual views
 
** Then building blocks
 
*** White box view
 
*** Underlying components as black boxes
 
 
* Other initiatives to look at: OneM2M, Open Interconnect Consortium (OIC)
 
 
* Two goals:
 
** Gap Analysis
 
** Recommendations to integrate with existing open source stacks
 
 
== Misc topics / Questions ==
 
 
* Are there different business applications we are targeting?
 
* Next meeting over Google Hangouts
 
 
== Next steps ==
 
 
* Add next level of details (ie building blocks) for the "IoT Server Platform"
 
* Andrea to add SIM Management details
 
* Plan a meeting at EclipseCon France (Benjamin)
 

Latest revision as of 08:29, 4 June 2015

June 4, 2015

Time: 3pm CEST / 9am EDT / 6am PDT

Dial-in details

Google Hangouts:


May 20, 2015

Time: 3pm CEST / 9am EDT / 6am PDT

Dial-in details

  • North America 1-866-569-4992
  • Germany 49-692-2224-6059
  • France 33-(0)-17-070-8535
  • UK 0800-033-7806
  • Switzerland 41-44-580-2115
  • Sweden 46-85-063-8386
  • Italy 003-902-3604-8268

Participant conference extension: 713, then enter pin 68764

SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.

Agenda

  • Review architecture draft
  • Map components to existing open source projects and identify what needs to be developped

Participants

  • Benjamin Cabé
  • Ian Skerrett
  • James Kirkland
  • Kai Hudalla
  • Steffen Evers
  • Julien Vermillard
  • Andrea Ceiner


Methodology

  • Drafting business and technical context
  • What are the surrounding systems?
  • ARC42
    • Contextual views
    • Then building blocks
      • White box view
      • Underlying components as black boxes
  • Other initiatives to look at: OneM2M, Open Interconnect Consortium (OIC)
  • Two goals:
    • Gap Analysis
    • Recommendations to integrate with existing open source stacks

Misc topics / Questions

  • Are there different business applications we are targeting?
  • Next meeting over Google Hangouts

Next steps

  • Add next level of details (ie building blocks) for the "IoT Server Platform"
  • Andrea to add SIM Management details
  • Plan a meeting at EclipseCon France (Benjamin)


May 7, 2015

Time: 3pm CEST / 9am EDT / 6am PDT

Dial-in details

  • North America 1-866-569-4992
  • Germany 49-692-2224-6059
  • France 33-(0)-17-070-8535
  • UK 0800-033-7806
  • Switzerland 41-44-580-2115
  • Sweden 46-85-063-8386
  • Italy 003-902-3604-8268

Participant conference extension: 713, then enter pin 68764

SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.

Agenda

  • Refine the scope of the components identified during EclipseCon F2F meeting (see here)
  • Identify available OSS solutions for those components and where new software needs to be made available
  • Provide a first prioritization of the components' in order to get to a minimum viable server.

Participants

  • Benjamin Cabé, Eclipse Fdn
  • Steffen Evers, Bosch SI
  • Dominik Guggemos, Bosch SI
  • Kai Hudalla, Bosch SI
  • Andrea Ceiner, Eurotech
  • James Kirkland, Red Hat

Minutes

We went through the different functional blocks identified during the F2F meeting at EclipseCon, and refined their scope as well as prioritized them:

Communication/Protocol adapters

This should:

  • Provide transparency regarding the concrete communication that devices are using
  • Mediate between concrete protocols and internal representations of the data
    • We already have concrete protocol adapters: LwM2M, MQTT but we don't have common representation to be used in a back-end.
    • James K: translation and arbitration could be done using Camel

We need to define the "protocol agnostic" data format into which incoming messages will be translated.

There is an agreement that we want this protocol adapter to be "billion-device-proof".

Device Management

This should allow to:

  • Manage the identity of the device: serial number, ...
  • Access metadata of the device: manufacturer, applicable data model, ...
  • Kai: "We need a northbound API for interacting with devices"
    • There are existing APIs: OM2M, Kura, LwM2M
    • Concerns regarding OneM2M (SOAP based)

Data storage

Andrea suggests to keep data storage / archival out of scope, and focus on Data Mgmt and Device Mgmt components. The group agreed that data storage is indeed a second step, or may always remain a task for the final implementer.

Event Management/Rules Engine/BPM

Agreement that this is not a priority at the moment. Candidate technologies that were mentioned during the call:

  • Eclipse Ponte, Apache Camel

User Management/Identity/Security

It is out of the picture for now – and will be a cross-cutting concern anyways.

API

We ran out of time to discuss this topic.

Next steps

  • We will use the wiki as a collaborative platform to share thoughts, working documents, diagrams...
  • Kai Hudalla has volunteered to help sketch a high level architecture of the server solution
  • Next meeting: May 20, 3pm CEST / 9am ET / 6am PT

Back to the top