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

We need federation! #8

Open
adnidor opened this issue Jul 5, 2018 · 10 comments
Open

We need federation! #8

adnidor opened this issue Jul 5, 2018 · 10 comments

Comments

@adnidor
Copy link

adnidor commented Jul 5, 2018

No description provided.

@margau
Copy link
Member

margau commented Jul 6, 2018

I would suggest two types: Input Federation (e.g. for data coming from TTN) and output federation (get data from other instances, requires authentication and authorisation for non-public-sensors)

@margau
Copy link
Member

margau commented Jul 6, 2018

Maybe we even should think about local instances (at home) and cloud instances (inside "Freifunk-Mesh-Cloud")

@adnidor
Copy link
Author

adnidor commented Jul 6, 2018

I think it is better to think about the types as pull federation and push federation, similar to the activitypub standard.

@margau
Copy link
Member

margau commented Jul 6, 2018

Maybe, for me it seems best to do push federation from sensors to ingress, and pull federation to get/view data.

2 similar comments
@margau
Copy link
Member

margau commented Jul 6, 2018

Maybe, for me it seems best to do push federation from sensors to ingress, and pull federation to get/view data.

@margau
Copy link
Member

margau commented Jul 6, 2018

Maybe, for me it seems best to do push federation from sensors to ingress, and pull federation to get/view data.

@adnidor
Copy link
Author

adnidor commented Jul 6, 2018

What scenarios do we have for federation?

I can think of "User wants to display data from remote server", this would be a "pull" or "output" type federation.

We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.

I'm trying to think of a scenario for "push" or "input" federation but can't.

@adnidor
Copy link
Author

adnidor commented Jul 6, 2018

Not sure what you mean with "local" and "cloud" instances? Why should an instance run at home be different from an instance run in "the cloud"?

@margau
Copy link
Member

margau commented Jul 7, 2018

Local/Cloud: Aggregate Data on local homeserver (i.e. when connectivity issues occur), but view it on cloud/public instance

We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.

I think federation would be the right approach. Normal input is when a sensor is adding something. When another kind of aggregator - this would be a TTN-Gateway - is adding something, for me it seems the best to handle it as federation.

@hibas123
Copy link
Member

Local/Cloud: Aggregate Data on local homeserver (i.e. when connectivity issues occur), but view it on cloud/public instance

We don't need federation for getting data from TTN into Freifunk-IoT, the gateway can just push the data to the correct server in the first place.

I think federation would be the right approach. Normal input is when a sensor is adding something. When another kind of aggregator - this would be a TTN-Gateway - is adding something, for me it seems the best to handle it as federation.

I would also say, that something like gateways are very likely to occur. This would allow a setup, where not every device/aggregator needs direct internet/cloud access. Especially considering the exploits from the past on IoT devices.

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

3 participants