14:31:08 #startmeeting Pulp Triage 2020-06-19 14:31:08 !start 14:31:08 #info fao89 has joined triage 14:31:08 Meeting started Fri Jun 19 14:31:08 2020 UTC. The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:31:08 The meeting name has been set to 'pulp_triage_2020-06-19' 14:31:08 fao89: fao89 has joined triage 14:31:16 #info bmbouter has joined triage 14:31:16 !here 14:31:16 bmbouter: bmbouter has joined triage 14:31:29 !friday 14:31:29 ♪ It's Friday, Friday, gotta get down on Friday ♪ 14:31:34 * bmbouter sings it 14:31:36 * bmbouter dances 14:31:45 #info mikedep333 has joined triage 14:31:45 !here 14:32:10 !next 14:32:11 #topic https://pulp.plan.io/issues/7003 14:32:11 fao89: 6 issues left to triage: 7003, 7002, 6992, 6990, 6989, 6972 14:32:12 RM 7003 - dkliban@redhat.com - NEW - pulpcore-content allows for // in some parts of the URL but not others 14:32:13 https://pulp.plan.io/issues/7003 14:32:18 #info x9c4 has joined triage 14:32:18 !here 14:32:19 #info daviddavis has joined triage 14:32:19 !here 14:32:28 #info ipanova has joined triage 14:32:28 !here 14:32:36 #info dkliban has joined triage 14:32:36 !here 14:32:40 i think we shouhld accept 14:32:45 +1 14:32:49 #idea Proposed for #7003: Leave the issue as-is, accepting its current state. 14:32:49 !propose accept 14:32:50 fao89: Proposed for #7003: Leave the issue as-is, accepting its current state. 14:32:58 but we need to decide what the desired bheavior should be before putting it on the sprint 14:33:02 why isn't pulpbot saying we joined triage 14:33:10 #info dalley has joined triage 14:33:10 !here 14:33:10 dalley: dalley has joined triage 14:33:13 !here 14:33:17 weird 14:33:21 hahahahaha 14:33:24 don't worry 14:33:25 +1 14:33:27 daviddavis: he gives us a day off 14:33:30 hehe 14:33:31 daviddavis is a ghost 14:33:33 it will show you as joined in the logs 14:33:39 dalley: will do all the work :-P 14:33:56 if we can't decide now on the behavior can we skip? 14:33:59 +1 to accept 14:34:03 and discuss more on the issue 14:34:15 sure 14:34:16 otherwise it'll go to backlog and likely not come back 14:34:23 ok. let's skip for right now 14:34:25 bmboute: fine by me 14:34:56 !skip 14:34:57 #topic https://pulp.plan.io/issues/7015 14:34:57 fao89: 6 issues left to triage: 7015, 7002, 6992, 6990, 6989, 6972 14:34:59 RM 7015 - wibbit - NEW - Ability to link Repository with Remote 14:35:00 https://pulp.plan.io/issues/7015 14:35:38 I think it makes sense 14:35:39 thisis a story 14:35:42 this is a story. I'd like to work on moving this forward. 14:36:03 it should be really straightforwards though 14:36:10 #idea Proposed for #7015: convert to story 14:36:10 !propose other convert to story 14:36:10 fao89: Proposed for #7015: convert to story 14:36:15 +! 14:36:17 +1 14:36:17 I agree it's time, we should have a plan written onto it 14:36:30 I'm interested to groom if you wrote daviddavis 14:36:31 +1 14:36:35 ok cool 14:36:39 ty 14:36:51 #agreed convert to story 14:36:51 !accept 14:36:51 fao89: Current proposal accepted: convert to story 14:36:52 fao89: An error has occurred and has been logged. Please contact this bot's administrator for more information. 14:37:09 !accept 14:37:11 fao89: No action proposed, nothing to accept. 14:37:16 !next 14:37:17 #topic https://pulp.plan.io/issues/7002 14:37:17 fao89: 5 issues left to triage: 7002, 6992, 6990, 6989, 6972 14:37:18 RM 7002 - dkliban@redhat.com - NEW - Streamed responses don't appear in the access_log of the pulpcore-content app 14:37:20 https://pulp.plan.io/issues/7002 14:37:49 #info ttereshc has joined triage 14:37:49 !here 14:37:49 ttereshc: ttereshc has joined triage 14:37:51 i'd like us to accept and add to sprint 14:38:08 this makes it hard to troubleshoot things for on demand content 14:38:20 +1 14:38:22 +1 14:38:30 pulpbot caught coronavirus 14:38:30 dalley: Error: "caught" is not a valid command. 14:38:38 #idea Proposed for #7002: accept and add to sprint 14:38:38 !propose other accept and add to sprint 14:38:38 fao89: Proposed for #7002: accept and add to sprint 14:38:38 lol 14:38:57 #agreed accept and add to sprint 14:38:57 !accept 14:38:57 fao89: Current proposal accepted: accept and add to sprint 14:38:58 #topic https://pulp.plan.io/issues/6992 14:38:58 fao89: 4 issues left to triage: 6992, 6990, 6989, 6972 14:39:00 RM 6992 - wibbit - NEW - Documentation Error - Default Admin user 14:39:01 https://pulp.plan.io/issues/6992 14:39:20 accept and add to sprint 14:39:25 and add docs tag 14:39:29 we need to explicitly tell users to set the password 14:39:30 #idea Proposed for #6992: accept and add to sprint 14:39:30 !propose other accept and add to sprint 14:39:30 fao89: Proposed for #6992: accept and add to sprint 14:39:31 +1 14:39:40 +1 14:39:46 this is a bit confusing, I think the installer sets this? 14:39:55 but the docs we document are for the "manual install" 14:40:05 yep 14:40:13 and actually this link is to neither ... 14:40:30 so to me this is about install docs more than authentication docs, wdyt? 14:41:00 bmbouter: there is a warning box there 14:41:06 and that warning box has incorrect info 14:41:18 under the Basic Authentication section 14:41:32 we need to remove the sentence that says that the password defaults to 'password' 14:41:32 the instller sets this correctly https://github.com/pulp/pulp_installer/blob/6ca8a78197bb96597521bf9da7b1b6775e10fc57/roles/pulp_database/tasks/main.yml#L35 14:41:52 * bmbouter looks at our pulpcore install docs 14:42:10 bmbouter: do you see the warning box that i am talking about? 14:42:18 step 9 says to run it https://docs.pulpproject.org/installation/instructions.html 14:42:29 dkliban: I don't 14:42:37 * bmbouter goes to that section 14:42:40 https://docs.pulpproject.org/installation/authentication.html#basic-authentication 14:42:57 mmmmm yeah that is wrong 14:42:59 "but defaults to 'password'" needs to be removed 14:43:11 that's what this ticket is about 14:43:11 Wait, are those manual install (not pulp_installer) section of the instructions? 14:43:13 we have no default password 14:43:32 mikedep333: https://docs.pulpproject.org/installation/instructions.html are the "manual" instructions 14:43:48 It's under "API Authtentication" actually ,so no. 14:43:49 our install docs are messy :/ 14:44:22 so w.r.t to the bug, the issue is that warning box? 14:44:36 yes 14:44:36 and the claim that we have a defualt password (which is not true) 14:44:39 yes 14:44:48 i'll comment on the issue 14:44:54 +1 to accept add to sprint 14:44:56 i discussed it with wibbit 14:45:06 #agreed accept and add to sprint 14:45:06 !accept 14:45:06 fao89: Current proposal accepted: accept and add to sprint 14:45:08 #topic https://pulp.plan.io/issues/6990 14:45:08 fao89: 3 issues left to triage: 6990, 6989, 6972 14:45:10 RM 6990 - ttereshc - NEW - Concepts page gives a wrong impression that repositories are not typed 14:45:11 https://pulp.plan.io/issues/6990 14:45:13 dkliban: ty 14:46:27 I think this is mostly the pictures bein misleading and having no text stating otherwise. 14:46:31 agreed 14:46:39 and we could have better diagrams 14:47:13 i think we just did not d oa good job to keep up to date the docs and diagrams after we introduced types repos 14:47:15 #idea Proposed for #6990: Leave the issue as-is, accepting its current state. 14:47:15 !propose accept 14:47:19 agreed 14:47:21 +1 14:47:26 The diagrams are not wrong, but one shows two different content types and the next one adds two pieces of content to a repo. 14:47:31 +1 14:47:36 #idea Proposed for #6990: Leave the issue as-is, accepting its current state. 14:47:36 !propose accept 14:47:43 +1 14:47:46 +1 14:47:53 pulpbot is crazy 14:47:53 fao89: Error: "is" is not a valid command. 14:47:57 lol 14:48:00 #idea Proposed for #6990: Leave the issue as-is, accepting its current state. 14:48:00 !propose accept 14:48:00 fao89: Proposed for #6990: Leave the issue as-is, accepting its current state. 14:48:04 finally! 14:48:13 #agreed Leave the issue as-is, accepting its current state. 14:48:13 !accept 14:48:13 fao89: Current proposal accepted: Leave the issue as-is, accepting its current state. 14:48:14 #topic https://pulp.plan.io/issues/6989 14:48:14 fao89: 2 issues left to triage: 6989, 6972 14:48:15 RM 6989 - jsherril@redhat.com - NEW - cert auth does not work with current binding gems 14:48:16 https://pulp.plan.io/issues/6989 14:48:37 certs nightmare 14:48:53 this one is from yesterday's scrum 14:49:02 !propose other accept and add to sprint 14:49:02 #idea Proposed for #6989: accept and add to sprint 14:49:03 fao89: Proposed for #6989: accept and add to sprint 14:49:39 +1 14:50:11 #agreed accept and add to sprint 14:50:11 !accept 14:50:11 fao89: Current proposal accepted: accept and add to sprint 14:50:12 #topic https://pulp.plan.io/issues/6972 14:50:12 fao89: 1 issues left to triage: 6972 14:50:13 RM 6972 - fao89 - NEW - Clients should verify pulpcore/plugins versions 14:50:14 https://pulp.plan.io/issues/6972 14:50:33 this is a story 14:50:35 or a task 14:50:55 I think story, it's a user visible claim of functionality 14:51:06 +1 to a story 14:51:09 #idea Proposed for #6972: convert to a story 14:51:09 !propose other convert to a story 14:51:09 fao89: Proposed for #6972: convert to a story 14:51:14 also add bindings tag 14:51:17 when we implement this jsherrill won't be able to mix versions in some situations like is currently happening 14:51:22 +1 tho 14:51:41 #agreed convert to a story 14:51:41 !accept 14:51:41 fao89: Current proposal accepted: convert to a story 14:51:42 fao89: No issues to triage. 14:52:13 Open floor - https://hackmd.io/@pulp/triage/edit 14:52:23 it's time for the weekly redmine simplification! 14:52:33 * daviddavis cheers wildly 14:52:37 lol 14:52:57 bmbouter simplifies wildly 14:53:13 first topic? 14:53:30 Redmine Simplification 1: Delete the ‘External’ Redmine project. It’s no longer used and 100% of issues are in CLOSED. 14:53:37 +1 14:53:42 +1 14:53:49 +1 14:54:06 I can implement whatever of these we want to do, just after this meeting 14:54:12 Redmine Simplification 2: Configure Redmine to not show the Due Date, Start Date, and Estimated Time fields for all projects. They are unused. 14:54:19 +1 14:54:22 +1 14:54:23 +1 14:54:25 so we don't want to track any external effort in redmine? 14:54:30 ever? 14:55:02 I imagine if it's easy to configure it to not be shown, it's easy to configure it to be added back 14:55:09 ttereshc: occassionally there are external things but if they don't track back to an upstream user-visible thing then I don't think we shoiuld 14:55:33 for example kickstarts in debian were not working, the fix wasn't in pulp it was in yarl, we opened https://pulp.plan.io/issues/4725 and linked to the upstream issue 14:56:00 it used to be quite useful to track what is blocking our tasks and where our time goes 14:56:18 bmbouter, and what if it's your contribution to a different project? 14:56:31 time tracking for who though? 14:56:55 the scrum status is how paid time is tracked is my belief 14:57:02 just to see that your time during the sprint goes to other project 14:57:05 ok 14:57:10 works for me, just asking 14:57:21 it was the reasonto create this project in the first place 14:57:23 no problem in the discussion at all 14:57:42 yeah I think it comes out of exactly what you're brinigng up, using redmine as a time tracking tool for employees 14:57:56 and to me thats one of the reaosns I propose removing it because I don't think that's what redmine is for 14:58:24 in theory it might help with time estimation to complete a task if your other task depends on this external contribution of yours 14:59:01 we can move on, I'm not against removing, just trying to make sure that it won't be useful 14:59:17 who has used it recently>? 14:59:27 it feels like we often create things,then remove and then add back :) 14:59:31 lol 15:00:05 so my goal with all of this is to take the user view 15:00:22 "not being used" is a good indicator that no one would miss it... 15:00:27 as a user, this area of redmine doesn't have a place for me 15:00:39 fair enough 15:01:01 ttereshc: I like how you're questioning it though, we need everyone to speak up to make sure our collective actions are right 15:01:11 I really value that 15:01:19 +1 to that 15:01:39 I appreciate the discussion as well :) 15:02:01 i hope pulp-bot is counting in its head 15:02:06 for the start and due dates - one needs this if wants to use the Gantt chart 15:02:10 pulpbot does not like you ttereshc 15:02:10 fao89: Error: "does" is not a valid command. 15:02:13 he's not so good at math anymore 15:02:21 it's reciprocal 15:02:40 pulpbot does not like itself today. 15:02:41 x9c4: Error: "does" is not a valid command. 15:02:44 lol 15:02:55 ttereshc++ 15:02:55 fao89: ttereshc's karma is now 194 15:03:00 \o/ 15:03:01 there we go 15:03:06 pbot woke up 15:03:14 !friday 15:03:14 ♪ It's Friday, Friday, gotta get down on Friday ♪ 15:03:29 so I tried to use gantt chart for rpm roadmap and it's very laborious to maintain that 15:03:49 yup I remember that 15:04:02 I'm +1 to remove those fields but I'm just highlighting what they are for 15:04:36 again, not being used: +1 15:04:58 +1 15:05:31 +1 15:05:43 +1 15:06:18 not sure if we should go to simplification 2 or 3 15:06:34 I think we just did (2) 15:06:34 Redmine Simplification 2: Configure Redmine to not show the Due Date, Start Date, and Estimated Time fields for all projects. They are unused. 15:06:43 Redmine Simplification 3: Remove the ‘Target Release - Deployment’ field. It was never used. It originally was for the “puppet installer” from many years ago, which is now not even an active Redmine project. 15:06:43 i think 3 15:06:51 +1 15:06:59 +1 15:07:01 (3) and (4) are very related both on the same thing 15:07:15 Redmine Simplficiation 4: Remove the ‘Versions - Deployment’ same reasoning as above, never used. 15:07:17 do we need any "Target Release *" fields? 15:08:14 not that i can recall 15:08:55 I mean the one which is just "Target Release" is used in the pulp2 release process but I don't think any other are used 15:09:12 ttereshc: exactly 15:09:21 yeah 15:09:37 i think we should keep target release but not all the otehr versions of it 15:10:01 and then when we stop releasing pulp 2 all together we can remove target release also 15:10:04 so hopefully soon 15:10:14 this is specifically for the puppet one... 15:10:38 let's remove the puppet one 15:10:38 all the other target releases I'm not going to make a proposal on until pulp2 is fully never going to release (so a while from now) 15:10:50 the puppet one has exactly one entry 'master' 15:10:55 lol 15:10:57 yup 15:11:18 ttereshc: not only do we take stuff away and bring it back, we introduce things and never use them lol 15:11:35 yess, we are very versatile 15:11:40 many agile 15:11:42 very wow 15:12:37 so yeah scope-wise proposal (3) and (4) are only for the puppet installer which has been deprecated for I think 36 months+ 15:13:02 I think there is an agreement to remove those 15:13:18 +1 15:14:17 topic: Users are confused as to where to file “pulpcore” issues 15:14:42 this was just an observation. not sure if/how we can fix this. 15:15:01 of course pulpcore issues go in the Pulp project but that's not necessarily obvious. 15:15:15 more helpful docs? 15:15:15 * bmbouter checks redmine 15:15:38 is it bad to rename it to pulpcore? 15:15:45 Also the pulp project in redmine is not in a prominent place. 15:15:49 we could update the landing page text at the top of here: https://pulp.plan.io/projects/pulp 15:16:08 +1 15:16:17 I think we could rename s/Pulp/pulpcore/ also it lets us change that setting 15:16:24 +1 15:16:35 +1 to s/Pulp/pulpcore/ 15:16:49 I can handle both of these things pretty easily 15:16:50 I thought about that and the only misgiving I have is that we also file issues for stuff like the installer in the Pulp project 15:17:00 good point 15:17:03 yup, exactly my only concern 15:17:05 I was going to have the home page describe that some too 15:17:14 but we can also not s/Pulp/pulpcore/ 15:17:30 I could go either way on renameing s/Pulp/pulpcore/ honestly 15:17:46 let's maybe just update the landing page for now 15:17:51 are there aliases in redmine? 15:18:02 there are not, but I don't think it would change the url slug 15:18:06 so both pulp and pulpcore lead to the same project :) 15:18:15 true 15:18:15 nope :( 15:18:26 s/Pulp/pulpcore and installer/ ? 15:18:30 lol 15:18:57 current description points to the pulpcore github repo, so I'm not sure updating a landing page will help but we can try 15:19:10 oh 15:19:31 Can we make it that a user who does not not know files against pulp by default? 15:19:50 We can easily move issues later 15:19:52 I can update the Pulp project description at https://pulp.plan.io/projects/pulp/settings 15:20:09 daviddavis: +1 15:20:15 x9c4: that would be great if it's feasible 15:20:20 +1 to update the description 15:21:01 let's update the description today and think about other changes in the future? 15:21:26 +1 15:21:44 "pulpcore and installer" isn't entirely accurate since there are other projects like plugin_template and potentially the cli 15:22:10 altho pulpcore and the installer are the big repos in the project 15:23:40 hmmm ... maybe the installer should have it's own project? 15:23:47 is that too controvercial? 15:24:01 I checked our docs about bug reporting and our topic on #pulp channel, all point to pulp project to file issues, so I'm not sure where/what we can change 15:24:26 I think at least the description would be good 15:25:18 +1 15:25:22 +1 15:25:27 ok we have five min left, let's just update the description for now 15:25:40 I can do that unless bmbouter you want to 15:25:59 daviddavis: it would be cool if you did I'll do the other AIs form 1-4 15:26:11 +1 15:26:20 ty 15:26:40 the last item from open floor is an issue in import/export I could use some feedback on 15:26:54 https://hackmd.io/bI4Pc9fTRfGNAH_d6ASX4Q?view 15:27:02 it's how to model the code for DistributionTrees given that it's a content unit with content 15:27:31 I'm hoping maybe some people could look at it today but not necessarily right now 15:27:41 I can bring it up again monday though 15:28:27 that's all I got 15:28:32 I can give it a read 15:28:43 just what's on this hack is that the ask? 15:28:46 or also code? 15:30:04 I feel like I need a bit more background on what is possible to do with current export functionality to help in any way ;/ 15:30:05 yea 15:30:15 I have to learn more about export 15:30:15 it's about which solution and there's an open question 15:30:20 ha 15:30:25 ok, maybe I'll set up a meeting 15:30:31 I'm off to a meeting 15:31:03 oh me too 15:31:28 daviddavis: sounds good 15:31:36 without context I think export could mimic publish, as it gets subrepos from the distribution tree 15:34:30 is this the end of open floor? 15:34:56 !end 15:34:56 #endmeeting