IBM Watson™ Discovery Service Ideas

We've moved...

You'll be redirected shortly, we've moved to our new idea portal:

WDS needs to be deployable to IBM Cloud Isolated Environments

WDS Premium is not sufficient for many customers as it only provides container based separation/isolation on shared infrastructure.  As we move away from the fully dedicated "Bluemix" capability to the IBM Cloud Isolated offering where customers can drive their consumption from the public catalog, but deploy onto their own private infrastructure in IBM Cloud, we need to provide this deployment option for Watson services such as WDS.  If we are offering Watson services, such as WA and WDS, on ICP we REALLY should be providing the option for a higher isolation level WITHIN our cloud environment and not force customers to deploy on-prem just to get infrastructure isolation.

  • Graham Walker
  • Aug 30 2018
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? FSS Customers in particular.
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
  • Admin
    Phil Anderson commented
    August 30, 2018 12:18

    What deployment model are you describing, I'm aware of Dedicated, ICP, Premium - we're either on or going to be on all of these, are you saying there's another one out there?

  • Graham Walker commented
    September 03, 2018 09:12

    Hi Phil,  

    Thanks for your reply.

    My understanding is that the old Dedicated model where we effectively created a customer specific version of the whole Bluemix environment on dedicated cloud infrastructure is being deprecated.  What will replace this is the ability to drive consumption of services such as Watson from within the Public catalog but the customer will be able to select to deploy this on dedicated infrastructure in customer specific VLANs.  

    One of the first services that support this is the IBM Kubernetes Service.  You can choose to deploy worker nodes in shared public infrastructure or you can choose to deploy worker nodes on dedicated infrastructure.  In both cases the Kubernetes service as a whole is monitored and managed from within IBM Public Cloud.  If this was the old "Dedicated" model the entire Kubernetes infrastructure would have been replicated on the customers dedicated infrastructure rather than just the parts that need to be isolated (ie., the worker nodes).  

    Similarly we could do the same thing for services such as Watson.  For instance Watson Discovery Service would have an option to deploy a private instance of the service.  In this case the WDS container would be deployed onto a worker node running on customer dedicated infrastructure in their own VLAN, but would establish a link back to the public environment for monitoring, management, upgrades and so on.  The main difference in this case would be that there would be no other tenants/containers running on the worker node other than the customers Watson service. 

    The benefit of this is that customers can still use a cloud environment while achieving higher levels of security through the use of dedicated infrastructure within their own VLANs and they can still take advantage of the aspects of an "as a Service" public service.  If they deploy a service behind their firewall on something like ICP they have the ultimate in a secure environment but it is completely cut off from any monitoring, management, upgrade, etc that an "as a Service" service would usually enjoy and does not enable them to take advantage of the benefits of cloud where they don't have to own and manage their own infrastructure.

  • Admin
    Phil Anderson commented
    September 05, 2018 12:44

    Thank you for the information Graham, I haven't gotten any details on this but I suspect we'll hear more from Lisa Juliani as these efforts are typically done for all of Watson