Versions Compared

Key

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

Table of Contents

Meeting Time and Conference information

Meeting Time:  3rd Monday of each month at 1pm EST as needed (if Wednesday at 8am PT on a bi-weekly basis, i.e. alternating with the TSC Meeting. If there are no agenda items, the meeting is will be cancelled)

EdgeX Working Group 2 is inviting you to a scheduled Zoom meeting.

Topic: EdgeX - Monthly Architects Meeting
Time: Nov 30 2020 10Time: Jan 18, 2023 08:00 AM Pacific Time (US and Canada)
Every month on the Third Mon, until Nov 18        Every 2 weeks on Wed, until Dec 4, 2024, 50 occurrence(s)

Please download and import the following iCalendar (.ics) files to your calendar system.
Monthly: https://zoom.us/meeting/vpEufuytpzstxwJXp3nHvYoHt7mRqmscaw/ics?icsToken=98tyKuqtrTIvH92Vt1_Hd7MvA5X5buHylmlZgJtNzxHNFRlcShehO9BTP6F8Ec-B

...

Meeting ID: 353 955 907
Passcode: 150365

One tap mobile
+16699006833,,353955907# US (San Jose)
+12532158782,,353955907# US (Tacoma)

Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
877 369 0926 US Toll-free
855 880 1246 US Toll-free
+1 778 907 2071 Canada
+1 204 272 7920 Canada
+1 438 809 7799 Canada
+1 587 328 1099 Canada
+1 647 374 4685 Canada
+1 647 558 0588 Canada
855 703 8985 Canada Toll-free

Meeting ID: 353 955 907

Find your local number: https://zoom.us/u/ajhw77vTU

Meeting Agenda/Minutes/Recordings

Currently running bi-weekly:

Previously run monthly:

Open Topics

  • Review hybrid app-device service UCR (and any subsequent ADR) with the community
  • What to do about the future of system management
  • Core/High - Ensure that service location data is pulled from trusted source (i.e. not Consul) (Tony's ADR)
  • High - V2 API - should we add security foundation added to that (per some of earlier V2 API designs via Dell and Bryon N)?
    • Adding token to authenticate a micro service call (is this in scope for Ireland)
    • May not be needed unless all services are distributed
    • We need to explore alternatives to provide secure / locked out service to service communications
  • High - How to handle binary data in V2
    • Is CBOR still the right way?
    • Simplicity versus performance
    • We should have new requirements/use cases to change this
    • Jim to find the objectors to CBOR before we cover and get any suggestions/requirements for non-CBOR
  • Med - Address how to get device resource info (for app services and Kuiper)
    • Probably not ADR worthy
    • Either provide Lenny’s convenience APIs or tool to dig out the device resource information in the (cached) profiles
    • How/when to invalidate the cache if we use the profile-digging approach
  • Med - Keep commit history from beginning to end (don’t squash them until PR approved)
  • Med - Standardizing units of measure
  • Med - Declarative Kong applicability
    • Allowing us to drop Progress DB
    • But can you configure groups/users ACL
    • Only supports JWT users
  • Low - Is the Wiki the best place to document project decisions (those outside of or smaller than ADRs).  This was our initial take.  Should we revisit?
  • Low (must be done before V2 is done) - Naming scheme changes for config.Clients (key name change)
    • Use consistent name that all other services use for core data
    • Consistency in the naming vs changing all the names to use service name as part of key
    • Related to system management hard coded list of services.
    • Separate issue in arch meeting – high once report back
    • Other naming issues (secret store vs secret service)
    • Opportunity to make all config/naming consistent
    • Jim take resp – get WG leads – try to prioritize this survey
  • Low - Revisit combine core services at least at all executables in one image
    • Release would be easier but image would be bigger with more complex compose files
  • Low - Digital twin (and LWM2M) applicability
  • Low - Time series database support and applicabilityIan Johnson has an example of app service to InfuxDB export (snap in the store)

On Hold Topics or Pending Research

  • None at this time