Maximo

 View Only

  • 1.  AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 15 days ago

    I am doing a new install of the IBM Maximo Application Suite (BYOL) in AWS and on the "Specify stack details" page  (2nd page of the install) I need to provide a MASLicenseUrl but in order to generate a License file I must provide a hostname which I do not yet know as AWS has not set anything up yet? How do I get what my hostname will be to create the License File in the License Key Center?

    Please help?

    Thanks in advance,



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------


  • 2.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 15 days ago

    Will localhost work until I get stuff setup and then I can come back and modify a YAML file with the real names?



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 3.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 14 days ago
    Edited by Arif Ali 14 days ago

    sls.ibm-sls.svc

    This is an internal hostname of the SLS service.

    I use this most often. However, technically it does not matter what you provide as a hostname in the license file itself (when you are generating the license file from the license key center perspective). The URL field in the BYOL automation is looking for a host where you'd end up hosting this file (likely a S3 bucket URL).

    I recommend a study of this Ansible Role to get a good grasp on how SLS can be customized (when you do have to customize).



    ------------------------------
    Arif Ali
    ------------------------------

    Original Message


  • 4.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 14 days ago

    Thank you for the response. I was just using an IP address I had in AWS free and assumed I would just make a config file change after install once I go there. It has been running the install just fine. I see the IP addy at the header of the license.dat file.

    Now I am fighting why I get this from AWS when I do the installer:

    2024-04-30T19:37:40.122-04:00    │ Comments
    2024-04-30T19:37:40.122-04:00    │ --------
    2024-04-30T19:37:40.122-04:00    │  * Validation = 'FAILED'
    2024-04-30T19:37:40.122-04:00
    │     There are not enough resources available to create the desired infrastructure in that region.

    │  There are not enough resources available to create the desired infrastructure in that region.
    2024-04-30T19:37:40.122-04:00    │  Recommendation:
    2024-04-30T19:37:40.122-04:00    │  - Cleanup resources in that region.
    2024-04-30T19:37:40.123-04:00    │  - Specify a different region.
    2024-04-30T19:37:40.123-04:00    │ "Resource Quota Validation Failed"
    2024-04-30T19:37:40.123-04:00    │ 
    2024-04-30T19:37:40.123-04:00    ╵
    2024-04-30T19:37:42.377-04:00    2024-04-30 23:37:39 ==== OCP cluster creation completed ====

    Seems pretty crazy the IBM is breaking the resources for all of EAST N., VIRGINIA when trying to do an install. LOL

    Backed it all out and trying it again. Will open ticket with IBM next if it breaks a 3rd time.

    Thanks,



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 5.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 14 days ago

    Have you looked through this documentation for any clues?  Sounds like you may have a service quota problem?

    https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=services-troubleshooting-installation-problems



    ------------------------------
    Arif Ali
    ------------------------------

    Original Message


  • 6.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    IBM Champion
    Posted 13 days ago

    Hi-

    Can I suggest trying the steps in this  AWS Workshop: https://catalog.us-east-1.prod.workshops.aws/workshops/78554b88-0cd8-45a1-b9ee-2c1078aa6995/en-US

    It has a step by step walkthrough for deploying MAS on AWS, and also discusses the default quota limits that need to be changed.



    ------------------------------
    Mark Brown
    AWSSr. Partner Solution Architect
    ------------------------------

    Original Message


  • 7.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 12 days ago

    @Mark, is there a way to get this AWS documentation updated for the latest release? The versions of OCP/MAS I see are outdated for some time.



    ------------------------------
    Arif Ali
    ------------------------------

    Original Message


  • 8.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 12 days ago

    I agree, it was a challenge.

    Also, it would be nice if the documentation told us somewhere how long the install takes. I have been running for 8 hours now and it is stuck on 

    2024-05-02T11:49:37.938-04:00 TASK [ibm.mas_devops.suite_app_verify : Wait for application workspace to be ready (480s delay)] ***


    For the past 6 hours. I can log into the Cluster and I see what appears to be all the parts that are needed but on the AWS side I am seeing 34 items with CREATE_IN_PROGRESS and only 13 CREATE_COMPLETE. I have a ticket with IBM open and the person has informed me it will take 10-12 hours. I feel like I may be stuck but I will give it until tomorrow to see if it finishes.

    I already see 

    9 Nodes
    436 Pods
    6 StorageClasses
    18 PersistentVolumeClaims

    In the cluster and under installed operators I am seeing all this:

    IBM Cert Manager
    3.25.9 provided by IBM

    IBM Cloud Pak foundational services
    3.23.10 provided by IBM

    IBM Maximo Manage
    8.7.3 provided by IBM

    IBM Maximo Application Suite
    8.11.5 provided by IBM

    IBM NamespaceScope Operator
    1.17.9 provided by IBM

    IBM Suite License Service
    3.8.1 provided by IBM

    IBM Truststore Manager
    1.5.1 provided by IBM

    IBM Truststore Manager
    1.5.1 provided by IBM

    OpenShift Data Foundation
    4.12.12-rhodf provided by Red Hat

    Operand Deployment Lifecycle Manager
    1.21.9 provided by IBM


    Package Server
    0.19.0 provided by Red Hat

    Crunchy Postgres for Kubernetes
    5.5.1 provided by Crunchy Data

    IBM User Data Services
    2.0.12 provided by IBM Digital Growth and Commerce

    It really seem like all is there and just AWS has a bug on the last things it thinks it still needs to do.

    DeployWaitCondition
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeployWaitCondition
    CREATE_IN_PROGRESS
    		 - -
    Bootnode
    CREATE_COMPLETE
    		 - -
    Bootnode
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    Bootnode
    CREATE_IN_PROGRESS
    		 - -
    BootnodeSecurityGroup
    CREATE_COMPLETE
    		 - -
    BootnodeSecurityGroup
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    BootnodeSecurityGroup
    CREATE_IN_PROGRESS
    		 - -
    CallLambdaFunctionGetSubnetForBootnode
    CREATE_COMPLETE
    		 - -
    CallLambdaFunctionGetSubnetForBootnode
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeploymentRoleProfile
    CREATE_COMPLETE
    		 - -
    DeploymentRoleProfile
    CREATE_IN_PROGRESS
    		Eventual consistency check initiated
    DeploymentRoleProfile
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeploymentRoleProfile
    CREATE_IN_PROGRESS
    		 - -
    DeploymentRole
    CREATE_COMPLETE
    		 - -
    DeploymentConfigBucket
    CREATE_COMPLETE
    		 - -
    DeploymentRole
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeploymentRole
    CREATE_IN_PROGRESS
    		 - -
    DeploymentConfigBucket
    CREATE_IN_PROGRESS
    		Eventual consistency check initiated
    DeploymentConfigBucket
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    CallLambdaGetHostedZoneName
    CREATE_COMPLETE
    		 - -
    CallLambdaGetHostedZoneName
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeploymentConfigBucket
    CREATE_IN_PROGRESS
    		 - -
    CallLambdaRandomizer
    CREATE_COMPLETE
    		 - -
    CallLambdaRandomizer
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    CallLambdaFunctionGetSubnetForBootnode
    CREATE_IN_PROGRESS
    		 - -
    CallLambdaRandomizer
    CREATE_IN_PROGRESS
    		 - -
    CallLambdaGetHostedZoneName
    CREATE_IN_PROGRESS
    		 - -
    LambdaFunctionGetSubnetForBootnode
    CREATE_COMPLETE
    		 - -
    LambdaFunctionRandomizer
    CREATE_COMPLETE
    		 - -
    LambdaFunctionGetHostedZoneName
    CREATE_COMPLETE
    		 - -
    LambdaFunctionGetSubnetForBootnode
    CREATE_IN_PROGRESS
    		Eventual consistency check initiated
    LambdaFunctionRandomizer
    CREATE_IN_PROGRESS
    		Eventual consistency check initiated
    LambdaFunctionGetHostedZoneName
    CREATE_IN_PROGRESS
    		Eventual consistency check initiated
    LambdaFunctionGetSubnetForBootnode
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    LambdaFunctionRandomizer
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    LambdaFunctionGetHostedZoneName
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    LambdaFunctionRandomizer
    CREATE_IN_PROGRESS
    		 - -
    LambdaFunctionGetSubnetForBootnode
    CREATE_IN_PROGRESS
    		 - -
    LambdaFunctionGetHostedZoneName
    CREATE_IN_PROGRESS
    		 - -
    LambdaRole
    CREATE_COMPLETE
    		 - -
    LambdaRole
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    DeployWaitConditionHandle
    CREATE_COMPLETE
    		 - -
    DeployWaitConditionHandle
    CREATE_IN_PROGRESS
    		 - Resource creation Initiated
    LambdaRole
    CREATE_IN_PROGRESS
    		 - -
    DeployWaitConditionHandle
    CREATE_IN_PROGRESS
    		 - -
    eipmas811
    CREATE_IN_PROGRESS
    		 - User Initiated


    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 9.  RE: AWS IBM Maximo Application Suite (BYOL) Install Hostname? License Key Center

    Posted 12 days ago

    My install broake after running for 10 hours. It hung on the 

    2024-05-02T11:49:37.938-04:00 TASK [ibm.mas_devops.suite_app_verify : Wait for application workspace to be ready (480s delay)] ***

    Eventually it came back with a 
    CREATE_FAILED

    On the Events Tab I have

    2024-05-02 20:02:30 UTC-0400eipmas811 CREATE_FAILED

    -The following resource(s) failed to create: [DeployWaitCondition].

    2024-05-02 20:02:30 UTC-0400DeployWaitCondition CREATE_FAILED

    -WaitCondition timed out. Received 0 conditions when expecting 1


    I have this error on the Resources tab

    DeployWaitConditionarn:aws:cloudformation:us-east-1:705711432389:stack/eipmas811/d73732d0-088b-11ef-9276-0affeae28239/d73d7460-088b-11ef-9276-0affeae28239/DeployWaitConditionHandle AWS::CloudFormation::WaitCondition CREATE_FAILED

    Working with support but interesting to see this stuff is still not stable. Glad they have 1 year to work out the kinks.



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message