<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>There is a need to distinguish between server side py26 support which is generally under the control of the service provider and py26 support on the client side. For a service provider to push all of their hypervisors and service machines to RHEL 7 is under their control but requiring all of their users to do the same is much more difficult.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Thus, I feel there should be different decisions and communication w.r.t. the time scales for deprecation of py26 on clients compared to the server side. A project may choose to make them together but equally some may choose to delay the mandatory client migration to py27 while requiring the server to move.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Tim<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Sahdev P Zala [mailto:spzala@us.ibm.com] <br><b>Sent:</b> 09 October 2015 20:42<br><b>To:</b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org><br><b>Subject:</b> Re: [openstack-dev] [Murano] py26 support in python-muranoclient<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><tt><span style='font-size:10.0pt'>> From: Clark Boylan <<a href="mailto:cboylan@sapwetik.org">cboylan@sapwetik.org</a>></span></tt><br><tt><span style='font-size:10.0pt'>> To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a></span></tt><br><tt><span style='font-size:10.0pt'>> Date: 10/09/2015 02:00 PM</span></tt><br><tt><span style='font-size:10.0pt'>> Subject: Re: [openstack-dev] [Murano] py26 support in python-muranoclient</span></tt><br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> </tt><br><tt>> </tt><br><tt>> On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote:</tt><br><tt>> > Serg, Jeremy,</tt><br><tt>> > </tt><br><tt>> > Thank you for your response, so the issue I ran into with my patch is the </tt><br><tt>> > gate job failing on python26.</tt><br><tt>> > You can see it here: </tt></span><a href="https://review.openstack.org/#/c/232271/"><tt><span style='font-size:10.0pt'>https://review.openstack.org/#/c/232271/</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> > </tt><br><tt>> > Serg suggested that we add 2.6 support to tosca-parser, which is fine</tt><br><tt>> > with </tt><br><tt>> > us.</tt><br><tt>> > But I got a bit confused after reading Jeremy's response.</tt><br><tt>> > It seems to me that the support will be going away, but there is no </tt><br><tt>> > timeline (and therefore no near-term plan?)</tt><br><tt>> > So, I'm hoping Jeremy can advise whether he also recommends the same </tt><br><tt>> > thing, or not.</tt><br><tt>> There is a timeline (though admittedly hard to find) at</tt><br><tt>> </tt></span><a href="https://etherpad.openstack.org/p/YVR-relmgt-stable-branch"><tt><span style='font-size:10.0pt'>https://etherpad.openstack.org/p/YVR-relmgt-stable-branch</span></tt></a><tt><span style='font-size:10.0pt'>which says</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Juno support would run through the end of November. Since Juno is the</tt><br><tt>> last release to support python2.6 we will remove python2.6 support from</tt><br><tt>> the test infrastructure at that time as well.</tt><br><tt>> </tt><br><tt>> I personally probably wouldn't bother with extra work to support</tt><br><tt>> python2.6, but that all depends on how much work it is and whether or</tt><br><tt>> not you find value in it. Ultimately it is up to you, just know that the</tt><br><tt>> Infrastructure team will stop hosting testing for python2.6 when Juno is</tt><br><tt>> EOLed.</tt><br><tt>> </tt><br><tt>> Hope this helps,</tt><br><tt>> Clark</tt><br></span><br><tt><span style='font-size:10.0pt'>Thanks Clark and Jeremy! This is very helpful. </span></tt><br><br><tt><span style='font-size:10.0pt'>Serg, now knowing that CI testing is not going to continue in few weeks and many other projects has dropped python 2.6 support or getting there, if Murano decides the same that would be great. If Murano team decide to continue the 2.6 support, we will need to enable support in tosca-parser as well. As you mentioned it may not be a lot of work for us and we are totally fine in making changes, but without automated tests it can be challenging in future. </span></tt><br><br><tt><span style='font-size:10.0pt'>Thanks! </span></tt><br><tt><span style='font-size:10.0pt'>Sahdev Zala</span></tt><br><br><br><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> __________________________________________________________________________</tt><br><tt>> OpenStack Development Mailing List (not for usage questions)</tt><br><tt>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></tt><br><tt>> </tt></span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><span style='font-size:10.0pt'>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> </tt></span><o:p></o:p></p></div></div></body></html>