Installing Maximo AI Service by using the CLI in noninteractive mode

You can install Maximo® AI Service by using the Maximo Application Suite CLI in noninteractive mode.

1. Copy the Maximo Application Suite CLI license to a local folder, for example, /home/{user}/git/devops-configs.
   For more information about obtaining the license, see Setting up IBM Maximo Application Suite.
2. Open a command line and run the following command.

   docker run -v /home/{user}/git/devops-configs:/tmp -ti --rm --pull always quay.io/ibmmas/cli:master

3. Ensure that the installation process is successful. The following text is an example of the installation process. Provide values during the installation process and follow the prompts. *** denotes a 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 5c9621f2a073 skipped: already exists
   Copying blob fe0a337f348a skipped: already exists
   Copying blob 2686ea3b22ef skipped: already exists
   Copying blob 47f5b092a7aa skipped: already exists
   Copying blob 76feb2c4dd7f skipped: already exists
   Copying blob 8bc213e3816c skipped: already exists
   Copying blob 0df697abec85 skipped: already exists
   Copying config 3bafaf4d51 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
   
   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 "***e" \
     --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