Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
Describe the bug
A clear and concise description of what the bug is.
@fketelaars had described in a private meeting that IPC kernel parameters are 'hard-coded' in the deployer. If that is true, then the Deployer should use the script described in CPD v4.7.x docs (https://www.ibm.com/docs/en/cloud-paks/cp-data/4.7.x?topic=settings-changing-kernel-parameter#kernel-settings__kernel-nto) so that the correct parameters are are set. The 'static' values make an assumption of 16 vCPU and 64 GB RAM. Using the script accommodates varies node resource configurations and makes the deployer compliant with IBM docs (in this respect).
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Install CPD v4.7.x and DV (Watson Query) on 'fresh' cluster.
Expected behavior
A clear and concise description of what you expected to happen.
Verify if deployer uses 'static' values for kernel parameter settings that Tuned daemon needs to implement.
Screenshots
If applicable, add screenshots to help explain your problem.
None.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Not applicable.
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Not applicable.
Additional context
Add any other context about the problem here.
Describe the bug A clear and concise description of what the bug is.
@fketelaars had described in a private meeting that IPC kernel parameters are 'hard-coded' in the deployer. If that is true, then the Deployer should use the script described in CPD v4.7.x docs (https://www.ibm.com/docs/en/cloud-paks/cp-data/4.7.x?topic=settings-changing-kernel-parameter#kernel-settings__kernel-nto) so that the correct parameters are are set. The 'static' values make an assumption of 16 vCPU and 64 GB RAM. Using the script accommodates varies node resource configurations and makes the deployer compliant with IBM docs (in this respect).
To Reproduce Steps to reproduce the behavior:
See error
Install CPD v4.7.x and DV (Watson Query) on 'fresh' cluster.
Expected behavior A clear and concise description of what you expected to happen.
Verify if deployer uses 'static' values for kernel parameter settings that Tuned daemon needs to implement.
Screenshots If applicable, add screenshots to help explain your problem.
None.
Desktop (please complete the following information):
Version [e.g. 22]
Not applicable.
Smartphone (please complete the following information):
Version [e.g. 22]
Not applicable.
Additional context Add any other context about the problem here.
None.