summaryrefslogtreecommitdiff
path: root/etc/trove
Commit message (Collapse)AuthorAgeFilesLines
* [goal] Deprecate the JSON formatted policy fileGhanshyam Mann2020-12-261-1/+1
| | | | | | | | | | | | | | | | | | As per the community goal of migrating the policy file the format from JSON to YAML[1], we need to do two things: 1. Change the default value of '[oslo_policy] policy_file'' config option from 'policy.json' to 'policy.yaml' with upgrade checks. 2. Deprecate the JSON formatted policy file on the project side via warning in doc and releasenotes. Also replace policy.json to policy.yaml ref from doc and tests. [1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html Change-Id: I790409da69df8479ad2fe152b15c32ba45067c23
* Datastore containerizationLingxian Kong2020-05-276-504/+0
| | | | | | | | | | | | | 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-8/+0
| | | | | | | | | | | | | | 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
* Support to create public trove instanceLingxian Kong2019-09-111-6/+2
| | | | | | | | | | | | | | | | | | | | - The users need to specify the network to create Trove instance, but trove-taskmanager will create port in that network for Nova instance creation. Using port gives Trove more capabilities to define how the database service is exposed. - Deprecate ICMP protocol for the instance. - Restrict 'nics' parameter for creating instance. - Add 'access' parameter for creating instance. - Add 'public_network_id' option in order to create floating IP for the instance. - Do not create records for security groups, but Trove can still delete existing instances for backward compatibility. - Delete unreasonable Host, Account, Storage API. Story: 2006500 Task: 36468 Task: 36466 Change-Id: I80827e1ad5e6b130cbf94c2bb7a909c44d5cf1e5
* Support keypair in devstackLingxian Kong2019-08-292-306/+0
| | | | | | | | | | | | | Since Trove already supports to specify a Nova keypair when creating instance for management convenience, devstack needs to be changed to create the management keypair and add to Trove config file. One extra change in this patch is to use a single config file for Trove API, task-manager and conductor. Change-Id: I1e6c4f4305104815bdf89b31776a4955de61bc89 Story: 2005429 Task: 30463
* Deprecate the config option default_neutron_networksLingxian Kong2019-03-262-2/+2
| | | | | | | | Use `management_networks` instead. `management_networks`will be used as admin networks which will be attached to Trove instance automatically. Change-Id: I5c6004b568c3a428bc0f0a8b0e36665d3c5b3087
* Be compilance with latest oslo.messagingMarcin Piwowarczyk2018-10-135-123/+1
| | | | | | | | | | | | | | | | | | | | | | Support for the [oslo_messaging_rabbit] section has been removed in oslo.messaging==9.0.0 package [1]. That's why integration tests failures on build devstack step. This is the moment where we need to use the transport_url directive in the [DEFAULT] section instead. Moreover rpc_backend property (which was used in trove to enable fake RPC backend) has been removed from DEFAULT section and API tests fails on TIME_OUT as they starts on rabbit RPC backend. Fake RPC can be now configured as described here [2]: transport_url = 'fake:/' [1] https://docs.openstack.org/releasenotes/oslo.messaging/unreleased.html [2] https://docs.openstack.org/oslo.messaging/latest/configuration/conffixture.html Change-Id: Id6c5a9198d5a213cb085407a1d8b534e7c755f69 Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
* Update auth_uri option to www_authenticate_uricaoyuan2018-04-112-2/+2
| | | | | | | | | Option auth_uri from group keystone_authtoken is deprecated[1]. Use option www_authenticate_uri from group keystone_authtoken. [1]https://review.openstack.org/#/c/508522/ Change-Id: I46bb0acaf1dec9bb4b91d4a2180b3e7ed66741c2
* fix a typo in documentationmelissaml2018-03-231-1/+1
| | | | Change-Id: Ic53adfb74c628c8ca85b2fa2107999c1ae816833
* Merge "Add functionality to define different Message and Notification ↵Zuul2018-03-194-0/+112
|\ | | | | | | destination"
| * Add functionality to define different Message and Notification destinationwangjun2018-01-054-0/+112
| | | | | | | | | | | | | | | | | | Sometime,huge notification messages will effect the rabbitMQ cluster's performance.This commit adds functionality do define different Message and Notification destination. Closes-Bug: #1734823 Change-Id: I2ef4d008c9ca91a03d8c7e1380e0188bf6792595
* | Generate policy sample file automatically.Zhao Chao2018-02-122-243/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | A new entrypoint in setup.cfg and a config file are added for using olso.policy helper script to generate the sample file. A new tox target also is added to simplify the environment setting up. Now policy sample file can be generated automatically, so the in-repo sample file is no longer needed. Co-Authored-By: Andrew Laski <andrew@lascii.com> Partial-Implements: blueprint policy-in-code Change-Id: Ic336fa154ccc05b5e9db3a8e751a484b1cc5aa9c Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
* | Remove support of creating volume from Nova.Zhao Chao2018-02-092-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Current Nova server volume support is broken. Nova also declared the 'os-volumes_boot' will be deprecated in the future. As creating volumes by cinderclient has been supoorted for a long time, we could just drop support of Nova server volume. This patch also migrate to the new block_device_mapping_v2 parameter of Nova servers creating API. Closes-Bug: #1673408 Change-Id: I74d86241a5a0d0b1804b959313432168f68faf89 Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
* | Remove the heat related documentsZhongShengping2018-01-172-8/+4
| | | | | | | | | | | | | | | | This patch[1] removed heat related support. [1]https://review.openstack.org/#/c/385513/ Change-Id: Ib1b6f9f36097ae043d92fef3b32cf1f0ebac9672
* | Remove policy.json fileDai Dang Van2017-12-072-97/+243
|/ | | | | | | | | | | We already had default rule in code, so we should not still define all of them again in policy file. Besides, we should you yaml format for now instead json. Another thing, we don't need to config policy file in Devstack enviroment. Change-Id: I783ba51695271d358764557899fe91e84620556d
* Merge "Comment out the option oslo_messaging_rabbit.rabbit_password"Zuul2017-11-245-5/+5
|\
| * Comment out the option oslo_messaging_rabbit.rabbit_passwordStephen Ma2017-08-215-5/+5
| | | | | | | | | | | | | | | | The option oslo_messaging_rabblt.rabbit_password has been deprecated. Therefore the option is commented out in the sample config files etc/trove/ directory. Change-Id: I613087217c88b8a5dbf8dfc3f51e48b8fe4c84c8
* | Merge "Open the volume_support of redis"Zuul2017-11-092-6/+5
|\ \
| * | Open the volume_support of redisjiansong2017-11-032-6/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | In the past, we support volume_support when we support redis-cluster[1], but we did not update to conf[2]. we are making the sample conf files match the default configuration in code. [1]:https://review.openstack.org/#/c/203702/ [2]:https://review.openstack.org/#/c/107117/ Closes-Bug: #1701469 Change-Id: I428e274fdb85621b21453780e90a8a0ab401ffd9
* | Merge "Remove exists_notification_ticks from sample conf"Zuul2017-10-231-1/+0
|\ \
| * | Remove exists_notification_ticks from sample confSamuel Matzek2017-07-261-1/+0
| |/ | | | | | | | | | | | | | | The exists_notification_ticks conf option was removed under commit 08dc866fb241f535cce0609b02a34853882538f5 but was not removed from the sample configuration file. Change-Id: I3608929bd1ce4cd6ec767665b6f60fd5d86127b4
* | Remove inexistent option in install guide.Fan Zhang2017-08-071-10/+0
|/ | | | | | | | | Remove notifier_queue_* because the options are no longer needed and should be removed. Closes-bug: #1706528 Change-Id: Idfd205473f1756a69d0d9607e9f8c1dd9780553c
* Merge "Wrong comment symbol in configuration file"Jenkins2017-06-161-1/+1
|\
| * Wrong comment symbol in configuration fileLiuYang2017-02-241-1/+1
| | | | | | | | Change-Id: Icf6fa8296ae3bfa05a8e4f07c38ede1fb951d18d
* | Add port 16379 to conf.samplejiansong2017-04-262-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a point that is easily hidden. In the case of not open port 16379, redis cluster can still be deployed successfully, but this success is a false success, there is no data communication between the various nodes. This is because 16379 is the port for data port[1]. We set the default value in cfg, but in the case of conf,it is easy to be covered. Adding 16379 to conf.sample helps the user to reduce some problem caused by the redis configuration. [1]:https://redis.io/topics/cluster-tutorial Change-Id: If517072c1c875df68106af14dac1802bb959d17e
* | fix-gate: change trove auth URL's to reflect new URL settingsAmrith Kumar2017-04-235-8/+8
| | | | | | | | | | | | | | | | | | | | | | Trove's code was setup to use :5000 and :35357 for keystone's auth end points. Change that to reflect the new settings that are /identity/ and /identity_admin/. See also [1] [1] https://review.openstack.org/#/c/456344/ Change-Id: I3d6f6649430ee40879de15fee0b215dc32e8b666 Related: I46294fb24e3c23fa19fcfd7d6c9ee8a932354702
* | Add support for module-reapply commandPeter Stachowski2017-02-271-1/+2
|/ | | | | | | | | | | | | | | | | | | | Server side support for the new 'reapply' command. This reapplies a given module to all instances that it had previously been applied to. Originally, a module designated live-update would automatically be re-applied whenever it was updated. Adding a specific command however, allows operators/users more control over how the new payload would be distributed. Old 'modules' could be left if desired, or updated with the new command. Scenario tests were updated to test the new command. DocImpact: update documentation to reflect module-reapply command Change-Id: I4aea674ebe873a96ed22b5714263d0eea532a4ca Depends-On: Ic4cc9e9085cb40f1afbec05caeb04886137027a4 Closes-Bug: #1554903
* Add support for Oslo Policies to TrovePetr Malik2016-12-061-0/+96
| | | | | | | | | | | | | | | | | | The Oslo Policy library provides support for RBAC policy enforcement across all OpenStack services. Update the devstack plugin to copy the default policy file over to /etc/trove in the gate environments. Note: Not adding a rule for 'reset-password' instance action as that API was discontinued years ago and is now just waiting for removal (Bug: 1645866). DocImpact Co-Authored-By: Ali Adil <aadil@tesora.com> Change-Id: Ic443a4c663301840406cad537159eab7b0b5ed1c Implements: blueprint trove-policy
* Merge "Use http_proxy_to_wsgi middleware"Jenkins2016-11-213-3/+19
|\
| * Use http_proxy_to_wsgi middlewareMasaki Matsushita2016-08-033-3/+19
| | | | | | | | | | | | | | | | This commit enables to handle HTTP_X_FORWARDED_PROTO by using http_proxy_to_wsgi middleware of oslo.middleware. Change-Id: I6a11c8470205ca78bdb027fa9a06fec3acda33ad Closes-Bug: #1590608
* | Implement full online backups for DB2Mariam John2016-09-131-1/+1
| | | | | | | | | | | | | | | | | | Currently Trove supports full offline backups for DB2. In this implementation, we have added support for full online backups for DB2 using archival logging. Change-Id: I30b5b0b85120fd105cc3db57983b062fad5fab5a Implements: blueprint db2-online-backup
* | Merge "Trove workbook for scheduled backups"Jenkins2016-09-091-0/+19
|\ \
| * | Trove workbook for scheduled backupsMorgan Jones2016-08-251-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | A Mistral workbook adding a workflow for creating a backup. This is used by the "trove schedule-create" command to schedule a backup. Change-Id: I68d997abf4ec7c32044dd18cf2a70e687c0fed9f Implements: blueprint schedule-backups
* | | Merge "Add trove-guestagnet.conf sample for log rotation"Jenkins2016-08-232-0/+40
|\ \ \
| * | | Add trove-guestagnet.conf sample for log rotationMasaki Matsushita2016-08-092-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds a configuration sample of guestagent to use log rotation. Change-Id: I2f2fb0d42f2f9d674daf3adff8725a365cc1a5b3 Closes-Bug: #1269615
* | | | guest_id missing err, switch config_drive defaultGreg Retkowski2016-08-061-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes the default setting for use_nova_server_config_drive from False to True. By default, nova does not use a config drive for launched instances. Therefore trove must implicitly request the config drive be used so that it can inject guest_info.conf into the guest VM. This commit also adds an error to guestagent when guest_id is missing. If the guest_id configuration parameter is not set at guestagent startup it will throw a RuntimeError. This case typically occurs because guest_info.conf was not injected into the guest, or was not included in the set of configs that guestagent reads at startup. And finally, this commit adds a section in the 'building guest images' documentation describing how configuration is injected into the guest agent. Change-Id: I084c841472183893a63ca7b70d560f44a2f08901 Partial-Bug: 1609915
* | | Introduce "icmp" option for security group ruleMasaki Matsushita2016-08-041-0/+2
| |/ |/| | | | | | | | | | | | | | | | | | | This change introduces new datastore option "icmp" to configure whether to permit ICMP. It helps users to check DB instance health in different way from access DB ports. DocImpact Closes-Bug: #1485884 Change-Id: I61edeb38ded5543b7976a01363108a7b5b4fc5b5
* | Switch from MySQL-python to PyMySQLJeremy Stanley2016-06-304-5/+5
|/ | | | | | | | | | | | | | | | | | | | | As discussed in the Liberty Design Summit "Moving apps to Python 3" cross-project workshop, the way forward in the near future is to switch to the pure-python PyMySQL library as a default. https://etherpad.openstack.org/p/liberty-cross-project-python3 BaseMySqlRootAccess.enable_root(): catch also InternalError because the PyMySQL error is not wrapped into a SQLAlchemy OperationalError, but a generic SQLAlchemy InternalError. Similar change is made in 026_datastore_versions_unique_fix.py. This change requires a trove integration change to add the PyMySQL to the guest image: Id4d013d174ba40a453819f900aaa316a93e59b48. Partially implements: blueprint trove-python3 Co-Authored-By: Victor Stinner <vstinner@redhat.com> Depends-On: Id4d013d174ba40a453819f900aaa316a93e59b48 Change-Id: I65e8a8d5dc251a8b00529cdfb1a6ada3d5720f68
* Switch test config file to use os_region_nameMatt Fischer2016-06-051-1/+1
| | | | | | The old value of nova_region_name has not been used in some time. Change-Id: I8fdd6d8ae4f0982b37cff7b5583429ccb6bd4aaf
* remove verbose option in Trove config filesAmrith Kumar2016-05-264-10/+0
| | | | | | | | | | This option is now deprecated and will be removed in Newton. The default is True, time to get rid of it in Trove. Partial-Bug: 1586066 Change-Id: I63e3a2832d0862254548be36fea77d5d4fa381b3 related: https://review.openstack.org/#/c/314573/ ref: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095166.html
* Merge "Add MongoDB config server port to cfg"Jenkins2016-03-181-1/+1
|\
| * Add MongoDB config server port to cfgMatt Van Dijk2016-03-091-1/+1
| | | | | | | | | | | | | | | | | | The configuration server port 27019 was missing from the Trove config files. Add it, and replace the hardcoded version in the guestagent with a ref to the conf. Change-Id: Ibca4cbed7669a0fde82af4e3c402f80d24bd9fad Closes-bug: #1555180
* | Implement Backup and Restore for CouchDBMariam John2016-03-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The recommended method for doing full backups in CouchDB has been a simple filesystem copy of the data files. This is because CouchDB stores data in wholly contained append only files. For example, when a user creates a database, a corresponding <database-name>.couch file is created in the database directory. The backup functionality has been implemented by compressing the database directory and then encrypting it and sending it over to store in Swift. Similarly, the restore functionality has been implemented by fetching the files from Swift and uncompressing them into the database directory. After this, the ownership of the directory needs to be updated. To test the changes, follow the steps: - Create a CouchDB instance - Access the admin console called Futon using the following url: http://10.0.0.5:5984/_utils/ - Create a database from there and create one or more documents - Create a backup of this CouchDB instance - Create another CouchDB instance from the backup created above - Access the admin console for this new instance and verify that the database created above is there couchdb client library for the integration tests has been added to global-requirements: https://review.openstack.org/#/c/285191/ Change-Id: Iad6d69bf60ace73825819081964a43ad53d6c6fc Implements: blueprint couchdb-backup-restore
* | Merge "Addition of DB2 backup & restore functionality"Jenkins2016-03-151-0/+6
|\ \
| * | Addition of DB2 backup & restore functionalityIshita Mandhan2016-03-151-0/+6
| |/ | | | | | | | | | | | | | | | | Implementation of backup and restore functionality for db2 databases. Backup occurs on instance and then it is compressed and streamed to Swift. Restore works backwards. Change-Id: I78dd67369a1670ca72a89cc111cae40ed091fe47 Implements: blueprint db2-backup-restore
* | Moved CORS middleware configuration into set_defaultsMichael Krotscheck2016-03-142-26/+42
|/ | | | | | | | | | | The default values needed for trove's implementation of cors middleware have been moved from paste.ini into a common set_defaults method, invoked on load. Unlike similar patches on other services, this patch does not include config-generation hooks, as trove doesn't use them yet. Change-Id: Id8e04249498f63e42dadcacbd2c08b525adc0958 Closes-Bug: 1551836
* Add backup & restore for CassandraPetr Malik2016-02-131-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement backup and restore functionality for Cassandra datastore. We implement full backup strategy using the Nodetool (http://goo.gl/QtXVsM) utility. Snapshots: Nodetool can take a snapshot of one or more keyspace(s). Snapshot(s) will be stored in the data directory tree: '<data dir>/<keyspace>/<table>/snapshots/<snapshot name>' A snapshot can be restored by moving all *.db files from a snapshot directory to the respective keyspace overwriting any existing files. NOTE: It is recommended to include the system keyspace in the backup. Keeping the system keyspace will reduce the restore time by avoiding need to rebuilding indexes. The Backup Procedure: 1. Clear existing snapshots. 2. Take a snapshot of all keyspaces. 3. Collect all *.db files from the snapshot directories package them into a single TAR archive. Transform the paths such that the backup can be restored simply by extracting the archive right to an existing data directory (i.e. place the root into the <data dir> and remove the 'snapshots/<snapshot name>' portion of the path). The data directory itself is not included in the backup archive (i.e. the archive is rooted inside the data directory). This is to make sure we can always restore an old backup even if the standard guest agent data directory changes. Attempt to preserve access modifiers on the archived files. Assert the backup is not empty as there should always be at least the system keyspace. Fail if there is nothing to backup. 4. Compress and/or encrypt the archive as required. 5. This archive is streamed to the storage location. The Restore Procedure: 1. Create a new data directory as it does not exist. 2. Unpack the backup to that directory. 3. Update ownership of the restored files to the Cassandra user. Notes on 'cluster_name' property: Cassandra has a concept of clusters. Clusters are composed of nodes - instances. All nodes belonging to one cluster must all have the same 'cluster_name' property. This prevents nodes from different logical clusters from accidentally talking to each other. The cluster name can be changed in the configuration file. It is also stored in the system keyspace. When the Cassandra service boots up it verifies that the cluster name stored in the database matches the name in the configuration file and fails if not. This is to prevent the operator from accidentally launching a node with data from another cluster. The operator has to update the configuration file. Similarly, when a backup is restored it carries the original cluster name with it. We have to update the configuration file to use the old name. When a node gets restored it will still belong to the original cluster. Notes on superuser password reset: Database is no longer wide open and requires password authentication. The 'root' password stored in the system keyspace needs to be reset before we can start up with restored data. A general password reset procedure is: - disable user authentication and remote access - restart the service - update the password in the 'system_auth.credentials' table - re-enable authentication and make the host reachable - restart the service Note: The superuser-password-reset and related methods that potentially expose the database contents are intentionally decorated with '_' and '__' to discourage a caller from using them unless absolutely necessary. Additional changes: - Adds backup/restore namespaces to the sample config file 'trove-guestagent.conf.sample'. We include the other datastores too for the sake of consistency. (Auston McReynolds, Jul 6, 2014) Implements: blueprint cassandra-backup-restore Co-Authored-By: Denis Makogon <dmakogon@mirantis.com> Change-Id: I3671a737d3e71305982d8f4965215a73e785ea2d
* Merge "Move rabbit conf settings to separate section"Jenkins2016-02-015-97/+113
|\
| * Move rabbit conf settings to separate sectionDoug Shelley2015-12-225-97/+113
| | | | | | | | | | | | | | | | | | | | oslo.messaging has deprecated the use of messaging config settings, specifically rabbit_* settings, in the [DEFAULT] section. This commit moves the rabbit settings to a [oslo_messaging_rabbit] section in each of the relevant trove service sample config files. Change-Id: Ia869768102a8a841313cd7e0fd8a9fdab257d3e3 Closes-Bug: #1528391
* | Added Keystone and RequestID headers to CORS middlewareMichael Krotscheck2016-01-081-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | CORS middleware's latent configuration feature, new in 3.0.0, allows adding headers that apply to all valid origins. This patch adds headers commonly used in openstack to trove's paste pipeline, so that operators do not have to be aware of additional configuration magic to ensure that browsers can talk to the API. For more information: http://docs.openstack.org/developer/oslo.middleware/cors.html#configuration-for-pastedeploy Change-Id: Idf2cd7a0d0d701002f2c1f178475da39ae1a9caf
View Lorry Controller Status