| *** tosky has quit IRC | 00:34 | |
| *** jamesmcarthur has joined #storyboard | 00:35 | |
| *** jamesmcarthur has quit IRC | 00:40 | |
| *** jamesmcarthur has joined #storyboard | 00:52 | |
| *** jamesmcarthur has quit IRC | 00:56 | |
| *** jamesmcarthur has joined #storyboard | 01:04 | |
| *** jamesmcarthur has quit IRC | 02:56 | |
| *** jamesmcarthur has joined #storyboard | 03:02 | |
| *** jamesmcarthur has quit IRC | 03:25 | |
| *** jamesmcarthur has joined #storyboard | 03:56 | |
| *** jamesmcarthur has quit IRC | 04:03 | |
| *** jamesmcarthur has joined #storyboard | 04:30 | |
| *** udesale has joined #storyboard | 04:30 | |
| *** jamesmcarthur has quit IRC | 04:35 | |
| *** jamesmcarthur has joined #storyboard | 05:05 | |
| *** jamesmcarthur has quit IRC | 05:10 | |
| *** zbr|ssbarnea has joined #storyboard | 05:14 | |
| *** zbr has quit IRC | 05:16 | |
| *** udesale has quit IRC | 05:45 | |
| *** udesale has joined #storyboard | 05:55 | |
| *** jamesmcarthur has joined #storyboard | 06:07 | |
| *** jtomasek has joined #storyboard | 06:07 | |
| *** jamesmcarthur has quit IRC | 06:11 | |
| *** jtomasek has quit IRC | 06:27 | |
| *** jamesmcarthur has joined #storyboard | 06:44 | |
| *** jamesmcarthur has quit IRC | 06:48 | |
| *** jtomasek has joined #storyboard | 06:57 | |
| *** jmccrory has quit IRC | 07:06 | |
| *** jmccrory has joined #storyboard | 07:06 | |
| *** udesale has quit IRC | 07:15 | |
| *** jtomasek has quit IRC | 07:18 | |
| *** jtomasek has joined #storyboard | 07:18 | |
| *** udesale has joined #storyboard | 07:20 | |
| *** jamesmcarthur has joined #storyboard | 08:45 | |
| *** jamesmcarthur has quit IRC | 08:50 | |
| *** tosky has joined #storyboard | 08:56 | |
| *** jpich has joined #storyboard | 08:58 | |
| *** jamesmcarthur has joined #storyboard | 10:46 | |
| *** jamesmcarthur has quit IRC | 10:51 | |
| *** udesale has quit IRC | 11:17 | |
| *** jpich has quit IRC | 12:27 | |
| *** jpich has joined #storyboard | 12:27 | |
| *** jamesmcarthur has joined #storyboard | 12:45 | |
| *** jamesmcarthur has quit IRC | 12:50 | |
| *** tosky has quit IRC | 13:44 | |
| *** jtomasek has quit IRC | 14:04 | |
| *** jtomasek has joined #storyboard | 14:05 | |
| *** jtomasek has quit IRC | 14:08 | |
| *** jtomasek has joined #storyboard | 14:08 | |
| *** jtomasek has quit IRC | 14:44 | |
| *** diablo_rojo has joined #storyboard | 15:19 | |
| *** jamesmcarthur has joined #storyboard | 15:26 | |
| *** zbr has joined #storyboard | 15:46 | |
| *** zbr|ssbarnea has quit IRC | 15:47 | |
| *** udesale has joined #storyboard | 15:48 | |
| *** jtomasek has joined #storyboard | 15:59 | |
| *** tosky has joined #storyboard | 16:11 | |
| *** zbr|ssbarnea has joined #storyboard | 16:11 | |
| *** zbr has quit IRC | 16:13 | |
| *** zbr has joined #storyboard | 16:24 | |
| *** zbr|ssbarnea has quit IRC | 16:26 | |
| *** jamesmcarthur has quit IRC | 16:34 | |
| *** jtomasek has quit IRC | 16:35 | |
| *** jpich has quit IRC | 16:36 | |
| *** jpich has joined #storyboard | 16:36 | |
| *** jpich has quit IRC | 16:39 | |
| *** jpich has joined #storyboard | 16:39 | |
| *** jpich has quit IRC | 16:44 | |
| *** jamesmcarthur has joined #storyboard | 16:46 | |
| *** udesale has quit IRC | 17:04 | |
| *** jamesmcarthur has quit IRC | 17:24 | |
| *** jamesmcarthur_ has joined #storyboard | 17:25 | |
| *** jamesmcarthur_ has quit IRC | 17:27 | |
| -openstackstatus- NOTICE: Any changes failed around 16:30 UTC today with a review comment from Zuul like "ERROR Unable to find playbook" can be safely rechecked; this was an unanticipated side effect of our work to move base job definitions between configuration repositories. | 17:29 | |
| *** jamesmcarthur has joined #storyboard | 17:35 | |
| fungi | note i'm around for a meeting at 1900z today if anyone else is game | 18:07 |
|---|---|---|
| fungi | there is a new xenial-based storyboard01.opendev.org server deployed which we can repoint the storyboard.openstack.org dns name to as soon as i get a moment, and then i'll take a brief several-minute outage to move the db onto the new server while dns changes propagate | 18:09 |
| fungi | i also bumped its ram from 4gb to 8gb in hopes of improving performance for the local db | 18:10 |
| fungi | we'll see if it helps at all | 18:10 |
| fungi | i've also updated https://etherpad.openstack.org/p/gCj4NfcnbW with a revised migration plan now that i've worked through the kinks with the dev server | 18:39 |
| SotK | I'll be around, though I might be a couple of minutes late | 18:48 |
| fungi | no worries. we usually don't need the whole hour anyway | 18:48 |
| diablo_rojo | I am also around for a meeting. | 18:53 |
| diablo_rojo | I will try to update the agenda quick | 18:53 |
| diablo_rojo | SotK, I updated the agenda | 18:58 |
| diablo_rojo | Assuming you want to meet today? | 18:58 |
| SotK | thanks :) | 19:06 |
| *** jungleboyj has joined #storyboard | 19:18 | |
| jungleboyj | fungi: What is the state of storyboard-dev. Trying to do some development on it and hitting all kinds of http 500 errors. | 19:19 |
| *** enriquetaso has joined #storyboard | 19:19 | |
| fungi | jungleboyj: interesting. it should be functional. checking (but also the weekly sb meeting is underway right this moment) | 19:20 |
| jungleboyj | fungi: Ok. Won't interrupt now. Have a list of bugs we may need to open. | 19:20 |
| fungi | jungleboyj: i'm able to log into it and browse around so far | 19:20 |
| jungleboyj | We can do that too but when I try to create a 'Worklist' on the 'Cinder Board' I created it throws an HTTP 500. | 19:21 |
| fungi | did you maybe reuse an open tab to it from a few weeks ago? we completely moved the server hosting that deployment | 19:21 |
| fungi | ahh | 19:21 |
| jungleboyj | Nope, just opened the tab yesterday. | 19:21 |
| fungi | thanks, details help | 19:22 |
| fungi | so on https://storyboard-dev.openstack.org/#!/board/127 i guess? | 19:22 |
| jungleboyj | I have a bug: https://storyboard.openstack.org/#!/story/2004948 | 19:22 |
| *** whoami-rajat has joined #storyboard | 19:23 | |
| fungi | thanks. that helps! | 19:23 |
| jungleboyj | fungi: Yep. | 19:23 |
| *** jamesmcarthur has quit IRC | 19:55 | |
| fungi | looking at the sql error from the story, the board_worklists table definitely has a list_id column and every existing row has an integer value populated | 20:15 |
| fungi | is it possible we were previously relying on an auto-increment there or something? | 20:15 |
| fungi | i've appended the full tracebacks in a comment on https://storyboard.openstack.org/#!/story/2004948 | 20:32 |
| *** dtantsur is now known as dtantsur|afk | 20:39 | |
| *** jamesmcarthur has joined #storyboard | 20:41 | |
| *** jamesmcarthur has quit IRC | 20:41 | |
| *** jamesmcarthur has joined #storyboard | 20:42 | |
| *** enriquetaso has quit IRC | 21:04 | |
| jungleboyj | fungi: Can I ask a couple other questions we came up with today? | 21:08 |
| diablo_rojo | jungleboyj, you can ask any of us :) | 21:09 |
| diablo_rojo | SotK, and I are around too. | 21:09 |
| jungleboyj | Ok. | 21:09 |
| jungleboyj | So, We were looking at the security bug option. There is a option to mark something as a security issue but then we need to add a user. | 21:10 |
| jungleboyj | Is that the VMT group? | 21:10 |
| jungleboyj | If so, I didn't see anywhere that is documented and the VMT group isn't in storyboard-dev | 21:11 |
| diablo_rojo | It doesn't have a default group. You are supposed to add people/groups by hand at this point. | 21:11 |
| diablo_rojo | I think it exists, but I don't remember exactly what the name of it is. | 21:12 |
| * diablo_rojo tries to find it | 21:12 | |
| jungleboyj | Ugh. So, there is a vmt group but | 21:12 |
| jungleboyj | I think we need to have something defined if that is the process. | 21:12 |
| diablo_rojo | The plan is to create groups for each projects coresec | 21:12 |
| diablo_rojo | They aren't currently created for all projects yet though. | 21:13 |
| jungleboyj | Ok. I don't see any coresec groups out there. | 21:14 |
| diablo_rojo | The creation/edit of groups is an admin feature at this point if I recall | 21:14 |
| diablo_rojo | Doable though obviously | 21:15 |
| jungleboyj | Ok, I will open a bug about that. | 21:15 |
| jungleboyj | Is there any plan to handle duplicate bugs? I think the answer to that was no? | 21:15 |
| diablo_rojo | Bug for what exactly? THat the cinder corsesec group isnt there yet? | 21:16 |
| diablo_rojo | I don't think that needs a bug :) | 21:16 |
| jungleboyj | diablo_rojo: That there is no documentation that I can find that explains how to handle a security bug in sotryboard. | 21:16 |
| diablo_rojo | There isn't a defined plan atm, but its something on our radar | 21:16 |
| diablo_rojo | At that point we add the cinder coresec group, you can set up a template story and have the private box checked and the cinder coresec group added and link that in documentation whereever you need. | 21:17 |
| diablo_rojo | You want docs about general handling of security bugs though? | 21:17 |
| diablo_rojo | Easy addition. | 21:18 |
| diablo_rojo | What else you got? :) | 21:19 |
| jungleboyj | I am trying to get the Cinder team on board with moving here and they are stuck on the lack of a way to handle security bugs. They are grumbling about no attachments but I have moved pass that. I am trying to sell this but ... | 21:22 |
| jungleboyj | So, I think if we can at least get some documentation around the security part that will help. | 21:23 |
| jungleboyj | The other question was about if there was going to be a way to mark a bug as duplicate. | 21:23 |
| diablo_rojo | Attachments are being implemented right now so that shouldn't be on the list of concerns | 21:24 |
| diablo_rojo | And there definitely are ways to handle private bugs. If you my assurances aren't enough, perhaps fungi can speak to your concerns. | 21:24 |
| diablo_rojo | *if my assurances | 21:25 |
| diablo_rojo | As for duplicates, the current approach is to cross link, and mark any new ones as invalid. Similar to how you would handle duplicate patches for the same issue in gerrit. | 21:26 |
| diablo_rojo | You could even update the title to start with DUPLICATE if you want to make it more obvious | 21:26 |
| diablo_rojo | Happy to add to documentation if that quells fears. | 21:27 |
| jungleboyj | So the answer comes down to us documenting how we want to use it and having people do that. | 21:27 |
| diablo_rojo | I can probably have a patch up by the end of the week. | 21:28 |
| jungleboyj | A patch about what? | 21:29 |
| diablo_rojo | Updating the docs | 21:30 |
| diablo_rojo | But yes, CInder specific documentation will be equally important | 21:30 |
| jungleboyj | Ok. I can take a look at that and see if helps. | 21:30 |
| diablo_rojo | Sure. I can add you as a reviewer when I get it up. | 21:30 |
| jungleboyj | That was what I was trying to get the team started with ... | 21:30 |
| diablo_rojo | Happy to help there as well. If you need eyes or suggestions. | 21:31 |
| fungi | yeah, sorry, in the middle of monitoring a very hot wok, but work with the openstack vmt (hi!) on a documented vulnerability reporting process for vulnerability:managed deliverables using storyboard. at the moment there aren't any but i have some ideas and i've worked with the zuul team on their vulnerability reporting process for storyboard | 21:31 |
| jungleboyj | Been working on an etherpad to get ideas out there right now: | 21:32 |
| jungleboyj | https://etherpad.openstack.org/p/cinder-launchpad-design | 21:32 |
| fungi | it's less of a storyboard team problem and more of an official openstack vmt problem | 21:32 |
| jungleboyj | Yes, I realize there was freudian slip in there. | 21:32 |
| jungleboyj | fungi: I saw that there was a zuul-security board or something. | 21:33 |
| diablo_rojo | jungleboyj, cool I will take a look after lunch and see what I can do to help. | 21:33 |
| jungleboyj | I really want to use this as an opportunity to improve Cinder's processes but I am getting a lot of pushback from the team that they don't want to go down this path. | 21:33 |
| jungleboyj | Trying to figure out how to sell this. | 21:34 |
| fungi | it's still a lot of breaking new ground since each team seems to have slightly different processes and expectations and features of lp or trello or other systems they've been relying on | 21:34 |
| jungleboyj | fungi: If zuul is working through this and will have a process determined that will be good. | 21:34 |
| fungi | yeah, zuul is already managing to handle embargoed reports of suspected security vulnerabilities via storyboard going on a year now | 21:35 |
| fungi | there are definitely still some rough edges but at least they're known and being worked through (biggest at the moment is SotK's attachments work) | 21:36 |
| jungleboyj | fungi: Ok, I mean, I am happy once we get through the 500 errors to start trying to get things set up and documented for Cinder and set up our process but I feel like we need to be given a process for security bugs. | 21:43 |
| jungleboyj | We don't have very many so I am not holding our migration on that but need to understand where we are headed on that front. | 21:44 |
| fungi | once cinder actually decides to move, we'll want to coordinate the import with the vmt since private reports will need to be manually imported. the auto-importer works on an anonymous basis and can only see public bugs in lp | 21:46 |
| fungi | hopefully there aren't too many of those hanging out indefinitely private, but it might also present a good opportunity to make some hard choices about switching a few to public or something at that point | 21:47 |
| jungleboyj | fungi: Ok, let me keep pushing forward a design and see if I can get the team onboard. We will need to deal with the security stuff when we move. | 21:55 |
| fungi | absolutely, so please do keep me or others on the openstack vmt in the loop | 21:55 |
| fungi | but there is enough support in sb to be able to handle embargoed defect reports with some associated documentation pending, though we have ideas on how to improve that too | 21:56 |
| jungleboyj | Ok, if there is documentation that I can point our documentation at it would be helpful. | 21:58 |
| fungi | we just haven't had a vulnerability:managed project for the openstack vmt choose to move to sb yet, so we've deferred nailing down specific process since we might race further improvements in the service and just make more work for ourselves, but definitely don't want to be a roadblock | 21:59 |
| fungi | sort of a chicken-and-egg situation i guess | 21:59 |
| *** zbr|ssbarnea has joined #storyboard | 22:00 | |
| fungi | the user-facing vulnerability reporting documentation i came up with for zuul can be found at https://zuul-ci.org/docs/zuul/user/vulnerabilities.html | 22:00 |
| *** zbr|ssbarnea has quit IRC | 22:01 | |
| fungi | recording the associated process the maintainers are following is still on my to do list | 22:01 |
| *** zbr has quit IRC | 22:02 | |
| jungleboyj | fungi: Ok. | 22:05 |
| jungleboyj | I found some bugs in the Cinder test migration that didn't match to bugs in Launchpad. Would that happen if someone created them in Storyboard after the migration? | 22:05 |
| fungi | there are a few possible causes. the import is a snapshot in time which can be incrementally updated to pull in new comments by rerunning but currently fails to update some status changes on rerunning (this is probably something we want to fix) | 22:07 |
| fungi | they could certainly be bugs created directly in sb, or bugs which were further updated in lp after the last import run | 22:08 |
| fungi | if you have an example i might be able to do less speculating | 22:08 |
| jungleboyj | This was the one I was looking at: https://storyboard-dev.openstack.org/#!/story/1777142 | 22:08 |
| fungi | the story numbers are usually a tip-off since we have an offset for new story creation in sb and map imported stories to their corresponding lp bug numbers | 22:09 |
| fungi | and yeah, https://launchpad.net/bugs/1777142 is clearly an entirely different bug in this case | 22:10 |
| openstack | Launchpad bug 1777142 in linux (Ubuntu) "package linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-4.13.0-45-generic.list-new': Operation not permitted" [Low,Expired] | 22:10 |
| fungi | the story you referenced is a test story dhellmann created directly in storyboard-dev while trying to work through some process ideas for handling cycle goals | 22:11 |
| fungi | i think he was testing use of the sb api there | 22:12 |
| dhellmann | yeah, I created a bunch of dummy stories in the dev server while developing the script to automate creating the tracking stories | 22:13 |
| dhellmann | for goals | 22:13 |
| jungleboyj | fungi: dhellmann Ok. Thanks for verifying. | 22:37 |
| *** mkarray has joined #storyboard | 22:42 | |
| SotK | sorry I'd gone away from IRC and missed all this discussion | 22:46 |
| SotK | one improvement to that reporting URL in the zuul docs for vulnerability:managed projects would be to replace it with https://storyboard.openstack.org/#!/story/new?force_private=true&team_id=1 | 22:47 |
| SotK | which automatically adds the vmt | 22:47 |
| SotK | you can specify team_id multiple times in that URL to add project-specific teams too | 22:48 |
| SotK | https://storyboard.openstack.org/#!/story/new?force_private=true&team_id=1&team_id=2 adds the vmt and the zuul-security teams for example | 22:49 |
| SotK | the workflow we want to get to eventually involves automatically adding the relevant teams based on which projects are affected by the story if its a security issue, and also subscribing members of that team to the story | 22:52 |
| SotK | regarding duplicate stories, there's no hard plan for anything more streamlined than the current "mark invalid and link to the original", but there has been some vague discussions in the past at PTGs iirc | 22:52 |
| SotK | looking at the etherpad, task states are defined in the api codebase | 23:00 |
| SotK | there's a long discussion about task states in https://storyboard.openstack.org/#!/story/2001432 | 23:01 |
| SotK | (specifically, they're defined here: http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/db/models.py#n330) | 23:02 |
| SotK | for worklists and boards, users have permission to add, move, and archive cards | 23:04 |
| fungi | SotK: thanks for the suggestion (the zuul-security team isn't team_id=1 on our sb deployment, but easy enough to look up) | 23:04 |
| fungi | out of curiosity, how hard would it be to support team names instead of id numbers? | 23:05 |
| fungi | i have no idea whether they're uniquely constrained, but assume they likely are | 23:05 |
| SotK | they are | 23:05 |
| SotK | should be on the same order of difficulty as supporting project names | 23:06 |
| fungi | cool, maybe i'll add a story so we remember that's a thing we could improve | 23:07 |
| SotK | owners of worklists/boards can do everything, so add, move, and archive both lanes and cards, and edit the title/description/permissions/automaticness of lanes and boards | 23:07 |
| SotK | fungi: thanks | 23:07 |
| SotK | fungi: you can also add project_id=679 to autofill the project with openstack-infra/zuul if that would be useful | 23:08 |
| * SotK makes a story to document worklist/board permissions in the UI, since I keep remembering that we don't and then forgetting again | 23:09 | |
| fungi | SotK: yeah, i knew about project_id= but since that particular document applies to multiple zuul projects i didn't want to limit it to just one of them | 23:11 |
| fungi | in the per-repository readme or contributing files that makes perfect sense to include | 23:11 |
| SotK | makes sense | 23:12 |
| * SotK goes to sleep | 23:13 | |
| diablo_rojo | Sleep well SotK! | 23:15 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!