2025.1.0
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.
Create an image of the virtual machine configured per your site's requirements.
New and updated features in Altair NavOps 2025.1.0.
Cloud cost tracking, Automation based scalability, and Cloud migration for HPC.
An introduction to cloud scaling, a typical scaling setup and an overview of steps to set up 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.
Register NavOps with Azure so that you can later add a cloud credential in NavOps.
Add an Azure cloud account to NavOps so that you can create a cloud environment or an appliance.
Create a resource group that will contain a virtual network and a virtual machine for cloud bursting.
Create a virtual network so that you can later create a virtual machine for cloud bursting.
Create a virtual machine in Azure.
Install Accelerator on the virtual machine and configure the VM per your site's environment.
Install the PBS Professional MoM on the virtual machine and configure the VM per your site's environment.
Install the Grid Engine Execd on the virtual machine and configure the VM per your site's environment.
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 image of the Linux virtual machine configured per your site's requirements.
Create an image of the Windows virtual machine configured per your site's requirements.
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 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.
Requirements for deploying Windows cloud nodes.
Create the necessary components in GCP that are required for cloud scaling and then add your Credential to NavOps before creating a cloud environment.
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.
Create the necessary components in OpenStack that are required for cloud scaling and then add your credential to NavOps before creating a cloud environment..
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 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 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 when they are no longer needed.
Create rules to automatically scale-up and scale-down deployment of nodes on the cloud.
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.
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.
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.
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 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.
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.
