<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 12 avr. 2023 à 08:56, Sean Mooney <<a href="mailto:smooney@redhat.com">smooney@redhat.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami <<a href="mailto:tkajinam@redhat.com" target="_blank">tkajinam@redhat.com</a>> wrote:<br>
><br>
><br>
><br>
> On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann <<a href="mailto:gmann@ghanshyammann.com" target="_blank">gmann@ghanshyammann.com</a>> wrote:<br>
>><br>
>> ---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---<br>
>> > Hi,<br>
>> ><br>
>> > Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:<br>
>> > > This probably causes a bit wider effect than just retiring the winstackers<br>
>> > > project.<br>
>> > ><br>
>> > > I see some projects (cinde, designate, glance and os-brick) depend on<br>
>> > > os-win which is under<br>
>> > > governance of winstackers and will be retired. Also, even some more<br>
>> > > projects (Neutron, os-vif,<br>
>> > > ovsdbapp, oslo.log, etc) supports windows without os-win.<br>
>> > ><br>
>> > > If we retire Winstackers, then is it reasonable to remove all<br>
>> > > implementations to support Windows ?<br>
>> ><br>
>> > That's very good question IMO. And, from Neutron perspective very important according to the removal of netifaces dependency - it would be much easier to remove it by removing all "windows" module from Neutron repo rather than refactoring it.<br>
>><br>
>> I agree. Thanks, Takashi for raising it.<br>
>><br>
>> If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal)<br>
>> need to be removed also. This is not a good situation for us as window support of OpenStack, if I am<br>
>> not wrong, Cloudbase is the only company maintaining and supporting the window support since starting.<br>
>> If there is any company having their customer based on windows then this is the right time to step up and help<br>
>> in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the<br>
>> alternate way in projects for window support (the one you mentioned has window support ).<br>
>><br>
> Please correct me if I'm wrong but what cloudbase has been maintaining is support for windows guest<br>
> instead of windows host.<br>
that is incorrect cloudbase provide the third party ci that test<br>
deploying openstack compute nodes on windows.<br>
that is the in/out of tree hyperV virt driver and the ovs on windows<br>
supprot used with os-vif and neuton ml2/ovs plugsins on windows.<br>
<br>
while we are happy to review fixes for hyper v /windows hows we now no<br>
longer have any way to test these changes in ci ro locally as we<br>
don't have a maintained way to deploy devstack on hyper v/windows hosts.<br>
<br>
out side fo the cloud base init package which is optional there is no<br>
depency on cloudbase to support windows guest.<br>
that is unaffected. but windows host support is now effectivly<br>
unmainated and untested.<br>
<br></blockquote><div><br></div><div>FWIW, the Nova project usually follows a procedure for virt drivers that are no longer tested by a 3rd party CI.</div><div>If no maintainers can continue to verify that a in-tree virt driver won't have any regression, then the Nova community deprecates the virt driver.</div><div><br></div><div>Here, that means that by a next release, we will deprecate Hyper-V virt driver unless someone tells us that they can help.</div><div>-Sylvain (which will create a specific ML thread for it)<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> My previous question was about Windows host support (whether we can remove<br>
> all implementations to run OpenStack services in windows hosts, instead of linux hosts) and guest support<br>
> can be kept now.<br>
><br>
>><br>
>> -gmann<br>
>><br>
>> ><br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann <a href="mailto:gmann@ghanshyammann.com" target="_blank">gmann@ghanshyammann.com</a>><br>
>> > > wrote:<br>
>> > ><br>
>> > > > Thanks, Lucian, for the updates and email link.<br>
>> > > ><br>
>> > > > As the next step, we will discuss it in TC and take the next action.<br>
>> > > ><br>
>> > > > -gmann<br>
>> > > ><br>
>> > > > ---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---<br>
>> > > > > Hi,<br>
>> > > > > Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can<br>
>> > > > no longer lead the Winstackers project. Since there weren’t any other<br>
>> > > > interested parties, I think there’s no other option but to retire the<br>
>> > > > project.<br>
>> > > > > [1]<br>
>> > > > <a href="https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044.html" rel="noreferrer" target="_blank">https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044.html</a><br>
>> > > > > Regards,Lucian Petrut<br>
>> > > > ><br>
>> > > > > On 22 Mar 2023, at 19:43, Ghanshyam Mann <a href="mailto:gmann@ghanshyammann.com" target="_blank">gmann@ghanshyammann.com</a>><br>
>> > > > wrote:<br>
>> > > > > Hi Lukas,<br>
>> > > > ><br>
>> > > > > I am reaching out to you as you were PTL for OpenStack Winstackers<br>
>> > > > project in the last cycle.<br>
>> > > > ><br>
>> > > > > There is no PTL candidate for the next cycle (2023.2), and it is on the<br>
>> > > > leaderless project list. Please<br>
>> > > > > check if you or anyone you know would like to lead this project.<br>
>> > > > ><br>
>> > > > > - <a href="https://etherpad.opendev.org/p/2023.2-leaderless" rel="noreferrer" target="_blank">https://etherpad.opendev.org/p/2023.2-leaderless</a><br>
>> > > > ><br>
>> > > > > Also, if anyone else would like to help leading this project, this is<br>
>> > > > time to let TC knows.<br>
>> > > > ><br>
>> > > > > -gmann<br>
>> > > > ><br>
>> > > > ><br>
>> > > ><br>
>> > > ><br>
>> > ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Slawek Kaplonski<br>
>> > Principal Software Engineer<br>
>> > Red Hat<br>
>><br>
<br>
<br>
</blockquote></div></div>