Archimedes Trajano

For NFS, I don't think it is possible given the way I have implemented it. For one, NFS requires the export to be known first. It can't really guess where...

I wonder how they would do it for NFS. Unless the can control the NFS daemon to create and export other paths which doesn't really sound right.

The thing is I won't know the "base" export folder.

I haven't been maintaining this, but I am thinking it looks like an SELinux issue.

Conceptually the plugin would be configured to run on a host and have access to the whole `/dev/` tree of the host. The host is still expected to provide the...

If there are multiple seed nodes detected then pool and brick registrations are stopped.

Since Docker only allow updates to Config labels, the labels will contain the actual configuration data keyed against the value of `SEED` which is the config name.

The plugin would need to access the `/var/run/docker.sock` file in order to communicate with the engine.

It works in a swarm but you need to install the plugin on every node. That's a limitation of Docker at the moment.

does it show anything on `/var/log/messages` (that's where docker normally dumps its logs)