214 Commits

Author SHA1 Message Date
Jenkins
70adcf6e8a Merge "Changes names of some quota values" 2015-10-27 20:46:16 +00:00
Sonali Goyal
e6620ff00f Changes names of some quota values
Some variables which were actually per-tenant were
incorrectly named with a _user. Corrected this
confusion by making the old names deprecated
and providing new per-tenant names.

Closes Bug: #1232969

Change-Id: I541ed990c0cdd40b3805d2e2a166363d9ff2ad04
2015-10-21 12:42:22 +00:00
Amrith Kumar
391b0d966d The verbose option in section [DEFAULT] has been deprecated
For more details about why this was done (by the oslo log team), see
references provided below. The change here just removes the entry from
the test config file to avoid the error.

https://review.openstack.org/#/c/206437/3

Change-Id: I941ef163561b80539397788b65aae7d4548bac49
Closes-Bug: #1507217
2015-10-17 18:37:09 -04:00
Peter Stachowski
8f8a758539 Add Redis backup/restore functionality
Performs backup using the Redis client to persist data to the file
system, then streams the result to swift.

Performs restore by replacing the data file with the Swift backup
and starting the server again in the correct manner.

Note: Running the int-tests require that volume_support is set
to false in the test.conf file.

To run:
./redstack install
./redstack kick-start redis
(vi /etc/trove/test.conf and change volume_support to false)
./redstack int-tests --group=backup (or --group=redis_supported)

Co-Authored-by: hardy.jung <hardy.jung@daumkakao.com>
Co-Authored-by: Peter Stachowski <peter@tesora.com>

Depends-On: I633273d438c22f98bef2fd1535730bcdb5e5cff0
Implements: blueprint redis-backup-restore
Change-Id: I1bd391f8e3f7de12396fb41000e3c55be23c04ee
2015-09-02 20:21:16 +00:00
Peter Stachowski
16d91d9838 Add generic int-test classes
The int-tests in Trove are very MySQL specific, which makes it difficult
to reuse code for other datastores.  This changeset breaks them down
into 'groups' and 'runners.'  Runners can be over-ridden to add
datastore specific handling/tests.  This should allow most generic
code to be reused across datastores, while also providing for datastore
specific enhancements.

Runner implementations are stored in a new package
'trove.tests.scenario.runners'.  A datastore-specific implementation can
be added to the appropriate runner module file. Its name has to match
'PrefixBaseRunnerClassName' pattern, where 'BaseRunnerClassName' is the
name of the default runner and 'Prefix' is the datastore's manager
name with the first letter capitalized.

Example:
    Given the default implementation for negative cluster tests in
    'trove.tests.api.runners.NegativeClusterActionsGroup'.  One can
    provide a custom implementation for MongoDB (with manager mongodb)
    in 'trove.tests.api.runners.MongodbNegativeClusterActionsRunner'

This initial changeset adds tests for basic actions on instances
and clusters.  Some basic replication tests were also migrated.

The concept of a helper class for datastore specific activies
was also created.  This makes it easy to have tests use standard
methods of adding data and verifying that the datastore behaves
as it should.

Vertica was refactored to use the new infrastructure.

Running the tests can be accomplished by specifying one of the
new groups in int-tests (see int_tests.py for the complete list):

./redstack kick-start mongodb
./redstack int-tests --group=instance_actions --group=cluster
or
./redstack int-tests --group=mongodb_supported (to run all
tests supported by the MongoDB datastore)

As with the original int-tests, the datastore used is the one
referenced in test configuration file (test.conf) under the
key dbaas_datastore.  This key is automatically set when
kick-start is run.

Additional Notes:

Also temporarily disabled volume size check in
instances tests.
It is supposed to assert that the used space on the
Trove volume is less that the size of the volume.
It however often fails because 'used' > 'size'.
From inspection of the instance it appears that the reported
'used' space is from the root volume instead of the
attached Trove volume. Plus it sometimes returns int instead of float.

