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

who send mqtt message to topic #112

Open
yuexian1234 opened this issue Apr 19, 2022 · 3 comments
Open

who send mqtt message to topic #112

yuexian1234 opened this issue Apr 19, 2022 · 3 comments

Comments

@yuexian1234
Copy link

i find the cloud app code is just update the device status, and the edge app just subcribe the mqtt topic.
i want to know,who send message to mq topic? kubeedge controller or cloudapp self.
thanks

@RyanZhaoXB
Copy link

hello. the cloud app updates the device status to kube-apiserver and the module of device controller in cloudcore will watch the modification and send it to the edgecore through cloudhub. the module of devicetwin in edgecore will rebuild the message and send it to the mq topic through event bus.

@yuexian1234
Copy link
Author

hello. the cloud app updates the device status to kube-apiserver and the module of device controller in cloudcore will watch the modification and send it to the edgecore through cloudhub. the module of devicetwin in edgecore will rebuild the message and send it to the mq topic through event bus.

thanks
but how the edgecore known which topic to send?

@RyanZhaoXB
Copy link

hello. the cloud app updates the device status to kube-apiserver and the module of device controller in cloudcore will watch the modification and send it to the edgecore through cloudhub. the module of devicetwin in edgecore will rebuild the message and send it to the mq topic through event bus.

thanks but how the edgecore known which topic to send?

we make it in the code of edgecore and mapper. every mapper on this node subscribes these topics to receive the messages and the mapper will check the device id to determine whether the message should be handled by itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants