summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Updated from global requirementsjuno-eol2014.2.4stable/junoOpenStack Proposal Bot2015-09-122-1/+2
| | | | Change-Id: I50d8b87e91f3b0d32e9c655402fbd8df1878c568
* Expect ValidationError on an empty user updatePetr Malik2015-09-081-3/+4
| | | | | | | | | | | | | Applying an empty change on user attributes should raise a ValidationError. This is needed for Trove int-tests to run on the stable/juno branch. Depends-On: I5ab58fd64f4745a2e558392bff649b05401ed57a Cherry-picked-from: f8f318352729d38a6e70e63a47b919dc9aad95c2 Closes-Bug: 1482279 Change-Id: I778bb408ba1f3b58037b77e56e33ee0020156c86
* Updated from global requirementsOpenStack Proposal Bot2015-08-133-38/+38
| | | | Change-Id: I2e04a524bd60b0abad462c37140a23e98fc5a369
* Bump stable/juno version to 2014.2.4Adam Gandelman2015-04-131-1/+1
| | | | Change-Id: Id86057997c973f16c77370440a39d112317e4d9e
* Merge "Updated from global requirements" into stable/juno2014.2.3Jenkins2015-04-112-5/+5
|\
| * Updated from global requirementsOpenStack Proposal Bot2015-04-102-5/+5
| | | | | | | | | | | | 2014.2.3 blocker, need neutronclient<2.4.0 for Juno Change-Id: Ia47fcf4148b513ec33a05985e1afc9bd7a09c7d1
* | Ensure Replication Tests do not use a stale tokenNikhil Manchanda2015-04-101-0/+2
|/ | | | | | | | | | Fixed the replication tests to re-authenticate the common test dbaas client in order to ensure that we do not use a stale auth_token when running the replication tests. Change-Id: I37a2a4b7dca056e84b48c66cbe3b8c8fb6a2f1db Closes-bug: 1394831 (cherry picked from commit 500613e68f365596dcec4c0466978be409be99ee)
* Fixed NotificationTransformer to handle missing InstanceServiceStatusNikhil Manchanda2015-04-081-2/+13
| | | | | | | | | | | Fixed NotificationTransformer to not send exists notifications for new Trove instances which do not have an InstanceServiceStatus created for them yet. The notifications for these instances will eventually be sent during the next iteration of the scheduled task. Change-Id: I002ab89f8c7715310f1890a34967c8172a5d96ef Closes-Bug: 1379729 (cherry picked from commit 80f898d3ba16d5c644447dbacf3a1bad6eaa6488)
* Updated from global requirementsOpenStack Proposal Bot2015-03-091-1/+1
| | | | Change-Id: I6e789fc1fe463cb90ef301d35b2ff991d79c3ec6
* Updated from global requirementsOpenStack Proposal Bot2015-02-162-32/+32
| | | | Change-Id: I4331007469a570adc42dea52dc27868944d8be5e
* Bump stable/juno version to 2014.2.3Matt Riedemann2015-02-091-1/+1
| | | | | Change-Id: Ib8a29258d99de75b49a9b19aef36bb99bc5fcac0 Related-Bug: #1419919
* Merge "Updated from global requirements" into stable/juno2014.2.2Jenkins2015-01-271-2/+2
|\
| * Updated from global requirementsOpenStack Proposal Bot2015-01-141-2/+2
| | | | | | | | Change-Id: I608f577652b49e4707de1d6c2339df906ba3f688
* | Increase test rate limit to avoid rate limit errorAmrith Kumar2015-01-222-8/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 (cherry picked from commit a67c0ca7030362c35ea8dd183229bc73173cf60b)
* | Fix trove-tox-doc-publish-checkbuild failuresBrian Hunter2015-01-211-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | The owners of maven.research.rackspacecloud.com/ seem to have introduced a 301 redirect permanent from http -> https URLs on around Jan 10th. This has broken the master/trove check builds since that time. Maven, when running in the infrastructure CI environment, fails to follow these redirects. This code change simply refers to the maven software repositories using https URLs. Local testing of this change against Tesora's downstream CI found that it may be necessary to purge the broken/cached file from the bare-trusty CI build machines ala: rm /home/jenkins/.m2/repository/com/rackspace/cloud/api/wadl-tools/1.0.9 (continued..) /wadl-tools-1.0.9.jar Closes-Bug: #1412949 Change-Id: I2dece05c74ad18a96fa05791e368ff7283a5e4e5 (cherry picked from commit 386ddc22680e8e9be3a34241067b0e34a192ebea)
* Updated from global requirementsOpenStack Proposal Bot2014-12-141-1/+1
| | | | Change-Id: Ia530441999320b766dd71815e1e0182699c429a7
* Bump stable/juno next version to 2014.2.2Alan Pevec2014-12-051-1/+1
| | | | Change-Id: If016d6f492c2b23d6ce3e77731cd1d9de94a9b18
* Updated from global requirementsOpenStack Proposal Bot2014-12-031-10/+10
| | | | Change-Id: I4d7105e5a36c0cbca90b5a9e5c6bb3ed7ea8f301
* Updated from global requirementsOpenStack Proposal Bot2014-11-272-11/+11
| | | | Change-Id: Ie8e0c9e644f99213c487303572be8d7ae36c8129
* Opening stable/junoThierry Carrez2014-10-162-1/+2
| | | | | | | Bump version to next stable release on juno branch, and set defaultbranch in .gitreview for convenience. Change-Id: I8dad70cd47a44892191376b20aa334f2ac7cb3b4
* Merge "restart_required cfg-param is bool and not string" into proposed/juno2014.2.rc32014.2proposed/junoJenkins2014-10-152-3/+5
|\
| * restart_required cfg-param is bool and not stringCraig Vyvial2014-10-142-3/+5
| | | | | | | | | | | | | | | | | | | | | | There was a break to the previous version of the configuration paramenters API when the configurations parameters were moved to the database. The actual type of the restart_required parameter should be a JSON boolean value, and not a string to be compatible with the previous configuration parameters API. Change-Id: If45944e25a55813ddf8f80010811da04d667ca19 Closes-Bug: #1379665
* | cluster_config argument missing in prepare()Sreedhar Chidambaram2014-10-141-0/+1
|/ | | | | | | | | Due to a bad merge, the prepare() call in postgresql does not have cluster_config argument. Added that to make sure postgres is in line with other data stores. Change-Id: I1c3e5032447124dae47ae23ebf820fdcf8080588 Closes-Bug: #1380745
* convert restart_required to 'true' or 'false' string2014.2.rc2Craig Vyvial2014-10-101-1/+3
| | | | | | | | | The output of the configuration-parameters-list/show was inadvertently changed when the parameters were moved into the database in Juno. Change-Id: Ic7d215482f5a9ab8ba2059cae7b91a99b35f2795 Closes-Bug: #1379665
* Refreshed translationsNikhil Manchanda2014-10-1010-3542/+230
| | | | | | | | | | | | | Updated translations by running the following: $ python setup.py extract_messages $ python setup.py update_catalog --no-fuzzy-matching \ --ignore-obsolete=true $ source \ ../infra/project-config/jenkins/scripts/common_translation_update.sh $ setup_loglevel_vars $ cleanup_po_files trove Change-Id: I2fcb4e3a0714a73a7026ce2d2c3ffde8aaee1236
* Merge "Use unique passwords for replication user"2014.2.rc1Jenkins2014-10-0210-33/+127
|\
| * Use unique passwords for replication userMorgan Jones2014-10-0110-33/+127
| | | | | | | | | | | | | | | | | | | | | | | | | | Generates a unique user with a random password for each slave. The replication user and password is passed to each slave during the snapshot attach process. Replication user is deleted from both the master and the slave during the detach process. Co-Authored-By: Nikhil Manchanda <SlickNik@gmail.com> Co-Authored-By: Denis Makogon <dmakogon@mirantis.com> Change-Id: I9cb158a161714bfff90225227f5c652120393ba7 Closes-bug: 1357065
* | Add templates for replica and replica sourceIccha Sethi2014-10-0117-30/+100
|/ | | | | | | | | | | This patch adds templates for replica and replica source. Previously this was hard coded in the code. This gives deployers the ability to customize their replication configurations. Closes-Bug: 1370125 Change-Id: Ie1b4cff1685d2577240eb43ffecac3c977ba964c
* Merge "Partially address concerns in Couchbase restore strategy"Jenkins2014-10-016-32/+92
|\
| * Partially address concerns in Couchbase restore strategyAmrith Kumar2014-09-266-32/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a preliminary fix for community review. I expect to be making some changes as well. This change addresses some concerns about the Couchbase restore strategy. In particular, the concerns that are addressed include string injection in some execute calls, and issues around the permissions on the secret file used to store the password. This change set aims to fully address the issue around the password file but is a partial solution to the string injection problem. Additional changes are required to completely address that. Some additional bugs have also been raised to address issues related to other concerns discovered while fixing this bug. More to come. Change-Id: Icd8033caea4866f57f8cb4c5861d21797136ff90 Partial-Bug: #1349939
* | Merge "Use different timeouts for create and restore"Jenkins2014-09-303-3/+9
|\ \
| * | Use different timeouts for create and restoreNikhil Manchanda2014-09-293-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Make the replication snapshot timeout configurable"Jenkins2014-09-304-2/+7
|\ \ \
| * | | Make the replication snapshot timeout configurableMorgan Jones2014-09-294-2/+7
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Mandate detach replicas before deleting replica source"Jenkins2014-09-294-0/+19
|\ \ \
| * | | Mandate detach replicas before deleting replica sourceIccha Sethi2014-09-294-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the user attempts to delete an instance which has replicas attached to it, forbid the delete. Closes bug: #1362299 Change-Id: I644243aef74d9a34b7726139f9fa5ca8bdb1452c
* | | | Merge "Discover config file for mongodb"Jenkins2014-09-293-12/+21
|\ \ \ \ | |/ / / |/| | |
| * | | Discover config file for mongodbrumale2014-09-253-12/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mongodb 2.6 uses diff config file as opposed to lower versions. Given diff file candidates code selects config file that is available Change-Id: I8fe9eea39a47aa890834a0c55e98c062f9b9fd15 Closes-Bug: #1368468
* | | | Merge "Updated from global requirements"Jenkins2014-09-291-2/+2
|\ \ \ \ | |_|/ / |/| | |
| * | | Updated from global requirementsOpenStack Proposal Bot2014-09-261-2/+2
| | |/ | |/| | | | | | | Change-Id: I4a445dedb3a67c0f156f90bb677219d245a78111
* | | Merge "Sync latest process and str utils from oslo"Jenkins2014-09-282-25/+47
|\ \ \
| * | | Sync latest process and str utils from osloTristan Cacqueray2014-09-222-25/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This sync required changes to fix these issues: * Make execute method clean password in exception * Make sure mask_password works properly ------------------------------------------------ The sync pulls in the following changes (newest to oldest): 6a60f842 - Mask passwords in exceptions and error messages (SSH) 63c99a0f - Mask passwords in exceptions and error messages 66142c34 - Make strutils.mask_password more secure ----------------------------------------------- Closes-Bug: 1343604 Closes-Bug: 1345233 SecurityImpact Change-Id: I3b49b1d667f6ade9ae3f6765d735440a3e838917
* | | | Merge "Document Trove configuration options"Jenkins2014-09-272-238/+334
|\ \ \ \
| * | | | Document Trove configuration optionsPeter Stachowski2014-09-212-238/+334
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the Trove configuration options do not have adequate help text to describe what the configuration option can be used for, and/or what valid values for the option are. Since the auto-generated docs are based on this help text, they currently look very empty and are not very helpful. example: See "Configure the database" in chapter 4. Database Service under http://docs.openstack.org/trunk/config-reference/content All options now have help strings to clarify how/when they can be used. Also removed periodic_interval option (not referenced in the code). DocImpact: A separate patch set will be created for the actual doc changes. Closes-Bug: #1334465 Change-Id: I3ea1bd255514438c3d356d23d42f3fb3ddd45274
* | | | Merge "Isolate unit tests from integration tests data"Jenkins2014-09-272-232/+234
|\ \ \ \
| * | | | Isolate unit tests from integration tests dataDenis M2014-09-252-232/+234
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reasons: - unit tests are depending on integration tests data, such as: - datastore and its versions; - distribution package maintainers are not able to package Trove since ice house RC1. Gate behaviour: - gate tests are not failing because unit tests are running right after fake-mode tests, so sqlite still exist. Changes: - fixing those unit tests that are failing while building Trove package (more info see at bug-report). Change-Id: Ib9a41d68481d32cdd81fc4d7c015a63c4da33bb3 Closes-Bug: #1302784
* | | | Merge "Fixed database migration script issues"Jenkins2014-09-2712-36/+472
|\ \ \ \ | |_|_|/ |/| | |
| * | | Fixed database migration script issuesSimon Chang2014-09-1912-36/+472
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The db downgrade scripts are currently not dropping foreign key constraints, causing errors when the script tries to drop related tables on downgrade. This commit address issues in the migration scripts, and also introduces a new test script to test the migration scripts, so that issues can be prevented in the future. The new test script is based on the existing migration test script implementated in Nova. Change-Id: I240d81afc3e43fd3711de8c156cfb43fd14850bf Closes-Bug: #1347114
* | | | Merge "Make --repo-path an optional argument for db_recreate"Jenkins2014-09-251-1/+1
|\ \ \ \ | |_|/ / |/| | |
| * | | Make --repo-path an optional argument for db_recreateSergey Gotliv2014-09-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | db_recreate uses repo-path to call db_sync, but for db_sync this argument is optional so it should be optional for db_recreate as well. Closes-Bug: #1279734 Change-Id: I68b0eb3c705525a047eb6bffe8d5e1b4b083cd91
View Lorry Controller Status