Hi all,
Please find this week’s Eclipse Sparkplug Specification Project meeting notes below.
Eclipse Sparkplug Specification Project – Meeting Notes – 12 January 2021
- Attendees
- Chad Kienle
- Frederic Desbiens
- Ian Craggs
- Ilya Binshtok
- Josh Wolf
- Nathan Davenport
- Travis Cox
- Wes Johnson
- Major chunks of work that remain
- Specification cleanup
- Tracked via Github issues
- Normative/non-normative statement creation remains
- Diagrams/flowcharts need to be recreated
- What format should we use? Needs to be AsciiDoc compatible
- Basic flow of annotation to TCK to reporting
- Will be used as a template for other sections/annotations
- Defining Sparkplug scenarios that must be covered by any compatible implementation
- Review of recent progress
- Using opensource apache based HiveMQ test tooling
- Annotation -> TCK -> spin up test resources -> test compatible implementation
- Junit5 test example
- Setup MqttConnection
- Setup HiveMQ test container
- HiveMQ community edition MQTT Server in docker container
- Setup interceptor via HiveMQ extension
- Wes will PR this today/tomorrow
- How will a compatible implementation communicate scenarios under test to the TCK?
- Client sends MQTT message stating which scenario(s) it is trying to test?
- TCK exposes REST API so client can define which scenarios are under test?
- How should we document the Sparkplug test scenarios?
- In the spec?
- In a separate document attached to the spec?
- HiveMQ Test interceptors can be used to inject/modify MQTT Sparkplug message packets to better test failure cases
- Network proxy can be used to simulate network failures (Ian Craggs has experience with this tool)
- Do we plan to modify any documented behavior (introduce any breaking changes) in the upcoming Sparkplug specification release? [Answer] No, the goal of the first release is to resolve
any ambiguities in the previous version of the spec and to convert the specification to AsciiDoc format so it is easier to maintain going forward.
- Goal for next meeting:
- Finish E2E test
- Complete more specification clean up
Thanks,
Nathan
