JEOS enablement in sumaform

[MalloZup]

So this is follow-up from #432 since it was too much risky to add JEOS clients and ubuntu ones.

what to do:

• find a mechanism to install qemu-agent on various SLES clients. ( qemu-guest agent is not provided by default)
• run the testsuite and see if all JEOS images are ok
• optionally do it for centos7

[Bischoff]

@rjmateus is this finished ? if yes we might close this card

[rjmateus]

I think It is @Bischoff

find a mechanism to install qemu-agent on various SLES clients. ( qemu-guest agent is not provided by default)

We have now support for JEOS. But the first item I'm not sure I understand it. @moio do you agree this can be closed?

[MalloZup]

we can close this issue.

https://github.com/uyuni-project/sumaform/blob/master/backend_modules/libvirt/base/main.tf#L14

The qemu-agent is needed because at that time, historically we used bridge mode. I think since you have the PR merged , you find out a mechanism or network setup to get the ips without the qemu-agent .
I"m closing this because it solved.

The qemu-agent step is only a detail which I think you have managed to solve. thx

[Bischoff]

The qemu-agent is needed because at that time, historically we used bridge mode. I think since you have the PR merged , you find out a mechanism or network setup to get the ips without the qemu-agent .

Well, we can get IPs without qemu-agent. But it's way slower. I am pretty sure we still use qemu-agent, even on JeOS. How this is exactly done is mistery to me, however.

I"m closing this because it solved.

The qemu-agent step is only a detail which I think you have managed to solve. thx

OK.

[gmoro]

Just a note here, qemu-guest-agent is installed by default in SLE15-SP2 onwards and in TW and Leap 15.2 as well

[Bischoff]

Also, I found that the agent is activated by the provider, not in sumaform (qemu_agent parameter of the libvirt domain). So there has never been anything to do at sumaform level

[MalloZup]

yeah I think it got fixed on sle15sp2, thx didn't know