Implement Hyper-V support

[baude]

Implementing a new supported platform

During Development

Create PR's addressing the following:

• stream-metadata-go - Add Hyper-V artifact stream-metadata-go#55

  • Example PR
  • Add platform to the Media struct in release/release.go
  • Add supporting code for new platform to toStreamArch func in release/translate.go

• fedora-coreos-tracker - Add Hyper-V metadata #1425

  • Example PR
  • Update the metadata for the new platform

• coreos-assembler

  • Example PR
  • Implement required functionality to support new platform

• fedora-web

  • Example PR
  • Add platform to sites/static/js/coreos-download.js

• fedora-coreos-browser - HyperV added to browser list fedora-coreos-browser#45

  • Example PR
  • Add a list element for new platform in browser/index.html

• build pipeline - Add hyperv to default artifacts fedora-coreos-pipeline#815

  • Example PR
  • Add platform to the list found in jobs/build.Jenkinsfile for building the new artifact

• fedora-coreos-docs - Add documentation for Microsoft Hyper-V fedora-coreos-docs#545

  • Example PR
  • Add a provisioning-<platform>.adoc that walks through how to setup the new platform
  • Add an entry in the modules/ROOT/nav.adoc that points to new documentation

At Release

1. Merge metadata changes:

   • stream-metadata-go
   • fedora-coreos-tracker
   • fedora website
   • fedora-coreos-browser

2. Create and push signed tags with appropriate versions

   # Ensure gpg key for signing in github settings that is associated to redhat email.
   # Verify you are on the upstream repo's main branch.
   
   git status
   
   RELEASE_VER=vx.y.z
   # Replace 'x.y.z' with the appropriate numbers.
   
   git tag -s ${RELEASE_VER}
   # Give appropriate detail to tag, check previous tags with 'git show ${RELEASE_VER}'
   
   git push git@github.com:coreos/targeted-repo.git ${RELEASE_VER}
   # Navigate to the targeted-repo's tag section to ensure a valid signed tag is listed.
   # e.g. https://github.com/...repo/tags 
   

   1. Tag stream-metadata-go following the above steps. After tagging, ensure that dependabot has picked up latest version, and merged it into fedora-coreos-stream-generator && coreos-assembler.

      • These can be triggered manually by navigating to fedora-coreos-stream-generator's Dependabot and coreos-assembler's Dependabot respectively; then, clicking "Check for updates".
        • This might need to be done a few times, as the Dependabot might not pickup tag changes for a few attempts after initial tagging.

   2. Tag fedora-coreos-stream-generator following the above steps.

3. Merge the following changes:

   • coreos-assembler

4. Wait for updates made to coreos-assembler to be propagated to latest container

   • Download latest version of coreos-assembler container. Verify platform support functionality.

5. Merge changes for:

   • Build pipeline

6. Wait for new images to reach stable then merge documentation.

   • fedora-coreos-docs merged

[bgilbert]

Updates for the checklist template:

• Add steps for adding Ignition and Afterburn support
• Replace link to pipeline example PR
• Add platforms.yaml update

Applied in #1439.

[baude]

the fedora-web PR can be found -> https://pagure.io/fedora-web/websites/pull-request/282

[bgilbert]

We never decided in #1411 whether serial console is needed. I've added a checklist step to enable that, and we can skip the checkbox if we decide to just stick with graphical console.

[baude]

Note: serial console is not needed

[bgilbert]

Hyper-V images will be available in the next set of FCOS releases. I've gone ahead and merged the docs PR in advance.

[travier]

Thanks a lot work all the work here @baude @bgilbert @dustymabe

[bgilbert]

Looks like we missed adding hyperv to cmd-generate-release-meta. Fix in coreos/coreos-assembler#3546. The example coreos-assembler PR does do that, so no checklist update is necessary.