This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Marcelo,
Here are comments from the Tiger team on the items that were denied:
1. Detection of Residual Environments (Cleanup):
"Clean VM" is a relative requirement, we had several customers who had to fix "clean vms" because they use predefined VMs as a corporate standard, so I would institute on checking existing version as we see. Like if we need certain version of k3s, or other libs we need to check if installed version matches the one we use.
2. Hostname & /etc/hosts Validation:
I disagree, we need to check the "hostname -f" and specified domains (and it doesn't matter if it is in DNC or in /etc/hosts), I've seen many issues like that.
In addition, we need the following in our pre-checker:
We need to ensure k3s and ctr tools are not installed, because Instana installs them and need to ensure the correct versions are in use.
We need to ensure proxy is not changing certificates and if it is then we need to add the corporate CA certificate to Instana backend as well
We need to ensure acceptor ports have been changed when single tenant domain is in use
Just to add some notes here....
We have additional requirements for the pre-req checker, and I am not sure if it already exists. Please see the following aha ideas:
https://ideas.ibm.com/ideas/INSTANA-I-3848
https://ideas.ibm.com/ideas/INSTANA-I-3897
One more scenario I just encountered. A customer had <unit>.<tenant>.<base domain> instead of <unit>-<tenant>.<base domain> in their /etc/hosts file and the install failed. We should validate that the base domain, agent-acceptor, and unit-tenant all resolve properly before we start the install.