Formatting to mount existing DDN exascaler? #816
-
I find the documentation unclear on how to use the pre-existing-network-storage module with the DDN exascaler. @heyealex an example would likely help me. When I deploy my application the wrong lustre IP address is being used and the lustre filesystem is not mounted. This is what I am including in my yaml blueprint:
From the variables.tf file of the pre-existing-network-storage module I see the format for server_ip should be I can manually mount the filesystem using the following code so I know the exascaler is working:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
Hello Tristan -
I believe it's the I hope this helps get you unblocked! Let me know if I can clarify anything else or if this does not work for you. |
Beta Was this translation helpful? Give feedback.
Hello Tristan -
I ran a quick test to determine what is produced by the DDN EXAScaler module, and got the following valid network storage output:
I believe it's the
@tcp
after the IP that you are missing in your example. This should definitely be documented better, and I'll make a task for us to do that in …