19:00:53 #startmeeting storyboard 19:00:54 Meeting started Wed Jan 25 19:00:53 2017 UTC and is due to finish in 60 minutes. The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:57 The meeting name has been set to 'storyboard' 19:01:08 #topic Announcements 19:01:13 None I have noted 19:01:22 #topic Urgent Items 19:01:26 also none 19:01:31 #topic In-progress work 19:01:56 I looked at the migration scripts 19:02:01 there is some work to be done 19:02:16 yay 19:02:17 How long is the list? 19:03:10 - add support for branches 19:03:29 - make worklists and add tags to handle priority/importance 19:03:34 Is that going to be a large effort? 19:03:48 - misc bugfixing 19:04:11 for 'make worklists and add tags', could we use the old api and then translate it? 19:04:11 that is all I've found so far, having imported monasca and half of keystone 19:04:16 that way the script itself doesn't need to change 19:04:34 I'm not sure what you mean, but probably 19:04:37 and we'd have a different script for converting flat priority to tags + worklists 19:04:45 either way none of the things seem like much work 19:04:50 (instead of building it into the migration scripts) 19:05:10 oh I see what you mean 19:05:14 we could do that 19:05:37 we'd need it to be quick so it doesn't hang around in the middle. 19:05:51 Indeed. 19:05:58 oh actually 19:06:16 (but yeah I figured that way the migration script is done there, and it should be fairly easy to script things for changes within storyboard itself) 19:06:21 we can't do that because we decided we were making the tags be "$projectname-$priority" right? 19:06:28 oh we can still do that ignore me 19:06:35 * zara_the_lemur__ ignores :) 19:06:55 :) 19:07:06 I think that is about all 19:07:15 monasca is easy to import 19:07:27 were you able to check for any strange characters? 19:07:36 nope, that is in "misc bugfixing" 19:07:39 ah okay 19:07:40 cool 19:07:46 So we want to wait to port Monasca till these things are done? 19:07:49 I assume? 19:08:04 yeah 19:08:14 but I can look at them in the coming week or so I expect 19:08:52 Excellent. 19:09:20 there was also interest from... refstack i suspect? in migrating 19:09:26 they want to discuss it at the ptg 19:09:42 hogepodge: ^ any details there? just so we're prepped to have people around to talk 19:10:05 he mentioned something about it coming up in a meeting but i don't know for sure which one 19:10:31 fungi, think it was the interop wg 19:10:33 fungi: defcore/interopwg is talking about moving to storyboard 19:10:45 we're changing our name, so it's an ideal time to change our tracker 19:10:52 anyway, didn't mean to sideline, just noting tat we're looking at a couple of teams now anyway 19:11:05 thanks diablo_rojo and hogepodge 19:11:10 np 19:11:25 * SotK is excited for people to start migrating 19:11:35 ace 19:11:35 SotK, okay so what can I do to help get the mgiration scripts up to par? 19:14:34 guessing his internet is not being great right now 19:15:12 We can talk about that later I suppose. 19:15:17 yeah 19:15:36 fungi, any other smaller projects you think would be safe in reaching out to, to move over? 19:15:43 Just off the top of your head? 19:15:56 diablo_rojo: there are so many i wouldn't even know where to start 19:16:13 that's the thing about small projects. there are significantly more of them 19:18:48 * SotK returns 19:19:01 we're working on another blog post at the moment, so soon we should have a thing with more info on the api up 19:19:13 at that point we might see more eager volunteers 19:19:51 Maybe after that post gets up I can send something out to the ML asking if there are projects interested in moving. 19:19:55 thoughts on that? 19:20:37 yeah, I feel like smaller projects probably have more freedom to come to us. 19:20:41 seems fine to me as long as we're in a state with the import script that we're comfortable it will work for them 19:20:44 yeah 19:21:20 Yeah that I think is the priority now. 19:21:22 +1 19:21:34 Get that up to snuff so we can start getting people moved over. 19:22:11 fungi, any idea when the TC release goals for Queens will get set? Could make moving to SB a release goal? 19:22:43 regarding help, you can look at adding branches support if you want to code, or otherwise provide reviews and make sure I'm not doing anything weird on the LP side 19:23:16 that's a great point. in http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html#work-items we identify bringing it to teh tc, and the new goals process is a great means of doing that bit 19:23:48 yep! 19:23:48 yeah, that seems like a good plan 19:24:20 SotK, I'm definitely on it for the reviews. I can see if I can figure out what migration of branches would look like. Might need to chat about that after this in a little more detail to get me rolling on it. 19:24:31 Hi sorry to disturb, which meeting (working group) is currently going on? 19:24:50 armstrong, its the storyboard project 19:24:59 diablo_rojo: sure, we can chat later :) 19:25:08 SotK, sweet :) 19:25:18 diablo_rojo: I will try to dig up my scripts for the python client, since they should give some hints around that 19:25:21 fungi, so what do I need to do to make that happen? 19:25:32 zara_the_lemur__, that would be super handy 19:26:16 ok thanks 19:26:47 diablo_rojo: well, we _just_ settled on pike cycle goals this week... probably start formulating a goal to propose to the governance repo and you'll be ready to push it when we're closer to thinking about queens goal setting (boston summitish timeframe i think?) 19:27:24 Okay cool. I will make that todo :) 19:28:18 i think the idea is that we set queens goals in time for teams to make progress planning them at the pike-cycle ptg 19:28:40 so the summit/forum before that is when we do goals gathering 19:29:39 and you can look at other goals already proposed/merged to the governance repo for inspiration 19:30:32 Okay cool. That's the plan. 19:30:43 Thanks fungi :) 19:31:35 * zara_the_lemur__ has 'update webclient components' listed as in-progress; did not do that this week. 19:32:16 I did finally write up some detailed notes on trying the test openid server 19:32:43 (a dummy openid server jeblair made to allow auth when not connected to the internet, for development purposes) 19:33:02 which is a cool resource but has been in review for a long time 19:33:40 flagging it up as something it'd be great to get more eyes on 19:33:52 as I'd hate it to be stuck up there if it's just me trying to set it up wrong 19:34:00 and it's fine to merge 19:34:02 Got that link? 19:34:39 sure, 1 sec 19:34:57 #link https://review.openstack.org/#/c/397998/ 19:35:12 it got buried for a little while because I completely forgot about it 19:35:44 Will review it today :) 19:36:34 I've added a comment with where I got up to with that so that hopefully others can see what I'm missing and we can get it moving :) 19:37:46 I have a couple of patches up in review, neither is amazing or urgent. 19:37:52 and with that phenomenal sales pitch 19:38:11 #link https://review.openstack.org/#/c/416070/ 19:38:19 I already reviewed the openid server :) 19:38:36 That one too 19:38:45 SotK: (I should've replied there, the answer is 'yeah I agree it needs fixing, I just don't know when I'll get around to it so would rather make incremental progress') 19:38:57 and 19:38:59 #link https://review.openstack.org/#/c/418122/ 19:39:02 which we talked about 19:39:31 diablo_rojo: yes, thanks! :D 19:42:08 * SotK will add a +2 later 19:42:08 with the openid server, I don't want to merge if I can't get it working and I don't feel I can say 'this person who isn't the author has tried it and can show others how to use it' 19:43:32 thanks 19:43:52 are you having trouble getting an openstackid instance running? or are you testing against one of our existing instances? 19:44:46 worth noting, i think clarkb discovered that openstackid.org (and probably openstackid-dev.openstack.org) won't authenticate your service if it lacks a reverse dns entry 19:44:46 fungi: this is just a fake-openid provider for use on something like a plane or something like that; I don't think we've looked into openstackid much yet. 19:45:02 oh! okay, completely different 19:45:07 yeah, sorry for the confusion 19:45:13 fungi: correct, it has to be a valid tld and all that 19:45:15 * fungi misunderstood, didn't look at your change 19:45:24 foo.clarkb.test.local or whatever i used wasn't good enough 19:45:38 (I wouldn't've brought it up in the meeting due to the confusion-potential, but it's been languishing for ages so this is me poking around for help. :)) 19:46:36 and that's useful to know, thanks 19:47:19 I talked to smarcet about it and I think they intend on relaxing that requirement but not sure if it happened yet 19:49:20 okay, I'll keep a general ear out for that 19:49:24 #topic Open Discussion 19:49:34 I realised I should've changed that about 30 minutes ago 19:49:36 oh well 19:50:15 we have 10 minutes to discuss openly 19:50:53 after that, we require deceit. 19:52:13 should we have an idea of where we want the migration scripts to be this time next week? 19:52:34 Done would be great :) 19:52:35 Lol 19:52:51 I agree 19:53:01 done would be ideal 19:53:08 as long as I don't have to define done ;) 19:53:32 is there a day it'd be good for everyone to be around for this? 19:53:47 * SotK doesn't know yet 19:54:21 okay, please keep me posted 19:54:23 I will be here today and tomorrow. 19:54:42 I shall keep posted 19:55:17 if you spin up the test instance somewhere I have access to, I can test it 19:55:32 might catch some things in 'misc bugfixing' 19:55:59 spin up/apply scripts 19:56:01 alright, I'll see what I can do :) 19:56:44 btw I'm figuring you're doing most of the 'actually write the scripts stuff' because that's how we started out, but also feel free to poke me about that if you want 19:56:56 I just figured it wasn't something that divided up well 19:57:43 yeah, I don't think there is a *huge* amoun to do 19:58:28 if you do think of something, let me know :) 19:58:50 otherwise I'll handle more... words... 19:58:52 * zara_the_lemur__ cries 19:58:55 will do 19:59:12 :) 19:59:43 next blogpost needs to be up in the next two weeks, I think 19:59:46 i'm around the rest of this week if you need to ping me for help with it 19:59:46 I'm responsible for that for now 19:59:51 * diablo_rojo pats zara_the_lemur__ on the shoulder 20:00:01 There there would you like a hot beverage? 20:00:03 but mostly unavailable all next week 20:00:09 thanks, we better finish 20:00:11 #endmeeting