Skip to main content

Deployment

Generally, HPCBOX is deployed directly from your Cloud Resource provider's marketplace, for example, Azure Marketplace or Google Cloud Marketplace.

In some cases, you will need to contact HPCBOX support at boxhelp[at]drizti.com or at HPCBOX Support to enable the HPCBOX deployment assets to appear as a private offer within your Cloud Subscription.

Microsoft Azure​

On Microsoft Azure, make sure you have Contributor privileges and search for HPCBOX within Azure Portal

Use the self-guided Azure Portal Wizard to deploy HPCBOX within your subscription.

Search for HPCBOX​

Searching for HPCBOX on Azure Portal will display all flavors of HPCBOX available for deployment within your subscription. Please contact HPCBOX Support at boxhelp[at]drizti.com or at HPCBOX Support for assistance in helping you select the correct cluster configuration for your application needs.

Azure Portal step 1

Once you select the flavor of HPCBOX suitable to your needs, click on the Create button to launch the Azure Portal deployment Wizard for HPCBOX.

Basics​

On the first page of the wizard, provide basic settings for your HPCBOX Cluster including ResourceGroup, Location and a Tag for easy identification for your HPCBOX cluster.

tip

Hovering over the ℹ️ icon displays further information on the specific option.

info

The Tag name is also used to save the connection profile in case your HPCBOX cluster has multiple login nodes. This connection profile is saved in the ConnectApp on the user's workstation and further information on this can be found in the Connecting section of the documentation.

Azure Portal step 2

Cluster Settings​

In the next section of the wizard, we can:

  • select the type of worker nodes we want to have on our HPCBOX cluster and the Azure hardware SKU size for each worker type.

  • select either a cluster attached disk and its size for cluster storage or specify an external file server like Azure NetApp.

    • if selecting cluster attached storage, we can specify the size for our user HOME directories and a storage reserved for installing applications on the cluster.

  • select an existing Virtual network/Subnet or create a new one dedicated to the HPCBOX cluster.

    Azure Portal step 4

    info

    If selecting an existing VNET/Subnet, make sure that your initial deployment of HPCBOX does not include workers of any type. Once the cluster is deployed with just the head/management node, assign Network Contributor or Contributor role to the node's identity on the Virtual Network before trying to add new worker nodes as described in Resizing.

    Completion​

    Once the HPCBOX cluster is successfully deployed, navigate to the selected resourcegroup and review the resources that were created as part of the deployment. Look for a Virtual Machine ending with -m-01.

    Azure Portal step 4

    This will be your HPCBOX Head/Management node and the one you will be connecting to for management and operation of your cluster.