Jan Lübbe

Thanks. Please note that for the exporter, you need to allow access to `/dev` and udev.

It looks to me like this creates three independent jobs, which would cause the common stage (labgrid-base) to be built multiple times. The existing build.sh runs the stages sequentially in...

When using the remote access layer (lg-coordinator, lg-exporter), the places are expected to be relatively static (as they normally refer to real HW). Right now I don't see an obvious...

This is by design, as during a coordinator restart we would miss all events from the exporters happening during the restart, which could lead to an inconsistent state on any...

I see some issues with this PR, which we'll need to discuss. The UUU resource doesn't support the normal udev matching, which means that the client can't know whether the...

Nevertheless, for a quick check a `labgrid-client exporters` would be nice. It could show the list of exporters, with the number of exported groups and resources as columns.

Yes, this sounds useful. We should also keep track of some statistics in the coordinator and report those as well (such as: uptime, event count, number of resources).

With dev-requirements, it will also pull in the full crossbar, yapf and the documentation tools, which should not be needed for a client only container. Is the additional size so...

@khilman would using $PATH work for you?

I'd prefer to handle new power controllers via https://github.com/pdudaemon/pdudaemon