Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backup/recovery: uncommenting and refactoring legacy code #1241

Merged

Conversation

sk4zuzu
Copy link
Contributor

@sk4zuzu sk4zuzu commented May 7, 2020

#1185 #1199
Please note this unusual PR is not intended to be merged to develop branch yet. :) Please leave your comments.

@sk4zuzu sk4zuzu requested review from plirglo and seriva May 7, 2020 22:42
@sk4zuzu sk4zuzu merged commit 189da81 into hitachienergy:feature/backup-restore May 8, 2020
plirglo added a commit that referenced this pull request Jun 29, 2020
* backup/recovery: uncommenting and refactoring legacy code (#1241)

* backup/recovery: adding ansible code for syncing files between hosts (#1257)

* backup/recovery: adding ansible code for syncing files between hosts

* backup/recovery: adding rsync to package requirements

* backup/recovery: fixing rsync code + adding random name for private key

* backup/recovery: adding ssh code (transfer via pipeline)

* backup/recovery/prometheus: enabling admin API + initial implementation

* backup/recovery: adding initial code for restoring monitoring snapshots (#1259)

* backup/recovery: moving sync code to roles + cleanups

* backup/recovery: adding initial code for restoring monitoring snapshots

* backup/recovery: adding kubernetes backup sync (copy-only)

* backup/recovery: checking if snapshots are available first

* backup/recovery: adding on-the-fly sha1 calculation (#1262)

* backup/recovery: adding on-the-fly sha1 calculation in the download_via_ssh copy method

* backup/recovery: fixing on-the-fly sha1 calculation

- monitoring: reverting invalid tar argument order
- download_via_ssh: making the inline_script fail properly

* Postgres Backup Initial

* postgres backup

* Add all config files to backup

* backup/recovery: monitoring refactor (#1270)

- switching from ssh to rsync
- adding grafana backup/restore
- adding prometheus etc backup/restore

* backup/recovery: adding loadbalancer (#1279)

* backup/recovery: logging (WIP) (#1277)

- work in progress, does not work with elasticsearch clusters yet

* backup/recovery: adding rabbitmq (without messages) (#1291)

* backup/recovery: adding rabbitmq (without messages)

* backup/recovery: adding rabbitmq (archive fix)

* Epicli backup/restore improvements and refactor (#1299)

* epicli: moving component parser to separate module

* backup/recovery: moving backup storage to repository hosts

* backup/recovery: PatchEngine refactor (adding yaml based config)

* backup/recovery: adding backup common tasks

* backup/recovery: adding recovery common tasks

* backup/recovery: kubernetes refactor

* backup/recovery: load_balancer refactor

* backup/recovery: logging refactor

* backup/recovery: monitoring refactor

* backup/recovery: rabbitmq refactor

* backup/recovery: postgresql refactor (unfinished)

* backup/recovery: adding optional -b build_directory parameter (#1301)

* merge, modify postgres to use new setup (#1308)

* Postgres recovery fix (#1339)

* merge, modify postgres to use new setup

* recovery fix

* backup/recovery: fixing user vs default config merge logic (or lack of it) (#1345)

* Modify backup / restore roles according to test results (#1356)

* merge, modify postgres to use new setup

* recovery fix

* centos testing changes

* fix after redhat tests

* merge

* Add provider to backup / restore

* Notes about kubernetes

* backup/recovery: adding missing provider value to role vars (fix) (#1358)

* backup/recovery: epicli invocation refactor + adding schema validations

* Change in Postgresql recovery task

* backup/recovery: moving schema validation to earlier stage

* backup/recovery: splitting PatchEngine into BackupEngine and RecoveryEngine

* SchemaValidator: adding ability to check individual documents (without the base schema)

* backup/recovery: reusing modified SchemaValidator

* backup/recovery: removing unneeded/broken kubernetes recovery code

* backup/recovery: removing unused code and trailing whitespace

* backup/recovery: removing abandoned component parser

* doc_list_helpers: adding missing unit tests for the "select_single" helper

* Backup / recovery documentation (#1377)

* Feature/restore and backup validation (#1379)

* Add recovery components validation

* Reformating

* Update core/src/epicli/data/common/validation/configuration/recovery.yml

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Update core/src/epicli/data/common/validation/configuration/recovery.yml

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Update core/src/epicli/data/common/validation/configuration/recovery.yml

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Update core/src/epicli/data/common/validation/configuration/recovery.yml

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Update core/src/epicli/data/common/validation/configuration/recovery.yml

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Add regex for deeper validation

* Add validations config for backup manifest

* Fix true/false in additional values

Co-authored-by: Michał Opala <sk4zuzu@gmail.com>

* Fix postgres check for RedHat (#1389)

* Hotfix for the elasticsearch recovery procedure (#1381)

* backup/recovery: logging/elasticsearch snapshot restore fix

- ensuring kibana is always down
- deleting all indices prior to restore

* backup/recovery: logging/elasticsearch snapshot restore fix

- ensuring all filebeat instances are always down

* backup/recovery: logging/elasticsearch snapshot restore fix

- ensuring kibana and filebeat instances will not be started (via reboot) during restore

* backup/recovery: fixing load_balancer in RedHat (#1390)

* Fix database check (#1391)

Co-authored-by: Irek Głownia <48471627+plirglo@users.noreply.github.com>
Co-authored-by: Marcin Pyrka <pyrka.marcin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants