Page History
...
Also choose the size of each of the 3 OSTs that will be attached to your OSS
Then select the type of VM for your OSS.
The next section is used to setup the storage class and the networking.
First give you storage account a name.
Then chose the durability and High Availablity features for your storage. See the section "Replication for Durability and High Availability" at https://azure.microsoft.com/en-us/documentation/articles/storage-introduction/ for an explanation of the different selections shown here.
Next to setup is the network that the lustre servers and clients will use. You can use an existing network if you have one. In the case we don't so we create a new one.
We give it a name and pick an /16 address range to use.
Next we setup the subnets, one for the server and one for the clients.
Name the subnets. You can also change the address ranges, but they need to be in the /16 range you specified above.
After section the OKs in the previous window, a summary of what has been entered is shown in the summary.
Read the terms of use and purchase your Lustre Filesystem.
Next you will see the dashboard with a spinning "deploying". It will take awhile. Occassionally it will notrefresh when it is done, so check on it occasionally by refreshing the page.
When it is done chose "resource groups" in the left pane and then your new resource group that you created.
You should see "succeeded" user "last deployment:
You will also see an "overview" of your resources in the resource group.
If you choose "deployments" you can see that the process was done in 4 separate deployments, If you chose the first one a summary will appear where you can see the MGS public address to use to SSH to your MGS and the link to the ganglia output that can be used to monitor the activity in your Lustre filesystem. Also shown is the mount command to use on your clients to mount the Lustre Filesystem.
If you need to access the other nodes in the cluster and you have used the key option, you have two options. The best method is to run a pagent and ssh with forwarding enabled so the MGS node can get the private key from your workstation. The other less secure way as you make you are exposing your private key would be to copy your private key to the MGS so it can be used to access the other nodes.
You can use this method to log in to your clients to run benchmarks or try out some applications.
following is what the dashboard link will show
Replication for Durability and High Availability
Overview
Content Tools