Hi,
Le 13/07/2016 à 21:17, Denis Makogon a écrit :
I have free capacity to work on porting code to Py3. So, if any PTL is
running out of team capacity i can help to work on project to enable Py3
support.
If you would like to help, you can try to run functional tests on
DevStack. Begin with pr
Hello to All.
I have free capacity to work on porting code to Py3. So, if any PTL is
running out of team capacity i can help to work on project to enable Py3
support.
Kind regards,
Denys Makogon
2016-07-06 13:01 GMT+03:00 Flavio Percoco :
> On 24/06/16 12:17 -0400, Sean Dague wrote:
>
>> On 0
On 24/06/16 12:17 -0400, Sean Dague wrote:
On 06/24/2016 11:48 AM, Doug Hellmann wrote:
Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200:
On 06/23/2016 11:21 PM, Clark Boylan wrote:
On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:
Excerpts from Thomas Goirand's messa
On 06/24/2016 12:13 PM, Amrith Kumar wrote:
>> -Original Message-
>> From: Doug Hellmann [mailto:d...@doughellmann.com]
>> Sent: Thursday, June 23, 2016 5:16 PM
>> To: openstack-dev
>> Subject: Re: [openstack-dev] [all] Status of the OpenStack p
On 27 June 2016 at 13:20, Jens Rosenboom wrote:
> 2016-06-22 9:18 GMT+02:00 Victor Stinner :
>> Hi,
>>
>> Current status: only 3 projects are not ported yet to Python 3:
>>
>> * nova (76% done)
>> * trove (42%)
>> * swift (0%)
>>
>>https://wiki.openstack.org/wiki/Python3
>
> How should differe
2016-06-22 9:18 GMT+02:00 Victor Stinner :
> Hi,
>
> Current status: only 3 projects are not ported yet to Python 3:
>
> * nova (76% done)
> * trove (42%)
> * swift (0%)
>
>https://wiki.openstack.org/wiki/Python3
How should differences between python3.4 and python3.5 be handled?
Ubuntu Xenial
On 06/24/2016 11:48 AM, Doug Hellmann wrote:
> Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200:
>> On 06/23/2016 11:21 PM, Clark Boylan wrote:
>>> On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:
Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:
>>
Excerpts from Daniel P. Berrange's message of 2016-06-24 09:25:35 +0100:
> On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote:
> > On 06/23/2016 06:11 PM, Doug Hellmann wrote:
> > > I'd like for the community to set a goal for Ocata to have Python
> > > 3 functional tests running for al
On 23/06/16 12:11 -0400, Doug Hellmann wrote:
Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200:
On 06/22/2016 09:18 AM, Victor Stinner wrote:
> Hi,
>
> Current status: only 3 projects are not ported yet to Python 3:
>
> * nova (76% done)
> * trove (42%)
> * swift (0%)
>
>h
Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200:
> On 06/23/2016 11:21 PM, Clark Boylan wrote:
> > On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:
> >> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:
> >>> On 06/23/2016 06:11 PM, Doug Hellmann wrote:
To: openstack-dev
>>> Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
>>>
>> [... snip ...]
>>>
>>> Let's see what PTLs have to say about planning, but I think if not
>>> Ocata then we'd want to set one for th
June 23, 2016 5:16 PM
> > > To: openstack-dev
> > > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python
> > > 3
> > >
> > [... snip ...]
> > >
> > > Let's see what PTLs have to say about planning, but I thin
Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +:
>
> > -Original Message-
> > From: Doug Hellmann [mailto:d...@doughellmann.com]
> > Sent: Thursday, June 23, 2016 5:16 PM
> > To: openstack-dev
> > Subject: Re: [openstack-dev] [all]
> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Thursday, June 23, 2016 5:16 PM
> To: openstack-dev
> Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
>
[... snip ...]
>
> Let's see what PTLs ha
On 06/23/2016 11:21 PM, Clark Boylan wrote:
On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:
Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:
On 06/23/2016 06:11 PM, Doug Hellmann wrote:
I'd like for the community to set a goal for Ocata to have Python
3 functional t
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote:
>
>
> Le 23/06/2016 02:42, Tony Breeds a écrit :
> > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
> > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
> > > > Do you think it looks like possible to have Nova ported
Le 22/06/2016 à 09:18, Victor Stinner a écrit :
Current status: only 3 projects are not ported yet to Python 3:
* nova (76% done)
* trove (42%)
* swift (0%)
If you want to help, please review my patches! I sent patches to these
projects.
Nova:
https://review.openstack.org/#/c/332686/
Swift
On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote:
> On 06/23/2016 06:11 PM, Doug Hellmann wrote:
> > I'd like for the community to set a goal for Ocata to have Python
> > 3 functional tests running for all projects.
> >
> > As Tony points out, it's a bit late to have this as a priori
Le 23/06/2016 à 23:04, Thomas Goirand a écrit :
Just think about it for a while. If we get Nova to work with Py3, and
everything else is working, including all functional tests in Tempest,
Hum, that's a long list of expectations :-)
then after Otaca, we could even start to *REMOVE* Py2 suppo
Le 23/06/2016 à 18:11, Doug Hellmann a écrit :
I'd like for the community to set a goal for Ocata to have Python
3 functional tests running for all projects.
We can already experiment functional tests right now ;-) I expect to get
many small issues in all projects, but it may take time to fix
+1 on the idea of running function tests to see the fallout. Right now
python-memcached is labelled as py3 compatible and in keystone our unit
tests pass, but I'm skeptical about its behavior in functional and tempest
tests.
On Jun 23, 2016 1:14 PM, "Sean Dague" wrote:
So, given that everything i
On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote:
> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:
> > On 06/23/2016 06:11 PM, Doug Hellmann wrote:
> > > I'd like for the community to set a goal for Ocata to have Python
> > > 3 functional tests running for all projects.
Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:
> On 06/23/2016 06:11 PM, Doug Hellmann wrote:
> > I'd like for the community to set a goal for Ocata to have Python
> > 3 functional tests running for all projects.
> >
> > As Tony points out, it's a bit late to have this as a p
On 06/23/2016 06:11 PM, Doug Hellmann wrote:
> I'd like for the community to set a goal for Ocata to have Python
> 3 functional tests running for all projects.
>
> As Tony points out, it's a bit late to have this as a priority for
> Newton, though work can and should continue. But given how close
On Thu, Jun 23, 2016 at 12:58:23PM -0400, Davanum Srinivas wrote:
+1 from me as well. I get questions on support for these often enough.
> +1 from me as well Doug! ("community to set a goal for Ocata to have Python
> 3 functional tests running for all projects.")
>
> -- Dims
>
> On Thu, Jun 23,
So, given that everything in base iaas is over besides Nova, and there
is some python 3 support in Devstack, before Newton is over one could
get a python 3 (except Nova) job running, and start seeing the fallout
of full stack testing. We could even prioritize functional changes in
Nova to get full
+1 from me as well Doug! ("community to set a goal for Ocata to have Python
3 functional tests running for all projects.")
-- Dims
On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmann wrote:
> Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200:
>> On 06/22/2016 09:18 AM, Victor Stinn
On 06/23/2016 11:11 AM, Doug Hellmann wrote:
> Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200:
>> On 06/22/2016 09:18 AM, Victor Stinner wrote:
>>> Hi,
>>>
>>> Current status: only 3 projects are not ported yet to Python 3:
>>>
>>> * nova (76% done)
>>> * trove (42%)
>>> * swif
Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200:
> On 06/22/2016 09:18 AM, Victor Stinner wrote:
> > Hi,
> >
> > Current status: only 3 projects are not ported yet to Python 3:
> >
> > * nova (76% done)
> > * trove (42%)
> > * swift (0%)
> >
> >https://wiki.openstack.org/
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote:
>
>
> Le 23/06/2016 02:42, Tony Breeds a écrit :
> > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
> > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
> > > > Do you think it looks like possible to have Nova ported
Le 23/06/2016 02:42, Tony Breeds a écrit :
On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
Do you think it looks like possible to have Nova ported to Py3 during
the Newton cycle?
It doesn't depend on me: I'm sending patches, and
On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
> Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
> > Do you think it looks like possible to have Nova ported to Py3 during
> > the Newton cycle?
>
> It doesn't depend on me: I'm sending patches, and then I have to wait for
> reviews.
Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
Do you think it looks like possible to have Nova ported to Py3 during
the Newton cycle?
It doesn't depend on me: I'm sending patches, and then I have to wait
for reviews. The question is more how to accelerate reviews.
Right now, I'm splitting
On 06/22/2016 09:18 AM, Victor Stinner wrote:
> Hi,
>
> Current status: only 3 projects are not ported yet to Python 3:
>
> * nova (76% done)
> * trove (42%)
> * swift (0%)
>
>https://wiki.openstack.org/wiki/Python3
>
> Number of projects already ported:
>
> * 19 Oslo Libraries
> * 4 Devel
Hi,
Current status: only 3 projects are not ported yet to Python 3:
* nova (76% done)
* trove (42%)
* swift (0%)
https://wiki.openstack.org/wiki/Python3
Number of projects already ported:
* 19 Oslo Libraries
* 4 Development Tools
* 22 OpenStack Clients
* 6 OpenStack Libraries (os-brick, ta
35 matches
Mail list logo
