Skip to main content
Jump to: navigation, search

Difference between revisions of "IoT/M2MIWG/Weekly call minutes"

< IoT
Line 18: Line 18:
  
 
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
 
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
 +
 +
----------------------------------------
 +
 +
= Feb 1, 2017 (WG Call)=
 +
 +
== Participants ==
 +
 +
*Dan Gross, Samsung
 +
*James Sutton, IBM
 +
*David Bericat, Red Hat
 +
*Laurent Lagosanto, MicroEJ
 +
*Roxanne Joncas, Eclipse Foundation
 +
*Benjamin Cabé, Eclipse Foundation
 +
*Brad Micklea, Codenvy
 +
 +
== Agenda ==
 +
=== Eclipse IoT Testbeds: review strategy and next steps. ===
 +
Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem.
 +
Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers
 +
More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing
 +
Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing
 +
There are many options for collaboration
 +
 +
*Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
 +
*Laurent Lagosanto: Potential use case for Eclipse Edje.
 +
*David Bericat: Excited and look forward to working with everyone.
 +
 +
'''Next Steps''': Stay tuned, we will be updating the group at large and scheduling individual meetings.
 +
 +
=== 2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters. ===
 +
'''Big set of changes:'''
 +
*Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
 +
*A messaging transport that is agnostic to the content of the payload.
 +
*Three qualities of service for message delivery:
 +
**At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
 +
**At least once", where messages are assured to arrive but duplicates can occur.
 +
**"Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
 +
*A small transport overhead and protocol exchanges minimized to reduce network traffic.
 +
*A mechanism to notify interested parties when an abnormal disconnection occurs.
 +
 +
'''Notes from the meeting:'''
 +
*Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
 +
**The CONNECT packet can contain information regarding what QoS are supported by the server
 +
**Supporting QoS 2 on the server is not mandatory anymore
 +
**Scalability
 +
*It will affect the Paho client and so a new Paho client will be created.
 +
**Improve API
 +
**Feedback from community
 +
**Work nicely with the new MQTT 5 features
 +
*The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.
 +
 +
'''IMPORTANT:''' Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt
 +
 +
=== 3. PMC topics: project documentation, build machines, Docker, … ===
 +
Skipped this item - not enough PMC members on the call
 +
 +
=== 4. Misc. updates ===
 +
*WG Meeting at the Eclipse IoT Day San Jose Add your project for project update or intro: https://wiki.eclipse.org/EclipseIoT_SanJose2017
 +
*IoT Developer Survey Test it and give us feedback! It will go live next week. https://www.surveymonkey.net/r/Preview/?sm=PpPJLkX2kyFIkd4FpbfnijKgtSau8CTbzClUcIqMOv8UHpkGU6kxWrpBNJfYHpzC
 +
*Member companies are encouraged to ask for a special link that they can use to promote the survey to their communities, and have access to answers based on this segment.
 +
Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/
 +
  
  

Revision as of 09:49, 2 February 2017

The Internet of Things Industry Working Group is holding bi-weekly calls on Wednesdays, at 12pm ET.
Participation to these calls is restricted to members of the IWG, but the minutes are public. We alternate between marketing-focused calls (upcoming events coordination, community outreach, etc.), and technical calls mostly targeting project leads, to synchronize cross-project activities.

The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a SIP client on your computer if possible.

  • 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.


Feb 1, 2017 (WG Call)

Participants

  • Dan Gross, Samsung
  • James Sutton, IBM
  • David Bericat, Red Hat
  • Laurent Lagosanto, MicroEJ
  • Roxanne Joncas, Eclipse Foundation
  • Benjamin Cabé, Eclipse Foundation
  • Brad Micklea, Codenvy

Agenda

Eclipse IoT Testbeds: review strategy and next steps.

Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem. Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing There are many options for collaboration

  • Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
  • Laurent Lagosanto: Potential use case for Eclipse Edje.
  • David Bericat: Excited and look forward to working with everyone.

Next Steps: Stay tuned, we will be updating the group at large and scheduling individual meetings.

2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters.

Big set of changes:

  • Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
  • A messaging transport that is agnostic to the content of the payload.
  • Three qualities of service for message delivery:
    • At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
    • At least once", where messages are assured to arrive but duplicates can occur.
    • "Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
  • A small transport overhead and protocol exchanges minimized to reduce network traffic.
  • A mechanism to notify interested parties when an abnormal disconnection occurs.

Notes from the meeting:

  • Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
    • The CONNECT packet can contain information regarding what QoS are supported by the server
    • Supporting QoS 2 on the server is not mandatory anymore
    • Scalability
  • It will affect the Paho client and so a new Paho client will be created.
    • Improve API
    • Feedback from community
    • Work nicely with the new MQTT 5 features
  • The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.

IMPORTANT: Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt

3. PMC topics: project documentation, build machines, Docker, …

Skipped this item - not enough PMC members on the call

4. Misc. updates

Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/



Archives

Copyright © Eclipse Foundation, Inc. All Rights Reserved.