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

Reliable message delivery design proposal #1343

Merged
merged 2 commits into from
Feb 7, 2020

Conversation

fisherxu
Copy link
Member

@fisherxu fisherxu commented Dec 24, 2019

What type of PR is this?

/kind design

What this PR does / why we need it:

Provide a reliable message delivery mechanism between cloud and edge.

Which issue(s) this PR fixes:

Fixes #725

Special notes for your reviewer:
/cc @kevin-wangzefeng @rohitsardesai83 @sids-b @kadisi @chendave @subpathdev @du2016 @cwl233

Does this PR introduce a user-facing change?:

Add reliable message delivery design proposal

@kubeedge-bot kubeedge-bot added the kind/design Categorizes issue or PR as related to design. label Dec 24, 2019
@kubeedge-bot
Copy link
Collaborator

@fisherxu: GitHub didn't allow me to request PR reviews from the following users: du2016.

Note that only kubeedge members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

What type of PR is this?

/kind design

What this PR does / why we need it:

Provide a reliable message delivery mechanism between cloud and edge.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:
/cc @kevin-wangzefeng @rohitsardesai83 @sids-b @kadisi @chendave @subpathdev @du2016 @cwl233

Does this PR introduce a user-facing change?:

Add reliable message delivery design proposal

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubeedge-bot kubeedge-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 24, 2019
- "@kadisi"
creation-date: 2019-12-23
last-updated: 2019-12-23
status: alpha
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
status: alpha
status: provisional

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

@kevin-wangzefeng
Copy link
Member

Comment from community meeting:

  1. Add more detials(definition, behavior) about the modules in diagram
  2. Clarify data structure that would be used in key-value store


- CloudHub will sequentially send data from the NodeMessageQueue to the corresponding edge node,
and will also store the message ID in an ACK channel. When the ACK message from the edge node received,
ACK channel will trigger to save the message resourceVersion to K8s as CRD, and send the next message.
Copy link
Member

Choose a reason for hiding this comment

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

about ack channel, I recommend using sync.Cond to implementation it.

Copy link
Member Author

Choose a reason for hiding this comment

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

We have used the sync.Map now.

@fisherxu fisherxu force-pushed the reliab-proposal branch 2 times, most recently from 96c599a to 1a22073 Compare February 7, 2020 02:40
@kevin-wangzefeng
Copy link
Member

/approve

@kubeedge-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kevin-wangzefeng

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubeedge-bot kubeedge-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2020
@kadisi
Copy link
Member

kadisi commented Feb 7, 2020

/lgtm

@kubeedge-bot kubeedge-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 7, 2020
@kubeedge-bot kubeedge-bot merged commit df46cea into kubeedge:master Feb 7, 2020
@fisherxu fisherxu deleted the reliab-proposal branch February 8, 2020 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/design Categorizes issue or PR as related to design. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reliable message delivery from cloud to edge
4 participants