search

flatcar / nebraska

Update monitor & manager for applications using the Omaha protocol, optimized for Flatcar Container Linux.
https://www.flatcar.org/docs/latest/nebraska
Apache License 2.0
170 stars 42 forks source link

[RFC] Cascading nebraska's #283

Open vbatts opened 4 years ago

vbatts commented 4 years ago

Propose that someone can bring up an Nebraska instance on premise, that itself subscribes to a "parent" Nebraska.

In this way, it can pull down the update payloads ready for being packages selected for a group. This allows a singular download, that will be broadcast from this child instance. Reducing load on the parent, and reducing the bandwidth of the child's network.

Another aspect of this will be reporting up the subscriber count. i.e. if a child (or grandchild..) has N flatcar subscribers, that the parent could see that child has N subscribers.

Lastly, there will be a management, and ACL, aspect to this. To see these numbers at which ever point in the chain, and see links to the children if your user has rights to these children.

pothos commented 4 years ago

In general this is already supported by running with the parameters -enable-syncer -host-flatcar-packages -flatcar-packages-path … (the detail questions of reporting the count not)