Home
Configure Microsoft Azure Cloud Scaling
Create the necessary components in Microsoft Azure that are required for cloud scaling and then add your Credential to NavOps before creating a cloud environment.
Install PBS MoM on the VM
Install the PBS Professional MoM on the virtual machine and configure the VM per your site's environment.

Welcome
What's New
New and updated features in Altair NavOps 2025.1.0.
Get Started
Cloud cost tracking, Automation based scalability, and Cloud migration for HPC.
Cloud Scaling Overview
An introduction to cloud scaling, a typical scaling setup and an overview of steps to set up cloud scaling.
Configure Amazon Web Service Cloud Scaling
Create the necessary components in AWS that are required for cloud scaling and then add your credential to NavOps before creating a cloud environment.
Configure Microsoft Azure Cloud Scaling
Create the necessary components in Microsoft Azure that are required for cloud scaling and then add your Credential to NavOps before creating a cloud environment.
- Register the NavOps Application with Azure
  Register NavOps with Azure so that you can later add a cloud credential in NavOps.
- Add a Microsoft Azure Credential
  Add an Azure cloud account to NavOps so that you can create a cloud environment or an appliance.
- Create a Resource Group
  Create a resource group that will contain a virtual network and a virtual machine for cloud bursting.
- Create a Virtual Network
  Create a virtual network so that you can later create a virtual machine for cloud bursting.
- Create a Virtual Machine
  Create a virtual machine in Azure.
- Install Accelerator on the VM
  Install Accelerator on the virtual machine and configure the VM per your site's environment.
- Install PBS MoM on the VM
  Install the PBS Professional MoM on the virtual machine and configure the VM per your site's environment.
- Install Grid Engine Execd on the VM
  Install the Grid Engine Execd on the virtual machine and configure the VM per your site's environment.
- Install Slurm on the VM
  Install Slurm on the Linux virtual machine and configure the VM per your site's environment. Follow the instructions in the Slurm Quick Start Administrator Guide.
- Create an OS Image
  Create an image of the virtual machine configured per your site's requirements.
- Create an Azure Cloud Environment
  Create an Azure cloud environment so that Accelerator execution nodes can be deployed in the cloud. Provide information about the cloud environment such as region, OS image, resource group name, network name, network security group name, subnet name, managed storage, maximum number of VMs per low latency network and tags.
- Create an Azure Node Class
  Create an Azure Node Class so that Accelerator execution nodes can be deployed in the cloud. A Node Class provides the infrastructure for the workload to run on. It is an instance type which defines benchmarked hardware. A Node Class exists in an Environment and consists of instance type, OS image, security group id, network security group, tags, SSH-keys and cloud-init script.
Windows Deployment on AWS and Azure
Requirements for deploying Windows cloud nodes.
Configure Google Cloud Platform Cloud Scaling
Create the necessary components in GCP that are required for cloud scaling and then add your Credential to NavOps before creating a cloud environment.
Configure Oracle Cloud Scaling
Create the necessary components in Oracle Cloud that are required for cloud scaling and then add your Credential to NavOps before creating a cloud environment.
Configure Openstack for Cloud Scaling
Create the necessary components in OpenStack that are required for cloud scaling and then add your credential to NavOps before creating a cloud environment..
Add, Register, and Deploy a Cluster
After creating a cluster, it has to be registered by installing the NavOps CLI and agent. You can add node configurations containing custom resources and scripts and deploy the cluster.
Node Configurations
Node configurations enable you to customize a node associated with a cluster. Compared to operations performed via the cloud-init script these configurations are managed on the WLM server increasing flexibility and security. Node configurations are supported for PBS, Grid Engine and Slurm clusters.
Deploy Cloud Nodes Manually
Deploy nodes manually (without the intervention of the workload manager) for testing purposes or when your site wants to keep nodes deployed for an indeterminate amount of time.
Undeploy Cloud Nodes Manually
Undeploy cloud nodes when they are no longer needed.
Automate Cloud Scaling for Accelerator
Create rules to automatically scale-up and scale-down deployment of nodes on the cloud.
Automate Cloud Scaling for PBS Professional
Create rules to automatically scale-up and scale-down deployment of nodes on the cloud. Use node configuration to customize a node associated with a PBS cluster.
Automate Cloud Scaling for Grid Engine
Create rules to automatically scale-up and scale-down deployment of nodes on the cloud. Use node configuration to customize a node associated with a Grid Engine cluster.
Automate Cloud Scaling for Slurm
Create rules to automatically scale-up and scale-down deployment of nodes on the cloud. Use node configuration to customize a node associated with a Slurm cluster.
Generate API Keys
NavOps uses API keys to connect the NavOps server, WLM agent, head node and cloud nodes. Each cluster has a dedicated API KEY, if you would like to generate additional key please use the following instructions. The key is generated and displayed once. Make sure you save it as you won't be able to access it again. The key is generated for a specific cluster. The key is set on the deployed nodes. It is also present in the NavOps agent on the head node and the MoMs. The default expiry date of the key is one year. When the key expires, you can generate another one and replace the key manually on the head node.
Cost Center
Cost centers provide visibility of expenditure to dynamically manage cloud operations and plan ahead. Cost centers are associated with node delpoyments. The limits defined in the cost center are checked before deploying nodes. The estimated costs accrued by cost centers are displayed visually as well as in a table.
Accounting
The accounting dashboard provides a set of reports containing charts and tables tracking Burn Rate, Core Count, Node Count and Total Cost for the Cloud connector, Cloud credentials, Cloud environment, Node class and Cluster datasets. These reports can be produced for a custom date and time range or a set of preset date and time ranges.
Known Issues

Install PBS MoM on the VM

Install the PBS Professional MoM on the virtual machine and configure the VM per your site's environment.

Use SSH to connect to the virtual machine. For more information see Connect to your VM on Linux.

A startup script is provided during the creation of the cloud environment. This script (cloud-init script) is executed after a cloud node is deployed and is used to set up the system environment so that nodes deployed in the cloud can communicate with the workload manager. A service specifically designed for cloud instance initialization is cloud-init and is utilized by NavOps when booting cloud nodes, therefore it must be installed on the VM. For more information about installing cloud-init, refer to the Cloudinit Documentation.

The PBS Professional installer package will need to be copied to the virtual machine. Use SCP to copy the tarball file to the virtual machine. For more information, see Move files to and from a Linux VM using SCP.

SSH into the virtual machine using the public IP address of the VM:
```
ssh IPV4PublicIP
```
where IPV4PublicIP is the public IP address of the virtual machine.
Figure 1. Bursting Virtual Machine
Enter the command:
```
sudo -i
```
Copy the PBS Professional installation package to the VM.
Using the PBS Professional Installation Guide, install and configure the system. Make the path same as the one on the Head Node. The scaling process uses a lot of data from the server, this make it easier to run the cloud-init and create the environment.
Configure the VM for your site's environment such as mounting file systems, connecting it to the authentication service, installing any applications, etc.
Check if cloud-init is installed. For example:
```
yum list installed | grep cloud
```
If cloud-init is not present, install it. For example:
```
yum install cloud-init
```
Submit a job and test to ensure it is working as expected.
Disable PBS so that your image won't boot up with it.: systemctl stop pbs; systemctl disable pbs