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

[dustymabe]

• no cloud agents: azure
  • investigated no cloud agents: azure #65
  • action items completed
    • Add mechanism for reporting instance health to cloud platforms afterburn#120
    • Support cloud-specific grub fragments #110
    • Ignore SR-IOV interfaces on Azure #115
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: aws no cloud agents: aws #66
  • investigated
  • action items completed
    • Add udev rules and scripts to support specific clouds #104
    • Support cloud-specific grub fragments #110
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: gcp no cloud agents: gcp #67
  • investigated
  • action items completed
    • Support base and user configs ignition-dracut#32 (for OS Login enablement)
    • Support cloud-specific grub fragments #110
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: openstack no cloud agents: openstack #68
  • investigated
  • action items completed
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: packet no cloud agents: packet #69
  • investigated
  • action items completed
    • Add mechanism for reporting instance health to cloud platforms afterburn#120
    • Support cloud-specific grub fragments #110
    • initramfs: support configuring network on DHCP-less platforms #111
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: vmware no cloud agents: vmware #70
  • investigated
  • action items completed
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: digitalocean no cloud agents: digitalocean #71
  • investigated
  • action items completed
    • initramfs: support configuring network on DHCP-less platforms #111
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: virtualbox no cloud agents: virtualbox #73
  • investigated
  • action items completed
  • working artifact can be hacked together
  • pipeline building artifact
• no cloud agents: qemu 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.