Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-3205

Design proposal for how HAC and current quay.io architecture should integrate

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Critical Critical
    • quay-io
    • None
    • quay.io

      Need to review the technical architecture behind HAC and propose a design that allows quay.io to integrate with it.

      Functional requirements:

      1. Authentication (what is user's identity)
      2. Authorization (how is quay.io authorized to be part of HAC)
      3. Availability (How quay.io should host plugins for consumption by HAC)

       

      Non-Functional requirements:

      1. Performance (how do we make sure quay.io's web presence remains fast and usable)
      2. Scale (how do we make sure quay.io's web presence can sustain a potentially large number of simultaneous users now that we're in HAC)
      3. Resilience (how do we make sure that quay.io's web presence remains available at all times)

            syahmed@redhat.com Syed Ahmed
            bdettelb@redhat.com Bill Dettelback
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: