1.In _validate_opts:
The following code is True forever, We will delete it.
2. Add unit test for ca_certs in _validate_opts.
Change-Id: I25a9a4aaae6fd5677d07d376f66188dc0b92bc3b
The current settings inside freezer-manage reflect on using host and
port which are no longer used. In addition, there seems to be no
splitting of the values in freezer-manage which means that it would
create a problem when trying to install against a list of hosts as
the ElasticSearch driver will refuse to accept the list.
This patch unifies all references of to 'hosts' and changes the option
to use ListOpt which is comma seperated values in the configuration
file which are then split into an array by oslo.config, which avoids
having to split things inside freezer.
Closes-Bug: #1681931
Change-Id: I613d0672ec2b186cd0d6365e795b35d9cff26dcd
Abstract storage configuration section to load different database
backend drivers. so we can keep supporting elasticsearch for
a while after moving to oslo.db also this will help in adding
API v2 as the elasticsearch driver will be changed.
Each db driver will register it's configuration on the run time.
Change-Id: Ie861e569f4add783c6f580cd0c08ed0fb3440151
This patch has added the necessary helper class
in the existing mechanism to validate client doc.
Change-Id: I9d2ade12b9306936fe32cbe7fba3adfcf4e367b6
Closes-Bug: #1650163
Partial-Bug: #1592308
This patch adds full pep8 check support. All code style problems
is fixed.
Closes-Bug: #1646103
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Change-Id: I1fce70a1b4e4c70379fc3876f85170b06a044059
Method on_get returns list of backups, not a single backup.
This patch fixes this issue.
Change-Id: I50ae24b11b58bcea3d2c9f117957300a926cd3ab
Closes-Bug: #1646573
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
fix freezer-scheduler job-start action by remove _version from elk
document being passed to elasticsearch.
Change-Id: I655ed59a5687ef1ea14c2b75d973f01666b3bb24
Closes-Bug: #1590413
Align to the other Openstack project and
use testr instead of pytest
Includes:
- pylint and pep8 fixes.
- py34 compliance
- requirements updated
- updated path to dsvm gate job
Change-Id: I10a5ea8d581029eba8f3ab5e016a1dd1919fa117
Depends-On: I4f9050cd551e87d2e398b6f94dc904154d0b1b13
Add support for options to be passed the the elasticsearch connection
The following options are supported in the freezer-api.conf file:
hosts='http://localhost:9200'
use_ssl=False
ca_certs=''
use_ssl=False
timeout=60
retries=20
The provided values are the respective defaults.
Implements blueprint: api-conf-db-options
Change-Id: I373503bf845d0ac8091c83280ac21611d30d1a07
Refactoring logging to use oslo.log to have standard OpenStack logging.
Refactoring log messages to enable i18n translations.
Refactoring Exception messages to enable i18n translations.
New requirement oslo.log.
Change-Id: I68850f9236f228c2ba99db2c3f3fb3a412f5ee4c
The freezer scheduler is to be executed
as daemon process on the client machines
It has the following responsibilities:
* when using the api:
- register -if necessary- as a client in the api
- download the list of jobs from the api
- schedule the jobs for execution
- launch the freezer client at the scheduled time
- collect metadata and exit codes and upload them to the api
- periodically poll the api for new/updated jobs
- if a job is part of a session (a coordinated group of jobs)
it updates the session status when job starts/stops
* when not using the api
- load jobs configurations from files
- schedule the jobs for execution
- launch the freezer client at the scheduled time
The freezer scheduler can also be used to manage jobs
and sessions using the following positional parameters:
job-list
job-get
job-create
job-delete
job-start
job-stop
session-list
session-get
session-create
session-delete
session-list-job
session-add-job
session-remove-job
or to register the client in the api using the positional parameter:
register
Implements blueprint: freezer-scheduler-start
Change-Id: I06ae202a0f464f7240c137744a5b54d1177cabd9
removes distinction between actions and configs in the api
The v1/jobs endpoint is the single point of access to the api
to store, search and retrieve operating instruction about
a single freezer run.
optional scheduling informations can be added to a job to
allow for future/recurrent job execution.
removes api endpoints
- v1/actions
- v1/configs
adds api endpoints:
- v1/jobs
Implements blueprint: freezer-api-jobs
Change-Id: Ideeef14dfccd21ddd10b4faa438124c04d2e1ff8
- Overview displays charts/reports (Currently only placeholders)
- Configurations allows to define new backup configurations and link them to
instances
- Backups shows a list of all succesful backups and allows to restore them
- Restores shows a history of all restored backups
It communicates with the api server via the client apis (freeezer.client.client).
The "glue code" between client apis and the UI lives in freezer.api.api.
Implements: Blueprint freezer-api-web-ui
Change-Id: I48cd8cba2b0169c6e64f650233c1a31b91ced34f
Adds an endpoint to the api for the registration of freezer clients
Change-Id: I1ca2a5e0021d383df70dfd001ab12967714c35bc
Implements: blueprint freezerclient-registration
First implementation of the freezer API.
Slightly more than a skeleton with basic functionality
Change-Id: Iae04affea3aa0f4a943599b528df49d9d4a5b845
Implements: blueprint freezer-api-first-rel
gengchc2