19:00:49 #startmeeting refstack 19:00:50 Meeting started Mon Oct 19 19:00:49 2015 UTC and is due to finish in 60 minutes. The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:53 The meeting name has been set to 'refstack' 19:01:34 hi 19:01:40 roll call 19:01:57 #link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-15-10-19 19:02:04 o/ 19:02:28 o/ 19:03:21 hello rockyg: pvaneck: let's just wait a couple minutes .. 19:04:22 o/ 19:04:40 let's start ... 19:04:57 #topic Infra hosting 19:05:15 pvaneck: could you update us the good news !! 19:05:48 sure 19:06:19 we are now fully moved over to https://refstack.openstack.org 19:06:34 refstack.net is now setup to redirect to this site 19:07:00 Yeah! Congratz all of us) 19:07:06 people trying to upload to refstack.net will also get an error message saying that the site has moved 19:07:59 Indeed we all should feel good with this progress ... we work on this since June ... 19:08:13 so we can maybe decommission refstack.net dreamhost server after a while 19:08:44 davidlenwell:^^ 19:09:00 maybe give it a month or so 19:09:05 yay! 19:09:14 I want to especially thank pvaneck: fungi: and krotscheck: for their contributions 19:09:47 so now the data is saved at an official place that should encourage more data upload ... 19:10:02 catherineD: they did all the hard work, i just took credit ;) 19:10:11 haha 19:10:23 * fungi is a proper leader! 19:10:45 fungi: yea yea ... we won't be here without you !!! And you know it !!! 19:11:00 ++ 19:11:34 pvaneck: would you say that with the move this bugs are also fixed ( or handled) 19:11:39 #link RefStack sign in sometimes slow https://bugs.launchpad.net/refstack/+bug/1499542 19:11:40 Launchpad bug 1499542 in refstack "RefStack sign in sometimes slow" [High,Confirmed] 19:11:53 #link First login with OpenStackID is wonky https://bugs.launchpad.net/refstack/+bug/1504691 19:11:53 Launchpad bug 1504691 in refstack "First login with OpenStackID is wonky" [High,Confirmed] - Assigned to Catherine Diep (cdiep) 19:12:22 catherineD: the refstack sign in slowness one can be marked resolved 19:12:54 rockyg: the second link is from you ... 19:13:09 some of the "first login with OpenstackID" is wonky can be considered resolved 19:13:29 Yay! 19:13:34 That was caching? 19:13:41 however rockyg mentions issues with the logout that has not been resolved 19:13:48 pvaneck: I know that the session patch fixed some issues 19:14:13 pvaneck: ic 19:14:14 the wonkiness came from server side sessions being stored in memory 19:14:24 I finally have some time to focus on some of this stuff. 19:14:26 It' 19:14:34 s almost relaxing 19:14:45 the logout issue has to do with the persistence of the openstackid_session 19:14:56 which i have a patch almost ready for 19:15:16 I am so happy that we have the server up before the summit.... 19:15:38 rockyg: thx for being our tester and submitted the bug .... 19:15:52 ok let's move on ... 19:15:53 It would be great if we could get a few more test results that are marked visible in, now. maybe hogepodge? 19:16:33 i think there was some ipv6 routing issues in/around internap which were causing v6-based connections from refstack.net to openstackid.org to fail and get retried over ipv4 19:16:47 which were contributing to one of those issues 19:17:11 but should be no longer since refstack.openstack.org and openstackid.org are in the same network/region now 19:17:31 rockyg: could you log into the site and see whether there is other areas that we should pay attention to ... 19:17:42 Interesting. So, the whole interweb could get more wonky until the ipv6<->ipv4 implentation corner cases get fixed. 19:18:04 fungi: that is great ... we should really move off refstack.net anyway ... 19:18:23 catherineD, yeah, I'm going out to it and spending fifteen or so minutes minimum just doing exploratory testing. 19:18:48 rockyg: thank you! 19:18:53 catherineD,I also filed that bug about somehow highlighting the flagged tests when all tests are displayed 19:19:49 rockyg: For that bug, I think we already have the flagged icon displayed 19:19:56 with all tests 19:20:14 rockyg: wondering if the flag icon is not showing for you 19:20:17 I think I finished the review of the signing doc, but want to verify. 19:21:01 pvaneck, Yeah. Nothing. All the tests and segments looked the same. Or maybe I hadn't opened to the right level? Maybe uplevel needs a flag, too. 19:21:21 rockyg: let's discuss f-2-f next week? 19:21:34 what browser do you use rockyg? 19:22:47 FF or Chrome. I think Chrome be FF doesn't handle the certs through multiple proxies well. 19:23:50 rockyg: pvaneck: let's meet to discuss this f-2-f next week? 19:24:08 yup 19:24:12 that would be easier ... 19:24:13 sure whenever 19:24:45 #topic No RefStack IRC meeting on October 26th and November 2nd 19:25:13 is that ok with everyone ? 19:26:07 The refstack designe session is on Thursday .... 19:26:26 ++ 19:26:26 yea, that is fine. a lot of people travelling 19:27:14 sslypushenko__: I hope you be able to attend the design session on Thursday? 19:27:45 It depends from time) 19:28:04 What time it would be? 19:29:10 it is 4:30 pm Tokyo time ... I think it is 7:00 am UTC? 19:29:21 let me check 19:30:55 It looks like, i will be able attend this meeting 19:31:05 sslypushenko___: thank you so much!!! 19:31:32 #topic Tokyo summit agenda 19:31:45 #link Please add topics that you think we should discuss. https://etherpad.openstack.org/p/refstack-tokyo-summit . 19:32:20 major discussion would be on data models for vendor to data affiliation ... 19:33:06 I think that we should also try to do a crossproject with QA for how tempestlib etc are planned to move forward. 19:33:07 I think the data model topic is best to discuss f-2-f 19:33:32 Really need to get on the same page as them, or vice versa for future testing. 19:34:18 rockyg: +1 that would be on QA agenda right? 19:35:38 can attend some qa sessions 19:35:51 pvaneck: definitely ... 19:35:53 Yes. There is a working session that the refstack devs should attend, if possible. 19:36:24 rockyg: sure will look into that and put it on my summit sched 19:36:54 I don't think they have a crossproject identified with us yet. I think catherineD should reach out to Matt Treinish to get on QA's schedule 19:37:20 sorry I am late 19:37:26 hi 19:38:03 hi dliu 19:38:06 rockyg: the qa schedule is pretty much locked down at this point 19:38:26 hi paul 19:38:29 the time for proposing a session was a few weeks ago 19:39:08 mtreinish, maybe informal? BoF type? 19:39:46 rockyg: maybe, but why not just come to the contib meetup on fri. 19:41:15 Ah, perfect. pvaneck and catherineD .... you have now been officially informed of where to get on the same page as QA.... 19:41:26 Thanks, mtreinish! 19:42:17 yep noted 19:42:22 mtreinish: that would be great.. we will come Friday and many of the QA session as I did in the past summit ... thanks 19:42:58 #topic Data model 19:43:22 #link started with Mark Voelker's patch ( https://review.openstack.org/#/c/226902/ ) 19:43:39 I create this UNL data model for us to discuss 19:43:55 #link RefStacl Data Model https://goo.gl/zWYnoq 19:44:53 Great! 19:45:06 it is just a starting point .... I would like for us to think about it now so we will have productive session at ths summit ... hopefully after the design session we will come up with an agreed models for us to implemented 19:45:22 Cool. 19:45:57 I will work on a few use ases scenario for the summit session ... 19:46:11 thank you Catherine, great job 19:46:34 for now is there any open discussion anyone want to bring up or ... do we want to take the rest of the time to discuss the data model 19:46:39 dliu: thx 19:47:04 welcome 19:47:32 dliu: you can probably also attend the refstack design sessions at the summit remotely 19:47:52 Yes 19:48:00 dliu: great .. 19:48:10 think only one hour time difference between your location and tokyo? 19:48:27 corret 19:48:30 correct 19:48:37 anything else? if not let's discuss the model 19:48:45 tokyo is one hour ahead of beijing 19:49:13 can we look at page 3 on https://goo.gl/zWYnoq 19:49:46 yes 19:50:40 IMO "product" can be replaced with vendor meta 19:51:16 It increases flexibility in future 19:51:40 what would be the fields ... just like the test meta data? 19:51:55 meta-key and value? 19:52:05 yeap 19:52:21 notice that I do not associate user or vendor to data ... 19:52:28 on page 3 19:52:46 data are associated with group .... 19:53:00 is that OK with everyone? 19:53:02 hmmm 19:54:22 in my mind , at the minimum a user will belong to its own group 19:54:26 me, too, hmmmm.... gotta think about that some 19:54:27 May we should allow to associate results with groups and users? 19:54:43 say user john belong to john_group 19:55:32 so when the user first upload data .. the admin_group = john_group ... 19:55:41 It will make user's life harder 19:56:31 sslypushenko___: how so? 19:56:58 I am think at some point the data admin group will belong to the product_admin 19:57:07 or vendor_admin_group ... 19:57:18 user should keep in mind all this stuff related with groups 19:57:36 I need some more time to think 19:58:06 sslypushenko___: yes please ... as ssaid I just want to throw something out there for us to think about and discuss ... 19:58:20 so that we have a productive f-2-f later. ... 19:58:52 It is really helps) Thank you 19:59:20 everyone please think about the models... give as many inputs .. because everyone would have diff perspective ... together we make RefStack ROCK!!! 19:59:40 let's end the meeting .... 19:59:40 yes 19:59:56 thank you all ! 20:00:00 #endmeeting