Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
I just made a general remark regarding why migrating to 2.7 is profitable (I understood Bartek's question this way). The point about Red Hat guaranteeing security fixes to 2.6 is a good one. Also, it's true we don't use SSL for fuelclient so yes, if other OpenStack projects keep 2.6 we should stick to it also. P. On 01/14/2015 08:32 AM, Bartłomiej Piotrowski wrote: On 01/13/2015 11:16 PM, Tomasz Napierala wrote: On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Regards, I can hardly see it as a justification for maintaining yet another package on our own while Red Hat is supposed to provide backports of security fixes to python 2.6 until 2020. I wanted to hear exact use cases of 2.7 features that allow us to accomplish things easier than it is now with 2.6. As Doug already said, clients and Oslo libraries will maintain compatibility with 2.6. So what is the real gain? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
Guys, The question not about Do we want to drop 2.6 or not?. The question about Do we have resources to do that in this release cycle?. It may be not as easy at it seems and it obviously requires additional testing. - Igor On Wed, Jan 14, 2015 at 11:18 AM, Przemyslaw Kaminski pkamin...@mirantis.com wrote: I just made a general remark regarding why migrating to 2.7 is profitable (I understood Bartek's question this way). The point about Red Hat guaranteeing security fixes to 2.6 is a good one. Also, it's true we don't use SSL for fuelclient so yes, if other OpenStack projects keep 2.6 we should stick to it also. P. On 01/14/2015 08:32 AM, Bartłomiej Piotrowski wrote: On 01/13/2015 11:16 PM, Tomasz Napierala wrote: On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Regards, I can hardly see it as a justification for maintaining yet another package on our own while Red Hat is supposed to provide backports of security fixes to python 2.6 until 2020. I wanted to hear exact use cases of 2.7 features that allow us to accomplish things easier than it is now with 2.6. As Doug already said, clients and Oslo libraries will maintain compatibility with 2.6. So what is the real gain? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 14 Jan 2015, at 09:18, Przemyslaw Kaminski pkamin...@mirantis.com wrote: I just made a general remark regarding why migrating to 2.7 is profitable (I understood Bartek's question this way). The point about Red Hat guaranteeing security fixes to 2.6 is a good one. Also, it's true we don't use SSL for fuelclient so yes, if other OpenStack projects keep 2.6 we should stick to it also. I have problems understanding this „SSL” case. It was just one example, and I mean security support in general. For me it does not matter that RH provides security fixes. They do it, because with their enterprise policies they need to. We could use their fixces, but in our case it would also require supporting other distros (Ubuntu for now). Regards, -- Tomasz 'Zen' Napierala Sr. OpenStack Engineer tnapier...@mirantis.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 14 Jan 2015, at 08:50, Kamil Sambor ksam...@mirantis.com wrote: Tomasz we are not using ssl in our client so now we not gain anything from moving to 2.7 . I meant „security support” in terms of fixing security issues within Python itself. For 2.6.x line it’s over, as Przemek mentioned above: With the 2.6.9 release, and five years after its first release, the Python 2.6 series is now officially retired. All official maintenance for Python 2.6, including security patches, has ended. REgards, -- Tomasz 'Zen' Napierala Sr. OpenStack Engineer tnapier...@mirantis.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 01/13/2015 11:16 PM, Tomasz Napierala wrote: On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Distributors do support it as part of their offering. Shipping python 2.6 from source as is is indeed nothing you want to do, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 01/13/2015 11:16 PM, Tomasz Napierala wrote: On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Regards, I can hardly see it as a justification for maintaining yet another package on our own while Red Hat is supposed to provide backports of security fixes to python 2.6 until 2020. I wanted to hear exact use cases of 2.7 features that allow us to accomplish things easier than it is now with 2.6. As Doug already said, clients and Oslo libraries will maintain compatibility with 2.6. So what is the real gain? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
Tomasz we are not using ssl in our client so now we not gain anything from moving to 2.7 . Best regards, – Kamil S. On Wed, Jan 14, 2015 at 8:32 AM, Bartłomiej Piotrowski bpiotrow...@mirantis.com wrote: On 01/13/2015 11:16 PM, Tomasz Napierala wrote: On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Regards, I can hardly see it as a justification for maintaining yet another package on our own while Red Hat is supposed to provide backports of security fixes to python 2.6 until 2020. I wanted to hear exact use cases of 2.7 features that allow us to accomplish things easier than it is now with 2.6. As Doug already said, clients and Oslo libraries will maintain compatibility with 2.6. So what is the real gain? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 P. On 01/13/2015 08:39 AM, Bartłomiej Piotrowski wrote: On 01/12/2015 03:55 PM, Roman Prykhodchenko wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. While I come from the lands where being bleeding edge is preferred, I ask myself (as not programmer) one thing: what does 2.7 provide that you cannot easily achieve in 2.6? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 13 Jan 2015, at 10:51, Przemyslaw Kaminski pkamin...@mirantis.com wrote: For example https://www.python.org/download/releases/2.6.9/ All official maintenance for Python 2.6, including security patches, has ended. https://hg.python.org/cpython/raw-file/v2.7.9/Misc/NEWS Especially the SSL stuff is interesting http://bugs.python.org/issue22935 This looks like final word here. We cannot provide software, that has no security support. Regards, -- Tomasz 'Zen' Napierala Sr. OpenStack Engineer tnapier...@mirantis.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On Jan 12, 2015, at 9:55 AM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The intent was to keep 2.6 compatibility for client and Oslo libraries. Which libraries are you referring to that require at least 2.7? Doug The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On 01/12/2015 03:55 PM, Roman Prykhodchenko wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. While I come from the lands where being bleeding edge is preferred, I ask myself (as not programmer) one thing: what does 2.7 provide that you cannot easily achieve in 2.6? Regards, Bartłomiej __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
Hi Dmitry, Client uses REST API to interact with Fuel, how is Python version a factor? Fuel client is written in python it means it won't work on the master node with 2.6 python if you drop compatibility with it. What exactly is the use cases that requires a new client deployed on an old Fuel master node (or vice versa)? Fuel master node upgrade, we install newer client during the upgrade. It's not that hard ... It looks not so hard, but it should be well tested before it's merged, and it's risky because fuel client is installed on the host system, not into the container, hence in case if something goes wrong we cannot make automatic rollback. Thanks, On Mon, Jan 12, 2015 at 8:24 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: On Mon, Jan 12, 2015 at 9:10 AM, Evgeniy L e...@mirantis.com wrote: Agree with Igor, I think we cannot just drop compatibility for fuel client with 2.6 python, Hm, didn't Igor say in his email that we have to drop python 2.6 support? the reason is we have old master nodes which have 2.6 python, and the newer fuel client should work fine on these environments. Client uses REST API to interact with Fuel, how is Python version a factor? What exactly is the use cases that requires a new client deployed on an old Fuel master node (or vice versa)? Or we can try to install python 2.7 on the master during the upgrade. Lets do this. It's not that hard, see the link in an email from Ihar Hrachyshka on this thread. As for Nailgun I don't see any problems to use 2.7. Thanks, On Mon, Jan 12, 2015 at 7:32 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
You can get Python 2.7 via SCL: https://www.softwarecollections.org/en/scls/rhscl/python27/ On 01/12/2015 05:32 PM, Igor Kalnitsky wrote: Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
On Mon, Jan 12, 2015 at 9:10 AM, Evgeniy L e...@mirantis.com wrote: Agree with Igor, I think we cannot just drop compatibility for fuel client with 2.6 python, Hm, didn't Igor say in his email that we have to drop python 2.6 support? the reason is we have old master nodes which have 2.6 python, and the newer fuel client should work fine on these environments. Client uses REST API to interact with Fuel, how is Python version a factor? What exactly is the use cases that requires a new client deployed on an old Fuel master node (or vice versa)? Or we can try to install python 2.7 on the master during the upgrade. Lets do this. It's not that hard, see the link in an email from Ihar Hrachyshka on this thread. As for Nailgun I don't see any problems to use 2.7. Thanks, On Mon, Jan 12, 2015 at 7:32 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
Hi, Agree with Igor, I think we cannot just drop compatibility for fuel client with 2.6 python, the reason is we have old master nodes which have 2.6 python, and the newer fuel client should work fine on these environments. Or we can try to install python 2.7 on the master during the upgrade. As for Nailgun I don't see any problems to use 2.7. Thanks, On Mon, Jan 12, 2015 at 7:32 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Dropping Python-2.6 support
The python27 packages Ihar has linked do not conflict with the system python 2.6, so I don't see any problems with the rollback here. Is rollback the only concern for the master node upgrade use case? On Mon, Jan 12, 2015 at 9:51 AM, Evgeniy L e...@mirantis.com wrote: Hi Dmitry, Client uses REST API to interact with Fuel, how is Python version a factor? Fuel client is written in python it means it won't work on the master node with 2.6 python if you drop compatibility with it. What exactly is the use cases that requires a new client deployed on an old Fuel master node (or vice versa)? Fuel master node upgrade, we install newer client during the upgrade. It's not that hard ... It looks not so hard, but it should be well tested before it's merged, and it's risky because fuel client is installed on the host system, not into the container, hence in case if something goes wrong we cannot make automatic rollback. Thanks, On Mon, Jan 12, 2015 at 8:24 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: On Mon, Jan 12, 2015 at 9:10 AM, Evgeniy L e...@mirantis.com wrote: Agree with Igor, I think we cannot just drop compatibility for fuel client with 2.6 python, Hm, didn't Igor say in his email that we have to drop python 2.6 support? the reason is we have old master nodes which have 2.6 python, and the newer fuel client should work fine on these environments. Client uses REST API to interact with Fuel, how is Python version a factor? What exactly is the use cases that requires a new client deployed on an old Fuel master node (or vice versa)? Or we can try to install python 2.7 on the master during the upgrade. Lets do this. It's not that hard, see the link in an email from Ihar Hrachyshka on this thread. As for Nailgun I don't see any problems to use 2.7. Thanks, On Mon, Jan 12, 2015 at 7:32 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: Hi, Roman, Indeed, we have to go forward and drop python 2.6 support. That's how it supposed to be, but, unfortunately, it may not be as easy as it seems at first glance. Fuel Master is flying on top of Cent OS 6.5 which doesn't have python 2.7 at all. So we must either run master node on Cent OS 7 or build python2.7 for Cent OS 6.5. The first case, obviously, requires a lot of work, while the second one is not. But I may wrong, since I have no idea what dependencies python 2.7 requires and what we have in our repos. - Igor On Mon, Jan 12, 2015 at 4:55 PM, Roman Prykhodchenko m...@romcheg.me wrote: Folks, as it was planned and then announced at the OpenStack summit OpenStack services deprecated Python-2.6 support. At the moment several services and libraries are already only compatible with Python=2.7. And there is no common sense in trying to get back compatibility with Py2.6 because OpenStack infra does not run tests for that version of Python. The point of this email is that some components of Fuel, say, Nailgun and Fuel Client are still only tested with Python-2.6. Fuel Client in it’s turn is about to use OpenStack CI’s python-jobs for running unit tests. That means that in order to make it compatible with Py2.6 there is a need to run a separate python job in FuelCI. However, I believe that forcing the things being compatible with 2.6 when the rest of ecosystem decided not to go with it and when Py2.7 is already available in the main CentOS repo sounds like a battle with the common sense. So my proposal is to drop 2.6 support in Fuel-6.1. - romcheg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: