Can the jobserver also handle image serving requests?

[jhujasonw]

Investigate if the job server can be used as the "image server" so that it can handle serving image sync requests.

[jhujasonw]

Some quick notes:

• Job server as secondary sync

• PLUGIN: Job module: image-sync

  • Params: images_to_sync, image_source_server (null or the id of a job server with the updated image.)
  • Target_server: jobserver to run on
  • MPCC creates a new image-sync job for every job server registered with image-sync

• PLUGIN: Secondary server sets up a simple http server to serve images to pxelinux

  • The job server handling image-update jobs must also run the first image hosting server. MPCC will point to it via 302 from /images/image_name
  • MPCC does not hold the images itself.

[jhujasonw]

The answer to the question this ticket seems to be a YES with the following:

• iPXE used to load initrd
• jobserver handling image generation is first jobserver registered.
• if a image rebuild is requested, the version change and register of the initial job server must happen so that the image always has at least 1 job server present.
• jobservers running image-sync handle the 302 from MPCC correctly as well to sync the image.
• jobservers running image-sync jobmodule may not need tracking jobs created, and target__server may not be needed. They can check their version against the version reported to MPCC or make sure they are in the list of servers for that image/version.