Signed-off-by: Blake Devcich <blake.devcich@hpe.com>

Grab the end stats from dcp output and store it in the command status.

Signed-off-by: Blake Devcich <blake.devcich@hpe.com>

Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>

Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>

Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>

nnf-dm uses a configmap to store its configuration in. This is not
consistent with the other means of configuration (i.e. Storage and
Container Profiles).

This change removes the nnf-dm-config map and swaps it with using
NnfDataMovementProfiles.

Pinned profiles are used for copy_in/copy_out directives. Non-pinned
profiles are used for the Copy Offload API since the user can select any
profile they wish and can change profiles with each request. This means
that the nnf-dm reconciler now needs access to the `nnf-system`
namespace to get the non-pinned profiles.

Signed-off-by: Blake Devcich <blake.devcich@hpe.com>

Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>

Signed-off-by: Dean Roehrich <dean.roehrich@hpe.com>

Signed-off-by: Blake Devcich <blake.devcich@hpe.com>

For things like SCR that are using the Copy Offload API, the destination
can easily be created by the client software. SCR guarantees this.

Using profiles, allow the destination prep (mkdir to ensure dest exists)
to be skipped.

This way, copy_in/copy_out can still ensure the dest exists while
disabling this behavior for SCR.

Signed-off-by: Blake Devcich <blake.devcich@hpe.com>

Signed-off-by: Anthony Floeder <anthony.floeder@hpe.com>

update peer modules

Signed-off-by: Anthony Floeder <anthony.floeder@hpe.com>

Signed-off-by: Anthony Floeder <anthony.floeder@hpe.com>

Signed-off-by: Anthony Floeder <anthony.floeder@hpe.com>