Change-Id: I34fb974a32dc1b457026f5b9d98e20d1c7219009
Authored-By: Petr Malik <pmalik@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
2015-08-26 19:38:49 -04:00
Jared Rohe
8ad786e9be Remove rsdns directory
The rsdns service is no longer needed since trove now supports designate.
It is not being tested in the gate and is currently unsupported.

Remove other rsdns related files and references.

Change-Id: I44009dace44afb5467c51def33c794641ffa33c0
Closes-Bug: #1454028
2015-06-03 12:15:01 -07:00
Duk Loi
9b47609941 Move guestagent settings to default section
The guestagent related settings are in the database section of the
taskmanager.conf.sample file.  If a user were to use this sample then
the guestagent related settings will not be read by the taskmanager
service because it expects these guestagent related settings to be
in the default section.  This fix moves the guestagent related
settings to the default section.

Change-Id: I8dbdf7abcfd5f2341831cc6daaf5cb14d8d42d61
Closes-Bug: #1459415
2015-05-27 16:09:27 -04:00
Jenkins
85563e62ea Merge "Change nova_proxy_admin_tenant_name to id" 2015-04-24 19:41:00 +00:00
Sushil Kumar
c61a3bf5f9 Implement clustering for Vertica datastore
A specification for this change was submitted for review in
https://review.openstack.org/#/c/151279

- HP Vertica Community Edition supports upto a 3-node cluster.
- HP Vertica requires a minimum of 3 nodes to achieve fault tolerance.
- This patchset provides ability to launch HP Vertica 3-node cluster.
- The cluster-show API, would also list the IPs of underlying instances.

Code Added:
- Added API strategy, taskmanager strategy, and guestagent strategy.
- Included unit tests.

Workflow for building Vertica cluster is as follows:
- Guest instances are booted using new API strategy which then
  sends control to taskmanager strategy for further communication
  and guestagent API execution.
- Once the guest instances are active in nova,
  they receive "prepare" message and following steps are performed:
    - Mount the data disk on device_path.
    - Check if vertica packages have been installed, install_if_needed().
    - Run Vertica pre-install test, prepare_for_install_vertica().
    - Get to a status BUILD_PENDING.
- Cluster-Taskmanager strategy waits for all the instances
  in cluster to get to BUILD_PENDING state.
- Once all instances in a cluster get to BUILD_PENDING state,
  taskmanager first, configures passwordless ssh for os-users(root, dbadmin)
  with the help of guestagent APIs get_keys and authroize_keys.
- Once passwordless ssh has been configured, the taskmanager calls
  install_cluster guestagent API, which installs cluster on
  member instances and creates a database on the cluster.
- Once this method finishes its job then taskmanager calls
  another guestagent API cluster_complete to
  notify cluster member of completion of cluster creation.

New Files:
- A new directory, vertica, has been created, for api, taskmanager,
  guestagent strategies under
  trove/common/strategies/cluster/experimental.
- Unit-tests for cluster-controller, api and taskmanager code.

DocImpact
Change-Id: Ide30d1d2a136c7e638532a115db5ff5ab2a75e72
Implements: blueprint implement-vertica-cluster
2015-03-24 06:22:55 +00:00
Greg Lucas
bee72dd6bf Move sql_xx params to [database] conf section
Update trove configuration files to use the current convention for db
options:
- deprecate the used of [DEFAULT] sql_connection, sql_idle_timeout,
  sql_query_log
- add support for [database] connection, idle_timeout, query_log
- update sample/test conf files to use the new convention

DocImpact: Change to conf options in Install Guide - Install the
  Database service.

This has become more important, as the recent changes to devstack
now use the new [database] section, and the gate is failing due to
that.

Note: On my quick look at the code, there's more work needed to use
oslo_db properly, and it might be better to do that out-of-band
of this fix.

