14:31:21 #startmeeting Pulp Triage 2019-10-08 14:31:21 !start 14:31:21 #info fabricioo0 has joined triage 14:31:21 Meeting started Tue Oct 8 14:31:21 2019 UTC. The chair is fabricioo0. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:21 The meeting name has been set to 'pulp_triage_2019-10-08' 14:31:21 fabricioo0: fabricioo0 has joined triage 14:31:24 #info daviddavis has joined triage 14:31:24 !here 14:31:24 daviddavis: daviddavis has joined triage 14:31:29 #info dkliban has joined triage 14:31:29 !here 14:31:29 dkliban: dkliban has joined triage 14:31:40 #info ttereshc has joined triage 14:31:40 !here 14:31:40 ttereshc: ttereshc has joined triage 14:31:40 !next 14:31:41 fabricioo0: 5 issues left to triage: 5553, 5551, 5546, 5544, 5543 14:31:42 #topic https://pulp.plan.io/issues/5553 14:31:42 RM 5553 - ttereshc - NEW - django-admin collectstatic fails on pulp2-nightly-pulp3-source-centos box 14:31:43 https://pulp.plan.io/issues/5553 14:31:51 #info ipanova has joined triage 14:31:51 !here 14:31:51 ipanova: ipanova has joined triage 14:32:22 i think dalley was hitting this issue ^^ 14:32:26 #info bmbouter has joined triage 14:32:26 !here 14:32:26 bmbouter: bmbouter has joined triage 14:32:44 #info dawalker has joined triage 14:32:44 !here 14:32:44 dawalker: dawalker has joined triage 14:32:55 !propose accept and add to sprint 14:32:55 dkliban: propose accept Propose accepting the current issue in its current state. 14:32:57 rchan: that was also my understanding re #5494 14:33:10 #idea Proposed for #5553: accept and add to sprint 14:33:10 !propose other accept and add to sprint 14:33:10 fabricioo0: Proposed for #5553: accept and add to sprint 14:33:13 +1 14:33:22 +1 14:33:27 #info dalley has joined triage 14:33:27 !here 14:33:27 dalley: dalley has joined triage 14:33:46 #agreed accept and add to sprint 14:33:46 !accept 14:33:46 fabricioo0: Current proposal accepted: accept and add to sprint 14:33:47 fabricioo0: 4 issues left to triage: 5551, 5546, 5544, 5543 14:33:47 #topic https://pulp.plan.io/issues/5551 14:33:48 RM 5551 - jsherril@redhat.com - POST - Importer config can't be null 14:33:49 https://pulp.plan.io/issues/5551 14:34:11 there's a PR so add to sprint? 14:34:12 ttereshc, I was struggling with this and I know what the problem is. not sure how best to fix it 14:34:14 #info mikedep333 has joined triage 14:34:14 !here 14:34:14 mikedep333: mikedep333 has joined triage 14:34:19 5553 I mean 14:34:23 #idea Proposed for #5551: Leave the issue as-is, accepting its current state. 14:34:23 !propose accept 14:34:23 fabricioo0: Proposed for #5551: Leave the issue as-is, accepting its current state. 14:34:42 +1 to accept, it's on the sprint and reviewed, about to merge 14:34:50 +1 14:34:50 cool 14:34:58 #agreed Leave the issue as-is, accepting its current state. 14:34:58 !accept 14:34:58 fabricioo0: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:34:59 fabricioo0: 3 issues left to triage: 5546, 5544, 5543 14:35:00 #topic https://pulp.plan.io/issues/5546 14:35:00 RM 5546 - jsherril@redhat.com - NEW - migration plan creation expects 'plan' to be pre-serialized within bindings 14:35:02 https://pulp.plan.io/issues/5546 14:35:39 dalley, feel free to comment onthe issue if you know what the problem is 14:35:56 let's accept this one and add to sprint 14:36:02 it's an OpenAPI schema problem 14:36:32 agreed +1 14:36:34 #idea Proposed for #5546: accept and add to sprint 14:36:34 !propose other accept and add to sprint 14:36:34 fabricioo0: Proposed for #5546: accept and add to sprint 14:36:34 dkliban, I wonder if jsherrill uses jsonfield anywhere else 14:36:47 I don't think it's plugin specific 14:37:09 +add bindings tag 14:37:24 ttereshc: drf_yasg just released support for the json field 14:37:32 so we need to see how old the bindings are that he is using 14:37:54 i think newer version should have different behavior 14:38:07 ok 14:38:45 +1 to accepting 14:38:48 #agreed accept and add to sprint 14:38:48 !accept 14:38:49 fabricioo0: Current proposal accepted: accept and add to sprint 14:38:49 #topic https://pulp.plan.io/issues/5543 14:38:50 fabricioo0: 1 issues left to triage: 5543 14:38:51 RM 5543 - daviddavis - NEW - Get a KeyError when using the `fields` parameter 14:38:52 https://pulp.plan.io/issues/5543 14:39:01 accept and add to sprint I think 14:39:14 #idea Proposed for #5543: accept and add to sprint 14:39:14 !propose other accept and add to sprint 14:39:14 fabricioo0: Proposed for #5543: accept and add to sprint 14:39:30 +1 14:39:33 +1 14:39:54 #agreed accept and add to sprint 14:39:54 !accept 14:39:54 fabricioo0: Current proposal accepted: accept and add to sprint 14:39:55 fabricioo0: No issues to triage. 14:40:01 Open floor! 14:42:07 one more call for feedback on the discussion on pulp-dev from @daviddavis 14:42:28 https://www.redhat.com/archives/pulp-dev/2019-October/msg00029.html 14:42:41 bmbouter++ 14:42:41 daviddavis: bmbouter's karma is now 198 14:43:05 daviddavis: I think we would benefit froma timeline on that request 14:43:07 * dkliban looks 14:43:20 bmbouter: there's a deadline 14:43:23 in the email 14:43:25 tomorrow 14:43:35 indeed, perfect 14:43:39 daviddavis++ 14:43:39 bmbouter: daviddavis's karma is now 233 14:43:48 heck yea, I learned to add deadlines 14:44:10 yeah .... so this is a great plan 14:44:20 i'll send my +1 to the list 14:44:24 cool 14:45:40 in looking through the 3.0 blockers list one issue that could use some discussion is 5378 https://pulp.plan.io/issues/5378 14:46:06 yeah ... this is a tough one 14:46:08 if this is too much for open floor lmk but I can try to recap the situation 14:46:31 what is tough is coming up with a solution 14:46:36 the crux of the issue is the content we store is not exportable, 5378 doesn't really capture that aspect 14:47:02 nope 14:47:35 this kind of reminds me that we should make sure we have downloading content from pulp performance tested. because each file downloaded requires a DB query 14:47:39 last call for open floor! 14:47:55 I think it was, at least a little bit, but I don't know if the scale represented real-world usage 14:47:58 i think we are still discussing 14:48:44 the main issue is that a Publication cannot be exported to disk currently 14:49:06 bmbouter: i don't quite follow the logic 14:49:06 because in our DB you can have content that both is a directory for other content, and yet is a file itself 14:49:18 I wrote some about this here https://pulp.plan.io/issues/5086#note-24 14:49:58 say you have content at relative path /A and it actually serves data when the user requests /A 14:50:05 bmbouter: i think these are related issues, but not the same use cas 14:50:07 e 14:50:09 and there is also other content at /A/B 14:50:28 dkliban: I agree they aren't the same, but if we solve ^ then we'll also have the solution for the former 14:50:47 cool. so i think we should work on these in that order 14:51:02 agreed. the relatedness can be seen around /A for example 14:51:06 i would rather solve 5086 first 14:51:56 in terms of 5086, we need to have some sort of validation for publication creation ... or for repository version creation or both? 14:51:56 we can do 5086 first that sounds good 14:52:19 and we just talked about having validation for repository version creatino 14:53:06 I think it'll take more than validation 14:53:34 if it owuld be helpful for me to write up one option for a solution instead of slow rolling the description here I could do that too 14:53:58 go for it please 14:54:02 yeah ... that would be helpful 14:54:02 I want to respond to 5086 too 14:54:11 I am still not convinced we should address it for 3.0 GA 14:54:35 then maybe we should talk here more? 14:54:55 sure 14:55:28 I don't see the issue with having a plugin implement it first I guess 14:55:34 the issue is that our DB format isn't exportable and that's a GA backwards incompatability issue preventing exports 14:55:37 ofc it won't be available to all plugins 14:56:05 right but the issue is in core's data layout the plugin couldn't work around that 14:56:29 that's a separate issue though 14:56:33 I can discuss that if you'd like 14:57:28 that would be good. currently I see the current data format incompatability with POSIX as a GA blocker 14:57:56 these issues kind of derivatives of that concern (for me) 14:58:08 sure, I think that is actually a bug and could be fixed post-GA but I also think we could fix that before GA too without having to fix 5086 14:58:39 I believe that we need to solve /a /a/b problem before GA 14:58:48 that's fine with me 14:59:05 I just worry that we're going to rush the exporter code before GA and we'll have to live with it forever 15:00:46 daviddavis: I can see that point, we could mark it tech preview similar to S3 I'm comfortable w/ that 15:00:47 bmbouter: that sounds like a good compromise 15:00:56 cool ... let's discuss more on the issue 15:00:58 my main interest is the /a /a/b issue though, how can we work towards a resolution on that? 15:01:03 yep ... same here 15:01:10 can we file that as a separate issue? 15:01:11 I'm wondering if a separate issue would bring more clarity to that? 15:01:17 +1 15:01:26 great 15:01:30 I could, I think I could write the problem statement up clearly/briefly along with at least one idea to get us started 15:01:44 sounds good 15:01:45 +1 15:02:00 I'll do that and send it to pulp-dev as an advertisement for those interested 15:02:06 thank you 15:02:17 bmbouter++ 15:02:17 ttereshc: bmbouter's karma is now 199 15:02:40 will do! 15:03:01 that's the only open floor item I wanted to touch on ... others? 15:03:20 mikedep333 is this PR ok? https://github.com/pulp/pulp-rpm-prerequisites/pull/13 15:04:00 ttereshc, https://pulp.plan.io/issues/5553#note-2 15:04:49 should I end the triage? Or we have more items for open floor? 15:05:29 fabricioo0: maybe ask for last call? 15:05:33 or maybe that was :) 15:06:41 iballou: commented / approved 15:06:44 #endmeeting 15:06:44 !end