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

[ci.jenkins.io] Enable disk backup for datadisk #3527

Closed
dduportal opened this issue Apr 19, 2023 · 2 comments
Closed

[ci.jenkins.io] Enable disk backup for datadisk #3527

dduportal opened this issue Apr 19, 2023 · 2 comments

Comments

@dduportal
Copy link
Contributor

The goal is to ensure we have a daily backup of the JENKINS_HOME of ci.jenkins.io

Azure provides a Backup System, than can be used specifically for managed disks such as this one: https://learn.microsoft.com/en-us/azure/backup/backup-managed-disks.

We don't (and should not) need a VM-level backup as we use Puppet to manage the system: disaster recovery for ci.jenkins.io is to install a blank new VM and mount the resotre of the datadisk for Jenkins.

As per https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/data_protection_backup_instance_disk, we can define this using Terraform which implies importing ci.jenkins.io VM once for all.

A word about encryption:

  • The backup vault is, like the VM disks, encrypted at rest with an Azure PMK key (hardware level).
  • We can keep this behavior (encryption at rest with PMK) for the backup, as ci.jenkins.io deos not have any senstivie data (eventually credentials for GH org, but that is all).
  • Note: This encryption could be provided a custom key private for sensitvie backups such as trusted.ci's
@dduportal
Copy link
Contributor Author

@dduportal
Copy link
Contributor Author

Closing as superseeded by #3535

@dduportal dduportal removed this from the infra-team-sync-next milestone Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants