(In reply to Rob Young from comment #0)
> Description of problem:
> 
> Add the following content to the OSP 9 Release Notes:
> 
> The Trove DBaaS component tech preview will be deprecated beginning in RHOSP
> 9. All Trove DBaaS components and supporting documentation will be removed
> in RHOSP 10.

Please use the following content in the OSP 9 and 10 readme files.

DEPRECATION NOTICE: Based on ​customer feedback, and the constant message that support for commercially available database was an absolute must from the quasi totality of the customers we surveyed, we have came to the conclusion that we should rather concentrate our effort in having succesful partnerships around Trove rather than building a fully open-source solution that will not benefit our customers.
​
Beginning in RHOSP 10, ​the OpenStack Trove service, which has been in Tech Preview so far, will no longer be included in the RHOSP distribution. We are working with a trusted partner to provide our customers with a production ready DBaaS service. Please contact your sales account manager to learn more about this option.”

Hi Don,

Rob's written deprecation text above. What is the process from here to get this into the release notes?

Hi Elise,

It's already on our radar. :-) 

Setting requires_release_notes? and rhos-9.0 flags, along with draft text in the Doc_Text field queues it up for processing in the release notes. Adding Andrew Dahms to see if we need to make it more prominent there; at present our toolchain will automatically pull in the text and put it in the "Deprecated Functionality" section (Doc Type).

Do we need to do anything else for this bug?

Given that Tesora (The "partner") was bought by Stratoscale and they seem to have zero interest in openstack, where does that leave those of us who need DBaaS from their private cloud?