You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Daan Hoogland <da...@apache.org> on 2025/11/11 07:35:00 UTC
[DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013
(ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for
version numbers and generic spelling and logging commits only. Apart from
not having had any maintenance for more than a decade, I have not heard of
any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the
upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other
reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
RE: [DEPRECATE] retire UCS hypervisor plugin
Posted by Alex Mattioli <Al...@shapeblue.com>.
+1 on the idea and on what Rohit said
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>
Sent: 26 November 2025 14:21
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 for the proposed plan
Regards,
Nicolas Vazquez
From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, 25 November 2025 at 5:34 AM
To: dev <de...@cloudstack.apache.org>, users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013 (ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for version numbers and generic spelling and logging commits only. Apart from not having had any maintenance for more than a decade, I have not heard of any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
RE: [DEPRECATE] retire UCS hypervisor plugin
Posted by Alex Mattioli <Al...@shapeblue.com>.
+1 on the idea and on what Rohit said
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>
Sent: 26 November 2025 14:21
To: dev@cloudstack.apache.org; users@cloudstack.apache.org
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 for the proposed plan
Regards,
Nicolas Vazquez
From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, 25 November 2025 at 5:34 AM
To: dev <de...@cloudstack.apache.org>, users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013 (ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for version numbers and generic spelling and logging commits only. Apart from not having had any maintenance for more than a decade, I have not heard of any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
Re: [DEPRECATE] retire UCS hypervisor plugin
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
+1 for the proposed plan
Regards,
Nicolas Vazquez
From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, 25 November 2025 at 5:34 AM
To: dev <de...@cloudstack.apache.org>, users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013
(ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for
version numbers and generic spelling and logging commits only. Apart from
not having had any maintenance for more than a decade, I have not heard of
any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the
upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other
reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
Re: [DEPRECATE] retire UCS hypervisor plugin
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
+1 for the proposed plan
Regards,
Nicolas Vazquez
From: Rohit Yadav <ro...@shapeblue.com>
Date: Tuesday, 25 November 2025 at 5:34 AM
To: dev <de...@cloudstack.apache.org>, users@cloudstack.apache.org <us...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>
Subject: Re: [DEPRECATE] retire UCS hypervisor plugin
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013
(ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for
version numbers and generic spelling and logging commits only. Apart from
not having had any maintenance for more than a decade, I have not heard of
any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the
upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other
reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
Re: [DEPRECATE] retire UCS hypervisor plugin
Posted by Rohit Yadav <ro...@shapeblue.com>.
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013
(ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for
version numbers and generic spelling and logging commits only. Apart from
not having had any maintenance for more than a decade, I have not heard of
any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the
upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other
reason we shouldn't retire this plugin, please let it be known.
regards,
Daan
Re: [DEPRECATE] retire UCS hypervisor plugin
Posted by Rohit Yadav <ro...@shapeblue.com>.
+1 we should be able to deprecate them and eventually remove them. Many storage/hypervisor/network plugins were created as PoC and were only broadly supported without much depth. UCS was one of them, and it's likely it does not work and the s/w - h/w stack is deprecated / vendor EOL'd. We should be able to retire those, incl UCS.
Regards.
________________________________
From: Daan Hoogland <da...@apache.org>
Sent: Tuesday, November 11, 2025 13:05
To: dev <de...@cloudstack.apache.org>
Cc: PMC <pr...@cloudstack.apache.org>; users <us...@cloudstack.apache.org>
Subject: [DEPRECATE] retire UCS hypervisor plugin
devs,
The UCS hypervisor plugin has not had a functional commit since 7-8-2013
(ref 7cbd66f71cc244aca8ba7503e9f0d15b37355569) It has been upgraded for
version numbers and generic spelling and logging commits only. Apart from
not having had any maintenance for more than a decade, I have not heard of
any users of it ever.
I therefore propose we retire the plugin and mark it as deprecated in the
upcoming 20.3 and 22.1 releases to be totally removed in release 23.
If there are willing maintainers and/or users, or if there is any other
reason we shouldn't retire this plugin, please let it be known.
regards,
Daan