Authored-By: Greg Lucas <glucas@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
Closes-Bug: #1308411
Closes-Bug: #1434856
Change-Id: Ic9e5b20e21d09c4b1d49df660b89decf094440bb
2015-03-22 01:41:43 +00:00
Alex Tomic
75088205f1 Change nova_proxy_admin_tenant_name to id
The task manager can be configured with periodic events
that check for the existence of running nova instances.
The events run via a separate admin connection to nova.

Taskmanager.Manager populates the admin client context
with the tenant name provided by nova_proxy_admin_tenant_name
parameter instead of the uuid, which results in an invalid
management url that is composed of the two parameters:
<nova_compute_url>/<nova_proxy_admin_tenant_name>.

Changing tenant_name to tenant_id results in a valid endpoint.

DocImpact
deprecating option 'nova_proxy_admin_tenant_name'
to 'nova_proxy_admin_tenant_id'

Change-Id: Ia1315e41288ab1b24ac402bad15176cb1ae0e5cd
Co-Authored-By: Li Ma <skywalker.nick@gmail.com>
Closes-Bug: #1289101
2015-03-13 15:55:35 +01:00
Jenkins
e0144328a6 Merge "Integrate OSprofiler and Trove" 2015-03-12 10:20:51 +00:00
Greg Lucas
a4e054e3ac Inject guest conf files to configurable location
Introduce a configuration option for a directory on the guest where the
taskmanager should inject configuration files.

During instance creation inject the guest_info and trove-guestagent
conf files to the 'injected_config_location'. The default location is
/etc/trove/conf.d.

Also:
 - Change the default value for 'guest_config' to remove the risk of
   overwriting a guest image's conf file with the sample.
 - Add trove-guestagent.conf injection to heat template.
 - Add new 'guest_info' option that defaults to "guest_info.conf".

Depends-On: I1dffd373da722af55bdea41fead8456bb60c82b2

Co-Authored-By: Denis Makogon <dmakogon@mirantis.com>
Co-Authored-By: Duk Loi <duk@tesora.com>

DocImpact: This change introduces a new option with a default that
affects existing guest images. The guestagent init script for any
existing guest image will need to be modified to read the conf
files from /etc/trove/conf.d.  For backwards compatibility set the
injected_config_location to /etc/trove and guest_info to
/etc/guest_info.

Closes-Bug: 1309030
Change-Id: I1057f4a1b6232332ed4b520dbc7b3bbb04145f73
2015-03-09 14:24:08 +00:00
Petr Malik
004403c7b7 Do not use '/tmp' as default guestagent log location
The Problem:
Redstack sets 'GUEST_LOGDIR' to the 'log_dir' value from
'etc/trove/trove-guestagent.conf.sample' which happens to be '/tmp/'.

Aside from not being the canonical log file destination,
temporary directory in Linux is a subject to the, so called,
'restricted deletion' policy which dictates that only file owners
(and the directory owner) can delete the files, irrespective of
other access modifiers on the directory.

Redstack changes the owner of 'GUEST_LOGDIR' (default='/tmp')
to the 'trove' user. This may easily mask any potential issues with
the 'restricted deletion' that would only show up later on
production systems where '/tmp' is commonly owned by the root
(see bug/1423759).

The Solution:
Change the default value of 'log_dir' to a directory
which is not subject to the 'restricted deletion'.
Chose '/var/log/trove/' as it is a common place for
trove-related log files on the guestagent.

Change-Id: I39d801a7e19f329c129a0c6df0c3987049d16394
Closes-Bug: 1423760
Related-Bug: 1423759
Depends-On: I9dd6ed543a01ecc4f84065ea4bf3737960de6e24
2015-02-20 12:09:30 -05:00
Zhi Yan Liu
fe25422628 Integrate OSprofiler and Trove
*) Add osprofiler wsgi middleware
This middleware is used for 2 things:
1) It checks that the person who wants to trace is trusted and knows
the secret HMAC key.
2) It start tracing in case of proper trace headers
and adds the first wsgi trace point, with info about the HTTP request.

*) Add initialization of osprofiler at start of service
Initialize osprofiler with oslo.messaging notifier which
is used to send notifications to Ceilometer.

