Topic: Smart Data Transaction for CPS Weekly Meeting
Weekly Meeting
- Progress report:
- Documentation review with Ike completed. He indicated approval.
- Security results posted to the Release 6 page
- Moshe from Anylog joined in and we will be looking at ways to integrate Anylog's technology in this or other blueprints for release 7
- Looking at pushing source to Gerrit. Contacted CI subcommittee chair based on the CI Process for new projects.
- Tina suggested a TSC motion is needed to create a new project repo. Will try that.
Weekly Meeting
- Progress report:
- Logs pushed to Nexus and links updated in test document
- Will be reviewing docs with Ike later today
- API form just uploaded and Jeff has updated the API list page and the Release 6 release planning page with entries for SDT
- Will update the security results on the wiki when a Release 6 page is up
Weekly Meeting
- Progress report:
- Set up mailing list for Smart Data Transaction: sdt-blueprint@lists.akraino.org
- Test document complete except for links to Nexus
- Will be pushing logs to Nexus in the next couple of days
- Review request sent to document subcommittee
- Security subcommittee review required
- After that, the process subcommittee should forward recommendations to the TSC
Weekly Meeting
- Jim from Upstream committee joined and we discussed workarounds and inclusion in the next Akraino release
- We will need to take responsibility for maintaining any patches
- Clearly document the patches
- If those conditions are met inclusion in release 6 should not be a problem
- Progress report:
- All documents complete except test document BluVal section
- Lots of delays trying to get BluVal done in our test environment. DNS and proxy seems unreliable via the intranet.
- Pushing results to the Nexus requires a separate account. Should we create a non-corporate (Akraino?) account for the blueprint?
- Start sending documents for review by document committee
- Check what other reviews might be required
Weekly Meeting
- Progress report:
- Documentation mostly complete, except for Test Document
- Having trouble getting BluVal tests running in our test environment. Seems to be intranet issues.
- Will join the EdgeX security committee meeting Wednesday to discuss addressing upstream issues
- Asking Jim from Upstream committee if I can join the next committee meeting
Weekly Meeting
- Progress report:
- Phase 5: Security measures have been successfully enabled, moving on to BluVal etc. tests
- Problems with EdgeX security implementation components & Kong have been addressed with workarounds (including a patched Kong image)
- Contact established with Bryon Nevis through Jim White. Following up on Slack and possibly later to attend the security committee meeting.
- Architecture document drafted. Will need to be reviewed for release.
- Will be contacting Jim Xu from the Upstream & Downstream Sub-committee to discuss impact of EdgeX and Kong issues on the blueprint's inclusion in release 6.
Weekly Meeting
- Progress report:
- Phase 5:
- K8s security: Confirmed API protected by certificate and user account
- Docker: Enabled TLS security for private repository
- EdgeX: Enabled security measures provided by the github edgex-compose repository
- EdgeX security measures have encountered some difficulty because of problems, mainly from using k8s instead of docker-compose (e.g. edgex-go #3852 and #3851)
- Currently stuck on an issue with Kong reporting a DNS error looking up "localhost"
- Will try contacting mailing list and/or TSC chairs to see if anyone has any experience with this kind of error
- Phase 5:
- Prepare a demo, tentatively scheduled for 2/18
Weekly Meeting
- Progress report:
- Phase 4 complete, temperature sensor data relayed via LoRa to MQTT broker, tests implemented
- Phase 5: Security measures for K8s, EdgeX, and Docker under investigation, planned implementation by 2/8
- Akraino document preparation started
- Documents need to be reviewed by the sub-committee
Weekly Meeting
- Progress report:
- Device SDK Working Group meeting: LoRa device service to be submitted to edgex-examples
- New Jetson devices (x4) arrived 1/20.
- Phase 4 will complete today, moving on to Phase 5 (security, CD) and document preparation
Weekly Meeting
- Progress report:
- Phase 4, LoRa and sensor integration, in progress, planned completion 1/25
- Tasks for release 6 listed in progress report (slide 9): Documents, API form, BluVal + security checks are main items
- The full lab setup is configured and now we are working on device support and a pass-through app on the sensor nodes
- We'd like to build a second lab setup but need to add two more Raspberry Pi devices for that, also LoRa dongles if possible (meet with Fukano-san on Wednesday to discuss further)
- Device and Device SDK Working Group meeting was moved to 1/24
Weekly Meeting
- Progress report:
- Phase 3, basic inter-node communication, complete 1/7 (1wk delay)
- Update of tasks for release in progress
- Phase 4, LoRa and sensor integration, LoRa hardware arrives 1/11, sensor hardware 1/17
- Preparing materials for Device and Device SDK Working Group (next Monday)
Weekly Meeting
- Cancelled
Weekly Meeting
- Cancelled
Weekly Meeting
- Progress report:
- Phase 2, ARM-based edge node, complete
- Phase 3, multiple edge nodes & inter-node communication, in progress
Weekly Meeting
- Cancelled
Weekly Meeting
- MBI1: Kickoff, architecture & software stack review
- Progress report:
- Phase 1, VM-based Kubernetes cluster running EdgeX+Mosquitto, basic CI/CD w/ Jenkins, complete