summaryrefslogtreecommitdiff
path: root/trove/taskmanager
Commit message (Collapse)AuthorAgeFilesLines
* Fix deprecation warningsTakashi Natsume2022-10-152-3/+3
| | | | | | | | | | | | | | Fix the following deprecation warnings. * DeprecationWarning: Using the 'user' argument is deprecated in version '2.18' and will be removed in version '3.0', please use the 'user_id' argument instead * DeprecationWarning: Property 'user' has moved to 'user_id' in version '2.6' and will be removed in version '3.0' Change-Id: I18802ae1e2318eae3c62a26459178b259c728ac4 Signed-off-by: Takashi Natsume <takanattie@gmail.com>
* Uses userdata instead of personality filesHirotaka Wakabayashi2022-06-201-1/+1
| | | | | | | | | | | | | | | This PR uses userdata instead of personality files because of Nova's deprecates personality files[1] since the the NovaApi-2.57 microversion. Original problem is guest instance creation failure due to the lack of guestagent configuration files because of the recent code chage[2]. [1]: https://review.opendev.org/c/openstack/nova/+/522027 [2]: https://review.opendev.org/c/openstack/trove/+/823632 Task: 44821 Story: 2009934 Change-Id: Id6a6aae3de17c12001b1e9946a4c0ce28ff29f73
* Removes the deprecated argument tenant from TroveContextHirotaka Wakabayashi2022-03-171-1/+1
| | | | | | | | | | | | The tenant argument of RequestContext in oslo.context had been deprecated long time ago and it was finally removed in oslo.context-4.0.0. We should remove the tenant argument of TroveContext that derives from RequestContext and we should also update the requirements.txt in the master branch. Task: 44723 Story: 2009906 Change-Id: I69c7098cc0d61fbbba1dbf2eca87df0dd6fd70ba
* Adapt to file injection deprecation in novaBo Tran2022-01-241-13/+27
| | | | | | Story: #2009770 Task: #44247 Change-Id: I34d47e709a9a7478cb6a85d6e6e37da3f92e40b0
* Merge "Fix rebuild instances in replication cluster"Zuul2021-07-121-2/+31
|\
| * Fix rebuild instances in replication clusterLingxian Kong2021-07-121-2/+31
| | | | | | | | | | | | Story: 2009043 Task: 42806 Change-Id: I3499956a7ba0a5d0ab4a49f5938ce038446d91b7
* | Keep user defined configuration after resizing instanceLingxian Kong2021-07-101-23/+17
|/ | | | | | | | | | | | | * Never remove user defined config, changing the function name from save_configuration to reset_configuration in trove-guestagent. * Improved some logs * Do not remove Innodb Log Files after resize which will cause error: Can't open and lock privilege tables: Table './mysql/user' is marked as crashed and should be repaired Story: 2009033 Task: 42773 Change-Id: I9e3165ed9b38b15714542e35456415e65d438497
* Merge "Don't create nova instances with fqdn as their name"Zuul2021-06-031-2/+1
|\
| * Don't create nova instances with fqdn as their nameAndrew Bogott2021-05-311-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If dns integration is enabled, a db instance's 'hostname' refers to the dns-determined fqdn of a database instance. It will probably be something like whatever.trove.example.org Passing that fqdn into nova gets us a VM whose hostname is whatever.trove.example.org. Presumably that host is itself in a domain, so we wind up with an fqdn on the VM of something like whatever.trove.example.org.example.org. Seems wrong. Furthermore, if this is running in a cloud that already has automatic DNS integration (a standard neutron/designate thing) then we wind up trying to create a record in the 'example.org' domain with the record name of whatever.trove.example.org which is likely to confuse designate along with human users. Story: 2008915 Task: 42506 Change-Id: I6d223f9d1a15a1ed0a0269730a544c321cf6595f
* | Wait for volume status before resize_fsLingxian Kong2021-06-021-1/+6
|/ | | | | | Story: 2008916 Task: 42507 Change-Id: I7d29cf71d03174a439124fb3cf52c24e375d1f49
* Merge "Support to restore backup from remote location"Zuul2021-02-181-3/+4
|\
| * Support to restore backup from remote locationLingxian Kong2021-02-181-3/+4
| | | | | | | | | | | | | | | | In multi-region deployment with geo-replicated Swift, the user can restore a backup in one region by manually specifying the original backup data location created in another region. Change-Id: Iefef3bf969163af707935445bc23299400dc88c3
* | Remove the incorrect log for creating replication clusterLingxian Kong2021-02-181-1/+0
|/ | | | Change-Id: Ie370eff134ae0e1394d0b03049a46a125d0db71a
* Do not rely on description for checking port typeLingxian Kong2020-12-091-1/+1
| | | | | | Use port network ID is more reasonable. Change-Id: I219bf3db15124e67cd65c7d7f686ba73573e2761
* Merge "Support datastore version number for creating configuration"Zuul2020-11-191-1/+1
|\
| * Support datastore version number for creating configurationLingxian Kong2020-11-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | * Support "version_number" for creating configuration. * Fixed a bug for deleting datastore version, the config parameters should be deleted first. * Support "--version" for trove-manage datastore_config_parameters sub-commands. Change-Id: Ieb0def81f2347c06a05eb354ad36b4fa807f7621 Story: 2008358 Task: 41264
* | Fix the race condition for creating and deleting instanceLingxian Kong2020-11-161-5/+17
|/ | | | | | | Story: 2008353 Task: 41255 Change-Id: I02bb0434862819a8dbf3ecf3802c3420731b9ca7
* Merge "Make guest agent api changes backwards compatible"Zuul2020-11-101-1/+1
|\
| * Make guest agent api changes backwards compatibleSam Morrison2020-11-051-1/+1
| | | | | | | | Change-Id: I16303ad0b50a2265b7bd9d4736d5662f67076b61
* | Pass availability zone through to volume creation.Sam Morrison2020-11-091-10/+18
|/ | | | | | | | | | | New config option `enable_volume_az` (defaults to false) ensures that the instance and volume will be created in the same availability zone. Story: 2008313 Task: 41208 Change-Id: I62ea46991c7398fba4e5027d5170038624d5aec9
* Create floating IP in the user's projectLingxian Kong2020-10-121-2/+3
| | | | | | | | | | From the perspective of the public cloud, the floating IP should be created in the user's own project. Story: #2008246 Task: #41093 Change-Id: Ic358a2844c1b1f94a1b77ee67102b1c9c236a365
* Add user/project/trove-id metadata to trove server instancesAndy Botting2020-10-021-0/+4
| | | | | | | This can be handy when wanting to trace back what trove instance and real user/project the nova instance belongs too. Change-Id: I6ba7ea392df3b51ed9d230cacab14869348c217c
* Merge "Handle case where no networks are selected at create"Zuul2020-10-011-0/+3
|\
| * Handle case where no networks are selected at createSam Morrison2020-10-011-0/+3
| | | | | | | | | | | | | | | | | | | | | | Currently trove will error when no networks are selected and no management network is configured. This change will pass in None as the nics to nova server create which will let nova choose the network. Change-Id: Ica4f888bf1bc7b771cdfcb0af5c104b2aa6410fe Story: 2008213 Task: 40999
* | Only confirm resize when nova instance status is VERIFY_RESIZENguyen Thanh Cong2020-10-011-1/+3
|/ | | | | | | | | | When nova compute config auto confirm resize, resize database flavor will fail because nova vm was activated. It raise exception 409 Conflict. We just only confirm resize when nova instance status is VERIFY_RESIZE Change-Id: I081c53056677f548547509bd820ac2511c383351 Story: #2008189 Task: #40950
* [Postgresql] Create replicaLingxian Kong2020-09-112-6/+9
| | | | Change-Id: Ia00032074dc44a6fbfc1e2d5ab16d1734a1a732c
* Support to check if subnet is associated with routerLingxian Kong2020-08-241-7/+7
| | | | Change-Id: I8041fbfdb01a7a1efa721c623ab3f43efd2cc0f0
* Merge "Support to update instance access"Zuul2020-08-113-0/+71
|\
| * Support to update instance accessLingxian Kong2020-08-113-0/+71
| | | | | | | | Change-Id: I640cd8b50fd0e0f80a1a45399b8bfdac437ae2b9
* | Wait for instance after rebuildLingxian Kong2020-08-071-10/+26
|/ | | | Change-Id: Ie6a44c442e1d17587435638851a58058408d5ea8
* Support to rebuild instance by adminLingxian Kong2020-08-063-16/+98
| | | | Change-Id: I48f8c6f997daeb6d82ff62b3325277d86fee2147
* Merge "Using same config with primary for replicas"Zuul2020-07-271-2/+2
|\
| * Using same config with primary for replicasLingxian Kong2020-07-271-2/+2
| | | | | | | | Change-Id: Icadc95ea54e4509dc148f8e84f2eaac5840509f3
* | Support online volume resizeLingxian Kong2020-07-241-57/+54
|/ | | | | | | | | | Trove now supports to resize volume without downtime. To use this feature, the version of Nova and Cinder needs to be at least Pike, the config option ``cinder_service_type`` needs to be set to ``volumev3``. The cloud admin can disable this feature by setting ``online_volume_resize=False``, default is enabled. Change-Id: I000a4e90800454972dd39f2f82d286571bc0b96c
* Support backup strategy APILingxian Kong2020-07-171-3/+5
| | | | Change-Id: I0ddd7214dae6e29ddfaf045fdb282f4980a8afff
* Support subnet and IP for instance creationLingxian Kong2020-06-101-6/+10
| | | | | | | | | | Support ``subnet_id`` and ``ip_address`` for creating instance. When creating instance, trove will check the network conflicts between user's network and the management network, additionally, the cloud admin is able to define other reserved networks by configuring ``reserved_network_cidrs``. Change-Id: Icc4eece2f265cb5a5c48c4f1024a9189d11b4687
* Set status to ERROR if heartbeat expiresLingxian Kong2020-06-041-86/+83
| | | | Change-Id: Ib8f5062094c0ec7766d4c6c6e7c3c8168e15ebd6
* Datastore containerizationLingxian Kong2020-05-273-229/+194
| | | | | | | | | | | | | Significant changes: * Using docker image to install datastore. * Datastore image is common to different datastores. * Using backup docker image to do backup and restore. * Support MariaDB replication * Set most of the functional jobs as non-voting as nested virtualization is not supported in CI. Change-Id: Ia9c97a63a961eebc336b70d28dc77638144c1834
* Support ip address type for instancesLingxian Kong2020-04-262-9/+14
| | | | | | | | | | | | | | Include address type in getting instance response. * Deprecate confip option network_label_regex as we don't reply on Nova to get addresses, network names don't make any sense. * Add 'addresses' in instance API response, keep 'ip' as is but mark it deprecated in API doc, python-troveclient shouldn't break. Story: 2007562 Task: 39445 Change-Id: Ia0458b5ddae8959ce29c17e444e1a51a026283cd
* Added checks for deleting datastore version13.0.0.0rc113.0.0Lingxian Kong2020-04-231-3/+11
| | | | | | | | | | * Hard delete the datastore_configuration_parameters table record. * Make 'datastore_version_id' nullable for 'instances' table. * Check if the datastore version is still being used before removal. Story: 2007563 Task: 39451 Change-Id: I84e4a31f14f9327cc01ff2d699167d91112e1565
* Add python-troveclient in requirements.txtLingxian Kong2020-03-151-7/+7
| | | | Change-Id: I2bd0d81171df85c05423e19ab2e4afa82fcf880e
* Improve the function testsLingxian Kong2020-01-281-30/+3
| | | | | | | | | | | | | | | - Execute test groups in serial to make sure no more than 2 database instance are created at the same time. - Remove some unneccesary tests - Remove unneeded datastore, e.g. 'Test_Datastore_1' - Remove unsupported trovestack subcommands - Move unsupported DIB elements to the 'deprecated-elements' folder - Decrease default value of 'agent_call_high_timeout' to 5min - Add initial_deplay for pooling task - Use socket file to connect with database instead of using localhost IP Change-Id: Ie5030a671fbeb453eafa6cbe04e08da7b52e33c9
* Fix unmount path for instance upgradeLingxian Kong2019-12-271-4/+8
| | | | Change-Id: Ifee8620a41e439b028e0a4d65164a75a100ce4d9
* Support HEALTHY status for db instanceLingxian Kong2019-12-141-10/+18
| | | | | | | | | | | - 'HEALTHY' means the db service is responsive, 'ACTIVE' means the db service is alive. - Remove the CI job fakemodetests, but will add similar testing task in the future. - Fix the periodic CI job - Remove MongoDB and related jobs Change-Id: I5abe9091ba203297dc87db5fba139179166321f7
* Fix delete instanceLingxian Kong2019-12-101-5/+15
| | | | | | | Deal with the situation when Trove fails to look for the Nova server when waiting for the db instance ACTIVE Change-Id: I484d45f24176c89d999864d3eb1c48860b3038bd
* Support incremental backup for MariaDBLingxian Kong2019-12-081-1/+2
| | | | | | Enable the tests in CI as well. Change-Id: Ie9706d26355bd325baf50ec874f05e6904768a1a
* Fix mariadb CI - trove-scenario-mariadb-singleLingxian Kong2019-12-052-8/+15
| | | | | | | | | - Trove supports MariaDB 10.4 - From MariaDB 10.3, Mariabackup is used instead of Percona XtraBackup for backup functionality - Some log improvements Change-Id: Ibaa6fd7273b98451097b32fb6b881008a236be9f
* Use dedicated service credential configLingxian Kong2019-10-102-10/+11
| | | | | | The current admin credential config options are confusing Change-Id: I92c15c065edf364b955f2243b3599e0b8cae8b4f
* Remove all the resources when the Nova VM creation failedLingxian Kong2019-10-091-137/+7
| | | | | | | | | Backport candidate for stable/train Story: 2006664 Task: 36926 Change-Id: If0991e0cef40ca78752fcd509d8438e90c9557bc
* Remove the annoying debug logsLingxian Kong2019-09-261-3/+0
| | | | | | | | Even though those are debug level logs, it doesn't make sense for the operators. If it's timeout or error occurs, the operator could see the VM status and service status from the CLI. Change-Id: I3fc9ff9e9343c1c884eece4955f15766230ff9a0
View Lorry Controller Status