Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • High priority review of ADR for bootstrapping in OCI containers requested.
  • Incorporation of Vertical Solution WG adopter presentation feedback
    • Jim to collect and present after all 5 presentations
  • Backward compatibility and what to do about Mongo, Logging and Support Rules Engine for Hanoi?
    • Some think exemption to remove these under minor version for Hanoi may have been too hasty
    • Should we reverse course?  Are we too far down to reverse course?
  • Add a service dot setting to set up the adapter for listen on web services (Lenny to provide more details)
  • EdgeX UI - it is for dev/test right now.  Would we ever want to have a UI for production?  Under what constraints?
    • Being worked through Core WG
  • How should we apply semantic versioning to modules?  When do we update the minor and major versions of modules?  (comes from the Hanoi planning meetings)
  • Extract of Device Service requirements to ADR legacy - what are all the pieces that need to be moved there?
  • Per the Hanoi planning conference - we need to better define "bound checking" so that a design (and eventual implementation) can be brought forth to meet the requirements
    • Currently considering limiting the number of operations that can be performed on a service (like a device service) over a period of time or setting the max request size (that lends to DoS attacks)
    • Can the solution be more globally applied?
  • Design metadata about the “gateway” or host platform (identity, location, …)
    • Being worked in core WG
  • How do address module and component version release needs for examples (per Slack exchange with Luis Obando).  go.mod in the examples helps - or at least some documentation on dependencies.
  • How do we review/remove artifact removal (docker images in Docker Hub, snaps, etc.)?
    • New Docker policy will remove any image that is not pulled or pushed in 6 months.
  • Is order of event/readings being sent by a single device service important?  Are there async operations in any service that could change the order of events as they are sent from a DS to core to application services (with REST, 0MQ or MQTT infrastructure)?  What do customers desire here?  Is maintained order important?  What is the current state of the system and can we diagram/document that? 
    • Jim to do some research first.  Findings: there are places in DS, Core and Application Services where messages can get out of order.  If order is something that should be an option built in, it will require much work.

...