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

Formally deploy mqtt to Birmingham and expose a link to Cardiff #22

Closed
6 tasks
SamStudio8 opened this issue Feb 10, 2021 · 2 comments
Closed
6 tasks

Formally deploy mqtt to Birmingham and expose a link to Cardiff #22

SamStudio8 opened this issue Feb 10, 2021 · 2 comments

Comments

@SamStudio8
Copy link
Member

SamStudio8 commented Feb 10, 2021

Currently the mosquitto mqtt server is running ad-hoc in Birmingham, as it's being used more we'll need to formalise the deployment to make it safer and robust:

  • mosquitto should not run as me
  • Implement a mosquitto auth plugin that hooks to Majora (or a script to pull auth keys from Majora)
  • Expose a route to Cardiff to allow messages to be exchanged across the two halves of CLIMB-COVID
  • Use clean_client to allow clients to pick up missed messages
  • Set up an echo service that echoes messages to subscribers only if they meet a template
  • Set up an audit client to record all messages
@SamStudio8
Copy link
Member Author

Added to backlog #62

@SamStudio8
Copy link
Member Author

Read up briefly on how this would work. mqtt brokers on different networks can be joined with bridges that just broadcast and subscribe all topics to the other side. I additionally tried to Apache Kafka and kafka-python which is like mqtt on steroids. I think Kafka is overkill for the current phase but looks cool for some stuff I have in mind later.

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

No branches or pull requests

1 participant