ai-center
2022.4
true
- Getting Started
- About this guide
- About installation
- Supported use cases for single-node and multi-node installations
- Downloading installation packages
- installUiPathAS.sh
- sf-installer.zip
- sf.tar.gz
- sf-infra.tar.gz
- du-ondemand.tar.gz
- cv-ondemand.tar.gz
- configureUiPathDisks.sh
- supportability-tools
- ansible.tar.gz
- Network requirements
- Requirements
- Single-node requirements and installation
- Requirements
- Configuring the machines
- Configuring the DNS
- Configuring MS SQL Server
- Configuring the certificates
- Configuring Orchestrator
- Online single-node installation
- Procedure
- Offline single-node installation
- Procedure
- Multi-node requirements and installation
- Requirements
- Configuring the machines
- Configuring the load balancer
- Configuring the DNS
- Configuring MS SQL Server
- Configuring the certificates
- Configuring Orchestrator
- Online multi-node installation
- Procedure
- Offline multi-node installation
- Procedure
- Post-installation
- Overview
- Accessing AI Center
- Provision an AI Center tenant
- Updating Orchestrator and Identity Server certificates
- Resizing PVC
- Adding a new node to the cluster
- ML packages offline installation
- Configuring the cluster
- Configuring the FQDN post-installation
- Backing up and restoring the cluster
- Using the monitoring stack
- Setting up a Kerberos authentication
- Provisioning a GPU
- Provisioning a GPU
- Using the configuration file
- About the configuration file
- Node scheduling
- Manage node scheduling
- Migration and upgrade
- Migrating to the standalone or Automation Suite environment
- Upgrading AI Center
- Online upgrade
- Offline upgrade
- Rollback on error
- Downgrading Ceph from 16.2.6 to 15.2.9
- Basic Troubleshooting Guide
- General AI Center troubleshooting and FAQs
- AI Center standalone troubleshooting
- Troubleshooting
- Alert runbooks
- Using the Diagnostics Tool
- Using the Support Bundle Tool
- Exploring logs

AI Center Installation Guide
Last updated Jun 6, 2024
The AI Center cluster is exposing multiple URLs to access the cluster management tools and the suite core functionality, all based on a common FQDN.
You need to configure the DNS for the common FQDN and the subdomains specific to each tool as shown in the following table.
| Application | Domain | Example URL |
|---|---|---|
| AI Center | fqdn | aicenter.mycompany.com |
| Application Lifecycle Management (ALM) | alm.{{fqdn | alm.aicenter.mycompany.com |
| Monitoring / Observability | monitoring.{{fqdn | monitoring.aicenter.mycompany.com |
| Object Store | objectstore.{{fqdn | objectstore.aicenter.mycompany.com |
| Docker Registry | registry.{{fqdn | registry.aicenter.mycompany.com |
| Insights | insights.{{fqdn | insights.aicenter.mycompany.com |
Add a
A Record in Advanced DNS or Management section of your domain as shown in the following table:
| Type | Host | Value |
|---|---|---|
A Record (or CName)
| automationsuite (or a subdomain to access Automation Suite)
|
|
A Record (or CName)
| *.automationsuite (or a subdomain to access Automation Suite)
|
|
See the following example for the configuration:
Note: If the
* wildcard is too generic, add a separate record or rule for the following subdomains: alm, monitoring, objectstore, registry and insights.