| *** zaneb has quit IRC | 00:04 | |
| *** kumarmn has joined #openstack-tc | 00:19 | |
| *** kumarmn has quit IRC | 00:19 | |
| *** kumarmn has joined #openstack-tc | 00:19 | |
| *** kumarmn has quit IRC | 00:33 | |
| *** kumarmn has joined #openstack-tc | 00:34 | |
| *** kumarmn has quit IRC | 00:38 | |
| *** kumarmn has joined #openstack-tc | 00:46 | |
| *** kumarmn has quit IRC | 01:04 | |
| *** kumarmn has joined #openstack-tc | 01:04 | |
| *** kumarmn has quit IRC | 01:06 | |
| *** kumarmn has joined #openstack-tc | 01:06 | |
| *** Guest20946 is now known as mgagne | 01:10 | |
| *** mgagne has joined #openstack-tc | 01:10 | |
| *** ianychoi_ is now known as ianychoi | 01:26 | |
| *** kumarmn has quit IRC | 02:12 | |
| *** flwang1 has quit IRC | 02:21 | |
| *** flwang1 has joined #openstack-tc | 02:33 | |
| *** harlowja has quit IRC | 02:45 | |
| *** ykarel|away has joined #openstack-tc | 03:12 | |
| *** kumarmn has joined #openstack-tc | 03:55 | |
| *** kumarmn has quit IRC | 03:57 | |
| *** harlowja has joined #openstack-tc | 04:02 | |
| *** ykarel|away is now known as ykarel | 04:03 | |
| *** harlowja has quit IRC | 04:18 | |
| *** kumarmn has joined #openstack-tc | 05:58 | |
| *** kumarmn has quit IRC | 06:02 | |
| *** openstackstatus has quit IRC | 06:13 | |
| *** openstack has joined #openstack-tc | 06:15 | |
| *** ChanServ sets mode: +o openstack | 06:15 | |
| *** openstackstatus has joined #openstack-tc | 06:15 | |
| *** ChanServ sets mode: +v openstackstatus | 06:15 | |
| *** gcb has joined #openstack-tc | 06:46 | |
| *** lbragstad has joined #openstack-tc | 07:19 | |
| *** lbragstad has quit IRC | 07:28 | |
| *** gcb has quit IRC | 08:10 | |
| *** zaneb has joined #openstack-tc | 08:25 | |
| *** mriedem has joined #openstack-tc | 08:33 | |
| *** Guest87533 is now known as dansmith | 08:35 | |
| *** lbragstad has joined #openstack-tc | 08:36 | |
| *** bmace_ has quit IRC | 08:49 | |
| *** bmace_ has joined #openstack-tc | 09:05 | |
| *** zaneb has quit IRC | 09:06 | |
| *** zaneb has joined #openstack-tc | 09:11 | |
| *** zaneb has quit IRC | 09:16 | |
| *** gcb has joined #openstack-tc | 09:25 | |
| *** cdent has joined #openstack-tc | 09:30 | |
| *** rosmaita has joined #openstack-tc | 09:40 | |
| *** zaneb has joined #openstack-tc | 09:51 | |
| *** jpich has joined #openstack-tc | 09:51 | |
| *** ykarel has quit IRC | 10:06 | |
| *** ykarel has joined #openstack-tc | 10:06 | |
| *** lbragstad has quit IRC | 10:32 | |
| *** lbragstad has joined #openstack-tc | 10:41 | |
| *** gcb has quit IRC | 10:42 | |
| *** rosmaita has quit IRC | 10:47 | |
| *** gcb has joined #openstack-tc | 10:48 | |
| *** david-lyle has quit IRC | 10:57 | |
| *** ykarel is now known as ykarel|afk | 11:02 | |
| *** ianychoi_ has joined #openstack-tc | 11:06 | |
| openstackgerrit | Matt Riedemann proposed openstack/governance master: Add a resolution about stable branch EOL and "extended maintenance" https://review.openstack.org/548916 | 11:07 |
|---|---|---|
| mriedem | smcginnis: tonyb: cdent: fungi: persia: ^ | 11:07 |
| mriedem | ttx: ^ | 11:07 |
| mriedem | so let it be written, so let it be done | 11:07 |
| cdent | cool, noted, whereas | 11:07 |
| *** ianychoi has quit IRC | 11:08 | |
| ttx | thx! | 11:10 |
| *** ianychoi_ is now known as ianychoi | 11:10 | |
| *** david-lyle has joined #openstack-tc | 11:10 | |
| fungi | awesome | 11:15 |
| *** rosmaita has joined #openstack-tc | 11:31 | |
| *** zaneb has quit IRC | 11:48 | |
| *** ykarel|afk is now known as ykarel | 11:52 | |
| *** jpich has quit IRC | 11:59 | |
| *** ykarel is now known as ykarel|away | 11:59 | |
| *** ykarel|away has quit IRC | 12:04 | |
| *** david-lyle has quit IRC | 12:06 | |
| *** bmace_ has quit IRC | 12:12 | |
| *** lbragstad has quit IRC | 12:13 | |
| *** gcb has quit IRC | 12:15 | |
| *** rosmaita has quit IRC | 12:16 | |
| *** bmace_ has joined #openstack-tc | 12:16 | |
| *** zaneb has joined #openstack-tc | 12:18 | |
| *** bmace_ has quit IRC | 12:18 | |
| *** david-lyle has joined #openstack-tc | 12:19 | |
| *** ykarel|away has joined #openstack-tc | 12:21 | |
| *** mriedem has quit IRC | 12:23 | |
| *** zaneb has quit IRC | 12:24 | |
| *** cdent has quit IRC | 12:30 | |
| *** gcb has joined #openstack-tc | 12:36 | |
| *** ykarel|away has quit IRC | 12:37 | |
| *** gcb has quit IRC | 12:37 | |
| *** gcb has joined #openstack-tc | 12:41 | |
| *** lbragstad has joined #openstack-tc | 12:42 | |
| *** gcb has quit IRC | 12:48 | |
| *** gcb has joined #openstack-tc | 12:50 | |
| *** rosmaita has joined #openstack-tc | 12:57 | |
| *** kumarmn has joined #openstack-tc | 12:59 | |
| *** gcb has quit IRC | 13:01 | |
| *** kumarmn has quit IRC | 13:04 | |
| *** cdent has joined #openstack-tc | 13:20 | |
| *** rosmaita has quit IRC | 13:25 | |
| *** mriedem has joined #openstack-tc | 13:28 | |
| *** gcb has joined #openstack-tc | 13:30 | |
| *** lbragstad has quit IRC | 13:31 | |
| *** bmace has joined #openstack-tc | 13:39 | |
| *** kumarmn has joined #openstack-tc | 13:43 | |
| *** rosmaita has joined #openstack-tc | 13:44 | |
| *** mriedem has quit IRC | 13:46 | |
| *** mriedem has joined #openstack-tc | 13:52 | |
| *** gcb has quit IRC | 14:02 | |
| ttx | Hey, tc-members! Whoever is at Croke Park Hotel, we'll meet Friday at 9:30am as planned | 14:23 |
| cdent | ✔ | 14:23 |
| fungi | right on! | 14:24 |
| ttx | exact location tbd | 14:24 |
| fungi | that room is my favorite | 14:25 |
| dtroyer | I heard tbd was a bit cold this week…will bring a comforter from the room… | 14:26 |
| TheJulia | dtroyer: That is a great idea! | 14:43 |
| smcginnis | So everyone knocks on ttx's room at 9:30? | 14:56 |
| *** gcb has joined #openstack-tc | 15:03 | |
| *** diablo_rojo has joined #openstack-tc | 15:27 | |
| dtroyer | that's room 721 right? | 15:27 |
| smcginnis | Question for us to discuss at some point. The question came up in Cinder as to whether it is acceptable for an individual project to declare py2 support as deprecated, or if they would need to wait until we decide as a whole to deprecate it in OpenStack. | 15:29 |
| cdent | good question | 15:29 |
| cdent | kind of a badge of honor | 15:29 |
| *** gcb has quit IRC | 15:30 | |
| smcginnis | Maybe. :) | 15:30 |
| smcginnis | But really wondering if they would get scolded for not following the greater whole. | 15:30 |
| cdent | I would guess the critical factor is, as always, packagers. | 15:32 |
| dtroyer | It seems to me to be the next step in visible progress for the eventual migration. Indefinitely-long deprecation periods are usually not great, but at some point we need to take the next step. | 15:33 |
| cdent | But since we need to declare lack of support pretty soon anyway, I would think the "deprecated" (as in there but expect it to leave) is what all projects should be saying | 15:33 |
| cdent | jinxish | 15:33 |
| dhellmann | I was thinking the next step is to say "python 3 first" (assuming we're saying "python 2 first" now) | 15:34 |
| dhellmann | and to verify that we have all functional test and doc jobs moved over | 15:34 |
| smcginnis | It's an interesting point right now where we have some distros that do not fully support py3 and some soon to be released ones that will not support py2. | 15:34 |
| smcginnis | dhellmann: I agree with that plan. But in addition to that, wondering if it is acceptable if a given project just says "python 3 only." | 15:35 |
| dtroyer | dhellmann: yes, I think those can run parallel. I guess I'm saying projects that really are at the point where there is no more py3 migration work should go ahead and say so and default to py3 where possible | 15:36 |
| dtroyer | that an artificial hold-back on deprecation may not be useful | 15:36 |
| smcginnis | I guess still not clear. Not just saying they support py3 and recommending py3, but doing things like removing six compat code and saying YOU MUST rather than YOU CAN or YOU SHOULD. | 15:38 |
| dtroyer | ok, that is a bit harder | 15:39 |
| cdent | smcginnis: probalby too soon I would guess | 15:40 |
| cdent | sadly | 15:40 |
| dtroyer | I understood it to be starting the clock to enable that in the near future | 15:40 |
| cdent | yeah, that | 15:40 |
| dhellmann | dtroyer : right, I'm differentiating between "by default" and "only" | 15:40 |
| smcginnis | It would be starting that clock, but jumping out ahead of the rest. | 15:41 |
| dtroyer | unless we are planning/hoping for a py2 drop-dead reprieve, we have a hard deadline approaching to meet our deprecation timelines | 15:42 |
| dtroyer | I am ok starting those clocks as projects are ready and dealing with the exceptions. aside from distros dropping py2, do we have issues running mixed-mode here (cinder on py3, swift on p2 for example)? Also assuming no containers that would allow that easily | 15:44 |
| smcginnis | I do see more and more deployments opting for containerized deployments, so that really does make it a non-issue. | 15:45 |
| smcginnis | It's only an issue really if they want to install cinder and swift on the same host, but that's not a very good idea in the first place. | 15:45 |
| dmsimard | smcginnis: depends -- kolla has centos based containers for example which would not work (right now) if only py3 was available | 15:46 |
| dtroyer | right, just an example. but what prevents that besides the deployemnt tooling? | 15:46 |
| smcginnis | dtroyer: Can you clarify "that" in "what prevents that?" | 15:48 |
| dtroyer | sure. bettter example: is there anthing in the projects themselves that would prevent nova-compute running on py2 and cinder-volume running py3 on the same node at the same time? The issues are in deployment tooling/packaging, not in project deliverables? | 15:49 |
| smcginnis | I think maybe the right answer is first all projects MAY BE run py3 only, then once we've passed that bar projects are open to decide to change that to MUST BE. | 15:49 |
| smcginnis | dtroyer: Yes, I believe that is a correct statement. | 15:49 |
| dtroyer | I recall attempting to make this possible in DevStack and that we stopped short of that for $REASONS | 15:49 |
| dtroyer | not having to do with the projects themselves | 15:50 |
| smcginnis | One of the $REASONS I was given was swift not being able to be run py3, so that would mean dropping devstack support for swift. | 15:50 |
| dtroyer | and basically that's where I'm heading here. We hold back everyone until Swift and whoever else gets around to finishing py3 work? | 15:51 |
| smcginnis | I think we may need to. Unless we want to complicate things like running devstack deployments for testing. | 15:51 |
| smcginnis | Well, unless devstack can figure out a way to handle that. | 15:52 |
| dtroyer | I don't see running DevStack as a blocker to Cinder being able to say py2 is deprecated, starting the clock to when support is acutally removed | 15:52 |
| smcginnis | Oh, true. It could be declared deprecated, just not removed. | 15:52 |
| dtroyer | DevStack can figure that out, its just messier than it already is. The answer was going to be to put each service into a venv | 15:53 |
| smcginnis | Might be a good recommendation for all projects that are ready to start declaring it deprecated. | 15:53 |
| smcginnis | Then when swift and whatever else is ready, those projects that are ready and have deprecated it can start actually removing compat code. | 15:53 |
| dtroyer | right, that's what I am thinking too | 15:53 |
| smcginnis | That seems like a reasonable approach. | 15:54 |
| notmyname | what sort of timeframe is in your mind? | 15:54 |
| smcginnis | notmyname: You have any plans for next week? | 15:55 |
| smcginnis | ;) | 15:55 |
| EmilienM | ttx: ack, I'll try to join 9am | 15:55 |
| notmyname | that's ... a bit more aggressive than I was thinking ;-) | 15:55 |
| smcginnis | notmyname: Is the work scoped enough that declaring something like T would be reasonable? | 15:55 |
| dhellmann | from what I've seen swift is still blocked on some upstream issues | 15:56 |
| dhellmann | unfortunately I didn't have time to catch up with notmyname before the evacuation | 15:56 |
| smcginnis | And to be fair, if Cinder decides to call it deprecated now, we would not necessarily state when it would be expected to be removed. Just that, hey, this is going away in the nearish future so be ready for that. | 15:56 |
| notmyname | many of the problems are identified. they're not scoped, per se, but I don't think there are too many dependency issues | 15:57 |
| dhellmann | smcginnis : are every single one of cinder's jobs running py3 now, aside from the py2-specific ones? docs? functional tests? | 15:57 |
| smcginnis | I don't believe docs are at the moment. But that's kind of secondary in my mind. | 15:58 |
| notmyname | smcginnis: the T release is ... we're starting R now? so that's 18 months? | 15:58 |
| smcginnis | Unit tests and functional tests are running py3. | 15:58 |
| dhellmann | notmyname : the stuff associated with internals of the socket module caught my eye as potentially challenging to plan a "schedule" around fixing. Are those being actively worked on? Do we need help from upstream python to add APIs to replace the use of those internal bits? | 15:58 |
| dhellmann | smcginnis : at some point soon it's going to be hard for us to run py2 on a modern node in the gate, so it's pretty relevant | 15:58 |
| smcginnis | The biggest cocern at this point is third party CI is not running py3, so we are not sure if there are any hidden driver issues. | 15:58 |
| dhellmann | and we have doc tool dependencies we may not have looked at ensuring work with py3 | 15:59 |
| smcginnis | notmyname: Yeah, 18 months I think. | 15:59 |
| notmyname | dhellmann: I don't know. but TBH I hadn't ever really considered that an option | 15:59 |
| dhellmann | smcginnis : that's another good point | 15:59 |
| dtroyer | can we work backwards from when we (OpenStack) feels the drop-dead on py2 is? or do we plan to keep best-effort as long as the distros we use allow? | 15:59 |
| dhellmann | notmyname : it's worth discussing if there's a valid use case. it might be rejected, but there's no reason *assume* it will be | 16:00 |
| smcginnis | dhellmann: Yeah, docs tooling needs to be there, but I think we can run those under py2 and still expect users to deploy the services under py3. | 16:00 |
| dhellmann | "we were doing this and can't any more, how do we do that now?" | 16:00 |
| dhellmann | maybe there's an alternative, maybe we make one | 16:00 |
| dhellmann | smcginnis : distros that don't support py2 still want to package docs | 16:00 |
| smcginnis | dtroyer: Good idea. Looking at 2020 as a deadline, T might be a good target. | 16:00 |
| notmyname | "we were using internal variables before and you moved them!" isn't normally something that goes over well :-) | 16:00 |
| dhellmann | I mean, docs are going to be the least troublesome part of the port. let's just not ignore it. | 16:00 |
| dhellmann | notmyname : no, but if it's framed as "we need an API to do X and there isn't one" then it would be the start of a discussion | 16:01 |
| smcginnis | dhellmann: Yeah, definitely needs to be addressed. | 16:01 |
| notmyname | dhellmann: yeah, IIRC we ended up using them because we needed access to the actual socket object. it was to fix socket leaks in some conditions. so there may be valid justification | 16:02 |
| *** gcb has joined #openstack-tc | 16:02 | |
| dhellmann | notmyname : yep, that sounds like something we could build a good case around. I'm happy to help you find the people you need to talk to, as well. | 16:03 |
| dhellmann | I think one of the cases was adjusting some sort of buffer size or other behavior like that, and that feels like a missing API. If the other was a bug, that seems like an even easier thing to sell them on. | 16:04 |
| smcginnis | What if we rewrote parts in go? | 16:04 |
| * smcginnis ducks | 16:04 | |
| * dhellmann lobs a snowball at smcginnis | 16:04 | |
| dtroyer | smcginnis: what if that already happened? | 16:05 |
| notmyname | smcginnis: honestly, since we are/were planning on doing that, that is a valid thing :-) | 16:05 |
| dhellmann | sure; that's an alternative that lets us say we're not blocked on a python 3 port | 16:06 |
| smcginnis | This might be a more compelling reason for that to happen. | 16:07 |
| notmyname | smcginnis: just to be clear, are you suggesting that the T release has py3 support for everything (and py2 is depricated)? or that py2 is no longer used in the T release? and do you mean at the end of the T release or by the time the T release starts? | 16:10 |
| notmyname | I assume "py2 is depricated" means that py2 isn't run in the gate obs at all | 16:11 |
| dhellmann | hmm, I'm not sure I assume that, so we should definitely agree on exactly what we mean | 16:13 |
| smcginnis | notmyname: We may still want tests, but I was thinking T could be the point where all services are at least capable of being run with py3, and if a given project so chooses they would then be able to remove the six and all that compatibility code and at least declare for that project they only support py 3. | 16:13 |
| dhellmann | I'm much more concerned with the gaps identified in https://wiki.openstack.org/wiki/Python3#Python_3_Status_of_OpenStack_projects | 16:13 |
| dhellmann | T might be a good release to do that; there's still a chance it will be 8 months instead of 6 if we don't have a PTG a year from now | 16:14 |
| dhellmann | (pending a decision from the foundation and bod) | 16:14 |
| *** gcb has quit IRC | 16:15 | |
| notmyname | smcginnis: and that would be at the start or by the end of T? | 16:15 |
| smcginnis | By the end of T I think. | 16:15 |
| notmyname | ah, right. that's what dhellmann just said :-) | 16:16 |
| notmyname | "all openstack projects can at least run in both py2 and py3 by the end of the T release (expected roughly 18 months from now)" seems to be possible | 16:25 |
| *** gcb has joined #openstack-tc | 16:31 | |
| *** gcb has quit IRC | 16:37 | |
| dhellmann | we're pretty close to that already, so yeah | 16:41 |
| *** cdent has quit IRC | 16:46 | |
| ttx | ++ | 16:49 |
| *** rosmaita has quit IRC | 16:56 | |
| *** lbragstad has joined #openstack-tc | 16:57 | |
| *** mriedem has quit IRC | 17:02 | |
| *** diablo_rojo has quit IRC | 17:05 | |
| *** rosmaita has joined #openstack-tc | 17:06 | |
| fungi | let's rediscuss tomorrow, but sounds good to me | 17:09 |
| *** lbragstad has quit IRC | 17:10 | |
| *** lbragstad has joined #openstack-tc | 18:03 | |
| *** lbragstad has quit IRC | 18:06 | |
| *** lbragstad has joined #openstack-tc | 18:06 | |
| *** MatrixBridge has joined #openstack-tc | 18:11 | |
| *** MatrixBridge has left #openstack-tc | 18:11 | |
| *** gcb has joined #openstack-tc | 18:17 | |
| *** rosmaita has quit IRC | 18:24 | |
| *** lbragstad has quit IRC | 18:55 | |
| *** harlowja has joined #openstack-tc | 20:27 | |
| dhellmann | are we still planning to try to meet friday? | 21:21 |
| smcginnis | dhellmann: 9:30 tomorrow morning. Location TBD. | 21:46 |
| *** rosmaita has joined #openstack-tc | 22:25 | |
| *** kumarmn has quit IRC | 22:44 | |
| *** kumarmn has joined #openstack-tc | 23:03 | |
| *** kumarmn has quit IRC | 23:05 | |
| *** kumarmn has joined #openstack-tc | 23:05 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!