*) Use profile enabled context in services rpc interaction
Change context serializer to pass profile context to service;
rpc server will use trace info to initialize their profile context
to continue the profiling for the request as a transaction.

*) Add tracing on service manager and sqlalchemy db engine object

NOTE to test this:
You should put to localrc:
  CEILOMETER_NOTIFICATION_TOPICS=notifications,profiler
  ENABLED_SERVICES+=,ceilometer-acompute,ceilometer-acentral
  ENABLED_SERVICES+=,ceilometer-anotification,ceilometer-collector
  ENABLED_SERVICES+=,ceilometer-alarm-evaluator,ceilometer-alarm-notifier
  ENABLED_SERVICES+=,ceilometer-api

Run any command with --profile <SECRET_KEY>
  $ trove --profile <SECRET_KEY> list
  # it will print <Trace ID>
Get pretty HTML with traces:
  $ osprofiler trace show --html <Trace ID>
Note: Trace showing can be executed with the admin account only.

The change to enable Trove exchange in ceilometer has been merged:
Idce1c327c6d21a767c612c13c1ad52a794017d71 .

The change to enable profile in python-troveclient has been merged:
I5a76e11d428c63d33f6d2c2021426090ebf8340c

We prepared a common BP in oslo-spec as the integration change is
similar in all projects: I95dccdc9f274661767d2659c18b96da169891f30
Currently there are 2 other projects are using osprofiler: Glance &
Cinder, and some others are a work in progress.

Change-Id: I580cce8d2b3c4ec9ce625ac09de6f14e1249f6f5
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
2015-02-14 13:08:43 -05:00
Jenkins
c7cb6ef711 Merge "Support string flavor IDs" 2015-01-27 14:09:38 +00:00
Zhi Yan Liu
9f2db96e7e Using consistent control_exchange option for rpc
With oslo.messsaging adoption [0], trove config template files contain
some inconsistent and duplicated control_exchange option.

[0] Change Ibd886f3cb4a45250c7c434b3af711abee266671c

Change-Id: I024101edee1cf074181e8d58e69033bc509b582c
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
2015-01-07 22:31:45 +08:00
Sergey Gotliv
ea148d7dfe Integration with oslo.messaging library
Port Trove to use oslo messaging library instead of obsolete messaging
code from oslo incubator.

Change-Id: Ibd886f3cb4a45250c7c434b3af711abee266671c
Implements: blueprint rpc-versioning
2015-01-06 09:16:39 +02:00
Adam Gandelman
21fee8c3c5 Support string flavor IDs
This allows operating on Nova flavors with non-integer ids
by adding a new str_id field to the view that always contains the
unicode flavor id.  The current id field will now contain a value
only when the flavor's id can be cast to int, otherwise it will be
None.  Validation of flavor id when querying a flavor or creating an
instance has been updated to include non-empty strings in addition to
integers.

This will require a patch to python-troveclient to properly fallback
to str_id in absence of the integer id:

    https://review.openstack.org/#/c/123301/

Change-Id: Ie9cfefc6127bc76783cdf9668636342d7590b308
Closes-bug: #1333852
2014-12-23 12:56:19 -08:00
Jenkins
776e9f5226 Merge "remove keystonemiddleware settings from api-paste.ini" 2014-12-19 10:59:44 +00:00
Tim Simpson
52fc67e51e Create example generator
This code adds a feature to the tests where all of the example
snippets are generated and then validated. Tests fail if the new
examples don't match the old ones, meaning a dev changing the API
must update the snippets, triggering a conversation about the changes
during the pull request.

Implements: blueprint example-snippet-generator
Change-Id: I5f1bfd47558a646a56e519614ae76a55759a4422
2014-11-17 13:51:24 -06:00
Dirk Mueller
45b7614bed remove keystonemiddleware settings from api-paste.ini
They can/should be set in the trove.conf instead, to
centralize all user-preserved/editable changes in the main
configuration file, and allow the ability to track api-paste.ini
unmodified from master.

