*** tosky has quit IRC | 00:06 | |
*** dave-mccowan has joined #openstack-release | 00:36 | |
openstackgerrit | melanie witt proposed openstack/releases master: osc-placement: release stein 1.5.0 https://review.openstack.org/641531 | 01:04 |
---|---|---|
melwitt | mriedem ^ | 01:04 |
*** whoami-rajat has joined #openstack-release | 01:07 | |
*** lbragstad has quit IRC | 01:09 | |
*** dave-mccowan has quit IRC | 01:18 | |
*** mriedem is now known as mriedem_afk | 01:51 | |
*** mriedem_afk has quit IRC | 01:59 | |
*** dave-mccowan has joined #openstack-release | 02:18 | |
*** ekcs has quit IRC | 03:00 | |
*** lbragstad has joined #openstack-release | 03:11 | |
*** dtruong has quit IRC | 03:21 | |
*** udesale has joined #openstack-release | 03:24 | |
*** ricolin has joined #openstack-release | 03:48 | |
*** ykarel_ is now known as ykarel | 04:00 | |
*** dave-mccowan has quit IRC | 04:00 | |
*** dtruong has joined #openstack-release | 04:03 | |
*** ykarel has quit IRC | 04:07 | |
*** ykarel has joined #openstack-release | 04:26 | |
*** strigazi has quit IRC | 04:26 | |
*** bnemec has quit IRC | 04:26 | |
*** stephenfin has quit IRC | 04:26 | |
*** huats has quit IRC | 04:26 | |
*** dtruong has quit IRC | 04:45 | |
*** strigazi has joined #openstack-release | 04:53 | |
*** bnemec has joined #openstack-release | 04:53 | |
*** stephenfin has joined #openstack-release | 04:53 | |
*** huats has joined #openstack-release | 04:53 | |
*** mjblack has quit IRC | 04:56 | |
*** mjblack has joined #openstack-release | 04:58 | |
*** ekcs has joined #openstack-release | 05:05 | |
*** ricolin_ has joined #openstack-release | 05:07 | |
*** ricolin has quit IRC | 05:09 | |
*** lbragstad has quit IRC | 05:33 | |
*** jhesketh has quit IRC | 05:53 | |
*** jhesketh has joined #openstack-release | 05:54 | |
*** ricolin_ has quit IRC | 06:09 | |
*** ricolin has joined #openstack-release | 06:09 | |
*** zbr has joined #openstack-release | 06:14 | |
*** zbr|ssbarnea has quit IRC | 06:15 | |
*** e0ne has joined #openstack-release | 06:32 | |
*** jtomasek has joined #openstack-release | 06:45 | |
*** jtomasek has quit IRC | 06:48 | |
*** jtomasek has joined #openstack-release | 06:49 | |
*** lxkong has quit IRC | 06:52 | |
*** witek has joined #openstack-release | 07:04 | |
*** ykarel has quit IRC | 07:04 | |
*** ykarel has joined #openstack-release | 07:05 | |
*** armax has quit IRC | 07:12 | |
*** witek has quit IRC | 07:15 | |
*** e0ne has quit IRC | 07:17 | |
*** lxkong has joined #openstack-release | 07:21 | |
*** e0ne has joined #openstack-release | 07:21 | |
*** ekcs has quit IRC | 07:22 | |
*** pcaruana has joined #openstack-release | 07:25 | |
*** aojea has joined #openstack-release | 07:33 | |
*** dtantsur|afk is now known as dtantsur | 07:55 | |
*** tesseract has joined #openstack-release | 08:01 | |
*** cgoncalves has joined #openstack-release | 08:03 | |
*** e0ne has quit IRC | 08:04 | |
cgoncalves | hey release folks! any core available to review https://review.openstack.org/#/c/641513/? | 08:05 |
*** tosky has joined #openstack-release | 08:27 | |
evrardjp | I didn't got the chance to review yesterday, so I am fixing that today. | 08:29 |
evrardjp | cgoncalves: will do | 08:30 |
evrardjp | cgoncalves: isn't this adding a new feature behind the scenes: https://github.com/openstack/octavia-lib/commit/6b55d6219612472e23674bdb4fcbff394022f5fc | 08:33 |
evrardjp | I guess it's sync up though, so we could probably consider this as a bug | 08:34 |
*** jpich has joined #openstack-release | 08:44 | |
cgoncalves | evrardjp, yeah, syncing up stuff. thank you! | 09:20 |
*** witek has joined #openstack-release | 09:28 | |
*** ianw is now known as ianw_pto | 09:52 | |
openstackgerrit | Merged openstack/releases master: Release python-monascaclient 1.14.0 https://review.openstack.org/641464 | 10:12 |
openstackgerrit | Merged openstack/releases master: osc-placement: release stein 1.5.0 https://review.openstack.org/641531 | 10:14 |
openstackgerrit | Merged openstack/releases master: Release python-octaviaclient 1.8.0 (Stein) https://review.openstack.org/641514 | 10:16 |
openstackgerrit | Merged openstack/releases master: python-tackerclient stein release 0.15.0 https://review.openstack.org/641303 | 10:16 |
*** zbr|ssbarnea has joined #openstack-release | 10:17 | |
*** zbr has quit IRC | 10:18 | |
*** e0ne has joined #openstack-release | 10:25 | |
openstackgerrit | Merged openstack/releases master: Cut stable/stein branch for kuryr https://review.openstack.org/640932 | 10:28 |
openstackgerrit | Merged openstack/releases master: Release kuryr-libnetwork 3.0.0 https://review.openstack.org/640937 | 10:28 |
openstackgerrit | Merged openstack/releases master: Release python-zunclient 3.3.0 https://review.openstack.org/640933 | 10:28 |
jaosorior | ttx: regarding https://review.openstack.org/#/c/637857/ I did try to merge the fix for the README https://review.openstack.org/#/c/640023/2 ... but it couldn't merge cause no jobs were running there... enabling the jobs leads to some failures that I am not able to reproduce locally, and haven't been able to fix. | 10:29 |
ttx | jaosorior: ah. kind of a catch-22 there. Maybe that's one case where infra would be willing to force-merge the fix to unblock the knot. I'll bring it up at our team meeting this afternoon. | 10:33 |
jaosorior | ttx: thanks, appreciate that | 10:33 |
*** cdent has joined #openstack-release | 10:33 | |
*** ykarel is now known as ykarel|afk | 10:36 | |
*** luizbag has joined #openstack-release | 10:36 | |
*** ykarel|afk is now known as ykarel | 10:43 | |
*** odyssey4me has quit IRC | 10:53 | |
*** odyssey4me has joined #openstack-release | 10:53 | |
*** jpich has quit IRC | 10:55 | |
*** ykarel is now known as ykarel|afk | 10:56 | |
*** jpich has joined #openstack-release | 10:57 | |
openstackgerrit | Renat Akhmerov proposed openstack/releases master: Release Mistral Stein 3 https://review.openstack.org/641632 | 10:57 |
*** zbr has joined #openstack-release | 10:57 | |
*** udesale has quit IRC | 10:59 | |
*** udesale has joined #openstack-release | 10:59 | |
*** zbr|ssbarnea has quit IRC | 10:59 | |
*** ifat_afek has joined #openstack-release | 11:09 | |
*** ykarel|afk is now known as ykarel | 11:15 | |
*** zbr|ssbarnea has joined #openstack-release | 11:17 | |
*** dtantsur is now known as dtantsur|bbl | 11:19 | |
*** zbr has quit IRC | 11:19 | |
*** ricolin has quit IRC | 11:20 | |
*** udesale has quit IRC | 11:28 | |
*** electrofelix has joined #openstack-release | 11:42 | |
*** udesale has joined #openstack-release | 11:45 | |
*** zbr has joined #openstack-release | 11:46 | |
*** zbr has quit IRC | 11:46 | |
*** zbr has joined #openstack-release | 11:47 | |
*** zbr|ssbarnea has quit IRC | 11:48 | |
openstackgerrit | Tom Barron proposed openstack/releases master: Release manila client 1.27.0 https://review.openstack.org/641642 | 11:54 |
openstackgerrit | Juan Antonio Osorio Robles proposed openstack/releases master: TripleO: minor release for rocky https://review.openstack.org/637858 | 12:20 |
*** dave-mccowan has joined #openstack-release | 12:22 | |
*** ricolin has joined #openstack-release | 12:27 | |
*** udesale has quit IRC | 13:02 | |
*** udesale has joined #openstack-release | 13:08 | |
openstackgerrit | Juan Antonio Osorio Robles proposed openstack/releases master: TripleO: minor release for rocky https://review.openstack.org/637858 | 13:12 |
*** ykarel_ has joined #openstack-release | 13:14 | |
*** ifat_afek has quit IRC | 13:16 | |
*** ykarel has quit IRC | 13:17 | |
*** ykarel_ is now known as ykarel | 13:21 | |
cdent | smcginnis: if there such a thing a client lib final release exception? see the discussion near the end of https://review.openstack.org/#/c/640898/ | 13:22 |
*** mriedem has joined #openstack-release | 13:30 | |
e0ne | hi team. if we didn't do stein-2 release for horizon, what version should I specify for stein-3? | 13:40 |
e0ne | we've got version: 15.0.0.0b1 for stein-1 | 13:40 |
openstackgerrit | Ivan Kolodyazhny proposed openstack/releases master: Release Horizon stein-3 15.0.0.0b2 https://review.openstack.org/641668 | 13:42 |
*** lbragstad has joined #openstack-release | 13:48 | |
*** dtantsur|bbl is now known as dtantsur | 14:10 | |
smcginnis | e0ne: You got it right. This is the second beta release, so .0b2 is correct. | 14:21 |
smcginnis | cdent: There is the requirements feature freeze exception. | 14:22 |
e0ne | smcginnis: ok, thanks for the confirmation | 14:22 |
smcginnis | cdent: We may want to do a release with what is merged now. Then ask for a FFE for this once it merges. | 14:22 |
smcginnis | So at least everything else is made available right away. | 14:22 |
cdent | smcginnis: there was supposed to have been an osc-placement release last night | 14:22 |
smcginnis | cdent: I think I saw that. | 14:23 |
cdent | i'm not aware of it showing up a requirement for service projects | 14:23 |
cdent | so it's mostly a matter of "do we want to get these features out to deployers for stein" | 14:23 |
cdent | which, yes, it would be nice | 14:23 |
smcginnis | If no one is consuming it, that makes it easy. Low risk. | 14:23 |
cgoncalves | smcginnis, hi. any chance you could +W https://review.openstack.org/#/c/641513/ ? it prevents us in octavia from verifying and merge a feature | 14:27 |
smcginnis | cgoncalves: Sure, I will take a look shortly. | 14:28 |
openstackgerrit | Eric Fried proposed openstack/releases master: Release python-novaclient 12.1.0 https://review.openstack.org/641678 | 14:31 |
*** mriedem is now known as mriedem_afk | 14:34 | |
cgoncalves | smcginnis, thank you! | 14:37 |
smcginnis | cgoncalves: No problem! I'll try to watch for the requirements update too and help that through. | 14:38 |
*** mriedem_afk is now known as mriedem | 14:46 | |
openstackgerrit | Merged openstack/releases master: Release octavia-lib 1.1.1 https://review.openstack.org/641513 | 14:46 |
openstackgerrit | Akihiro Motoki proposed openstack/releases master: neutron Stein-3 beta deliverables https://review.openstack.org/641687 | 14:48 |
openstackgerrit | Akihiro Motoki proposed openstack/releases master: python-neutronclient 6.12.0 (Stein) https://review.openstack.org/641688 | 14:49 |
tosky | I always forget when the branching happens - is it going to happen tomorrow, next week, or during the RC week? | 14:51 |
openstackgerrit | Jeremy Freudberg proposed openstack/releases master: Release python-saharaclient 2.2.0 https://review.openstack.org/641690 | 14:57 |
fungi | tosky: at rc1 | 14:58 |
smcginnis | tosky: Clients can already branch is you don't think there is much risk of needing to backport bugfixes yet for stein. | 14:58 |
smcginnis | Service projects should be at the RC1 though. | 14:59 |
fungi | eubsequent rc tags and release tag wind up on the stable/stein branch | 14:59 |
fungi | er, subsequent | 14:59 |
tosky | fungi, smcginnis : thanks! I think I went through https://releases.openstack.org/stein/schedule.html but I was not totally sure | 14:59 |
smcginnis | I do mention it in the last couple countdown emails - http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003352.html | 15:01 |
tosky | uh, right | 15:01 |
smcginnis | SOrry, not saying RTFM, just confirming with myself that I didn't forget about it. ;) | 15:01 |
tosky | also: do I remember correctly that the devstack and grenade branching is a usually bit delayed? | 15:04 |
smcginnis | tosky: Yeah, looks like that happens post-RC1 once most projects are ready for it. | 15:08 |
smcginnis | https://releases.openstack.org/reference/process.html#rc1-week | 15:08 |
smcginnis | Again, not saying to read the manual, just making sure we have it documented. ^ :) | 15:08 |
tosky | sure, I asked because I remember that sometimes it happens not exactly during the RC week, even if the text may imply that | 15:10 |
tosky | sometimes the delay has been... remarkable :) | 15:10 |
tosky | thanks again | 15:11 |
smcginnis | Yeah... | 15:11 |
smcginnis | I think it's a combination of projects actually being ready, and QA team doing the final steps needed on the devstack and grenade side. | 15:11 |
smcginnis | Hopefully that's better now. | 15:11 |
tosky | so I need to hurry up with my native Zuul v3 grenade job; it's almost working now | 15:11 |
* smcginnis crosses fingers | 15:11 | |
tosky | I mean, it seems to be working even with some plugins, I need to fix the logging | 15:12 |
smcginnis | Great! I think other projects could benefit from seeing that work done elsewhere. | 15:12 |
cgoncalves | smcginnis, https://review.openstack.org/#/c/641693/ :) | 15:14 |
*** tellesnobrega has joined #openstack-release | 15:21 | |
tellesnobrega | hi folks, I'm cutting versions for the sahara plugins (new in stein) and I'm wondering if we should have the plugin version set to the same on sahara (10.*) | 15:22 |
tellesnobrega | or should we start from 1? | 15:22 |
smcginnis | tellesnobrega: It's best to start from 1. | 15:25 |
tellesnobrega | thanks smcginnis | 15:25 |
*** ykarel is now known as ykarel|away | 15:29 | |
openstackgerrit | Eric Fried proposed openstack/releases master: Release python-novaclient 13.0.0 https://review.openstack.org/641678 | 15:56 |
evrardjp | o/ | 16:00 |
smcginnis | #startmeeting releaseteam | 16:00 |
openstack | Meeting started Thu Mar 7 16:00:01 2019 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: releaseteam)" | 16:00 | |
openstack | The meeting name has been set to 'releaseteam' | 16:00 |
smcginnis | evrardjp: Quick! | 16:00 |
smcginnis | Ping list: smcginnis ttx dhellmann diablo_rojo hberaud evrardjp fungi armstrong | 16:00 |
evrardjp | :) | 16:00 |
smcginnis | #link https://etherpad.openstack.org/p/stein-relmgt-tracking Agenda | 16:00 |
smcginnis | Waay down around line 387 now. | 16:00 |
*** mlavalle has joined #openstack-release | 16:00 | |
smcginnis | Thank you as usual to ttx for getting an agenda together there. | 16:00 |
*** armstrong has joined #openstack-release | 16:00 | |
smcginnis | At least I assume it was ttx. :) | 16:01 |
fungi | aloha | 16:01 |
smcginnis | Morning fungi | 16:01 |
*** udesale has quit IRC | 16:01 | |
ttx | o/ | 16:01 |
ttx | yes I'm to blame | 16:02 |
evrardjp | fungi: always sending me a holiday vibe | 16:02 |
smcginnis | #topic Queens Tripleo release | 16:02 |
*** openstack changes topic to "Queens Tripleo release (Meeting topic: releaseteam)" | 16:02 | |
smcginnis | README issued blocked on being able to merge to stable. | 16:03 |
smcginnis | #link https://review.openstack.org/#/c/640023/ | 16:03 |
diablo_rojo | o/ | 16:03 |
smcginnis | I wasn't aware of these. I suppose they could switch over to noop, get this merged, then switch mack and figure things out. | 16:04 |
ttx | yeah they are blocked so I wanted to discuss a solution there | 16:04 |
smcginnis | ttx: Did you have something in mind? | 16:04 |
ttx | Looks like for some reason the jobs were disabled on Queens | 16:05 |
ttx | and now that they are trying to reenable them to get this technical change merged they see they are broken | 16:05 |
ttx | so I was windering if we should just not force-merge them, since it's extremely likely to be a one-off | 16:05 |
ttx | maybe fungi has an opinion on that :) | 16:06 |
fungi | yeah, i'm trying to digest the problem | 16:06 |
* evrardjp takes popcorn | 16:06 | |
smcginnis | Seems like they should get things fixed, but that would work to get things going for now. | 16:06 |
ttx | I guess they could just set noop instead of the set of failing jobs | 16:07 |
evrardjp | ofc | 16:07 |
fungi | they want to tag a new point release of tie from stable/queens? | 16:07 |
evrardjp | or just remove openstack-python-jobs | 16:07 |
ttx | I think they want to do a new tripleo release, and that includes some repo that they are no longer updating | 16:07 |
fungi | and their python 2.7 unit tests no longer work on that branch? | 16:07 |
ttx | except that our validation is now catching README formatting, so they kind of need to fix that | 16:08 |
ttx | so they are trying to, but they get no job to match, and adding the ones previously defined kinda fails | 16:08 |
ttx | Haven't gone deeper in the rabbit hole as to WHY those long-dead jobs tdo not work when reanimated | 16:09 |
fungi | yeah, i don't know how to set the no-op job just for specific branches of a repository but i can ask a few others | 16:09 |
evrardjp | sorry to be selfish here | 16:09 |
ttx | I feel like we should just force-merge it as it's really the only thing that will land there | 16:09 |
smcginnis | Something seems off about wanting to release something that can't pass unit tests. Really feels like they should fix things first. | 16:09 |
ttx | rather than spend time "fixing" it | 16:10 |
evrardjp | but shouldn't the team fix it in a one off to do this? | 16:10 |
smcginnis | And really seems like an issue for that team to figure out. Not really a release issue. | 16:10 |
evrardjp | that's what I meant -- they are in charge of their destiny? | 16:10 |
fungi | skimming the job log, it looks like some specific unit tests in there are failing | 16:10 |
ttx | That said, yes it's a bit weird tat they would want to do a release for something they can no longer fully test | 16:10 |
evrardjp | yup -- TestOsSvcDaemon.test_dir_only_upstart or something | 16:11 |
fungi | so maybe an easy suggestion is that they skip those specific unit tests in their py27 job | 16:11 |
smcginnis | They could also drop that repo from the release request and get everything else out. | 16:11 |
evrardjp | I think they should just fix it | 16:11 |
fungi | if they're not maintaining it, why does it need a new point release anyway? | 16:11 |
ttx | but then the deliverable will appear incomplete | 16:11 |
evrardjp | if you release it, it sends a message, right? | 16:11 |
ttx | fungi: yeah that is the point I raised just above | 16:11 |
fungi | but also, if they're not maintainind some particular repository in a deliverable and maintaining others, then it's not the same deliverable is it? | 16:12 |
ttx | happy with any outcome really -- we just need to tell them the best way out | 16:12 |
smcginnis | Do "we"? | 16:12 |
fungi | we can certainly present them with some of the options we came up with, but as to which is "best" that's likely up to them to decide | 16:12 |
evrardjp | fungi: ++ | 16:13 |
evrardjp | we could also recommend what we consider best | 16:13 |
evrardjp | from our perspective | 16:13 |
fungi | jaosorior, as ptl, can also just read the above for our list of suggestions | 16:13 |
ttx | ok, if no easy solution let's not spend the whole meeting on this | 16:13 |
evrardjp | but then they take the decision :) | 16:13 |
evrardjp | ttx: agreed | 16:13 |
smcginnis | I agree. We can give suggestions as a group of people who care, but I don't think this is anything on the release team to sort out. | 16:13 |
ttx | and schedule a discussion with jaosorior to walk through it | 16:13 |
smcginnis | Any more on this topic? | 16:14 |
ttx | nope | 16:14 |
smcginnis | #topic Review R-5 week tasks | 16:14 |
*** openstack changes topic to "Review R-5 week tasks (Meeting topic: releaseteam)" | 16:14 | |
ttx | I see two open tasks | 16:15 |
ttx | Generate release requests... (diablo_rojo and evrardjp) | 16:15 |
smcginnis | The first I can include in the countdown email. | 16:15 |
ttx | Freeze changes... (prometheanfire) | 16:15 |
smcginnis | Oh, looking at next week's tasks. | 16:15 |
ttx | smcginnis: that's next topic :) | 16:16 |
smcginnis | I believe diablo_rojo is ready to go on those release requests. | 16:16 |
diablo_rojo | smcginnis, correct | 16:16 |
evrardjp | mmm | 16:16 |
diablo_rojo | just regenerated the list and put it in the etherpad | 16:16 |
evrardjp | I think ttx has an opinion on this | 16:16 |
smcginnis | Thanks diablo_rojo and evrardjp for going through getting ready for that last week. | 16:16 |
diablo_rojo | its the same as it was | 16:16 |
diablo_rojo | I had already accidentally pushed the pankoclient patch | 16:17 |
ttx | I did record my opinion at https://review.openstack.org/#/c/640867/ | 16:17 |
* dhellmann slips into the back of the room late | 16:17 | |
evrardjp | ttx: beat me to it :) | 16:17 |
ttx | i.e. we should release libraries that have not been released since milestone-2 | 16:17 |
ttx | that is what we said we'd do | 16:18 |
ttx | and announced in email at the start of the cycle | 16:18 |
smcginnis | Right, we stated we would release c-w-i libs at each milestone. | 16:18 |
smcginnis | As long as there was something to release. | 16:18 |
ttx | Regarding tooling ISTR we had a magic CLI for that... dhellmann ? | 16:18 |
evrardjp | then yes somethign might have slipped through the cracks then | 16:18 |
smcginnis | But we also need to release the ones that didn't have anything to release previously so we have a branching point. | 16:19 |
ttx | smcginnis: and as long as they were not released otherwise in that same timeframe | 16:19 |
smcginnis | ++ | 16:19 |
dhellmann | we have propose-library-branches | 16:20 |
dhellmann | and propose-final-releases but I don't know if that works for just libraries; I think that's about RC->final transition | 16:20 |
ttx | but not list-deliverables --unreleased-since <date> | 16:20 |
smcginnis | No scripts that will generate the release requests, but can at least tell us what has not been released. | 16:21 |
evrardjp | smcginnis: I didn't think we had something based on date. | 16:21 |
dhellmann | ah, no, not based on date | 16:21 |
ttx | fwiw that same script is supposed to help at milestone-1 and milestone-2 too :) | 16:21 |
evrardjp | smcginnis: problem is that we can't presume the release anymore | 16:21 |
dhellmann | that would be a good tool to have, though | 16:21 |
evrardjp | because ppl are not forced to create for milestone x anymore | 16:22 |
evrardjp | if I understood correctly | 16:22 |
dhellmann | I think I expected us to just use list_library_unreleased_changes.sh | 16:22 |
ttx | dhellmann: i mean, we'd really be grateful if that script existed, right | 16:22 |
dhellmann | anything that has changes needs to be released, including if they are just for tests | 16:22 |
dhellmann | ttx: I will buy the author a beer | 16:22 |
smcginnis | dhellmann: ++ | 16:22 |
evrardjp | ttx: wow that wink crossed the oceans. | 16:22 |
ttx | dhellmann: I will buy the author a glass of wine. | 16:23 |
evrardjp | oh wait I have the impression this will backfire | 16:23 |
dhellmann | that escalated quickly | 16:23 |
evrardjp | :) | 16:23 |
smcginnis | So we have two things. Ones that haven't done any release yet that we can get with --unreleased, but that would also be included (presumable) in list_library_unreleased_changes.sh. | 16:24 |
evrardjp | dhellmann: want me to help there -- I think I would like to spend time on tooling, to refresh my knowledge, and clean what's not required if we can | 16:24 |
evrardjp | sorry wrongly phrased | 16:24 |
dhellmann | smcginnis : maybe not, if they haven't landed any changes | 16:24 |
evrardjp | dhellmann: do you want me to help there? | 16:24 |
ttx | It's also fine to generate them manually for this tmie, to see what's expected | 16:24 |
smcginnis | evrardjp: That would be great. It could use some attention I'm sure. | 16:24 |
smcginnis | dhellmann: True, there might be a few outside of that venn diagram overlap. | 16:24 |
evrardjp | ttx: probably best, because I am not sure when I will have time on this | 16:24 |
dhellmann | evrardjp : I'm not going to have time to do it, but I would be able to advise a bit | 16:25 |
openstackgerrit | Eric Fried proposed openstack/releases master: Release python-novaclient 13.0.0 https://review.openstack.org/641678 | 16:25 |
dhellmann | evrardjp : so if you want to own it that would be great | 16:25 |
dhellmann | generating the actual releases could be scripted by calling new-release repeatedly once there is a list of the things that needs the releases | 16:25 |
smcginnis | You could do it manually for now and make sure the necessary steps are written down. Then at some point use that documentation to automate. | 16:25 |
dhellmann | if you start with the ones that are completely unreleased then it will make looking at the output of list_library_unreleased_changes.sh less of a chore | 16:25 |
evrardjp | dhellmann: I think that's what in my pseudo code in my patch | 16:26 |
dhellmann | ++ | 16:26 |
diablo_rojo | I will get the patches for unreleased libs up today for you evrardjp | 16:26 |
evrardjp | but does list_library_unreleased_changes know about milestones? | 16:26 |
ttx | ok, let's move on --- I wrote down that evrardjp and diablo_rojo would work to generate those manually | 16:27 |
coreycb | hi all, does anyone know how i'd go about getting a 2.3.1 release of ldappool for stable/rocky? since it's an independent deliverable it's not obvious to me what is needed. https://github.com/openstack/releases/blob/master/deliverables/_independent/ldappool.yaml | 16:27 |
evrardjp | lgtm ttx | 16:27 |
evrardjp | diablo_rojo: we'll do this together :) | 16:27 |
ttx | the other item -- I haven't heard of prometheanfire this week | 16:27 |
evrardjp | I am just thinking of the next cycle at the same time :p | 16:27 |
evrardjp | anyway | 16:27 |
smcginnis | evrardjp: No, but if you get ones that haven't released at all, then any others that have changes that have not been released can be released. | 16:27 |
diablo_rojo | evrardjp, sounds good to me | 16:27 |
smcginnis | coreycb: It would not be for rocky since it's independent. | 16:28 |
ttx | but since the deadline is not there yet, I don't think we need to organize search and rescue just yet | 16:28 |
evrardjp | smcginnis: I didn't know we had the tooling for the ones with changes unreleased. That script name makes more sense to me know | 16:28 |
evrardjp | now* | 16:28 |
smcginnis | ;) | 16:28 |
smcginnis | OK, let's move on and we can work through any more details out of meeting. | 16:28 |
smcginnis | #topic Library freeze exceptions | 16:28 |
*** openstack changes topic to "Library freeze exceptions (Meeting topic: releaseteam)" | 16:28 | |
coreycb | smcginnis: ok. is it possible for me to update upper-constraints for stable/rocky ldappool? | 16:29 |
smcginnis | We did release octavia-lib today. | 16:29 |
ttx | yeah I spotted a lib release that was post-freeze... but it's bugfix enough I think | 16:29 |
smcginnis | They had issues that required a new release. | 16:29 |
ttx | happy to approve if everyone is happy with it | 16:29 |
ttx | oh it's done | 16:30 |
ttx | next topic :) | 16:30 |
smcginnis | I figured we would get that in the requirements update review if prometheanfire wanted an official FFE on that. | 16:30 |
ttx | Any missing library release ? | 16:30 |
* coreycb apologizes for interrupting a meeting | 16:30 | |
smcginnis | coreycb: No worries, sorry. | 16:30 |
ttx | or did we cover them all last week ? | 16:30 |
smcginnis | I believe we got all the libs, but we should double check that. | 16:31 |
ttx | os-client-config is the only one that shows as completely unreleased | 16:32 |
smcginnis | I think I had asked Monty about that one, but not sure if we got an answer. | 16:33 |
ttx | the others might not be recent (i.e. released since milestone-2) | 16:33 |
ttx | pycadf, shade had a single release | 16:34 |
fungi | mordred is around, i think | 16:34 |
smcginnis | Hmm, I see os-brick changes that should have gone out. | 16:34 |
mordred | what did I do? | 16:34 |
mordred | oh. poo. one sec | 16:34 |
dhellmann | os-client-config has a fair number of changes, including test job stuff | 16:34 |
ttx | same for automaton blazar-nova ceilometermiddleware cliff debtcollector kuryr mistral-lib mox3 os-acc | 16:35 |
mordred | yeah. sorry - we should likely cut a shade release | 16:35 |
ttx | those had a single release in stein ^ | 16:35 |
ttx | which might or might not be recent | 16:35 |
* ttx manually checks | 16:35 | |
ttx | pycadf - 5 weeks ago | 16:36 |
openstackgerrit | Monty Taylor proposed openstack/releases master: Release 1.31.0 of shade https://review.openstack.org/641716 | 16:36 |
ttx | automaton = 6 days ago | 16:36 |
ttx | blazar-nova = 6 days ago | 16:37 |
fungi | mordred: the bigger question was around os-client-config | 16:37 |
ttx | same for ceilometermiddleware | 16:37 |
ttx | cliff - 4 months ago | 16:37 |
mordred | yeah - it's mostly test fixes - there's one patch that might be release worthy | 16:37 |
dhellmann | mordred : at this point, we want a release so when we branch those test fixes end up in your stable branch | 16:38 |
ttx | debtcollector - 7 days | 16:38 |
mordred | dhellmann: ++ | 16:38 |
ttx | kuryr - 7 weeks | 16:38 |
dhellmann | so anything with any unreleased patches of any type should be released | 16:38 |
ttx | mistral-lib - 6 days | 16:38 |
ttx | mox3 - 7 days | 16:39 |
dhellmann | s/anything/any library/ | 16:39 |
ttx | os-acc - 4 months | 16:39 |
openstackgerrit | Monty Taylor proposed openstack/releases master: Release 1.32.0 of os-client-config https://review.openstack.org/641721 | 16:39 |
dhellmann | it sounds like we have a lot of tags to generate | 16:39 |
ttx | I only checked those who released only once in the cycle as good candidates | 16:39 |
mordred | there ya go - sorry about that | 16:40 |
ttx | I'd say kuryr, cliff, and os-acc might need a refresh | 16:40 |
ttx | the others should be "fresh enough" | 16:40 |
smcginnis | We must need better documentation on generating those lib releases. The ones 6 days ago must have been picked up by the script. Not sure why the older ones were not though. | 16:41 |
dhellmann | the only change in kuryr is to add the python 3.7 job | 16:42 |
ttx | ok so the one release they have is good enough | 16:42 |
dhellmann | cliff has a lower-constraints template change, we should probably tag that | 16:42 |
dhellmann | os-acc has no changes | 16:42 |
ttx | dhellmann: can you generate the cliff release req? | 16:43 |
evrardjp | smcginnis: I agree | 16:43 |
dhellmann | sure | 16:43 |
ttx | smcginnis: yes we need a tool | 16:43 |
ttx | in the mean time this manual checking will do | 16:43 |
openstackgerrit | Doug Hellmann proposed openstack/releases master: cliff 2.14.1 https://review.openstack.org/641722 | 16:43 |
ttx | ok all set | 16:45 |
smcginnis | Thanks! | 16:45 |
openstackgerrit | Kendall Nelson proposed openstack/releases master: Release python-aodhclient 1.2.0 https://review.openstack.org/640870 | 16:45 |
smcginnis | #topic Client library freeze | 16:45 |
*** openstack changes topic to "Client library freeze (Meeting topic: releaseteam)" | 16:45 | |
smcginnis | So still a few with no releases. | 16:45 |
smcginnis | We have several hours to go yet though. | 16:46 |
ttx | those are supposed to be caught by the task we already talked about | 16:46 |
ttx | Maybe y'all can use the etherpad as a tracking mechanism as you go through them manually | 16:46 |
ttx | that way we can play too | 16:47 |
smcginnis | Well, maybe that's an opportunity for more documention. We need need to capture the non-client lib ones at that deadline, then wait until end of today for the client lib ones. | 16:47 |
dhellmann | unreleased changes in client libraries: http://paste.openstack.org/show/747419/ | 16:48 |
smcginnis | So really we need to rerun this client list tomorrow morning and see what ultimately missed today's deadline. | 16:48 |
ttx | ++ | 16:48 |
smcginnis | evrardjp, diablo_rojo: Are you two on that task? Tomorrow get the final list and propose releases for any client libs that missed? | 16:49 |
diablo_rojo | smcginnis, yep I got it | 16:50 |
smcginnis | ++ Thanks! | 16:50 |
evrardjp | thanks diablo_rojo | 16:50 |
smcginnis | Overall I think it doesn't look too bad so far. | 16:50 |
diablo_rojo | Only 6 | 16:50 |
smcginnis | We've seen worse. ;) | 16:50 |
smcginnis | #topic Cycle highlights collection | 16:51 |
*** openstack changes topic to "Cycle highlights collection (Meeting topic: releaseteam)" | 16:51 | |
diablo_rojo | I have an email drafted ready to send | 16:51 |
smcginnis | Excellent | 16:51 |
smcginnis | I had a blurb in the last countdown. | 16:51 |
diablo_rojo | I can click the button whenever | 16:51 |
diablo_rojo | I took from you original introduction to remnind folks of the importance and how to | 16:52 |
smcginnis | If you want to send that now, I can add a reference to that in the countdown email I send out to try to increase odds someone reads them. | 16:52 |
diablo_rojo | Can do | 16:52 |
diablo_rojo | Sent | 16:52 |
smcginnis | Great, I'll grab the link and add it. | 16:52 |
smcginnis | #link http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003597.html | 16:53 |
smcginnis | #topic Forum brainstorming | 16:53 |
*** openstack changes topic to "Forum brainstorming (Meeting topic: releaseteam)" | 16:53 | |
*** tellesnobrega has left #openstack-release | 16:53 | |
ttx | I was wondering if we wanted to submit anything | 16:53 |
ttx | it closes tomorrow-ish (or was it extended ?) | 16:54 |
smcginnis | Ben was going to submit a PTL feedback session that we had talked about piggybacking on to get release process change feedback. | 16:54 |
smcginnis | I didn't have anything else that I could think of needing. | 16:54 |
ttx | ++ | 16:54 |
diablo_rojo | smcginnis, extended till the 10th | 16:55 |
smcginnis | OK, great. | 16:55 |
smcginnis | Anyone have any Forum appropriate release topics in mind? | 16:55 |
fungi | procrastinators rejoice! | 16:55 |
smcginnis | :) | 16:55 |
dhellmann | do we have a schedule for train settled? | 16:55 |
diablo_rojo | Not that I can think of? | 16:55 |
evrardjp | smcginnis: it's not listed in Ben session's draft though | 16:55 |
smcginnis | We will also have at least some hallway time during the PTG for release-specific topics. | 16:55 |
evrardjp | so we probably want to make sure PTLs are there by doing proper publicity of it | 16:55 |
dhellmann | I can imagine teams wanting to know by the ptg/forum | 16:55 |
smcginnis | dhellmann: I have a proposed schedule up. | 16:56 |
smcginnis | That would be good to finalize that. | 16:56 |
dhellmann | ok, I wasn't sure if the dates were firm -- yeah | 16:56 |
smcginnis | #link https://review.openstack.org/636742 | 16:56 |
smcginnis | Not firm until we approve it, but no one has pointed out major issues with the dates yet. | 16:56 |
ttx | maybe we should now | 16:57 |
smcginnis | If it's good enough, maybe we should get that approved so it's published and we can get broader community feedback if there is anything that doesn't land at a good time. | 16:57 |
ttx | It's FF after all | 16:57 |
smcginnis | #link http://logs.openstack.org/42/636742/2/check/openstack-tox-docs/26cf052/html/train/schedule.html | 16:58 |
dhellmann | works for me | 16:58 |
smcginnis | For your easy viewing pleasure. | 16:58 |
ttx | I would just approve it and send "this is it, if we missed something critical just let us know asap" email | 16:58 |
diablo_rojo | Hehe.. yeah.. I think doing elections is going to suck this round. | 16:59 |
smcginnis | I could mention in the countdown, but then also send its own ML post to increase odds of someone actually seeing it. | 16:59 |
diablo_rojo | If the goal is high visibility I think its own email would be better | 16:59 |
dhellmann | yeah, separate email thread | 16:59 |
dhellmann | and we should get the election officials to add those dates as early as we can | 17:00 |
prometheanfire | smcginnis: what's up? | 17:00 |
fungi | i'm open to brainstorming easier ways of handling the election scheduling for next round though i also can't be an official | 17:00 |
fungi | unless i decide not to run for the tc again that is | 17:00 |
smcginnis | Umm, think we had mentioned requirements freeze and that there are one or two libs that may or may not need to ask for an official FFE. | 17:00 |
diablo_rojo | dhellmann, thats going to require another tc convo I think. tonyb projected the dates and they look pretty simultanrous | 17:00 |
diablo_rojo | *simultaneous | 17:01 |
dhellmann | diablo_rojo : ok. that's one for mnaser then | 17:01 |
openstackgerrit | Duc Truong proposed openstack/releases master: Release python-senlinclient 1.11.0 (Stein) https://review.openstack.org/641520 | 17:01 |
diablo_rojo | fungi, yeah and if I ever want to run.. then it would be one less too | 17:01 |
fungi | yup! | 17:02 |
smcginnis | I think the only question on the schedule related to that was ATC deadline. That can be moved afterwards if it's determined it's not enough time. | 17:02 |
diablo_rojo | dhellmann, yeah I figured after this schedule got set we would bring it up in office hours or something | 17:02 |
ttx | we have one more topic, task assignment | 17:02 |
dhellmann | diablo_rojo , fungi : I might be talked into helping. I can't promise this early, though. | 17:02 |
smcginnis | ttx: Are you good with the propsoed train schedule? | 17:02 |
ttx | yes | 17:02 |
fungi | dhellmann: thanks, we'll keep that in mind | 17:02 |
diablo_rojo | dhellmann, noted :D | 17:02 |
smcginnis | Does someone want to approve that? Then I can get emails sent. | 17:03 |
fungi | (it is mostly automated at least) | 17:03 |
ttx | +2ed | 17:03 |
smcginnis | #topic Assign R-4 week tasks | 17:03 |
*** openstack changes topic to "Assign R-4 week tasks (Meeting topic: releaseteam)" | 17:03 | |
ttx | and+1ed | 17:03 |
smcginnis | Thanks | 17:03 |
*** dtruong has joined #openstack-release | 17:03 | |
smcginnis | The first task for next week I can include in the countdown email. | 17:03 |
ttx | The warn task should probably just be a weekly email thing | 17:03 |
ttx | yep | 17:03 |
smcginnis | The next task is thankfully a nicely scripted one. | 17:04 |
ttx | I'm happy to take the second one unless someone wants it | 17:04 |
smcginnis | diablo_rojo and evrardjp: Up for another one? | 17:04 |
smcginnis | Or ttx | 17:04 |
ttx | (I'll be around that week) | 17:04 |
evrardjp | I am not around next week | 17:04 |
smcginnis | Oh right, I should point out I'm at the Open Source Leadership Summit next week, so my availability will be spotty. | 17:04 |
diablo_rojo | smcginnis, such a leader ;) | 17:05 |
*** tesseract has quit IRC | 17:05 | |
smcginnis | heh | 17:05 |
smcginnis | OK, I'll put ttx down as owning the branching task. | 17:05 |
smcginnis | OK, we're over. Anything else? | 17:05 |
ttx | smcginnis: I'm not an open source leader so I'm not invited :P | 17:05 |
smcginnis | Hah | 17:05 |
evrardjp | ttx: FOMO? | 17:06 |
ttx | all done thx! | 17:06 |
diablo_rojo | evrardjp, always | 17:06 |
smcginnis | OK, thanks everyone! | 17:06 |
evrardjp | thx | 17:06 |
smcginnis | #endmeeting | 17:06 |
ttx | evrardjp: I *almost* submitted a talk but then decided to not travel THAT much | 17:06 |
diablo_rojo | thanks smcginnis | 17:06 |
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/" | 17:06 | |
openstack | Meeting ended Thu Mar 7 17:06:30 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:06 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-07-16.00.html | 17:06 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-07-16.00.txt | 17:06 |
openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2019/releaseteam.2019-03-07-16.00.log.html | 17:06 |
fungi | thanks smcginnis! | 17:06 |
fungi | #link https://sks-keyservers.net/pks/lookup?op=vindex&search=0xcdc08088c3cb45a9be08332b2354069e5b504663&fingerprint=on OpenStack Infra (Train Cycle) artifact signing key | 17:06 |
fungi | has a few root sysadmin signatures published for it now if any release managers are interested in doing the same | 17:06 |
smcginnis | Nice thing about doing this in our own channel, we can really go as long as we want. | 17:07 |
smcginnis | Thanks fungi | 17:07 |
evrardjp | ok | 17:07 |
*** e0ne has quit IRC | 17:07 | |
evrardjp | smcginnis: you closed it earlier though :p | 17:07 |
fungi | (was saving that for open discussion, but we didn't have one) | 17:07 |
smcginnis | fungi: How does one go about doing the same? | 17:07 |
evrardjp | I suppose trusting the key signing it and push it servers? | 17:07 |
evrardjp | noob to this | 17:07 |
evrardjp | or do you want something else? | 17:08 |
fungi | smcginnis: short answer is to fetch the key, check the signatures appear to be from keys of folks whose keys you've previously signed and trust, then sign that key and push your copy of it back to the keyserver network | 17:08 |
smcginnis | fungi: Any instructions somewhere on how that's all done? | 17:08 |
fungi | that's the long answer ;) | 17:09 |
fungi | lemme see what i can get you | 17:09 |
* smcginnis has never really worked with public keyservers | 17:09 | |
openstackgerrit | Kendall Nelson proposed openstack/releases master: Release python-aodhclient 1.2.0 https://review.openstack.org/640870 | 17:09 |
fungi | for the sysadmins we have https://docs.openstack.org/infra/system-config/signing.html#attestation but they're expected to actually inspect the key on our server's filesystem before attesting to it, so the steps for retrieving the key from the keyserver network and verifying the signatures on it are going to be somewhat different | 17:10 |
smcginnis | Cool, thanks. | 17:11 |
fungi | if you're looking for a recommended configuration using the sks keyservers, we have https://docs.openstack.org/infra/system-config/signing.html#configuration | 17:11 |
openstackgerrit | Merged openstack/releases master: Proposed release schedule for Train https://review.openstack.org/636742 | 17:12 |
fungi | that example configuration relies on some fancy newer protocols which further secure your communication with the keyservers | 17:12 |
fungi | where "newer" is taken to mean "from this century" | 17:13 |
*** ekcs has joined #openstack-release | 17:13 | |
*** armax has joined #openstack-release | 17:16 | |
fungi | smcginnis: to retrieve that key for inspection, you can `gpg2 --recv-keys 0xcdc08088c3cb45a9be08332b2354069e5b504663` | 17:17 |
fungi | and then `gpg2 --check-signatures 0xcdc08088c3cb45a9be08332b2354069e5b504663` to see if the signatures are from keys you already know/trust | 17:19 |
fungi | note that --list-signatures will also show signatures from keys which are not known to your current keyring | 17:21 |
smcginnis | Cool, looks like I've at least gotten that far. | 17:22 |
*** ricolin has quit IRC | 17:22 | |
smcginnis | fungi: I have two signing keys. Do you happen to know offhand how to switch which one is used as default. | 17:23 |
smcginnis | I should have the answer shortly, but figured I'd ask if you just knew it. | 17:23 |
fungi | smcginnis: in my ~/.gnupg/gpg.conf i use "default-key 0x48f9961143495829" | 17:24 |
smcginnis | Ah, perfect. Thanks fungi | 17:24 |
fungi | because my keyring also contains an older, weaker key i transitioned off of more than a decade ago | 17:24 |
*** dtantsur is now known as dtantsur|afk | 17:34 | |
*** ykarel|away has quit IRC | 17:43 | |
*** smrcascao has quit IRC | 17:57 | |
*** mriedem is now known as mriedem_afk | 17:58 | |
*** ekcs has quit IRC | 18:00 | |
*** irclogbot_2 has joined #openstack-release | 18:03 | |
*** zbr|ssbarnea has joined #openstack-release | 18:11 | |
*** witek has quit IRC | 18:13 | |
*** zbr has quit IRC | 18:13 | |
*** e0ne has joined #openstack-release | 18:19 | |
*** jpich has quit IRC | 18:20 | |
*** e0ne has quit IRC | 18:24 | |
*** e0ne has joined #openstack-release | 18:29 | |
openstackgerrit | Erno Kuvaja proposed openstack/releases master: Release python-glanceclient 2.16.0 for Stein https://review.openstack.org/641751 | 18:33 |
*** e0ne has quit IRC | 18:33 | |
smcginnis | fungi: Well, I must have gotten it mostly right - https://sks-keyservers.net/pks/lookup?op=vindex&search=0xcdc08088c3cb45a9be08332b2354069e5b504663&fingerprint=on | 18:38 |
fungi | success! | 18:39 |
*** mriedem_afk is now known as mriedem | 18:40 | |
*** ekcs has joined #openstack-release | 18:41 | |
*** pcaruana has quit IRC | 18:46 | |
openstackgerrit | Julia Kreger proposed openstack/releases master: Release python-ironicclient 2.7.0 for stein https://review.openstack.org/641757 | 18:57 |
openstackgerrit | Julia Kreger proposed openstack/releases master: Release python-ironic-inspector-client 3.5.0 for Stein https://review.openstack.org/641758 | 19:04 |
*** pcaruana has joined #openstack-release | 19:05 | |
openstackgerrit | Merged openstack/releases master: Release Mistral Stein 3 https://review.openstack.org/641632 | 19:10 |
openstackgerrit | Telles Mota Vidal Nóbrega proposed openstack/releases master: Release of all Sahara Plugins 1.0.0.0b1 https://review.openstack.org/641760 | 19:10 |
*** electrofelix has quit IRC | 19:14 | |
openstackgerrit | Merged openstack/releases master: Release Vitrage deliverables https://review.openstack.org/641114 | 19:19 |
openstackgerrit | Merged openstack/releases master: Release manila client 1.27.0 https://review.openstack.org/641642 | 19:19 |
openstackgerrit | Merged openstack/releases master: Release Horizon stein-3 15.0.0.0b2 https://review.openstack.org/641668 | 19:19 |
*** luizbag has quit IRC | 19:28 | |
*** pcaruana has quit IRC | 19:33 | |
*** tellesnobrega has joined #openstack-release | 19:34 | |
*** ekcs has quit IRC | 19:34 | |
tellesnobrega | smcginnis, can you help me understand what is the issue with https://review.openstack.org/#/c/641760/ | 19:34 |
*** armstrong has quit IRC | 19:40 | |
*** ekcs has joined #openstack-release | 19:43 | |
dhellmann | tellesnobrega : the release job is going to want to publish those deliverables to pypi and to do that it tries to verify that it can. That verification is failing because they either don't exist on pypi or the openstackci user does not have permission to publish. | 19:49 |
dhellmann | from checking sahara-plugin-cdh my guess is that they do not exist at all | 19:49 |
tellesnobrega | I don't think they exist on pypi yet | 19:53 |
dhellmann | tellesnobrega : ok, so you should be able to follow the infra manual instructions to fix that: https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases | 20:08 |
openstackgerrit | Andrey Kurilin proposed openstack/releases master: [rally] Release rally-openstack 1.4.0 package https://review.openstack.org/641787 | 20:15 |
*** e0ne has joined #openstack-release | 20:35 | |
*** ifat_afek has joined #openstack-release | 20:38 | |
*** aojea has quit IRC | 20:39 | |
*** ifat_afek has quit IRC | 20:55 | |
*** armax has quit IRC | 21:03 | |
*** e0ne has quit IRC | 21:14 | |
*** whoami-rajat has quit IRC | 21:17 | |
*** mtreinish has quit IRC | 21:25 | |
*** mtreinish has joined #openstack-release | 21:26 | |
*** smrcascao has joined #openstack-release | 21:36 | |
*** waverider has joined #openstack-release | 21:56 | |
*** e0ne has joined #openstack-release | 22:01 | |
*** dave-mccowan has quit IRC | 22:02 | |
*** tosky has quit IRC | 22:22 | |
*** tosky has joined #openstack-release | 22:29 | |
*** cdent has quit IRC | 22:33 | |
*** e0ne has quit IRC | 22:34 | |
*** e0ne has joined #openstack-release | 22:35 | |
*** e0ne has quit IRC | 22:36 | |
*** armax has joined #openstack-release | 22:44 | |
*** waverider has quit IRC | 22:53 | |
*** ekcs has quit IRC | 22:59 | |
*** mriedem is now known as mriedem_away | 23:02 | |
tellesnobrega | dhellmann, thanks | 23:04 |
*** ekcs has joined #openstack-release | 23:05 | |
dhellmann | smcginnis : I wonder if it would be a good idea to automate setting up pypi to register a project if it's not found | 23:11 |
tellesnobrega | dhellmann, apparently it is already | 23:15 |
dhellmann | oh? | 23:15 |
tellesnobrega | tosky pointed out to me that fungi told him that we didn't need to create the projects on pypi because it automagically works from release jobs | 23:16 |
smcginnis | That must have changed. | 23:16 |
smcginnis | I wonder how that can be automated. I suppose if it's all done under the openstackci account it should be able to do all the steps. | 23:16 |
tosky | from December? | 23:16 |
tosky | this is the past discussion: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-12-21.log.html#t2018-12-21T14:12:54 | 23:17 |
smcginnis | fungi: Are you still around? Can you confirm? If so, we will need to remove that check from our validation. | 23:17 |
dhellmann | so we should probably change our validation to pass if the project does not exist on pypi since it can be created properly, but we should continue to check for failure if the project exists and we do not have permission | 23:18 |
smcginnis | ++ Exactly what I was thinking. | 23:18 |
smcginnis | I can grab that if you want/ | 23:18 |
dhellmann | please | 23:19 |
tellesnobrega | what should I do from the sahara point of view? just wait for the update and recheck? | 23:19 |
smcginnis | tellesnobrega: I guess so. | 23:20 |
dhellmann | we could throw up a patch to remove that check, rebase the sahara release on top of it, then add another one to restore it | 23:21 |
dhellmann | that would let us go ahead until we get the more complicated check written | 23:21 |
smcginnis | dhellmann: Looks a little more complicated in that we don't actually check if it exists or not. Do you know if there is a simple pypi API for that to just do a quick check up front. | 23:21 |
dhellmann | it looks like we could use get_pypi_info() to tell if the project exists | 23:23 |
dhellmann | I guess the xmlrpc API just returns an empty list of roles if the project does not exist | 23:23 |
smcginnis | Hmm, is this right? "url = 'https://pypi.org/project/{}/json'.format(canonical_name)" | 23:25 |
smcginnis | Gets a 404 from my test - https://pypi.org/project/oslo.config/json/ | 23:25 |
smcginnis | Shoot, I need to go. I'll check back later. | 23:26 |
tonyb[m] | smcginnis: https://pypi.python.org/pypi/%s/json | 23:27 |
*** ekcs has quit IRC | 23:28 | |
tonyb[m] | Oh that 301's to https://pypi.org/pypi/%s/json | 23:28 |
tonyb[m] | so use that I guess | 23:28 |
tonyb[m] | "curl -s https://pypi.org/pypi/oslo.config/json | jq ." works for me | 23:29 |
dhellmann | yeah, I think someone came through and did a global search and replace of pypi.python.org and we didn't fix the path | 23:30 |
tonyb[m] | well requests etc will handle the 301 | 23:30 |
smcginnis | The path in code is wrong. | 23:31 |
dhellmann | is one of you working on the patches, or should I? | 23:33 |
dhellmann | I have a few minutes before dinner... | 23:33 |
dhellmann | tonyb[m] ? | 23:33 |
*** tosky has quit IRC | 23:34 | |
openstackgerrit | Doug Hellmann proposed openstack/releases master: Release of all Sahara Plugins 1.0.0.0b1 https://review.openstack.org/641760 | 23:35 |
openstackgerrit | Doug Hellmann proposed openstack/releases master: fix URL in get_pypi_info() https://review.openstack.org/641861 | 23:35 |
openstackgerrit | Doug Hellmann proposed openstack/releases master: only fail pypi permission validation if the project exists https://review.openstack.org/641862 | 23:35 |
dhellmann | that should do it ^ | 23:35 |
tellesnobrega | dhellmann, thanks :) | 23:36 |
tonyb | dhellmann: Wow we can create projects? I dind't knwo that I thought they needed to be pre-created and setup | 23:37 |
dhellmann | the only way to create them now is through twine and uploading a package | 23:37 |
dhellmann | so if it doesn't exist, it is created automatically by the release | 23:37 |
tonyb | Huh | 23:37 |
tonyb | #news to me | 23:37 |
dhellmann | that's the error tellesnobrega ran into: these projects don't exist yet, and we're trying to enforce that they do | 23:38 |
dhellmann | ok, it's dinner time here now, so I'm going to drop offline. Feel free to take those patches over if they're broken somehow | 23:38 |
tonyb | dhellmann: enjoy | 23:38 |
openstackgerrit | Merged openstack/releases master: python-neutronclient 6.12.0 (Stein) https://review.openstack.org/641688 | 23:41 |
openstackgerrit | Merged openstack/releases master: Release 1.32.0 of os-client-config https://review.openstack.org/641721 | 23:44 |
openstackgerrit | Merged openstack/releases master: Release 1.31.0 of shade https://review.openstack.org/641716 | 23:44 |
openstackgerrit | Merged openstack/releases master: cliff 2.14.1 https://review.openstack.org/641722 | 23:44 |
openstackgerrit | Eric Fried proposed openstack/releases master: Release os-brick 2.8.0 https://review.openstack.org/641863 | 23:50 |
smcginnis | Back. Thanks for getting those done dhellmann | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!