Skip to content

Commit

Permalink
add the proposal of edgex + openyurt
Browse files Browse the repository at this point in the history
  • Loading branch information
charleszheng44 committed Mar 16, 2021
1 parent e1c1651 commit b1cf200
Show file tree
Hide file tree
Showing 4 changed files with 487 additions and 0 deletions.
Binary file added docs/img/connect-device.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/img/struct-relation.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/img/system-arch.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading

1 comment on commit b1cf200

@Walnux
Copy link

@Walnux Walnux commented on b1cf200 Mar 17, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The implementation of "Custom Resource Definition(CRD) + EdgeX" proposal is excellent. I like it very much. :)
However, before deep-diving into the implementation detail, I'd like to ask some questions.

  1. What is the ultimate goal of the Proposal? It is to integrate EdgeX with OpenYurt or to add Device Management support into OpenYurt?
  2. If the main goal is to support Device Management, what is the reason as well as the supporting data to pick up the K8S CRD solution? Is there any other solution to supporting Device Management? what are their Pros and Cons?
  3. If we can conclude that CRD is a reasonable solution, do we really have to involve EdgeX to support DeviceMangement? Is there any other solution?
  4. EdgeX Device Profile/Device/DeviceProfile concept to manage devices is perfect. But I am not sure whether we do need to depend on EdgeX to implement the feature?

Please sign in to comment.