The typo has been in the class name since its introduction. The
documentation contains the correct name "NFSProviderDriver" already.

Signed-off-by: Bastian Krause <[email protected]>

This allows the user to import these resources from labgrid.resource
directly.

Signed-off-by: Bastian Krause <[email protected]>

The TFTPProvider, HTTPProvider and NFSProvider don't have a host
property unlike the remote variants.

Fix the `get_export_vars()` method by distinguishing local and remote
resources: use the provider's host attribute for remote resources,
otherwise return "localhost".

Signed-off-by: Bastian Krause <[email protected]>

There is no need to overwrite this method to only call the same method
on super(). This is the default.

Signed-off-by: Bastian Krause <[email protected]>

This path will be used by the NFSProviderDriver in a future commit.

Signed-off-by: Bastian Krause <[email protected]>

During the introduction of the provider drivers, it was assumed all
provider drivers work the same way: by relying on the
`internal`/`external` attributes of their corresponding provider
resource and symlinking the required file (either from
/var/cache/labgrid/$USER/$HASH/file or the given path, in case it's
locally available) to the `internal` path. For the target, the file
is now expected to be available below `external` as returned by
`stage()`.

This, however, does not work for NFS: all NFS servers known to me
don't touch the symlinks, meaning in our case that they point to a
location not exported via NFS. Exporting and mounting these destinations
to the same location is impractical at best or does not work at all.
On top of that, the `internal`/`external` lingo does not fit the NFS
mount use case.

To improve this situation, introduce a custom `stage()` method for the
NFSProviderDriver: assume that /var/cache/labgrid is exported via NFS,
always copy the file to be staged there (even if it would be locally
available) and return an NFSFile object containing the information
required to mount and access the NFS share: host, export and the file
path relative to the export.

Signed-off-by: Bastian Krause <[email protected]>

…vider

Now that the NFSProviderDriver no longer relies on the
`internal`/`external` attributes of the (Remote)NFSProvider resource,
let the NFSProvider inherit from Resource directly, so specifying these
obsolete attributes is no longer required. The same applies to the
RemoteNFSProvider which now inherits from NetworkResource directly.

Signed-off-by: Bastian Krause <[email protected]>

…mples

Signed-off-by: Bastian Krause <[email protected]>