Open Stack

 ---- On Thu, 13 Apr 2023 12:08:46 -0700  Jeremy Stanley  wrote --- 
 > On 2023-04-12 09:46:32 +0200 (+0200), Sylvain Bauza wrote:
 > [...]
 > > by a next release, we will deprecate Hyper-V virt driver
 > [...]
 > 
 > With 2023.1 being a SLURP release, does this mean deprecated through
 > at least 2024.1 (the next SLURP release) and then potentially
 > dropped as soon as 2024.2 (the following non-SLURP release)?

The situation is little different here, and it is difficult to guarantee that we can follow normal
deprecation phase here.

Nova hyperV driver has hard dependencies on os-win, and if that goes away, then as long
as hyperV is working with an older version of os-win, it is good to keep HyperV as deprecated.
But once it starts failing and we cannot fix/backport fixes in os-win(if we end up retiring it), then
HyperV driver also needs to be removed. Another challenge is how we keep it testing. HyperV CI
is also going away with Cloudbase, so we do not have any tests running for this driver to know
whether it is working.

IMO, the next possible way can be:
1. merge the 'not tested and experimental' message in Nova [1]
2. backport this message to 2023.1 antelope (Initially, I was not in favour of backport but seeing the
situation, I now agree with Sean's idea of backport it to Antelope)
3. if we retire os-win in the 2023.2 release and no alternate implementation for the HyperV
driver, we remove HyperV driver support in the next release, 2024.1 (considering the 'not tested
and experimental' warning backported to the 2023.1 previous SLURP release).

-gmann

 > -- 
 > Jeremy Stanley
 >