ai-center
2022.4
true
- Getting Started
- Network requirements
- Single-node requirements and installation
- Multi-node requirements and installation
- Post-installation
- 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
- Using the configuration file
- Node scheduling
- Migration and upgrade
- Basic Troubleshooting Guide
AI Center Installation Guide
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.