Change-Id: I9eae06f564c4f99255fc627dbd26006d9048be46
2014-11-10 14:26:46 +01:00
Amrith Kumar
a67c0ca703 Increase test rate limit to avoid rate limit error
The current rate limit is 200 requests per minute. I'm getting
consistent tox failures as the machine is exceeding this rate. The fix
impacts only test code and adjusts the limit and a test that has a
hard-coded reference to the old limit. Why 500 you may ask? Because
600 worked and 450 failed consistently with the rate limit error.

In addition, the change addresses the fact that some test
configuration values are duplicated in the test; the change makes the
test reference the configuration value.

Change-Id: I4bb290d8de6253d65b7877c743bb288ee2bce536
Closes-Bug: #1376689
Closes-Bug: #1378932
2014-10-15 17:24:46 +00:00
Jenkins
ba7ed70e1b Merge "Event simulator II" 2014-10-03 22:38:30 +00:00
Jenkins
4ea962bb26 Merge "Use different timeouts for create and restore" 2014-09-30 21:10:37 +00:00
Tim Simpson
220e3e7255 Event simulator II
The previous event simulator simulated time by making all tasks that
would have been launched as threads run in the same thread. That only
worked to a point but didn't properly simulate more complex behaviors
such as clustering.

This new one handles things properly by still running tasks in
eventlet's greenthreads but forcing them to only run one at a time.

Change-Id: Ife834e8d55193da8416ba700e55e7b0c2496f532
2014-09-29 10:32:29 -05:00
Morgan Jones
0fe9c9dd59 Make the replication snapshot timeout configurable
There is no way to tell how long the snapshot for replication
will take, and we have no good way to poll for the slave state.
Eventually, we will need to have an intelligent poll (perhaps
based on guest heartbeats), but in the meantime we will have
the the snapshot use a configurable timeout which can be set
as needed, and independently of the agent_call timeouts.

Co-Authored-By: Nikhil Manchanda <SlickNik@gmail.com>
Change-Id: I6316d748e91d1ec3eebe25a14bb43fbfe10db669
Closes-bug: 1362310
2014-09-29 00:24:19 -07:00
Nikhil Manchanda
1654031cc6 Use different timeouts for create and restore
Restoring an instance from a backup can take significantly longer than
just creating an instance. Introduce a new timeout for the restore case
with a higher default value

Change-Id: I44af03e9b2c966dd94fcfd0ff475f112ac21be5b
Closes-Bug: 1356645
2014-09-29 00:17:41 -07:00
Jenkins
290b300ede Merge "Clusters API Implementation" 2014-09-03 16:59:56 +00:00
amcrn
bc64756995 Clusters API Implementation
adds clusters api, with mongodb sharding as the first implemenation.

Co-Authored-By: Michael Yu <michayu@ebaysf.com>
Co-Authored-By: Mat Lowery <mlowery@ebaysf.com>
Co-Authored-By: rumale <rumale@ebaysf.com>
Co-Authored-By: Timothy He <the@ebaysf.com>

Partially implements: blueprint clustering

Change-Id: Icab6fc3baab72e97f3231eaa4476b56b8dafb2a3
2014-08-29 11:22:07 -07:00
Nikhil Manchanda
40244847b6 Cleaned up sample trove-guestagent.conf
Cleaned out the trove-guestagent.conf to only contain values that make
sense for the guest agent. There were also values that were different
between the sample conf, and the defaults in cfg.py, which were fixed
to be consistent, so as to have a single set of sane defaults.

Closes bug: 1336618

Change-Id: Ib3823856c288971665fa29489c4ffc5b899ccbaf
2014-08-28 14:14:58 -07:00
Jenkins
5dea4ea7b7 Merge "Load trove API extensions using stevedore" 2014-08-28 17:25:16 +00:00
Morgan Jones
86eacbeabc Mysql guest agent functionality for replication
Implement new strategy for replication
Implement replication strategy for mysql binlog replication.
Supporting methods in mysql service
Implement API methods in mysql manager
Define configuration settings for replication

