tracker: 'cloud'/'no cloud agents' work

[dustymabe]

• [x] no cloud agents: azure
  • [x] ~investigated #65~
  • [x] action items completed
    • [x] https://github.com/coreos/coreos-metadata/issues/120
    • [x] https://github.com/coreos/fedora-coreos-tracker/issues/110
    • [x] #115
  • [x] working artifact can be hacked together
  • [x] pipeline building artifact
• [ ] no cloud agents: aws #66
  • [x] ~investigated~
  • [ ] action items completed
    • [ ] #104
    • [x] https://github.com/coreos/fedora-coreos-tracker/issues/110
  • [x] working artifact can be hacked together
  • [x] pipeline building artifact
• [x] no cloud agents: gcp #67
  • [x] investigated
  • [x] action items completed
    • [x] https://github.com/coreos/ignition-dracut/issues/32 (for OS Login enablement)
    • [x] https://github.com/coreos/fedora-coreos-tracker/issues/110
  • [x] working artifact can be hacked together
  • [x] pipeline building artifact
• [x] no cloud agents: openstack #68
  • [x] investigated
  • [x] action items completed
  • [x] working artifact can be hacked together
  • [x] pipeline building artifact
• [ ] no cloud agents: packet #69
  • [x] investigated
  • [ ] action items completed
    • [ ] https://github.com/coreos/coreos-metadata/issues/120
    • [x] https://github.com/coreos/fedora-coreos-tracker/issues/110
    • [ ] https://github.com/coreos/fedora-coreos-tracker/issues/111
  • [ ] working artifact can be hacked together
  • [ ] pipeline building artifact
• [ ] no cloud agents: vmware #70
  • [ ] investigated
  • [ ] action items completed
  • [ ] working artifact can be hacked together
  • [ ] pipeline building artifact
• [ ] no cloud agents: digitalocean #71
  • [x] investigated
  • [ ] action items completed
    • [ ] https://github.com/coreos/fedora-coreos-tracker/issues/111
  • [ ] working artifact can be hacked together
  • [ ] pipeline building artifact
• [x] no cloud agents: virtualbox #73
  • [x] investigated
  • [x] action items completed
  • [x] working artifact can be hacked together
  • [x] pipeline building artifact
• [ ] no cloud agents: qemu #74
  • [ ] investigated
  • [ ] action items completed
  • [ ] working artifact can be hacked together
  • [ ] pipeline building artifact

[bgilbert]

What is the criterion for checking off a platform?

• Having a plan?
• Implementing the necessary pieces?
• Producing build artifacts for that platform?
• Having the pipeline upload images to that platform?

[dustymabe]

What is the criterion for checking off a platform?

added sub checkboxes

[Aketzu]

I would like to have check for Xen (and specifically paid XenServer). There is no general cloud-init support so installation is manual. With Atomic I added custom Kickstart URL which then downloaded xe-guest-utilities and queried VM name through xen interface.

[bgilbert]

@Aketzu Xen isn't currently in our list of target platforms, but it's worth discussing further. Could you open a new bug?

[dlabreu]

As a user of the oVIrt Project and Red Hat Virtualization, I find of great value have the guest agent on the Virtual machines, so I can sort to information right from the Engine Dashboard such as mentioned in here (Link) https://www.ovirt.org/develop/internal/guest-agent/guest-agent.html Some of the enterprises still run workloads on top of on-prem virtualization tools and as a hybrid approach I am certain that have the guest agents on the virtuals would add value instead of subtracting it.

If the decision is to ship without the agents I assume a good compromise would be to provide a very simple way to inject the agents on the virtual machines and also provided the project with nice documentation about. I am new to it but would be more than happy to work on the doc for the oVirt guest agent as I am a user of the technology.