fea60aa Bodhi: try and do critical path data generation in openshift

Authored and Committed by adamwill a year ago
    Bodhi: try and do critical path data generation in openshift
    
    The previous attempt to have staging Bodhi use grouped JSON
    critical path data didn't work because we did it in the backend
    (i.e. the composer), not the openshift pods where the web UI
    and the consumers run.
    
    We need at least the web UI and consumer pods to have the
    critpath data, as both those pods may create updates (Bodhi
    decides if the update is critical path at creation time). This
    attempts to handle that by having a daily openshift cron job
    that runs a simple container with the necessary packages in it,
    checks out the script, and runs it. It's run on a persistent
    storage volume which is also mounted by all the Bodhi pods in
    the place where Bodhi will look for the data.
    
    The cron job frequency is temporarily set to once an hour; this
    is so it will run soon after initial deployment. Once it has
    run once we can cut it back to once a day.
    
    Signed-off-by: Adam Williamson <awilliam@redhat.com>
    
        
  • Zuul
    success
    Jobs result is success
    a year ago