With this patch the scripts are generated by automatically
only from setuptools. The /bin/freezerc script is removed
and the content is incorporated in freezer.main
This patch should make more portable freezer on
win32 platform.
Unfortunately in order to support win32 platforms
we need to use a version of PBR >= 1.0.0,
to support env markers. Now requirements.txt reflects that
Change-Id: I31a4a13711f8c042072e3cc8785078fdbb971cb7
For some reason PBR wasn't installing the
packages listed in requirements.txt. By adding
explicitly the pbr version in setup.py and
adding setuptools requirements the issue is fixed.
Change-Id: Iccb66ae20a7108fe7f359ae656ed11c4e5d6f7a0
Freezer now uses pbr so to be aligned to the other
openstack projects.
Implements blueprint: switch-to-pbr
Change-Id: I67ffe7cf23b857f7d81420586361dcd708f0fc21
using trickle to limit bandwidth on linux by allowing freezer agent
to run a fork of itself through trickle and passing limit parameters
(upload-limit, download-limit) to trickle and remove it from
freezer agent.
Closes-Bug: #1466858
Change-Id: I0c3ac2e4085389dc71c8e242c84fefe7aea3c8a5
Currently the deps of oslo.i18n wasn't aligned with
Kilo global-requirements.
Now tests are not execute by runtests.py but tox
call directly py.test, as there was a bug in the exec
of runtests.py. This is a temporary solution as
testr will be used soon as testing framework
Close bug: 1498078
Change-Id: I07daddb14ab75fe089c98c8e00c24ecb550ada82
Now the ~/.freezer work_dir is created automatically it
it does not exists. The patch work on both Windows and Linux.
Close bug: 1480676
Change-Id: I2fabbe7c4c018417853192ffce6977f20dbf6229
Setting requirements to mins and caps aligned with global requirements
on packages where it's possible.
Commenting the ones that does not align.
Change-Id: Iba37d120c980ba849f79851fcbfc005651ed600d
In order to give flexibility Freezer needs to be able
to store data to a remote file system host using ssh/scp
instead instead of Swift.
Change-Id: Ia6a790e3e3b6bb9e4e36d457ba0b72c114f8a895
Implements: blueprint ssh-media
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
Finally pylint checks are executed now during the build.
Currently, as pylint is just enabled, checks for
Warnings, Refactor, Convention are disabled.
Closes bug: 1465063
Change-Id: I1a5447d7a7c2ec717e21aae67d26b0586edad7a5
fs_backup_mode now checks volume_id parameter in conf.
If we have volume_id - we execute cinder backup instead of tar or lvm backup.
As far as mongo_mode, mysql_mode, sql_server_mode are using fs_backup_mode
it will be execute cinder backup in case of provided volume_id parameter,
otherwise it will execute lvm or tar backup.
Implements blueprint: cinder-backup-mode
Change-Id: I7e70d3a0888cafee87232ab28c8fea48788e5de4
Add windows incremental support for backup and restore
Change-Id: I49a6b611f52a5d3a1950bd3f6f49cdb4a59354af
Implements: blueprint windows-backup-and-restore-incrementals
Backups for SQL Server, MySQL, MongoDB and filesystem on windows using
shadow copies (vssadmin), tar compression and encryption using openssl and tar..
Change-Id: I1f68e012f28891c19e4d94352511ec968382c8e2
Implements: blueprint add-windows-support-for-backup-and-restore
First implementation of the freezer API.
Slightly more than a skeleton with basic functionality
Change-Id: Iae04affea3aa0f4a943599b528df49d9d4a5b845
Implements: blueprint freezer-api-first-rel
Old backups are correctly removed, provided that
no not-to-be-removed backup depends upon them.
Incremental backups correctly start from level 0 when
there is no tar_metadata available for the last backup
Command line option --no-incremental is now incompatible
with --max-level and with --always-level
Add the following command which allows to specify
a datetime for old backup removal.
--remove-from-date YYYY-MM-DDThh:mm:ss
Closes-Bug: #1415865
Change-Id: Ie779ee354b67e9a1a012d28801b17dbd5cd353b6
LAUNCHPAD: https://bugs.launchpad.net/freezer/+bug/1415865
The PyPI installer for pyrsync was broken, so in order to assure a proper
install a workaround to fetch it from GitHub has been added. Updated tox.ini
file
Change-Id: Ib08dd822e04177a852d5f8846d10865e2e9417f8
There are issues porting to Windows when MySQLdb
C files have to be compiled. New library is
100% Python and 100% compatible.
LAUNCHPAD: https://blueprints.launchpad.net/freezer/+spec/windows-testing
Change-Id: Ic863bd231eaca5a891df61741df5e2ba6433ba4e
Now a basic unittest for tar.py
is available under tests/test_tar.py.
While writing unittest also one bug was discovered
and fixed.
LAUNCHPAD: https://blueprints.launchpad.net/freezer/+spec/unittest-tar
Change-Id: Ic8041b351d052253457a4e2720691e52f41eaf35
More Unittest needs to be implemented in Freezer.
The total coverage have to be at least 90%.
This commit is for freezer.backup unittest.
setup.py and tests directory re organized
according pytest best practices.
Change-Id: I61aa1b58d9501b81fda37dd785add27ba86d01c9
LAUNCHPAD: https://blueprints.launchpad.net/freezer/+spec/test-backup.py
The containers used by freezer to executed backups needs to have
freezer_ prefix in the name. If the user provider container doesn't
have the prefix, it is automatically added also to the container
segments name. This is done to quickly identify the containers
Added --path-to-backup to the existing ones (-F, --file-to-backup)
as can be more intuitive for the user
Bumped version to: 1.1.0 as 1.0.9-2 is now tagged in upstream
Change-Id: I891391ea07f75b5dcdc43d9b1d65a75837065f30
LAUNCHPAD: https://blueprints.launchpad.net/freezer/+spec/freezer-containers
- Fixed an issue when restoring multi level backup with queues
- Added th new option --action {backup, restore, info, admin}
- Extended examples in README and other minors log msg changes
- Changed homepage to github in setup.py
Change-Id: I5fa13971a3134d7f001dc3ce5aeabbc95a10626a
The following options are added/modified:
- --dereference-symlink {'none', 'soft', 'hard', 'all'}:
Follow Hard and soft links and archive and dump the files
they refer to according the choise option set.
- --lvm-auto-snap: now takes as argument the path you want to
guess for the lvm group and volume name
Also few types where removed. Dependencies are also update,
as now pymongo and mysqldb module needs to be installed
Change-Id: I99b780ff7b34dd85162634855357e1785db0e893
- freezer layout and code is now more
OpenStack oriented
- .gitreview points to review.openstack.org
- few more items are added in .gitignore
- tox.ini is added to be able to succesfully
py27 and pep8 gate jobs
- Code pep8 style is improved in this commit
- removed HACKING.rst and CHANGES.rst
- Bumped version to 1.0.9
Change-Id: If6dc5f32af83e726bb393017775e068fd2af8c04
OpenStack Proposal Bot