summaryrefslogtreecommitdiffstats
path: root/meta-openstack/Documentation
diff options
context:
space:
mode:
authorLiam R. Howlett <Liam.Howlett@WindRiver.com>2014-09-17 12:31:56 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2014-09-17 13:43:49 -0400
commit2090122e897dc470864c97a416420a550d2b79a0 (patch)
treebd26bafa7bfe53817fbae67590f3aef6bfa34320 /meta-openstack/Documentation
parent269e5c0fde3ce9eaded29150b773b6f337a91940 (diff)
downloadmeta-cloud-services-2090122e897dc470864c97a416420a550d2b79a0.tar.gz
trove: Add documentation on trove & troveclient setup.
This README covers general trove setup in OpenStack. Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta-openstack/Documentation')
-rw-r--r--meta-openstack/Documentation/README.trove76
1 files changed, 76 insertions, 0 deletions
diff --git a/meta-openstack/Documentation/README.trove b/meta-openstack/Documentation/README.trove
new file mode 100644
index 0000000..cdbfb58
--- /dev/null
+++ b/meta-openstack/Documentation/README.trove
@@ -0,0 +1,76 @@
1Summary
2=======
3
4This document is not intended to provide deail of how Trove in general works,
5but rather it highlights the deails of how Trove is set up and how OpenStack is
6configured to allow the Troveclient to interact with Trove.
7
8Trove Overview
9==============
10
11Trove is Database as a Service for OpenStack. It's designed to run entirely on
12OpenStack, with the goal of allowing users to quickly and easily utilize the
13features of a relational database without the burden of handling complex
14administrative tasks. Cloud users and database administrators can provision and
15manage multiple database instances as needed. Initially, the service will focus
16on providing resource isolation at high performance while automating complex
17administrative tasks including deployment, configuration, patching, backups,
18restores, and monitoring.
19
20Trove Setup
21===========
22
23Trove is set up to have the following:
24
25* The database and datastore are added as postgresql since this is the default
26 database configuration.
27
28* There is a keystone user and service created for Trove called "trove". The
29 role is admin.
30
31Interactions with Trove are handled through the troveclient on the command line.
32The troveclient binary is simply called trove. For details of how to use trove
33on the command line, please refer to the help:
34
35 $ trove
36
37Build Configuration Options
38===========================
39
40Trove and Troveclient are both in the package group of the controller. The
41troveclient is in the package group of the compute node. To add the unit tests
42to either image, add the following layer to your configuration:
43--with-template=feature/openstack-tests
44
45
46Test Steps
47==========
48
49This section describes test steps and expected results to demonstrate that
50Trove is integrated properly into OpenStack.
51
52Both components use the run_ostest_nose.sh script which needs to be manually
53copied to the target.
54
55
56Trove and Troveclient Unit Tests
57===============================
58
59On the controller:
60sh run_ostest_nose.sh -t /usr/lib64/python2.7/site-packages/trove
61
62Total: 741, Passed: 740
63
64
65On either the controller or compute node:
66sh run_ostest_nose.sh -t /usr/lib64/python2.7/site-packages/troveclient
67
68Total: 202, Passed: 202
69
70References
71==========
72
73 * https://github.com/openstack/python-troveclient
74 * https://github.com/openstack/trove
75 * https://wiki.openstack.org/wiki/TrovArchitecture
76 * https://wiki.openstack.org/wiki/Trove