Skip to content

Commit 467ddb8

Browse files
committed
Mention about the possibilities of using staging_target_path at NodeStage.
At present, it is unclear to SP that, how to use staging_target_path and the possibilities of using the same. This patch add more details on `staging target path` and its usage. Fix # #385 Signed-off-by: Humble Chirammal <[email protected]>
1 parent 9e773d2 commit 467ddb8

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

spec.md

+6-1
Original file line numberDiff line numberDiff line change
@@ -1931,7 +1931,12 @@ message NodeStageVolumeRequest {
19311931
// that the path is directory and that the process serving the
19321932
// request has `read` and `write` permission to that directory. The
19331933
// CO SHALL be responsible for creating the directory if it does not
1934-
// exist.
1934+
// exist.The CO will pass around the staging_target_directory from
1935+
// NodeStageVolume to NodePublishVolume. SP can stage a volume
1936+
// however it like inside the staging_target_directory.
1937+
// For example, SP can stage it directly at the starging_target_directory,
1938+
// or a subdirectory or file underneath. SP can also store other files/metadata
1939+
// inside the staging_target_directory if it like.
19351940
// This is a REQUIRED field.
19361941
string staging_target_path = 3;
19371942

0 commit comments

Comments
 (0)