Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-1576

Fedora CoreOS Garbage collection policy for OS releases

XMLWordPrintable

    • Garbage collection policy for OS releases
    • Upstream
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • 13% To Do, 0% In Progress, 88% Done
    • Sprint 246 - OSIntegration
    • 0
    • 0.000

      [390966925] Upstream Reporter: Benjamin Gilbert
      Upstream issue status: Open
      Upstream description:

      Each Fedora CoreOS release will produce several artifacts:

      • An ostree
      • Image artifacts for each platform
      • Cloud images, on those platforms where we upload image artifacts ourselves

      It will also depend on artifacts produced elsewhere:

      • Binary packages
      • debuginfo packages (not included in an image, but needed for debugging)

      We should have a clear garbage collection policy for each of these.

      1. Will koji delete packages included in previous FCOS releases?
      1. How long are ostrees retained for old releases?
      1. How long are old image artifacts retained?
      1. How long are old cloud images retained?

      The answers may have consequences for release metadata (#98). I'm in favor of retaining everything forever, but there's obviously a storage cost.

        1. Container Linux

      The Container Linux GC policy is slightly inconsistent:

      • Binpkgs, image artifacts, and update payloads live forever
      • AWS and Azure images live forever
      • GCE images are eventually garbage-collected

              gurssing@redhat.com Gursewak Singh
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: