15:00:20 <krotscheck> #startmeeting storyboard
15:00:21 <openstack> Meeting started Mon Aug  4 15:00:20 2014 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:25 <openstack> The meeting name has been set to 'storyboard'
15:00:30 <krotscheck> Agenda! https://wiki.openstack.org/wiki/StoryBoard#Agenda
15:00:35 <krotscheck> Woo agenda
15:01:12 <krotscheck> Roll call, anyone other than myself here?
15:01:28 * krotscheck notices that Ish__ just walked into the office, will be a couple of minutes late.
15:02:08 <gothicmindfood> o/
15:02:19 <krotscheck> Oh, good! Hi there gothicmindfood!
15:02:22 <gothicmindfood> hi!
15:02:26 * krotscheck was about to be worried about being alone in here.
15:02:37 <gothicmindfood> :)
15:02:50 <ttx> o/
15:03:00 <ttx> sorry, back-to-back meetings
15:03:06 <krotscheck> #topic Urgent Items
15:03:28 <krotscheck> Ok, so the puppet module didn’t happen last week, largely due to me focusing on search and totally forgetting about it until the last minute.
15:03:50 <krotscheck> Having said that, infra’s stated that they’ll be available as soon as I am.
15:04:18 <krotscheck> I’m setting up a dev environment so that I can test the current patch in time with the module update.
15:04:28 <krotscheck> Once I have that, I’ll ping someone on -infra and we’ll go from there.
15:04:42 <krotscheck> Any questions before I move on?
15:04:59 <krotscheck> Relevant review: https://review.openstack.org/#/c/98007
15:05:10 <jeblair> krotscheck: sounds like a plan
15:05:15 <krotscheck> Okie dokie.
15:05:25 <jeblair> krotscheck: thanks for the local testing -- that'll be a big help
15:05:54 <krotscheck> #topic MVP (Search)
15:06:16 <krotscheck> Ok, so we’re now on mysql 5.6, we’ve got a fulltext index, we’ve got the search endpoints.
15:07:08 <krotscheck> I’ve incorporated NikitaKonovalov’s front end changes into my refactor of our search criteria: https://review.openstack.org/#/c/110160/
15:07:36 <krotscheck> Now, having said that.
15:07:44 <krotscheck> Fulltext indexes only work on full words.
15:07:54 <krotscheck> So if I search for “story”, the search will not hit “storyboard"
15:08:28 <krotscheck> Furthermore, our API doesn’t yet support fulltext + filter on, say if I want to search on stories that are active with the term “story"
15:09:00 <krotscheck> I attempted to implement that last week only to run into what I think is a limitation in the fulltext library we’re using.
15:09:10 * krotscheck doesn’t know if mysql actually lets you do that)
15:09:47 <krotscheck> So there’s two options there. One: If it’s implementable on the services side, do that. Otherwise, create a text-only search UI on the frontend.
15:10:06 <krotscheck> Which of the two need to be done remains to be seen.
15:10:43 <krotscheck> Any questions on that?
15:11:25 <krotscheck> Oh, also there seems to be some kind of a bug in https://review.openstack.org/#/c/101476/
15:11:39 <krotscheck> #topic Launchpad Data Import
15:11:49 * krotscheck cedes the floor to mordred
15:11:53 <ttx> yeeha
15:12:02 * mordred has not gotten to this yet
15:12:04 * mordred hides
15:12:08 <krotscheck> Alrightey!
15:12:15 <krotscheck> #topic subscription
15:12:41 <krotscheck> UI is ready. We’ve rebased Ish1’s changes onto NikitaKonovalov’s patch.
15:12:46 <krotscheck> Well, sorry.
15:12:50 <krotscheck> Starring UI is ready.
15:12:57 <krotscheck> Not thea ctuall consumption of the subscription.
15:13:27 <krotscheck> We did run into one issue in that oslo.messaging blocks in a weird way, while also not providing the full feature set of rabbitmq.
15:13:45 <krotscheck> Apparenlty, the openstack project does not use topic exchanges.
15:14:11 <krotscheck> I’m sure there’s a good reason for it, does anyone know what that is?
15:15:23 <krotscheck> Either way, Ish1 and I decided to ditch oslo.messaging altogether because we’re not really gaining anything from the abstracion layer while losing some of rabbit’s functionality.
15:15:56 <krotscheck> And that’s now available in https://review.openstack.org/#/c/102842/
15:16:17 * krotscheck notes that ttx has a minor nit inline.
15:16:34 <krotscheck> Any questions on this?
15:16:47 <Ish1> I saw that comment. Will modify it.
15:17:03 <krotscheck> Awesome.
15:17:10 <ttx> no comment
15:17:12 <krotscheck> #topic Project Groups
15:18:04 <krotscheck> So, project group admin landed.
15:18:09 <krotscheck> WOOO!
15:18:32 <ttx> yay
15:18:38 <krotscheck> That still leaves us with the need to surface it to the non-admin user.
15:18:58 <krotscheck> We do have a story for that, it’s just not as high a priority given the other things.
15:19:29 <krotscheck> One question on that (ttx, jeblair), do you guys want to manage project groups manually or would you rather that become automated in some way?
15:19:58 <mordred> we tend to prefer automating stuch things
15:20:14 <ttx> but then there are corner cases we'll have to handle manually
15:20:18 <mordred> yah
15:20:26 <ttx> like "security supported code repositories"
15:20:39 <krotscheck> Sounds like we want some kind of import script for that as well.
15:20:54 <ttx> I guess we could sync program-derived projectgroups from programs.yaml
15:21:17 <ttx> source: http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
15:21:27 <ttx> but that's about it, everything else would be manual
15:21:38 <ttx> i.e. convenience grouping
15:21:43 * krotscheck ponders that…
15:22:46 <ttx> krotscheck: imho it's the same case as the teams. Some of those would be owned and synced by some external process that would call in the API
15:22:52 <krotscheck> I don’t really like the crossing of nomenclature there - that format uses “repo” for instance which isn’t entirely synonymous with “project”, especially if you consider storyboard from a standalone context.
15:23:02 <krotscheck> I like the data structure though.
15:23:17 <krotscheck> Either way: We still need a sync script.
15:23:21 <jeblair> i believe mordred added a 'group: foo' entry to review.projects.yaml
15:23:26 <ttx> krotscheck: agree that it's not a complete nomenclature overlap
15:23:39 * krotscheck makes a note to add sync script to the groups story.
15:23:42 <jeblair> with the expectation that it would be used to add a project to a storyboard group
15:23:55 <krotscheck> Oh really!
15:23:58 <krotscheck> Well, that simplifies things.
15:24:04 <krotscheck> Alright, Will note that as well.
15:24:13 <krotscheck> #topic tags
15:24:16 <jeblair> however, i'm betting we want that to be a sequence, not a single item?
15:24:29 <krotscheck> #topic Project Groups
15:24:39 <krotscheck> (Sorry, premature topic switch)
15:24:48 <krotscheck> jeblair: What do you mean by sequence?
15:24:59 <jeblair> krotscheck: multi-value
15:25:08 <krotscheck> Right, because one might be a member of more than one project.
15:25:16 <krotscheck> s/project/project group/
15:25:16 <jeblair> more than one group, yeah
15:25:40 <krotscheck> Yeah, it should.
15:26:08 <jeblair> so probably should land a change to the yaml file to change that, then we can start using it
15:26:47 <krotscheck> Anyone want to volunteer for that? I don’t mind taking it, I’m going to be rooting around in /config anyway
15:27:03 <jeblair> i don't think anything actuall _validates_ the yaml, so it's probably not hard
15:27:08 <krotscheck> ….doh. I just volunteered, didn’t I.
15:27:35 <krotscheck> mordred: Is there anything other than storyboard that’s using the group: field in review.projects.yaml?
15:27:46 <mordred> krotscheck: uhm ...
15:28:14 <mordred> krotscheck: it sure felt like there maybe was, but come to think of it, I think no
15:28:38 <krotscheck> Ok, so a bit of forensics necessary.
15:28:42 <krotscheck> Righto.
15:28:48 <krotscheck> #topic Tags
15:28:56 <krotscheck> I don’t think we’ve had any progress on that.
15:29:24 <krotscheck> Same with emails
15:29:40 <ttx> wasn't the spec approved on tags?
15:29:56 <krotscheck> Oh yeah!
15:29:57 <ttx> ah no, Clark +2ed it
15:30:11 <ttx> but that's still missing the second +2 from infra-core
15:30:26 <krotscheck> Point.
15:30:35 <krotscheck> @link https://review.openstack.org/#/c/97211/8/specs/storyboard_story_tags.rst
15:31:14 <jeblair> krotscheck: "#link"
15:31:32 <krotscheck> oops
15:31:34 <krotscheck> #link https://review.openstack.org/#/c/97211/8/specs/storyboard_story_tags.rst
15:31:37 <krotscheck> Let’s try that again
15:32:11 <krotscheck> jeblair, mordred: How does y’all’s review backlog look?
15:33:14 <jeblair> krotscheck: i should be able to look at that today; i just missed it in my recent pass at finding "specs that are ripe for review".
15:33:57 <krotscheck> jeblair: Thanks!
15:34:01 <krotscheck> #topic Emails
15:34:13 <krotscheck> Not started yet I believe.
15:34:29 <krotscheck> #topic Design Discussion
15:34:38 <krotscheck> Anyone have a topic to bring up during design discussion?
15:34:44 * krotscheck doesn't.
15:35:42 <ttx> o/
15:35:46 <krotscheck> Go for it!
15:36:03 <ttx> Not sure that qualifies, but I raised a question about the need to manage users from the admin interface
15:36:08 <krotscheck> Ah, yes!
15:36:19 <ttx> I was just wondering about the use case there
15:36:28 <krotscheck> So, the reason I added that is to allow someone like infra-core to create a jenkins user without having to go through launchpad.
15:37:01 <ttx> ok
15:37:27 <krotscheck> The end use case being “Hey I want to issue a long-lasting auth token for this user so we can integrate zuul/jenkins/etc
15:37:31 <ttx> just felt a bit weird to have an UI for it as we expect 99.99% of users to be autocreated, but I guess that doesn't hurt
15:38:02 <krotscheck> jeblair, mordred: ^ Thoughts on that?
15:38:30 * krotscheck doesn’t mind removing it from the UI, but the API does allow superusers to create new users directly.
15:39:15 <jeblair> krotscheck: i think we'd be fine with API-only access to do that (especially once we have a python client).  i don't think i _object_ to a ui though...
15:39:45 <krotscheck> Ditto there.
15:39:48 <krotscheck> *here
15:39:49 <ttx> krotscheck: yeah, now that the code is up, maybe we can keep it in -- just don't want junior admins to ask questions about that panel
15:40:11 <ttx> maybe we could just add a warning note saying most users will get autocreated
15:40:14 <jeblair> krotscheck: i don't really want admin users to be _too_ special
15:40:30 * krotscheck agrees with ttx.
15:40:48 <krotscheck> I can add some messaging to that UI.
15:40:54 <jeblair> for instance, i have very little access granted in gerrit by virtue of being an admin -- mostly i can add myself to a group that grants me more access, but day-to-day, i'm pretty much just a user.
15:41:35 <krotscheck> After all, since we index off of emails, once someone with an email logs in via launchpad it de-facto takes over the update authority to that user.
15:41:49 <jeblair> i relate that just to indicate that having a "safe" environment where you don't have to worry about admins having a too-different view of the system from users is nice.
15:42:23 <jeblair> krotscheck: that might be a problem
15:43:29 <krotscheck> jeblair: Yeah, that’s a tricky one. Because it’s also a good thing to preload users when we want to do the data import.
15:43:39 <jeblair> we should dig in to that at some point; it's probably okay for launchpad
15:43:42 <jeblair> krotscheck: gotcha
15:43:57 <krotscheck> Maybe we should add a user flag that disables launchpad for specific users...
15:44:47 <jeblair> krotscheck: yeah, we'd want to protect the admin-created ones from being taken over via openid
15:44:59 <krotscheck> Righto!
15:45:08 <krotscheck> Any disagreements to that?
15:45:40 <jeblair> (especially since the goal is to avoid needing to create them in LP; you wouldn't want to then need to create them in LP to prevent someone else from registering that email and taking it over)
15:45:55 <ttx> krotscheck: ++
15:46:23 <krotscheck> Alright, let’s move on to ongoing work.
15:46:50 <krotscheck> ttx, I’ll -2 that patch to indicate the discussion here.
15:46:58 <krotscheck> #topic Ongoing work.
15:47:15 <krotscheck> Let’s do reverse alphabetical today.
15:47:26 <krotscheck> ttx?
15:47:36 <ttx> sure
15:47:50 <ttx> I managed to empty my review backlog
15:48:04 <ttx> but not much above that
15:49:07 <krotscheck> That’s helpful :)
15:49:10 <ttx> that's all I had :)
15:49:24 <krotscheck> My turn…
15:49:25 <krotscheck> I did all the thigns I mentioned above.
15:49:40 <krotscheck> Also, making progress on splitting the javascript builds apart into individual reports.
15:50:41 <jeblair> about that
15:50:49 <krotscheck> Yes?
15:50:57 <jeblair> can you describe the motivation there a bit?
15:51:06 <krotscheck> Yeah-
15:51:34 <krotscheck> It’s mainly a question of getting all the reports to be easily accessible via the review UI.
15:51:56 <krotscheck> Right now, if the build passes, it’s not very easy to get at the test reports, because the link takes you straight ot the draft UI.
15:52:16 <jeblair> ah! yeah, that's a very good reason
15:52:18 <krotscheck> So that’s why I split out the draft build into its own thing.
15:52:42 <krotscheck> And the other ones, well, while I was in there I figured that I could make them a bit more configurable.
15:53:01 <krotscheck> And leave it to the individual projects to figure out what tests they wanted to run.
15:53:38 <krotscheck> clarkb left a really good comment on the first patch
15:53:42 <krotscheck> That lead to this one: https://review.openstack.org/#/c/111407/1/modules/openstack_project/files/jenkins_job_builder/config/javascript.yaml
15:54:05 <krotscheck> Less specific-template-per-test-type and more hey-name-your-own-test-target
15:54:41 <krotscheck> That’s it for me.
15:54:45 <jeblair> sounds reasonable.  i don't have an opinion on this wrt to storyboard; just noting that there's a balance between splitting things up (which may be convenient or necessary due to build node/configuration issues)
15:55:09 <jeblair> and on the other hand, combining things to reduce the impact/overhead from having multiple build nodes
15:55:17 <krotscheck> jeblair: Yeah, especially since npm is still volatile… it’s a questionable thing for us.
15:55:28 <krotscheck> But I’m working on that one too (just not recently)
15:55:29 <krotscheck> ish____?
15:55:33 <krotscheck> Your turn :)
15:55:36 <ish____> The publisher and subscriber modules are ready for the subscription project. That's it from my side.
15:55:41 <krotscheck> Neat!
15:55:56 <krotscheck> Anyone have questions on that?
15:56:12 <krotscheck> #link https://review.openstack.org/#/c/102842/
15:57:15 * krotscheck will let everyone go look at that review in downtime
15:57:19 <krotscheck> #topic Open Discussion
15:57:23 <krotscheck> What’s up?
15:58:13 * ttx switches to another call -- cheers
15:58:19 <krotscheck> Alright, I think that’s all then.
15:58:24 <krotscheck> Thanks everyone!
15:58:27 <krotscheck> #endmeeting