[gitlab-org/gitlab] Adapt Debian Distribution models for blob replication

### ROOT CAUSE The issue arises because the current Debian Distribution models lack the necessary attributes and relationships to support Geo-replication of blobs. This results in incomplete tracking of replication status, lack of synchronization between Geo sites, and potential data inconsistencies. The issue is tied to the Geo self-service framework, requiring modifications to enable proper replication and verification. ### CODE FIX To address this, update the Debian Distribution models to include replication tracking and Geo-specific fields: 1. **Add Replication Tracking Fields**: - Add columns to the `debian_distributions` table to track replication status and associated Geo sites: ```sql ALTER TABLE debian_distributions ADD COLUMN replication_status ENUM('pending', 'success', 'failed') DEFAULT 'pending'; ALTER TABLE debian_distributions ADD COLUMN replication_site_id INTEGER; ``` 2. **Modify Model Relationships**: - Update the `DebianDistribution` model to include a `belongs_to :replication_site` association (if using an ORM like ActiveRecord): ```ruby class DebianDistribution < ApplicationRecord belongs_to :replication_site, class_name: 'GeoSite', optional: true end ``` 3. **Implement Replication Logic**: - Add methods to handle replication via cloud storage services (e.g., AWS S3, Google Cloud Storage): ```ruby class DebianDistribution < ApplicationRecord def replicate_blob!(target_site) # Use cloud storage replication APIs to sync blobs blob_url = generate_blob_url target_site.replicate_blob(blob_url) update(replication_status: 'success', replication_site_id: target_site.id) rescue StandardError => e update(replication_status: 'failed') raise "Replication failed: #{e.message}" end end ``` 4. **Verification**: - Add background jobs to verify replication status periodically: ```ruby class ReplicationVerificationJob < ApplicationJob def perform(distribution_id) distribution = DebianDistribution.find(distribution_id) if distribution.replication_status == 'pending' # Check status via cloud storage distribution.update(replication_status: 'success' || 'failed') end end end ``` 5. **Database Schema Update**: - Ensure the `debian_distributions` table includes the new columns and relationships (adjust syntax for your ORM). This fix ensures that Debian distributions are properly replicated across Geo sites, with clear status tracking and verification mechanisms.