Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Prerequisites: Install the Azure CLI and Git, and then sign in or set your Azure subscription.
Important
Run the following command from a Linux shell where Azure CLI is installed and authenticated with the Azure account designated for deployment. Azure Cloud Shell isn't supported for this scenario.
Clone the Azure CycleCloud Workspace for Slurm on the latest stable release
git clone --depth 1 https://github.com/azure/cyclecloud-slurm-workspace.git
Copy the content of the UI definition file
./uidefinitions/createUiDefinition.json
Browse to the UI Definition Sandbox:
- For Azure Public Cloud Azure Public portal
- For Azure US Gov Azure US Gov portal
Paste the content of the UI Definition file into the multiline text box on the right.
Select
Preview >>
in the bottom-left corner to bring up a UI experience.Go through each page of the UI flow to make sure that necessary values appear in the output payload described in the next step.
Go through the UI flow to the
Review + create
page and then select the link labeledView outputs payload
to the right of theCreate
button to generate a pane with JSON-formatted text in its body on the right-hand side of the browser window.Copy the JSON-formatted text into a local JSON file.
Save it as
parameters.json
and note the path to it. This file is the Parameters File for the deployment.Open the shell of your choice and go to the folder or directory that contains the
cyclecloud-slurm-workspace
repository you cloned earlier.Accept the terms of the Cycle image plan:
az vm image terms accept --urn azurecyclecloud:azure-cyclecloud:cyclecloud8-gen2:latest
Run the following deployment command in a shell. Substitute values for fields in square brackets (be sure to delete the brackets). The current directory is as described in the previous step.
az deployment sub create --template-file ./cyclecloud-slurm-workspace/bicep/mainTemplate.bicep --parameters parameters.json --location [ANY AZURE LOCATION E.G. eastus] --name [OPTIONAL BUT HELPFUL, DELETE IF UNUSED]
Wait until the shell indicates that the deployment was successful. You can also track the progress of the deployment in the Azure portal. Go to the resource group shown in the UI, select Deployments from the Settings menu, and check the status of the deployment name that begins with "pid-" at the bottom of the displayed list.