Home
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..

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.
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 an Openstack Credential
  Add an OpenStack Cloud account to NavOps you can later add a cloud credential in NavOps.
- Prerequisites for Openstack Cloud Scaling
  Components that are necessary for OpenStack cloud scaling.
- Create an Openstack Cloud Environment
  Create an OpenStack cloud environment so that workload manager execution nodes can be deployed in the cloud. Provide information about the cloud environment such as region, OS image, subnet id, security group id and tags
- Create an Openstack Node Class
  Create an Openstack Node Class so that workload manager execution nodes can be deployed in the cloud. A Node Class provides the infrastructure for the workload to run on. It is a template of an instance which defines benchmarked hardware. A Node Class exists in an Environment and consists of instance type, OS image, security group id, tags, SSH-keys and cloud-init script.
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

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..

OpenStack is a set of software tools for building and managing cloud computing platforms for public and private clouds. OpenStack software controls large pools of compute, storage, and networking resources throughout a datacenter, managed through a dashboard or through the OpenStack API.

OpenStack cloud scaling is available for sites that have installed their own OpenStack private cloud on their premises and want to manage cloud scaling through NavOps. Since OpenStack installations can be highly diverse, it is recommended to work with your Altair support team to set up cloud scaling via OpenStack as not all implementations may be supported.