| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-01-09 | |||
| 16:03:39 | sshnaidm | I just want to be sure we're all on the same page | |
| 16:04:17 | sshnaidm | I think we stopped on moving modules to ansible SIG repo, linking with new names in Ansible repo | |
| 16:04:42 | sshnaidm | and redesigning if need with kind deprecation notices | |
| 16:04:49 | gtema | right | |
| 16:04:51 | sshnaidm | is it correct ^ | |
| 16:05:13 | sshnaidm | any comments, objections ? | |
| 16:05:52 | sshnaidm | ok, let's move on | |
| 16:06:07 | sshnaidm | about freezing current modules in Ansible github repo | |
| 16:06:42 | sshnaidm | I notices we still have patches merging: https://github.com/ansible/ansible/commits/devel/lib/ansible/modules/cloud/openstack | |
| 16:07:17 | sshnaidm | so, do we have a good way to make sure we really freeze them after a moving? | |
| 16:07:35 | sshnaidm | and we move them next week when gundalow is back from PTO | |
| 16:07:39 | gtema | drop permissions of cloudnull | |
| 16:07:42 | sshnaidm | mordred, stephenfin ^^ | |
| 16:07:58 | sshnaidm | gtema, :) | |
| 16:08:05 | gtema | he was approving lots of PRs | |
| 16:08:23 | sshnaidm | I'll talk with cloudnull | |
| 16:08:36 | sshnaidm | but I think we need to send something to Ansible core team | |
| 16:08:41 | sshnaidm | like make it official | |
| 16:09:12 | gtema | yeah, perhaps a good idea | |
| 16:09:13 | dtantsur | yep | |
| 16:09:15 | sshnaidm | and kindly to ask to ignore patches or make their bot to print a message there | |
| 16:09:28 | sshnaidm | like "from now please use gerrit in .. blabla" | |
| 16:10:06 | sshnaidm | #action sshnaidm to send message to Ansible core team about freezing OS modules | |
| 16:10:16 | mnaser | (sorry, i am in and out but following along) | |
| 16:10:33 | sshnaidm | mnaser, sure | |
| 16:10:42 | sshnaidm | ok, let's move on if no objections | |
| 16:10:47 | sshnaidm | Should we move modules with keeping history? | |
| 16:10:59 | Shrews | i think you'll probably need some process (and an actual collection) in place before they'll actually freeze them (if they even do) | |
| 16:11:02 | gtema | nope - ansible github is history | |
| 16:11:16 | mordred | yeah- I think moving with history is too much work at this point | |
| 16:11:25 | sshnaidm | Shrews, we will do it after a move I think | |
| 16:11:54 | sshnaidm | I think dtantsur had some experience with keeping history, was is complicated ? | |
| 16:12:04 | openstackgerrit | Dmitry Tantsur proposed openstack/os-client-config master: Add a release note for Python 2 support removal https://review.opendev.org/701761 | |
| 16:12:09 | yoctozepto | hi (just listening today) | |
| 16:12:10 | dtantsur | splitting a subtree in git is not hard | |
| 16:12:23 | dtantsur | but submitting all the resulting patches to gerrit is going to kill our infra | |
| 16:12:36 | sshnaidm | dtantsur, ack | |
| 16:12:38 | dtantsur | so somebody will have to (force-)push them to gerrit | |
| 16:12:46 | dtantsur | that's what we did for ironic-tempest-plugin in the end | |
| 16:12:54 | dtantsur | (actually, we also merged two git trees from two repos, that was fun) | |
| 16:13:05 | mordred | if someone wants do to the subtree split, I can do the gerrit goo | |
| 16:13:42 | sshnaidm | any volunteers? ^ | |
| 16:14:05 | dtantsur | c'mon, it's fun! | |
| 16:14:17 | gtema | not me. I do not see any benefit | |
| 16:14:31 | sshnaidm | if no volunteers - not keeping history then | |
| 16:14:44 | dtantsur | sshnaidm: I can do it if people find it useful | |
| 16:14:55 | dtantsur | but I don't insist if nobody does | |
| 16:15:06 | dtantsur | time for a poll? :) | |
| 16:15:08 | sshnaidm | I think it might be useful, but not deal-breaker | |
| 16:15:14 | gtema | dtantsur - actually only very few fixes were really landed, so - nope ;-) | |
| 16:15:27 | sshnaidm | dtantsur, does it have a poll? | |
| 16:15:37 | dtantsur | #poll Should we keep the git history of the moved modules? Yes, No | |
| 16:15:50 | dtantsur | given that it doesn't react, I might have done something wrong | |
| 16:16:02 | dtantsur | #startpoll Should we keep the git history of the moved modules? Yes, No | |
| 16:16:47 | sshnaidm | Yes, No | |
| 16:16:50 | sshnaidm | all right, let's make it simple.. no keeping history | |
| 16:16:57 | gtema | +1 | |
| 16:17:12 | sshnaidm | we have things to do beside that.. | |
| 16:17:27 | sshnaidm | let's move on | |
| 16:17:38 | sshnaidm | next question - python 2/3 compatibility | |
| 16:17:49 | sshnaidm | Ansible supports from 2.6(?), but Openstack is moving to 3 completely. Should we stick to Ansible and support from 2.6/2.7? | |
| 16:18:18 | dtantsur | if openstacksdk drops python 2, we cannot support it | |
| 16:18:23 | sshnaidm | dtantsur, we can use it for this topic ^ ) | |
| 16:18:30 | dtantsur | haha, let's try | |
| 16:18:44 | dtantsur | #startvote Should we let Python 2 live? Yes, No, OMG | |
| 16:18:45 | openstack | Begin voting on: Should we let Python 2 live? Valid vote options are Yes, No, OMG. | |
| 16:18:46 | openstack | Vote using '#vote OPTION'. Only your last vote counts. | |
| 16:18:54 | sshnaidm | OMG | |
| 16:19:01 | sshnaidm | #vote OMG | |
| 16:19:09 | dtantsur | #vote No | |
| 16:19:41 | gtema | #vote hehe | |
| 16:19:41 | openstack | gtema: hehe is not a valid option. Valid options are Yes, No, OMG. | |
| 16:19:42 | sshnaidm | interesting, what gundalow thinks about it, but we'll know that only next week | |
| 16:19:45 | dtantsur | To elaborate on my vote: we're planning something forward-looking, and Python 2 is dead today | |
| 16:19:48 | gtema | # vote no | |
| 16:19:53 | gtema | #vote no | |
| 16:20:18 | dtantsur | anyone else wants to play with the vote functionality? :) | |
| 16:20:42 | gtema | #vote again - no | |
| 16:20:43 | openstack | gtema: again - no is not a valid option. Valid options are Yes, No, OMG. | |
| 16:20:47 | sshnaidm | gtema, dtantsur made it case sensitive :o | |
| 16:20:56 | dtantsur | it's not case sensitive, but it requires a valid option | |
| 16:21:03 | gtema | doesn't looke like that | |
| 16:21:08 | dtantsur | #endvote | |
| 16:21:09 | openstack | Voted on "Should we let Python 2 live?" Results are | |
| 16:21:10 | openstack | OMG (1): sshnaidm | |
| 16:21:11 | gtema | simly "no" was accepted | |
| 16:21:12 | openstack | No (2): gtema, dtantsur | |
| 16:21:16 | dtantsur | as you see ^^ | |
| 16:21:19 | sshnaidm | ah, worked | |
| 16:21:52 | sshnaidm | ok, I hope Ansible people won't be mad we break their 2.7 support.. | |
| 16:22:02 | mordred | sorry - juggling two meetings - #vote no :) | |
| 16:22:14 | gtema | too late | |
| 16:22:27 | sshnaidm | too late, we decided no :) | |
| 16:22:30 | mordred | looks like there were no yes votes anyway :) | |
| 16:22:31 | dtantsur | #agreed Unless gundalow objects next week, we won't keep Python 2 support | |
| 16:22:36 | mordred | \o/ | |
| 16:22:42 | sshnaidm | mordred, you just want to join the winning part! | |
| 16:22:44 | mordred | I mean - sdk isn't keeping python 2 support anyway | |
| 16:22:56 | mordred | so, you know, don't know that these modules have much choice :) | |
| 16:23:01 | dtantsur | :D | |