Result of running
$ pyupgrade --py38-plus $(git ls-files | grep ".py$")
This was inspired by Nova [1] and Octavia [2]
Fixed PEP8 errors introduced by pyupgrade by running:
$ autopep8 --select=E127,E128,E501 --max-line-length 79 -r \
--in-place designate
and manual updates.
[1]: https://review.opendev.org/c/openstack/nova/+/896986
[2]: https://review.opendev.org/c/openstack/octavia/+/899263
Change-Id: Idfa757d7ba238012db116fdb3e98cc7c5ff4b169
- Remove old base objects
Co-authored-By: Nguyen Van Trung <trungnv@vn.fujitsu.com>
Change-Id: Icb8817a699a8c12957126a0499d95d13b8eeda6d
Implements: blueprint designate-rolling-upgrade
This commit will migrate:
- Pool and PoolList
- Related objects
Co-authored-By: Dai Dang Van <daidv@vn.fujitsu.com>
Change-Id: I59da0628a9dc23efe8d8665bbf3359e652eaa8c9
Implements: blueprint designate-rolling-upgrade
This commit will migrate:
- ZoneImport and ZoneImportList
- ZoneExport and ZoneExportList
- ZoneTransferAccept and ZoneTransferAcceptList
- ZoneTransferRequest and ZoneTransferRequestList
Co-authored-By: Nguyen Van Trung <trungnv@vn.fujitsu.com>
Change-Id: I80173ce20b5ef45f0bbbc2c5552b67e1aaec0c06
Implements: blueprint designate-rolling-upgrade
This is a pretty invasive change :)
A non complete list of changes:
* Database Tables
* Database Columns
* Designate Objects and fields on Objects
* Designate Objects Adaptors stop doing some of the renames
* All RPCAPI versions are bumped - totally backward
incompatable (function names have changed)
Change-Id: Ib99e918998a3909fa4aa92bf1ee0475f8a519196
Do the needful to move Zone Exports to an asynchronous resource in the
v2 API, as discussed at the Austin 2015 summe mid-cycle
* Make designate-zone-manager an RPC service, with a read-only connection
to the database
* Add a 'location' column to the zone_tasks table that stores a location
(swift, URI) that is used to determine where the export will be made
available to the user
* Add all the infrastucture to make zone export resources live (objects,
central, storage methods)
* Add a quota on the size of allowed synchronous exports
* Tests, docs
THIS DOES NOT IMPLEMENT
* Zone exports to Swift
* Debateable: See the note in zone_manager/service.py about how the configuration
and determination of future swift exports will work.
ApiImpact
Blueprint: async-export
Change-Id: I1c168b10358164c3ca5be986b4d615df71062851
Erik Olof Gunnar Andersson