Versions Compared

Key

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

Table of Contents

...

  • Replace any Java microserices that still exist.Implement hierarchical config organization

  • Improve the configuration of EdgeX

    • Refactor config-seed to only load the configuration appropriate to the application setting based on profiles (i.e. development, production, production docker or snap, etc.)
    • Replace the simple key/value pair organization of service configuration with more structured and hierarchical configuration as supported by Consul
    • Upgrade Consul and improve the configuration seed
    • Implement a process to move the latest configuration into the config-seed through the CI process
  • Refactor the core and supporting services (inclusive of export services as necessary)

    Refactor the services to implement data drive design, improves structure and organization of the code, improves ability to abstract infrastructure needs (database, messaging, etc.) to allow for replacements later, and allow services to bootstrap without artificial sleep mechanisms.  Separates the domain model from the contract model.

...

  • System management API (action, alerts, metric) as discussed and outlined here

  • System management Agent (see same document above outlining the agent functionality and duties)

  • As a stretch goal, the functionality added with this system management capability would facilitate systemd like bootstrapping.

  • Potentially explore "Gateway management" to include:
    • Demonstrate basic management of EdgeX via select 3rd party console (ex: VMware Pulse IoT Center, System Center, …)
    • Demonstrate EdgeX software updates
    • Updates to non-EdgeX components (drivers, end-devices)

...