Home
Get Started
Cloud cost tracking, Automation based scalability, and Cloud migration for HPC.
NavOps Workspace
Overview of the NavOps workspace.
API Keys
NavOps uses API keys to connect the NavOps server, WLM agent, head node and cloud nodes. The key is generated and displayed once. The key is generated for a specific cluster. It 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.

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.
- Log into NavOps
  Login to NavOps using the URL https://<hostname>:<port>/.
- NavOps Welcome Screen
  When you login to NavOps for the first time, a quick setup screen helps you get started.
- NavOps Workspace
  Overview of the NavOps workspace.
  - NavOps Home
    The NavOps Home page provides a dashboard to quickly view the current status and navigate to the main pages of the application.
  - Clusters
    NavOps supports Accelerator, PBS Professional, Grid Engine and Slurm workload managers. The type, id, name, state and other details of the registered clusters are displayed in the cluster page.
  - Credentials
    Cloud credentials provide the authentication to perform the required scaling actions in the cloud. One or more accounts can be added in one or more clouds. Amazon Web Services (AWS), Azure, Google Cloud Platform (GCP) and Oracle Cloud Infrastructure (OCI) are supported.
  - Environments
    Cloud Environment captures the cloud region and networking infrastructure within a cloud credential to support deployment of a Node Class.
  - Node Class
    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, Image, SSH-Keys, cloud-init, and Tags.
  - Inventory
    The Inventory displays a list of all the nodes deployed by NavOps during the scaling process. It shows the overall number of nodes, vcores and burn rate. You can filter the information by Cloud providers, Cloud credentials, Cloud environments, Node classes and Cost center.
  - Operations
    The Operations page displays a list of NavOps operations for specified time frame. You can filter the information by selecting the duration (Last 5 minutes to Last 7 days) and specifying the From and To date and time.
  - Tasks
    The Tasks page displays a list of all the tasks executed by NavOps. You can filter the information by Deploy and Undeploy tasks.
  - API Keys
    NavOps uses API keys to connect the NavOps server, WLM agent, head node and cloud nodes. The key is generated and displayed once. The key is generated for a specific cluster. It 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.
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.
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

API Keys

NavOps uses API keys to connect the NavOps server, WLM agent, head node and cloud nodes. The key is generated and displayed once. The key is generated for a specific cluster. It 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.

Click Add API Key to generate and add a new API Key. You can specify an expiry date or use the default date (1 year duration).

Click settings () to select the columns to be displayed in the table.

Columns Settings for NavOps API Keys — Figure 2. API Keys Columns