...
Topic: EdgeX - Monthly Architects Meeting
Time: Oct 19, Nov 30 2020 10:00 AM Pacific Time (US and Canada)
Every month on the Third Mon, until Nov 18, 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
...
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
Nov 30, 2020: Meeting Minutes; Meeting Recording
Sept 21, 2020: Meeting Minutes; Meeting Recording; Adopter Series Requirements Summary
...
Nov 18: Meeting Minutes; Meeting Recording
Open Topics
- We need to revisit CBOR binary support vs simple JSON / binary encoding (per Core WG meeting of 1/7/21).
- 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
- High - How to handle binary data in V2
- Use of CLI to generate new application or device service
- Per Core WG and TSC meetings (1/20/21), there is a big desire to add a feature to EdgeX tooling to more easily generate a new device or application service (using a command line tool and some template found in the SDK)
- Question is whether this should live in edgex-cli or is this a separate tool?
- CLI for replacing curl scripts; this doesn't see to fall in line with objectives of the current CLI.
- Client keys in configuration; use the service keys as the constants for the map keys (per Core WG meeting of 1/21/21)
- We are up to 58 repositories in Holding. May need to look at some cleanup in the new year.
- Done - resolved via email
- Core/High - New topics from Ireland Planning Meeting Ensure that service location data is pulled from trusted source (i.e. not Consul) (Tony's ADR)
- Covered in Security WG
- 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
- 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
Docker image naming - resolve naming standard we want
Drop “go” suffix and “docker” prefix??
- What version of Alpine for Docker images (make them consistent?)
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
Revisit combing - 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
Keep commit history from beginning to end (don’t squash them until PR approved)
Standardizing units of measure
- Low - Digital twin (and LWM2M) applicability
Declarative Kong applicability
- Low - Time series database support and applicability
On Hold Topics or Pending Research
- 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)
- Decision was to release (and tag) them with each EdgeX release (major)
- Enforce backward compatibility within a major release
- Scope this work for Ireland as it will impact DevOps (Jim to get with Ernesto)
- How do we review/remove artifact removal (docker images in Docker Hub, snaps, etc.)?
- Decision made to tag "latest" dot release with X.Y tagging and use X.Y in Docker Compose files (see minutes from 8/20).
- Open discussion still around what to do with old (very old) images.
- Let’s check what are other projects doing in this case (Kong, Consul, Vault, …)?
Also consult with community and adopters; what do they expect from us? Accenture, ThunderSoft, …
Jim to take this research and poll of adopters
- Adopters have been polled. Most want images available indefinitely. Tibco suggested keep them one year.
- Other organizations (Kong, Consul, Vault, etc.) are not removing images regardless of age or circumstances (there are a few exceptions).
...
- Ian Johnson has an example of app service to InfuxDB export (snap in the store)
Non-prioritized items
- Allowing dynamic changes to device profiles
On Hold Topics or Pending Research
None at this time
...