Bug 1288259 - [Docs] [Trove] Provide an overview of how to configure and use Trove
Summary: [Docs] [Trove] Provide an overview of how to configure and use Trove
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Radek Bíba
QA Contact: Deepti Navale
URL: https://wiki.openstack.org/wiki/Trove
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 23:58 UTC by Andrew Dahms
Modified: 2016-06-01 06:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-01 06:49:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2015-12-03 23:58:14 UTC
With Red Hat Enterprise Linux OpenStack Platform 8, Trove is now a supported component, and instructions on how to configure and work with Trove must be added to the documentation.

The following main use cases must be covered -

* Provide best practices on planning instance data and managing the database 
  services.
* Provide a manual procedure to configure Trove using RH recommended best 
  practices.
* Provide example automation scripts to create and configure Trove guest 
  database images for the database platforms listed above.

Comment 1 Andrew Dahms 2015-12-04 00:15:15 UTC
Assigning to Radek for review.

Radek - we are targeting this content for the 'Instance Services' guide for now, where it become a chapter.

Comment 3 Andrew Dahms 2016-05-20 01:25:24 UTC
Assigning Deepti as the QA contact.

Deepti - can you take a look at the changes for this bug?

Comment 6 Deepti Navale 2016-06-01 03:27:47 UTC
Thanks for the updates, Radek. Changes look good. I've merged the changes to osp8-liberty branch.

Comment 7 Radek Bíba 2016-06-01 06:49:20 UTC
Thanks, Deepti. I've republished both books and ported (cherry-picked and tweaked) the changes to master.


Note You need to log in before you can comment on or make changes to this bug.