<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Miriam Fixed";
panose-1:2 11 5 9 5 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I would be very sad to see this go, I actually run openSUSE in my home lab, though I am by no means an active user in production. Maybe this is something we can keep in tree but remove the tests for so it’s not consuming gate resources? This would be similar to the recent addition of Gentoo which has very limited, if any, gate testing at this time. If we’re still running into issues or if there are no known maintainers/users in production by B1 within the T cycle I’d be onboard with it being dropped.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Miriam Fixed"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Miriam Fixed"'>--<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Miriam Fixed"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Miriam Fixed"'>Kevin Carter<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Miriam Fixed"'>IRC: Cloudnull<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:mnaser@vexxhost.com">Mohammed Naser</a><br><b>Sent: </b>Friday, March 8, 2019 10:37 AM<br><b>To: </b><a href="mailto:openstack-discuss@lists.openstack.org">OpenStack Discuss</a><br><b>Subject: </b>[openstack-ansible] dropping suse support</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi everyone,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I've been trying to avoid writing this email for the longest time</p><p class=MsoNormal>ever. It's really painful to have to reach this state, but I think</p><p class=MsoNormal>we've hit a point where we can no longer maintain support for SUSE</p><p class=MsoNormal>within OpenStack Ansible.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Unfortunately, with the recent layoffs, the OSA team has taken a huge</p><p class=MsoNormal>hit in terms of contributors which means that there is far less</p><p class=MsoNormal>contributors within the project. This means that we have less</p><p class=MsoNormal>resources to go around and it forces us to focus on a more functional,</p><p class=MsoNormal>reliable and well tested set of scenarios.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Over the past few cycles, there has been effort to add SUSE support to</p><p class=MsoNormal>OpenStack Ansible, during the time that we had maintainers, it was</p><p class=MsoNormal>great and SUSE issues were being fixed promptly. In addition, due to</p><p class=MsoNormal>the larger team at the time, we found ourselves having some extra time</p><p class=MsoNormal>where we can help unbreak other gates. Jesse used to call this a</p><p class=MsoNormal>"labour of love", which I admired at the time and hoped we continue to</p><p class=MsoNormal>do as much as we can of.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>However, the lack of a committed maintainer for OpenSUSE has resulted</p><p class=MsoNormal>in constantly failing jobs[1][2] (which were moved to non-voting,</p><p class=MsoNormal>wasting CI resources as no one fixed them). In addition, it's causing</p><p class=MsoNormal>several gate blocks for a few times with no one really finding the</p><p class=MsoNormal>time to clean them up.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We are resource constrained at this point and we need the resource to</p><p class=MsoNormal>go towards making the small subset of supported features functional</p><p class=MsoNormal>(i.e. CentOS/Ubuntu). We struggle with that enough, and there seems</p><p class=MsoNormal>to be no deployers that are running SUSE in real life at the moment</p><p class=MsoNormal>based on bugs submitted.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>With that, I propose that we drop SUSE support this cycle. If anyone</p><p class=MsoNormal>would like to volunteer to maintain it, we can review that option, but</p><p class=MsoNormal>that would require a serious commitment as we've had maintainers step</p><p class=MsoNormal>off and it hurts the velocity of the project as no one can merge code</p><p class=MsoNormal>anymore.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>..Really wish I didn't have to write this email</p><p class=MsoNormal>Mohammed</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[1]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-functional-opensuse-150</p><p class=MsoNormal>[2]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-functional-opensuse-423</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>