Decision Management & Intelligence (ODM, DI)

Decision Management & Intelligence (ODM, DI)

Connect with experts and peers to elevate technical expertise, solve problems and share insights

 View Only

  • 1.  ODM deployment on Kubernetes

    Posted Mon September 05, 2022 05:39 AM
    I think there is a regression in the latest version of the Helm Chart to deploy ODM.
    Now, if you want to deploy a release only for Decision Center and Decision Runner, even when Decision Server Runtime is not enabled in the release, the Decision Server Runtime Console is deployed (it is supposed to be deployed only in runtime is enabled):
    decisionServerRuntime:
    enabled: false
    decisionCenter:
    enabled: true

    The easy solution is manually delete Pod, Services, Deployment and ReplicaSet created, but would be good if you can fix in coming version of the Chart.


    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------


  • 2.  RE: ODM deployment on Kubernetes

    Posted Wed September 07, 2022 10:36 AM
    Hi Eduardo,

    The behavior did not change. By default the components are enabled by default that means decisionRunner : true. This component require the Decision Server Console to be deployed.
    So if
    decisionServerRuntime:
    enabled: true
    or
    decisionRunner:
    enabled: true
    The Decision Server console is deployed.

    ------------------------------
    LAURENT GRATEAU
    ------------------------------

    Original Message


  • 3.  RE: ODM deployment on Kubernetes

    Posted Wed September 07, 2022 12:55 PM
    Edited by Eduardo Izquierdo Lázaro Wed September 07, 2022 12:56 PM

    Hi Laurent, you're right, that makes sense.

    However, this is an inconvenient related to another problem that I reported some time ago: the Helm Chart does not allow to specify a different DB for DS and for DC. IMO for PRODUCTION the DS and DC schemas should be in different DB instances as they are very different DBs and with very different usage pattern (one is for an interactive application with concurrence and the other is for a server side application with very low concurrence). I think you should support this in the ODM Helm Chart.

    To walk-around this, I usually deploy 2 releases of the Chart (one for DS and one for DC) pointing to a different DB. When decision runner is enabled in the DC Helm release, the console is duplicated.  I hope that deleting the Kubernetes objects of the console created in the DC Helm release and updating the reference to the testing server in the business console will work. Can you anticipate any potential problem here?

    Thanks.



    ------------------------------
    Eduardo Izquierdo Lázaro
    Automation Architect
    DECIDE
    Madrid
    609893677
    ------------------------------

    Original Message


  • 4.  RE: ODM deployment on Kubernetes

    Posted Thu September 08, 2022 02:49 AM
    Hi Eduardo,

    It's possible to configure 2 differents datasources for the same helm chart release.
    You can follow this documentation : https://www.ibm.com/docs/da/odm/8.10?topic=database-configuring-custom-external

    Steps are :
    - Create 2 datasources files (1 for DC, 1 for the Runtime) (Step 1/2)
    - Create a secrets that reference this 2 files (Step 3)
    - Use the parameter 
    externalCustomDatabase.datasourceRef=customdatasource-secret
    To inject the 2 datasoures.

    I hope this will help you,

    Laurent

    ------------------------------
    LAURENT GRATEAU
    ------------------------------

    Original Message


Related Content