IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Let the MDM Docker containers use environment settings from outside the image

The current Docker installable containers use static environment settings for for example database server, ldap server, kafka server, etc. This means we need to create an image for every environment increasing the possibility to have different code bases for the environments.

It would be better to externalize the environmental settings and pass then when the container starts. So the image can be made once and be used through the complete DTAP street. You then have the option to run multiple T environments (which now means yet an other image to be build).

Build 1 image and create multiple environment files. Creating an extra environment file most likely takes less time as creating a new image.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 25 2020
  • Not Under Consideration
Who would benefit from this IDEA? As a DEV engineer I only need to create 1 image instead of 1 per environment. As an OPS engineer I would like to run just 1 docker image for every environment so I don't need to take of the different images per environment.
Idea Priority High
Priority Justification Best practice to have environment specific settings not inside the image; Faster delivering of images (just 1 instead of 1 per environment; faster testing).
Customer Name ING
  • Attach files
  • Admin
    MAY LI commented
    28 Aug 04:25pm

    Hi Erik,

    We believe this type of customization can/should be performed by customers in their own environments (for example, by replacing values in configuration files with placeholders and then replacing placeholders in the startup scripts in the container, by reading values from ConfigMap and replacing configuration files with files from ConfigMap or other sources like volume.)

    Since this is related to install-able MDM container images which customers configure and the customization can vary from customers to customers, we have decided not to provide this out of the box.

    Hope this helps.

    Thank You

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    27 Aug 06:13am

    What we ment is not change the serversetting when the server is running, but at file level.

    For example for LDAP change the security.xml in the config\cells\<cell_name> directly before the server is started.

  • Admin
    MAY LI commented
    26 Aug 03:13pm

    Hi Erik, please see below the initial feedback I received from our development team.

    • If setting these through WAS deployment script, it will take too long a time for a container to start up and it may not feasible. It will require deep WAS hack to deal with WAS configuration file directly to parameterize these deployment information. We probably don't know which configuration file contains information for database server, ldap server, kafka server, etc. This is not a typical WAS configuration process. Since this is a WAS standalone environment, dealing with configuration file directly should not be a big problem.

    • When scripts are used to change configuration, we will have to first start the server (x seconds), run the scripts and restart the server (2x seconds). So the startup time will increase, which is not good in a container orchestration platform.

    Let me know your thoughts. Thank you.

  • Admin
    MAY LI commented
    25 Aug 04:46pm

    Hi Erik, thank you for submission. We will investigate and follow up here with status.

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions