[ptl] Need PTL volunteer for OpenStack Winstackers
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project.
- https://etherpad.opendev.org/p/2023.2-leaderless
Also, if anyone else would like to help leading this project, this is time to let TC knows.
-gmann
Hi,
Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards, Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project.
- https://etherpad.opendev.org/p/2023.2-leaderless
Also, if anyone else would like to help leading this project, this is time to let TC knows.
-gmann
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044... Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com> wrote: Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project, this is time to let TC knows.
-gmann
This probably causes a bit wider effect than just retiring the winstackers project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can
no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project.
[1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com>
wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers
project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the
leaderless project list. Please
check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project, this is
time to let TC knows.
-gmann
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the winstackers project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can
no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project.
[1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com>
wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers
project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the
leaderless project list. Please
check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project, this is
time to let TC knows.
-gmann
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the winstackers project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal) need to be removed also. This is not a good situation for us as window support of OpenStack, if I am not wrong, Cloudbase is the only company maintaining and supporting the window support since starting. If there is any company having their customer based on windows then this is the right time to step up and help in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the alternate way in projects for window support (the one you mentioned has window support ).
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can
no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project.
[1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com>
wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers
project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the
leaderless project list. Please
check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project, this is
time to let TC knows.
-gmann
-- Slawek Kaplonski Principal Software Engineer Red Hat
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the
winstackers
project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal) need to be removed also. This is not a good situation for us as window support of OpenStack, if I am not wrong, Cloudbase is the only company maintaining and supporting the window support since starting. If there is any company having their customer based on windows then this is the right time to step up and help in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the alternate way in projects for window support (the one you mentioned has window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining is
support for windows *guest* instead of windows *host. *My previous question was about Windows host support (whether we can remove all implementations to run OpenStack services in windows hosts, instead of linux hosts) and guest support can be kept now.
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann
gmann@ghanshyammann.com>
wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase
Solutions can
no longer lead the Winstackers project. Since there weren’t any
other
interested parties, I think there’s no other option but to retire
the
project.
[1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com
wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack
Winstackers
project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is
on the
leaderless project list. Please
check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project,
this is
time to let TC knows.
-gmann
-- Slawek Kaplonski Principal Software Engineer Red Hat
On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami tkajinam@redhat.com wrote:
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the winstackers project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal) need to be removed also. This is not a good situation for us as window support of OpenStack, if I am not wrong, Cloudbase is the only company maintaining and supporting the window support since starting. If there is any company having their customer based on windows then this is the right time to step up and help in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the alternate way in projects for window support (the one you mentioned has window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining is support for windows guest instead of windows host.
that is incorrect cloudbase provide the third party ci that test deploying openstack compute nodes on windows. that is the in/out of tree hyperV virt driver and the ovs on windows supprot used with os-vif and neuton ml2/ovs plugsins on windows.
while we are happy to review fixes for hyper v /windows hows we now no longer have any way to test these changes in ci ro locally as we don't have a maintained way to deploy devstack on hyper v/windows hosts.
out side fo the cloud base init package which is optional there is no depency on cloudbase to support windows guest. that is unaffected. but windows host support is now effectivly unmainated and untested.
My previous question was about Windows host support (whether we can remove all implementations to run OpenStack services in windows hosts, instead of linux hosts) and guest support can be kept now.
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote ---
Hi, Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can
no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project.
[1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
Regards,Lucian Petrut
On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com>
wrote:
Hi Lukas,
I am reaching out to you as you were PTL for OpenStack Winstackers
project in the last cycle.
There is no PTL candidate for the next cycle (2023.2), and it is on the
leaderless project list. Please
check if you or anyone you know would like to lead this project.
Also, if anyone else would like to help leading this project, this is
time to let TC knows.
-gmann
-- Slawek Kaplonski Principal Software Engineer Red Hat
Hi,
Dnia środa, 12 kwietnia 2023 08:50:51 CEST Sean Mooney pisze:
On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami tkajinam@redhat.com wrote:
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the winstackers project.
I see some projects (cinde, designate, glance and os-brick) depend on os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal) need to be removed also. This is not a good situation for us as window support of OpenStack, if I am not wrong, Cloudbase is the only company maintaining and supporting the window support since starting. If there is any company having their customer based on windows then this is the right time to step up and help in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the alternate way in projects for window support (the one you mentioned has window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining is support for windows guest instead of windows host.
that is incorrect cloudbase provide the third party ci that test deploying openstack compute nodes on windows. that is the in/out of tree hyperV virt driver and the ovs on windows supprot used with os-vif and neuton ml2/ovs plugsins on windows.
Exactly. In neutron we have ovs-agent related code to run it on windows host, like e.g.: https://github.com/openstack/neutron/tree/master/neutron/agent/windows
while we are happy to review fixes for hyper v /windows hows we now no longer have any way to test these changes in ci ro locally as we don't have a maintained way to deploy devstack on hyper v/windows hosts.
out side fo the cloud base init package which is optional there is no depency on cloudbase to support windows guest. that is unaffected. but windows host support is now effectivly unmainated and untested.
My previous question was about Windows host support (whether we can remove all implementations to run OpenStack services in windows hosts, instead of linux hosts) and guest support can be kept now.
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote --- > Hi, > Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can no longer lead the Winstackers project. Since there weren’t any other interested parties, I think there’s no other option but to retire the project. > [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044... > Regards,Lucian Petrut > > On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com> wrote: > Hi Lukas, > > I am reaching out to you as you were PTL for OpenStack Winstackers project in the last cycle. > > There is no PTL candidate for the next cycle (2023.2), and it is on the leaderless project list. Please > check if you or anyone you know would like to lead this project. > > - https://etherpad.opendev.org/p/2023.2-leaderless > > Also, if anyone else would like to help leading this project, this is time to let TC knows. > > -gmann > >
-- Slawek Kaplonski Principal Software Engineer Red Hat
On Wed, Apr 12, 2023 at 3:51 PM Sean Mooney smooney@redhat.com wrote:
On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami tkajinam@redhat.com wrote:
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com
wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the
winstackers
project.
I see some projects (cinde, designate, glance and os-brick) depend
on
os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any
functionality (user-facing or internal)
need to be removed also. This is not a good situation for us as window
support of OpenStack, if I am
not wrong, Cloudbase is the only company maintaining and supporting the
window support since starting.
If there is any company having their customer based on windows then
this is the right time to step up and help
in maintaining this project. Otherway (based on project wants and have
the bandwidth) is to implement the
alternate way in projects for window support (the one you mentioned has
window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining
is support for windows guest
instead of windows host.
that is incorrect cloudbase provide the third party ci that test deploying openstack compute nodes on windows. that is the in/out of tree hyperV virt driver and the ovs on windows supprot used with os-vif and neuton ml2/ovs plugsins on windows.
Thanks.
I was confused by some conversation logs in #openstack-tc and it was indeed mentioned cloudbase no longer maintains Winstackers (= Windows host support) earlier in this thread.
while we are happy to review fixes for hyper v /windows hows we now no longer have any way to test these changes in ci ro locally as we don't have a maintained way to deploy devstack on hyper v/windows hosts.
out side fo the cloud base init package which is optional there is no depency on cloudbase to support windows guest. that is unaffected. but windows host support is now effectivly unmainated and untested.
I completely agree with this statement.
My previous question was about Windows host support (whether we can
remove
all implementations to run OpenStack services in windows hosts, instead
of linux hosts) and guest support
can be kept now.
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann
gmann@ghanshyammann.com>
wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next
action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote
> Hi, > Thanks for reaching out. As mentioned here [1], Cloudbase
Solutions can
no longer lead the Winstackers project. Since there weren’t any
other
interested parties, I think there’s no other option but to
retire the
project. > [1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
> Regards,Lucian Petrut > > On 22 Mar 2023, at 19:43, Ghanshyam Mann
gmann@ghanshyammann.com>
wrote: > Hi Lukas, > > I am reaching out to you as you were PTL for OpenStack
Winstackers
project in the last cycle. > > There is no PTL candidate for the next cycle (2023.2), and it
is on the
leaderless project list. Please > check if you or anyone you know would like to lead this
project.
> > - https://etherpad.opendev.org/p/2023.2-leaderless > > Also, if anyone else would like to help leading this project,
this is
time to let TC knows. > > -gmann > >
-- Slawek Kaplonski Principal Software Engineer Red Hat
---- On Wed, 12 Apr 2023 00:09:51 -0700 Takashi Kajinami wrote ---
On Wed, Apr 12, 2023 at 3:51 PM Sean Mooney smooney@redhat.com> wrote: On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami tkajinam@redhat.com> wrote:
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote --- > Hi, > > Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze: > > This probably causes a bit wider effect than just retiring the winstackers > > project. > > > > I see some projects (cinde, designate, glance and os-brick) depend on > > os-win which is under > > governance of winstackers and will be retired. Also, even some more > > projects (Neutron, os-vif, > > ovsdbapp, oslo.log, etc) supports windows without os-win. > > > > If we retire Winstackers, then is it reasonable to remove all > > implementations to support Windows ? > > 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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any functionality (user-facing or internal) need to be removed also. This is not a good situation for us as window support of OpenStack, if I am not wrong, Cloudbase is the only company maintaining and supporting the window support since starting. If there is any company having their customer based on windows then this is the right time to step up and help in maintaining this project. Otherway (based on project wants and have the bandwidth) is to implement the alternate way in projects for window support (the one you mentioned has window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining is support for windows guest instead of windows host.
that is incorrect cloudbase provide the third party ci that test deploying openstack compute nodes on windows. that is the in/out of tree hyperV virt driver and the ovs on windows supprot used with os-vif and neuton ml2/ovs plugsins on windows.
Thanks. I was confused by some conversation logs in #openstack-tc and it was indeedmentioned cloudbase no longer maintains Winstackers (= Windows host support)earlier in this thread.
while we are happy to review fixes for hyper v /windows hows we now no longer have any way to test these changes in ci ro locally as we don't have a maintained way to deploy devstack on hyper v/windows hosts.
out side fo the cloud base init package which is optional there is no depency on cloudbase to support windows guest. that is unaffected. but windows host support is now effectivly unmainated and untested.
I completely agree with this statement.
Yes. AFAIK, it was only Cloudbase who maintained code as well as 3rd party CI for Nova HyperV driver.
-gmann
My previous question was about Windows host support (whether we can remove all implementations to run OpenStack services in windows hosts, instead of linux hosts) and guest support can be kept now.
-gmann
> > > > > > > > > On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann gmann@ghanshyammann.com> > > wrote: > > > > > Thanks, Lucian, for the updates and email link. > > > > > > As the next step, we will discuss it in TC and take the next action. > > > > > > -gmann > > > > > > ---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote --- > > > > Hi, > > > > Thanks for reaching out. As mentioned here [1], Cloudbase Solutions can > > > no longer lead the Winstackers project. Since there weren’t any other > > > interested parties, I think there’s no other option but to retire the > > > project. > > > > [1] > > > https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044... > > > > Regards,Lucian Petrut > > > > > > > > On 22 Mar 2023, at 19:43, Ghanshyam Mann gmann@ghanshyammann.com> > > > wrote: > > > > Hi Lukas, > > > > > > > > I am reaching out to you as you were PTL for OpenStack Winstackers > > > project in the last cycle. > > > > > > > > There is no PTL candidate for the next cycle (2023.2), and it is on the > > > leaderless project list. Please > > > > check if you or anyone you know would like to lead this project. > > > > > > > > - https://etherpad.opendev.org/p/2023.2-leaderless > > > > > > > > Also, if anyone else would like to help leading this project, this is > > > time to let TC knows. > > > > > > > > -gmann > > > > > > > > > > > > > > > > > > > -- > Slawek Kaplonski > Principal Software Engineer > Red Hat
Le mer. 12 avr. 2023 à 08:56, Sean Mooney smooney@redhat.com a écrit :
On Wed, Apr 12, 2023 at 2:42 AM Takashi Kajinami tkajinam@redhat.com wrote:
On Wed, Apr 12, 2023 at 2:28 AM Ghanshyam Mann gmann@ghanshyammann.com
wrote:
---- On Tue, 11 Apr 2023 02:01:38 -0700 Slawek Kaplonski wrote ---
Hi,
Dnia wtorek, 11 kwietnia 2023 10:49:44 CEST Takashi Kajinami pisze:
This probably causes a bit wider effect than just retiring the
winstackers
project.
I see some projects (cinde, designate, glance and os-brick) depend
on
os-win which is under governance of winstackers and will be retired. Also, even some more projects (Neutron, os-vif, ovsdbapp, oslo.log, etc) supports windows without os-win.
If we retire Winstackers, then is it reasonable to remove all implementations to support Windows ?
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.
I agree. Thanks, Takashi for raising it.
If we retire Winstackers then yes, it means all dependencies of any
functionality (user-facing or internal)
need to be removed also. This is not a good situation for us as window
support of OpenStack, if I am
not wrong, Cloudbase is the only company maintaining and supporting the
window support since starting.
If there is any company having their customer based on windows then
this is the right time to step up and help
in maintaining this project. Otherway (based on project wants and have
the bandwidth) is to implement the
alternate way in projects for window support (the one you mentioned has
window support ).
Please correct me if I'm wrong but what cloudbase has been maintaining
is support for windows guest
instead of windows host.
that is incorrect cloudbase provide the third party ci that test deploying openstack compute nodes on windows. that is the in/out of tree hyperV virt driver and the ovs on windows supprot used with os-vif and neuton ml2/ovs plugsins on windows.
while we are happy to review fixes for hyper v /windows hows we now no longer have any way to test these changes in ci ro locally as we don't have a maintained way to deploy devstack on hyper v/windows hosts.
out side fo the cloud base init package which is optional there is no depency on cloudbase to support windows guest. that is unaffected. but windows host support is now effectivly unmainated and untested.
FWIW, the Nova project usually follows a procedure for virt drivers that are no longer tested by a 3rd party CI. 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.
Here, that means that by a next release, we will deprecate Hyper-V virt driver unless someone tells us that they can help. -Sylvain (which will create a specific ML thread for it)
My previous question was about Windows host support (whether we can remove
all implementations to run OpenStack services in windows hosts, instead
of linux hosts) and guest support
can be kept now.
-gmann
On Fri, Mar 31, 2023 at 6:29 AM Ghanshyam Mann
gmann@ghanshyammann.com>
wrote:
Thanks, Lucian, for the updates and email link.
As the next step, we will discuss it in TC and take the next
action.
-gmann
---- On Thu, 30 Mar 2023 00:11:38 -0700 Lucian Petrut wrote
> Hi, > Thanks for reaching out. As mentioned here [1], Cloudbase
Solutions can
no longer lead the Winstackers project. Since there weren’t any
other
interested parties, I think there’s no other option but to
retire the
project. > [1]
https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044...
> Regards,Lucian Petrut > > On 22 Mar 2023, at 19:43, Ghanshyam Mann
gmann@ghanshyammann.com>
wrote: > Hi Lukas, > > I am reaching out to you as you were PTL for OpenStack
Winstackers
project in the last cycle. > > There is no PTL candidate for the next cycle (2023.2), and it
is on the
leaderless project list. Please > check if you or anyone you know would like to lead this
project.
> > - https://etherpad.opendev.org/p/2023.2-leaderless > > Also, if anyone else would like to help leading this project,
this is
time to let TC knows. > > -gmann > >
-- Slawek Kaplonski Principal Software Engineer Red Hat
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)?
---- 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
Le jeu. 13 avr. 2023 à 21:15, Jeremy Stanley fungi@yuggoth.org a écrit :
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)?
For the moment, we don't have yet agreed on a specific plan, but we'll discuss this during the next Nova meeting on Tuesday 1600UTC. -Sylvain
-- Jeremy Stanley
participants (7)
-
Ghanshyam Mann
-
Jeremy Stanley
-
Lucian Petrut
-
Sean Mooney
-
Slawek Kaplonski
-
Sylvain Bauza
-
Takashi Kajinami