Freezer-api is not working as it is expected, returning NULL value
for src_file option in freezer_action's json returned from API.
In other words when user define action via freezer client and define
valid and WORKING action JSON with option path_to_backup
(src_file is not supported by freezer-agent anymore).
In DB we can see backup_metadata is filled correctly,
freezer-scheduler/freezer-agent working correctly as they are reading
backup_metadata. Problem is that API is still returning json with
src_file set tu NULL because src_file is not present in backup_metada,
therefore is not filled in src_file column in action table.
Src_file option was changed to path_to_backup in freezer git repository
below, but API was never changed, this patch is fixing this behaviour.
Freezer's change :
c7f71ff70b
Doc changes in freezer:
https://review.opendev.org/#/c/705003/
Change-Id: I9e74910bd0ff4ad18b830c26ce90770b0dfa107b
There are some bugs in replace_action and
replace_job.
There are some bug in replace_tupe, such as, The session table can
only be modified whichever table is replaced.
Change-Id: Ie0ae7880299b4e94860324aa10eea6b8b859d278
1. This patch is for job_search unit test with search option.
This query is from freezer-scheduler.
2. Modify the function filter_tuple_by_search_opt, in order to
add excepion process.
Change-Id: I03ec588168464f68683d79c28aa7b2d4c8ea16f1
When there is more than one freezer agent, fox example:
client_id=node1, client_id=node2
freezer job-create --client node1 --file node1.json
freezer job-create --client node2 --file node2.json
The freezer agent node1, get two jobs,
instead of job about node1.json.
Change-Id: I8fea80adc1a9d72fe849fca561e496bee9a95f82
currently, sqlachemy driver of freezer-api only
support api version 2, the patch add v1 version
support
Change-Id: I2608b1152ee3e03409f0321221b1aa8efe3d3d33
Add jobs api in v2.
The other tables,api and test will be added in following patch.
ref: https://storyboard.openstack.org/#!/story/2004132
Story: #2004132
Task: #27578
Change-Id: Ia64d6d49e692a3d2875662252eb270fb04d9df33
Implements: bp add-mysql-support-for-freezer
Add backup api in v2.
The other tables,api and test will be added in following patch.
ref: https://storyboard.openstack.org/#!/story/2004132
Story: #2004132
Task: #27578
Change-Id: I27e010fb332e25b570aa56ac0432d71621c3929e
Implements: bp add-mysql-support-for-freezer
Add session api in v2.
The other tables,api and test will be added in following patch.
ref: https://storyboard.openstack.org/#!/story/2004132
Story: #2004132
Task: #27578
Change-Id: I1fc0669e67af7f468037e13e2bd8111c4ed26fb3
Implements: bp add-mysql-support-for-freezer
Add action api in v2.
The other tables,api and test will be added in following patch.
ref: https://storyboard.openstack.org/#!/story/2004132
Story: #2004132
Task: #27578
Change-Id: I511a281b599fd3846463cfa294172be2856162a1
Implements: bp add-mysql-support-for-freezer
Add clients api in v2.
The other tables,api and test will be added in following patch.
ref: https://storyboard.openstack.org/#!/story/2004132
Story: #2004132
Task: #27578
Change-Id: I8ac7cbd6fc41c25510c1a3ad000cb109f9306efc
Implements: bp add-mysql-support-for-freezer
Add support to oslo.db to be used as a DB driver. The DB driver will be
used with API v2. When it's completely implemented, API V1 will be
deprecated and removed by the end of the cycle. Freezer-api will keep
supporting V2 with Elasticsearch, Sqlalchemy drivers.
This patch implements the follow:
* Abstract Base DB driver to be implemented by each driver
* Base driver; will return only access to the db engine, session
* SqlAlchemy driver;
* ElasticSearch driver;
* Implement both drivers in freezer-manage
Partially-Implements: blueprint oslo-db
Depends-On: I81e417155da48f46dd2113e5745fb3c21c96499f
Depends-On: I2e5724b1f1a75121952e2beb3844d2c489e4df68
Depends-On: Idb4ac050652d1d0107bf3fcd447d7cbedd811809
Depends-On: I81d46c89859752c0cbc21ef02de90db7f19f942c
Change-Id: I93ed1b909f538728a1a9bd5c8b07baf7aeddb705
liyou01