Co-authored by: Nikhil Manchanda <SlickNik@gmail.com>
Co-authored by: Greg Lucas <glucas@tesora.com>

Partially implements: blueprint replication-v1
Change-Id: I70f0b5c37fe3c2d42426029bb627c141965eb524
2014-08-14 17:25:42 -07:00
boden
c9fd5a6a0b Load trove API extensions using stevedore
The current trove impl loads trove API extensions by searching on a
single file path which is exposed as a conf property. This results in a
less than optimal approach from a consumer extension POV. This change
replaces the single extension path approach with dyanmic loading  using
stevedore. Consumers can now bind into the API extensions using the
'trove.api.extensions' entry point; a standard means to define extension
points. Moreover this change refactors to the
trove.openstack.common.extensions logic into trove.common.extensions.

In addition this change includes base unit tests to ensure the
existing trove proper extension points are loaded and that some basic
checks are in place W/R/T validating trove extension points.

Change-Id: Id3e712b536aef3bc9c9d1603367cdc0d4816b970
Implements: blueprint dynamic-extension-loading
2014-08-13 14:04:48 -04:00
Iccha Sethi
2d12d7a2d0 Per datastore volume support
Implements blueprint: per-datastore-volume-support

Introduces volume support on a datastore basis using
config values in datastore config groups.

DocImpact: New config values device_path and volume_support
for each datastore have been added, instead of the DEFAULT
conf section.

Change-Id: I871cbed1f825d719b189f71a3ff2c748fb8abdc0
2014-08-01 11:01:13 -05:00
Jenkins
f27cc7b77a Merge "Make default extension path relative to pybasedir" 2014-07-23 04:39:22 +00:00
Jenkins
c68fef2b7a Merge "Add neutron support" 2014-07-23 03:20:00 +00:00
Anna Shen
90f225bf69 Add neutron support
- Add network driver to switch between nova-network (default) and neutron
- Add option to perform Security group management via neutron
- IP filter for instance detailed view (hiding trove owned/managed network info)
- Add unittests and intergration tests

Implements blueprint neutron-support

  Related patch:
    SHA:        bd54d99aa0b717007d79891eb7839b660616eb6f

Change-Id: Ia0103bcda6590a4e387038ec035aee15454cdf48
2014-07-22 03:33:50 -07:00
guang-yee
fbc389ec43 Use auth_token from keystonemiddleware
auth_token middleware in python-keystoneclient is deprecated and has
been moved to the keystonemiddleware repo.

Change-Id: Ib43223c2cfb31198b9438bb02f0d68f2bab7eb7e
Closes-Bug: #1342274
2014-07-21 17:30:04 -07:00
Ionuț Arțăriși
54097e23b8 Make default extension path relative to pybasedir
Change the default extension path in the sample config files as these
take precedence over the files values in common/cfg.py

Change-Id: I3c473fb9cd7e81341a1963a35834ef4c2fd69717
Closes-Bug: 1316195
2014-07-21 13:48:36 +02:00
Michael Yu
61935d3512 Add Backup/Restore support for Couchbase
Backup strategy:
- Save bucket metadata config (as json file) to /tmp/backups
- This is needed on restore to create the destination buckets
- Handles root enabled case by also saving /etc/couchbase/secret_key to /tmp/backups
- Use cbbackup to do the backup
- /tmp/backups will be zipped up, encrypted, and sent to Swift

Restore strategy:
- If /tmp/backups/secret_key exists, set root password
- Iterate through bucket metadata config (json file) and use Couchbase
  REST API to create each bucket
- Wait until bucket finishes creating
- Use cbrestore (which requires destination buckets to be manually
  created first) to do the restore
- cbrestore can only restore one bucket at a time

DocImpact
backup_namespace and restore_namespace were in the default conf group, now they are per datastore

