Installation du service Maximo AI à l'aide de l'interface CLI en mode interactif

Vous pouvez installer Maximo® AI Service à l' aide de l'interface de programmation (CLI) en mode interactif Maximo Application Suite CLI en mode interactif.

Procédure

  1. Copiez la licence CLI Maximo Application Suite dans un dossier local, par exemple /home/{user}/git/devops-configs.

    Pour plus d'informations sur l'obtention de la licence, voir Configuration de IBM Maximo Application Suite.

  2. Ouvrez une ligne de commande et exécutez la commande suivante.
    docker run -v /home/{user}/git/devops-configs:/tmp -ti --rm --pull always quay.io/ibmmas/cli:master
  3. Assurez-vous que le processus d'installation s'est déroulé correctement. Le texte suivant est un exemple de la procédure d'installation. Indiquez les valeurs au cours de la procédure d'installation et suivez les instructions. *** désigne une variable.
    [***~]$ docker run -v /home/***/git/***:/tmp -ti --rm --pull always quay.io/ibmmas/cli:master
Trying to pull quay.io/ibmmas/cli:master...
Getting image source signatures
Copying blob 095405e15023 done   |
Copying blob 671f5ec6b9c1 done   |
Copying blob 4fa67d0346c5 done   |
Copying blob 706d1e2e240b done   |
Copying blob 0df697abec85 skipped: already exists
Copying blob 11ea16df3746 done   |
Copying blob 9b4960ee63a1 done   |
Copying config 7e92c566f5 done   |
Writing manifest to image destination
IBM Maximo Application Suite CLI Container ***

https://github.com/ibm-mas/ansible-devops
https://github.com/ibm-mas/cli

MAS Management:
  - mas install to install a new MAS instance
  - mas update to apply a new catalog update
  - mas upgrade to upgrade an existing MAS install to a new release
  - mas must-gather to perform must-gather against the target cluster
  - mas uninstall to uninstall a MAS instance
  - mas configtool-oidc to configure OIDC integration
Disconnected Install Support:
  - mas setup-registry to setup a private container registry on an OCP cluster
  - mas teardown-registry to delete a private container registry on an OCP cluster
  - mas mirror-images to mirror container images required by MAS to a private registry
  - mas configure-airgap to configure a cluster to use a private registry as a mirror
OpenShift Cluster Management:
  - mas provision-aws to provision an OCP cluster on AWS
  - mas provision-roks to provision an OCP cluster on IBMCloud Red Hat OpenShift Service (ROKS)
  - mas provision-rosa to provision an OCP cluster on AWS Red Hat OpenShift Service (ROSA)
  - mas provision-fyre to provision an OCP cluster on IBM DevIT Fyre (internal)
AI Service (Standalone) Management:
  - mas aiservice-install to install a new AI Service instance

[ibmmas/cli:***]mascli$  mas aiservice-install

IBM Maximo Application Suite Admin CLI v***
Powered by https://github.com/ibm-mas/ansible-devops/ and https://tekton.dev/

AI Broker 9.0 Deprecation Notice

Maximo AI Broker (introduced with MAS 9.0) has been replaced with Maximo AI Service as of Aug 1 2025
To continue using the features that were enabled by the AI broker after that time, you must deploy and use Maximo AI Service 9.1:
 - Maximo AI Service 9.1 is compatible with both Maximo Application Suite 9.0 and 9.1 releases
 - If Maximo AI Service is deployed with Maximo Application Suite 9.0, you can use only the AI features that were included in Maximo Application Suite 9.0

Note: Maximo AI Service 9.1 includes a limited-use license to watsonx.ai and incurs an additional AppPoint cost

1) Set Target OpenShift Cluster
Server URL: ***
Login Token: ***
Disable TLS Verify? [y/n] y

2) IBM Maximo Operator Catalog Selection
The catalog you choose dictates the version of everything that is installed, with Maximo Application Suite this is the only version you need to remember; all other versions are determined by this choice.
Older catalogs can still be used, but we recommend using an older version of the CLI that aligns with the release date of the catalog.
 - Learn more: https://ibm-mas.github.io/cli/catalogs/

Supported Catalogs:
 - ***

Select catalog ***

Catalog Details
Catalog Image:         ***
Catalog Digest:        ***
AI Service Releases:   9.1
MongoDb:               ***

Two types of release are available:
 - GA releases of Maximo Application Suite are supported under IBM's standard 3+1+3 support lifecycle policy.
 - 'Feature' releases allow early access to new features for evaluation in non-production environments and are only supported through to the next GA release.

┌────────────┬───────┐
│            │ 9.1   │
├────────────┼───────┤
│ AI Service │ ***│
└────────────┴───────┘
Select release ***

3) License Terms
To continue with the installation, you must accept the license terms:
 - ***
Do you accept the license terms? [y/n] y

4) Configure Storage Class Usage
Maximo Application Suite and it's dependencies require storage classes that support ReadWriteOnce (RWO) and ReadWriteMany (RWX) access modes:
  - ReadWriteOnce volumes can be mounted as read-write by multiple pods on a single node.
  - ReadWriteMany volumes can be mounted as read-write by multiple pods across many nodes.

Storage provider auto-detected: NFS Client
  - Storage class (ReadWriteOnce): nfs-client
  - Storage class (ReadWriteMany): nfs-client
Use the auto-detected storage classes? [y/n] y

5) Configure AppPoint Licensing
By default the AI Service instance will be configured to use a cluster-shared License, this provides a shared pool of AppPoints available to all MAS & AI Service instances on the cluster.

Alternatively you may choose to install using a dedicated license only available to this AI Service instance.
  1. Install AI Service with Cluster-Shared License (AppPoints)
  2. Install AI Service with Dedicated License (AppPoints)
SLS Mode 1
License file ***
Contact e-mail address ***
Contact first name ***
Contact last name ***
IBM Data Reporter Operator (DRO) Namespace ***

6) Configure IBM Container Registry
IBM entitlement key ***

7) Configure AI Service Instance
Instance ID restrictions:
 - Must be 3-12 characters long
 - Must only use lowercase letters, numbers, and hypen (-) symbol
 - Must start with a lowercase letter
 - Must end with a lowercase letter or a number
Instance ID ***

8) Configure Operational Mode
Maximo Application Suite can be installed in a non-production mode for internal development and testing, this setting cannot be changed after installation:
 - All applications, add-ons, and solutions have 0 (zero) installation AppPoints in non-production installations.
 - These specifications are also visible in the metrics that are shared with IBM and in the product UI.

  1. Production
  2. Non-Production
Operational Mode 1

9) AI Service Settings

9.1) Storage Configuration
AI Service requires object storage for pipelines, tenants, and templates. You can either install MinIO in-cluster or connect to external storage.
Install Minio? [y/n] y
minio root username ***
minio root password ***

10) AI Service Tenant Settings
AI Service will reserve AppPoints for a fixed period of time based on the values you enter:
Tenant entitlement type ***
Entitlement end date (YYYY-MM-DD) ***

11) WatsonX Integration
This CLI section configures the integration between the AI Service and IBM watsonx.ai. AI Service
uses watsonx for model deployment and inferencing.

The WatsonX API key must be a **platform API key** associated with a user that has at least:
- **Editor permission** for the project
- **Viewer permission** for the space
You can generate this key by following IBM's documentation: https://www.ibm.com/docs/en/watsonx/w-and-w/2.2.0?topic=tutorials-generating-api-keys#api-keys__platform__title__1

The endpoint URL is your WatsonX Machine Learning service URL. It can be found in the watsonx.ai
documentation: https://cloud.ibm.com/apidocs/watsonx-ai-cp/watsonx-ai-cp-2.2.0#endpoint-url

The project ID refers to your specific watsonx.ai project where your ML models and assets are stored.

Watsonxai api key ***
Watsonxai machine learning url ***
Watsonxai project id ***

12) RSL Integration
RSL (Reliable Strategy Library) connects to strategic asset management via STRATEGIZEAPI.

RSL URL: *** 
Org ID: Get from MAS Manage > System Properties > 'mxe.rs.rslorgid'
Token: Use your IBM entitlement key (same as MAS installation)

Note: Future versions will auto-configure these from MAS Manage.

RSL url ***
ORG Id of RSL ***
Token for RSL ***
Does the RSL API use a self-signed certificate?? [y/n] y
RSL CA certificate (PEM format) ***

13) Configure MongoDb
The installer can setup mongoce in your OpenShift cluster (available only for amd64) or you may choose to configure MAS to use an existing mongodb
Create MongoDb cluster using MongoDb Community Edition Operator? [y/n] y
MongoDb namespace mongoce

14) Non-Interactive Install Command
Save and re-use the following script to re-run this install without needing to answer the interactive prompts again

export IBM_ENTITLEMENT_KEY=***
mas aiservice-install --mas-catalog-version *** --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
  --aiservice-instance-id  "***" \
  --storage-class-rwo "***" --storage-class-rwx "***" \
  --storage-pipeline "***" --storage-accessmode "***" \
  --license-file "***" \
  --uds-email "***" --uds-firstname "***" --uds-lastname "***" \
  --dro-namespace "***" \
  --mongodb-namespace "***" \
  --aiservice-channel "***" \
  --s3-accesskey "***" \
  --s3-secretkey "***" \
  --s3-host "***" \
  --s3-port "***" \
  --s3-ssl "***" \
  --s3-region "***" \
  --s3-bucket-prefix "***" \
  --s3-tenants-bucket "***" \
  --s3-templates-bucket "***" \
  --watsonxai-apikey "***" \
  --watsonxai-url "***" \
  --watsonxai-project-id "***" \
  --watsonxai-username "***" \
  --watsonxai-version "***" \
  --watsonxai-ca-crt "***" \
  --minio-root-user "***" \
  --minio-root-password "***" \
  --tenant-entitlement-type "***" \
  --tenant-entitlement-start-date "***" \
  --tenant-entitlement-end-date "***" \
  --rsl-url "***" \
  --rsl-org-id "***" \
  --rsl-token "Bearer ***" \
  --rsl-ca-crt "***" \
  --accept-license --no-confirm

15) Review Settings
Connected to:
 - https://console-openshift-console.apps.***

15.1) Pipeline Configuration
  Service Account ......................... Default
  Image Pull Policy ....................... Default
  Skip Pre-Install Healthcheck ............ No

15.2) OpenShift Container Platform
  Worker Node Architecture ................ ***
  Storage Class Provider .................. ***
  ReadWriteOnce Storage Class ............. ***
  ReadWriteMany Storage Class ............. ***
  Certificate Manager ..................... ***
  Cluster Ingress Certificate Secret ...... Default

15.3) Maximo Operator Catalog
  Catalog Version ......................... ***

15.4) IBM Container Registry
  IBM Entitled Registry ................... ***
  IBM Open Registry ....................... ***

15.5) AI Service
  Release ................................. ***
  Instance ID ............................. ***
  Environment Type ........................ ***

15.6) AI Service Tenant Entitlement
  Entitlement Type ........................ ***
  Start Date .............................. ***
  End Date ................................ ***

15.7) S3 Configuration
  Minio Root Username ..................... ***

  Host .................................... ***
  Port .................................... ***
  SSL Enabled ............................. ***
  Region .................................. ***
  Bucket Prefix ........................... ***
  Templates Bucket Name ................... ***
  Tenants Bucket Name ..................... ***

15.8) IBM WatsonX
  URL ..................................... ***
  Project ID .............................. ***
15.9) RSL
  URL ..................................... ***
  Organization ID ......................... ***

15.10) IBM Data Reporter Operator (DRO) Configuration
  Contact e-mail .......................... ***
  First name .............................. ***
  Last name ............................... ***
  Install Namespace ....................... ***

15.11) IBM Suite License Service
  Namespace ............................... ***
  Subscription Channel .................... ***
  IBM Open Registry ....................... ***
  License File ............................ ***

15.12) MongoDb
  Type .................................... ***
  Install Namespace ....................... ***

15.13) IBM Db2 Univeral Operator Configuration
  Action .................................. install
  Install Namespace ....................... Default
  Subscription Channel .................... Default

Please carefully review your choices above, correcting mistakes now is much easier than after the install has begun
Proceed with these settings? [y/n] y

16) Launch Install
If you are using storage classes that utilize 'WaitForFirstConsumer' binding mode choose 'No' at the prompt below
Wait for PVCs to bind? [y/n] y
✅️ OpenShift Pipelines Operator is installed and ready to use
✅️ Namespace is ready (***)
✅️ MAS CLI image deployment test completed
✅️ Latest Tekton definitions are installed (***)
✅️ PipelineRun for apmdevops install submitted

View progress:
  ***