Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support automatic migration of Devices between Device Services #1451

Closed
iain-anderson opened this issue Jun 18, 2019 · 3 comments
Closed

Support automatic migration of Devices between Device Services #1451

iain-anderson opened this issue Jun 18, 2019 · 3 comments
Labels
enhancement New feature or request unscoped Issues that are currently out of scope for all releases.
Milestone

Comments

@iain-anderson
Copy link
Member

🚀 Feature Request

[NB WIP: There may well be insuperable problems with this]

Relevant Package

core-metadata, device services

Description

In a scenario where a device can move between the connectivity domains of different device services (eg a radio-connected device physically moving in and out of range of various base stations), we wish to be able to automatically update the Device object in EdgeX accordingly.

Describe the solution you'd like

  • ProvisionWatchers to allow wildcarded DeviceService field, eg "device-bluetooth-basement-*"
  • core-metadata to match said wildcard when queried for PWs for a particular Device Service
  • DS implementation would have to generate a consistent name for a Device whichever DS discovers it
  • DS SDK to detect that a discovered device already exists, and update the Device's Device Service field to point to itself
  • DS SDK to react appropriately to the callback from core-metadata indicating that a Device now belongs to it / to another DS

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?
@iain-anderson iain-anderson added the enhancement New feature or request label Jun 18, 2019
@brandonforster brandonforster added this to the EdgeX Geneva milestone Oct 25, 2019
@michaelestrin michaelestrin added unscoped Issues that are currently out of scope for all releases. and removed geneva labels Dec 16, 2019
@michaelestrin
Copy link
Member

Discussed in last week's Device Services WG call and decided not to do this for Geneva. Changing label to unscoped.

@tsconn23 tsconn23 modified the milestones: EdgeX Geneva, EdgeX Hanoi May 7, 2020
@cloudxxx8
Copy link
Member

@iain-anderson do we still need this issue?

@jumpingliu
Copy link
Contributor

same as #4694

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request unscoped Issues that are currently out of scope for all releases.
Projects
Status: Odessa Done
Development

No branches or pull requests

6 participants