2e052b0262
The service tenant deployment model means Trove creates most of the resources(vm, volume, security group, etc.) relating to a database instance in the Trove service tenant rather than the end user. With this deployment model, most of the related resources behind the scenes are invisible to the user, which is a more secure deployment model for either private or public cloud provider. DevStack should follow this model as it will be recommended for Trove deployment in production. Changes included in this patch that are necessary in order to make that happen: - Add 'admin' role to Trove service user(username: trove, project: service) in DevStack. - Create Trove management network resources for Trove service user in DevStack. - Enable Trove remote client configuration by default in DevStack. - Mainly use alt_demo user in alt_demo project for integration tests, config trove user as the admin role user in integration tests. - Disable the module related tests(module_groups) for now because of no use cases but need effort to fix all the failed tests in the service tenant model. Story: #2005445 Task: #30489 Change-Id: I2efb69d3d50344914a875b773f62a227dba2ccaf |
||
|---|---|---|
| .. | ||
| backup | ||
| cluster | ||
| cmd | ||
| common | ||
| conductor | ||
| configuration | ||
| datastore | ||
| db | ||
| dns | ||
| extensions | ||
| flavor | ||
| guestagent | ||
| hacking | ||
| instance | ||
| limits | ||
| module | ||
| network | ||
| quota | ||
| taskmanager | ||
| templates | ||
| tests | ||
| volume_type | ||
| README | ||
| __init__.py | ||
| rpc.py | ||
| version.py | ||
| versions.py | ||
README
This is the trove code itself