IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
Hello Mitch - it's very much for automated testing, or DevOps procedures. Consider this scenario.
You have a large and complex workspace, you're maintaining it under source control along side the matching code. Every time a change to the workspace is checked in, or a change to the code, is made you wish to have your devops pipeline run, terraform, deploy the latest workspace, deploy the latest code, build and test that code and training work beautifully together. Then you want to cut across your environment from version -1 to version 0 when it's declared stable all automatically.
Workspaces can take a variable amount of time to train and this goes up as the workspace grows. At the moment after deploying the workspace, the devops pipeline needs to continue to poll the status of the workspace for when it goes from "Training" to whatever available is
When I saw the idea for a webhook back into the DevOps pipeline I thought that was a great idea. Instead of polling, Watson just calls back when it goes available, the next depedent step of the pipeline can run
I am automating the process of k-fold cross validation, therefore when I do 80% of the data deployment I have to wait for the training to be completed to send 20% of the data, and if I have to do 10 iterations on a same workspace takes a long time.
we have added webhooks to beta, but this is for pinging the webapp when a specific dialog node is hit to make a callout at runtime, not training.
can you explain why you are continually pinging when training? you can add more training and they will just wait in line to happen