Exception request for VEP #0171 (PR #163)

[Martin Sivak]

Dear maintainers,

The testing of an external orchestrator and redfish implementation uncovered a gap in how guest reboots and boot order changes are handled.

I understand the late submission leaves this VEP as best effort, but I would like to ask for consideration of the functionally minimal change (as proposed).

Which VEP you wish to ask an exception for
VEP #171 PR #163: Recreate VMI on reboot from guest

The reason the VEP is not merged by now
Submitted only in Dec and the Christmas break and holidays got in the way.

What is left to do
As proposed only a toggle name must be agreed upon. If one of the alternatives are selected then again, just a name is needed.

The extra time needed
Up to 7 additional days, to stay on the safe side and wait for some relevant people to come back from holidays.

Thanks in advance

Martin Sivak
Red Hat, Ecosystem Engineering

[Itamar Holder]

Hey Martin,

It will indeed be handled on a best-effort basis.

Let's see if we can reach agreements in a few days.

+1 from my side.

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/8d742034-c276-459d-b713-78c60d6ea040n%40googlegroups.com.