-
Notifications
You must be signed in to change notification settings - Fork 5
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
Move Schwarmstedt from Umland to own domain #57
Comments
Hm... When thinking about it, this might confuse users. Instead I propose to add a prefix to the names of the existing domains which reflect districts of Hannover e.g. "Hannover: Misburg" and then split the Umland domain further into regions of the region of Hannover like in this map with the prefix like e.g. "Region: Neustadt", "Region: Springe": https://www.hannover.de/Leben-in-der-Region-Hannover/Gesundheit/Gesundheitsschutz/Coronavirus-in-der-Region-Hannover/Infektionen-mit-COVID-19-in-der-Region-Hannover |
Do we have/need code to move nodes from ie. |
Sounds good. |
Would look something like this (i hope i got all Region and Umland definitions right) |
@Dark4MD The domX files are generated from |
@1977er Yes, using gen.py. Manu is right. Only the Umland nodes will be moved to new domains and the rest are just name changes. |
I don't think we should put them in an already big domain like umland, but implement a default domain like leetfeld? for this purpose. Maybe we could even setup some sort of notification on the nodes cli, when the domain is not set properly. |
Please remember to add the domain-switcher to the next firmware, to push the routers starting with sgs* to the domain Schwarmstedt. There are still too many routers in Schwarmstedt in the domain "Umland". |
This requires Firmware newer than vH25. |
...and is therefore effectively blocked by #87 |
With more than 300 nodes Umland is already twice as big as our second biggest domain. Schwarmstedt is the biggest mesh in Umland and should therefore be moved to a dedicated domain.
The text was updated successfully, but these errors were encountered: