This is an IBM Automation portal for Cloud Management 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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
A) The executeCommandWithTimeout does not handle standard error. We had to redirect stderr to stdout.
B) The executeCommandWithTimeout (may) block if standard input is not redirected from a file. (The command we are executing does not as far as I can tell read from standard input, so I don't really understand why this is happening) We redirected /dev/null to stdin (on Linux)
C) There seems to be no way of pushing scripts to the target server before running executeCommandWithTimeout. We have solved this on Linux with some code in the sensor.py that will rsync scripts to the target server. This should be standard feature, so adding some lines in the template should take care of that. We need to put both a CTS specific script and some python libraries shared by multiple CTSs to the target servers.
Do not place IBM confidential, company confidential, or personal information into any field.