Change-Id: Iaf4370dcc978df68e7d01c6f63795eaf50aac89d
Implements: blueprint backups-single-instance-couchbase
2014-07-17 22:51:10 +00:00
Jenkins
cc6a281bd6 Merge "Enable usage of config-drive for file injection" 2014-07-15 14:08:25 +00:00
Vipul Sabhaya
5018dae112 Enable usage of config-drive for file injection
* Some nova deployments allow the use of config-drive to do file
  injection.  Trove, when booting an instance, needs to send this
  to Nova when config-drive is to be used.

Closes-Bug: #1329535

Change-Id: I950b93a32f6c7224f30cf930e5f95710c07cbc26
2014-07-10 16:34:36 -07:00
Greg Lucas
ba21c3a3ab Change default for update_status_on_fail
Default 'update_status_on_fail' to True so that instances do not get stuck
in the BUILD state.

When this option is set, instances that remain in BUILD for longer than
the datastore's configured 'usage_timeout' will be considered failed and
moved to the ERROR state.

Closes-Bug: 1339826
Change-Id: I5f4b734830a21a1fbb6f169edb5424bac6f883cd
2014-07-10 13:36:07 -04:00
Matt Riedemann
e932c4777d Use (# of CPUs) api/conductor workers by default
This changes the default number of trove API and conductor workers to be
equal to the number of CPUs available on the host, rather than
defaulting to 1 as it did before.

Commit 75c96a48fc7e5dfb59d8258142b01422f81b0253 did the same thing in
Nova in Icehouse. Similar changes are being made to Glance and Cinder
as well.

DocImpact: trove_api_workeres and trove_conductor_workers will now be
           equal to the number of CPUs available by default if not
           explicitly specified in the trove configuration files.

UpgradeImpact: Anyone upgrading to this change that does not have
           trove_api_workers or trove_conductor_workers specified in
           the trove configuration files will now be running multiple
           API and conductor workers by default when they restart the
           respective trove services.

Closes-Bug: #1335284

Change-Id: Id300bbe991436a0f826ea715630669ab5922a6a4
2014-07-07 10:43:06 -07:00
Jenkins
367f4e0bc8 Merge "Add sample admin_{user,tenant_name,password}" 2014-07-02 19:49:03 +00:00
boden
87f0229e87 Expose trove conductor manager class as conf property
The current implementation of trove conductor hard-codes the conductor
manager class name in the cmd entry point thus not allowing it to be set
by consumers. This change exposes that classname on the conductor conf
so that consumers could plug-in their own manager class. Additionally
unit tests are provided to ensure a user defined and conductor manager
can be used in addition to the default trove conductor manager.

Change-Id: I6bf88dd9cf119f0eb6a197f4bda48c309511297e
Implements: blueprint pluggable-conductor-manager
2014-06-27 04:15:46 -04:00
Shuichiro MAKIGAKI
fd9178aef4 Add sample admin_{user,tenant_name,password}
Other OpenStack components have the same configs in api-paste.ini.
admin_token was removed by Bug #1299332, and admin_{user,password,
tenant_name} should be added instead of admin_token.

Change-Id: Icabb056c315556db8064ded882fba13c25ec2bca
Closes-Bug: #1325482
2014-06-21 17:46:42 +00:00
daniel-a-nguyen
83c7aaf178 Remove unused xml config file
Change-Id: I2b0129fcf3fb9f2e206dc0d6ac422c5bcc82d6af
Closes-Bug: #1324317
2014-05-28 17:13:01 -07:00
Jamie Lennox
9db80e79ea Remove admin_token from configs
A previous review removed the admin_token from the sample config file.
It appears that devstack doesn't use that file but instead uses one of
the .test files.

Admin tokens are actively discouraged as a form of authenticating in
auth_token middleware and the behaviour when using admin_token in
combination with a username and password (as this default produces in
devstack) can lead to problems in authentication.

Closes-Bug: #1299332
Change-Id: I78d2c184f7937006b808d580e3663ab055f7c5fe
2014-05-26 17:20:24 +10:00