B@D v1.0 release: deployment.

Issue Background

• Once Gold Master declaration is communicated, B@D deployment is the next step of the release process.
• This task is blocked by #142

Issue description

Prepare and execute the deployment

• Create a new folder and subfolders in S3 service following the same structure as now updating the version number, in this case to 1.0
• Upload to S3 the box, metadata and artifacts
  • VM (aka box)
  • Sources archives compressed: CIP code, LAVAv2 source, KernelCi sources...
  • Hashes

Test the deployment

• Download the box.
• Test integrity of the box: hashes/size/name
• Test integrity of the signatures
• Test the box:
  • Execute a health check following the instructions.
  • Execute reference tests following the instructions step by step.

Track and communicate the outcome

• Add the links and hashes.
• Communicate to the team that the deployment has finished through mail.

Download folder tree

ciptesting¬
           b@d¬
               b@d_v1_0¬
                       sources
                       box

Links and hashes

• Link to the box:
• Links to every file (metadata/artifacts). List them below
  • The source for B@D:
  • kernelci-backend-config code:
  • kernel-backend code:
  • The code for building the kernel within kernelci:
  • kernelci-frontend code:
  • The LAVAv2 code:
• Hashes
  • B@D 1.0 box:
  • board-at-desk-single-dev:
  • kernelci-backend-config:
  • kernelci-backend:
  • kernelci-build:
  • kernelci-frontend:
  • lava-server:
• GPG Sigs
  • B@D 1.0 box:
  • board-at-desk-single-dev:
  • kernelci-backend-config:
  • kernelci-backend:
  • kernelci-build:
  • kernelci-frontend:
  • lava-server:
• GPG Public Key:

Acceptance criteria

• Prepare deployment
  • Link to the new folder
• Links and hashes added to this ticket