You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 47 Next »

EdgeX Foundry will be holding a series of Tech Talks / Educational Technical Spin Up Calls hosted by Jim White, Dell

  • 30 minute deep-dive topics, followed by 30 minutes of open Q&A
  • Held Thursdays at alternating times (6pm & 9am EDT)
  • Email to request to be added directly to meeting invite
  • Calls will be recorded / posted to this Wiki page (along with any presentation material)

Additional resources to learn more

Thursday 6pm EDT Call information:

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (US Toll): +14086380968,,183149170# or +16465588656,,183149170#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 183 149 170
International numbers available:

Thursday 9am EDT Call information:

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (US Toll): +16465588656,,862983841# or +14086380968,,862983841#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 862 983 841
International numbers available:

Learning Sessions

    • What you need to start working with the existing code
    • How to get and run the code in your environment
    • Explore how to test that what you have running is working correctly
  • July 6 (9am EDT): Getting and Running EdgeX Docker Containers (Slides (PPTX); Meeting Recording)
    • Where to get the EdgeX Foundry micro service Docker Containers
    • Using Docker Compose to get the EdgeX Containers
    • Running the EdgeX containers
    • How to use EdgeX containers in development (hybrid native and Docker development)
    • Eventual container build process
    • Open Q&A

  • July 13 (6pm EDT): Core Data Micro Service - Deep(er) Dive (Slides (PPTX); Meeting Recording)
    • Core Data's general purpose
    • Core Data’s makeup – including technologies/libraries/tools used in Core Data
    • REST API outline (categorizing the APIs by purpose)
    • Core Data object model
      • Event's and Readings
      • Value Descriptors - what are they and how they are used in EdgeX
    • Some important configuration settings
      • Metadata check
      • Persistence via Mongo
      • "streamed" option
      • Message push to export services and/or rules engine

  • July 20 (9am EDT) - Meeting canceled (EdgeX MVP meeting)
  • July 27 (6pm EDT): Meta Data Micro Service Part 1 (Slides (PPTX)Meeting Recording)
    • Meta Data's general purpose
    • Meta Data's makeup
    • REST API outline
    • Meta Data object model
      • Device, Device Service
      • Addressable
    • Some important configuration settings
    • Meta Data Part 2 (in upcoming call, will cover Device Profile and Provisioning)

  • August 3 (9am EDT): Meta Data Micro Service Part 2 (Slides (PPTX); Meeting Recording)
    • Meta Data Profile Details
      • Commands
      • Resources
      • Device Resources
    • Provisioning from a Meta Data perspective
    • Provisioning from a Device Service perspective
  • August 10 (6pm EDT): Command Micro Service (Slides (PPTX); Demo API Walk Through shown in the talk; Meeting Recording)
    • Command general purpose
      • Why a command micro service
    • Command makeup - including technologies/libraries/tools/etc.
    • REST API outline
      • Command's API relationship to the Device Profile
    • Configuration settings
    • Quick update on ongoing project work 

August 17 (9am EDT): Configuration and Registry (C&R) Micro Service

Configuration and Registry (C&R) Micro Service Deep Dive
-C&R general purposes
-C&R makeup - Consul and additions
    Config Seed
    Config Watchers
Integration with other micro services
    How micro services bootstrap with C&R
    Configuration in micro services
    Default settings in development versus deployment (docker)

Configuration data organization and naming conventions
    key/value pairs
    association to microservice id namespace

Consul Web Interface

Registry and service health

Dynamic reloading of config data

Future Considerations and additions
more with watchers
Consul or ? (Consul's architecture)
  • No labels