19:01:19 #startmeeting refstack 19:01:20 Meeting started Tue Dec 6 19:01:19 2016 UTC and is due to finish in 60 minutes. The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:23 The meeting name has been set to 'refstack' 19:01:34 o/ 19:02:35 #link meeting agenda and notes, https://etherpad.openstack.org/p/refstack-meeting-16-12-06 19:02:48 hogepodge: hi 19:02:51 o/ 19:05:07 Let's start 19:05:34 #topic Update RefStack website with code in master 19:06:18 so we still plan to update the website on Friday ... which is a very aggressive date 19:06:28 but we will try 19:07:21 hogepodge: when we update the RefStack with master .. vendor/product registration feature will be available ... 19:07:29 catherineD: did you see the 503 error that some one posted to the defcore list? 19:08:04 catherineD: I imagin that it's user error, but I'm wondering if figuring out where the 503 is coming from could help in identifying an appropriate error message 19:08:10 The first thing we need to do is to create a Foundation organization 19:08:13 catherineD: great on the feature, thanks 19:08:30 catherineD: fungi does that bootstrapping for us? 19:08:58 hogepodge: I have monitored the #refstack IRC but not defcore .. will take a look 19:09:13 catherineD: it's in the mailing list 19:09:30 which bootstrapping? 19:09:39 oh, setting up the new ml? 19:09:57 hogepodge: First you need to create a Foundation organization ... we then need to coordiante with fungi to change a parameter i nthe database to make it a fundation type organization 19:10:04 catherineD: ok 19:10:46 fungi: we will need to to change one parameter in the database ... we will let you know when the time comes .. thanks! 19:11:14 oh, right, that. someone was going to get me the details on what row to add to the refstack db when you're ready? 19:11:19 sounds great 19:11:41 fungi: yes we will provide a sql statement with the correct UUID etc .. 19:12:17 o/ 19:13:03 hogepodge: once fungi: updates the parameter . You will be the first member of the Foundation ... after that you can add other users to the foudnation user group etc ... 19:14:11 and the foundation members willl be the admin who have privilleges to do a lot of actions on the website 19:14:23 o/ 19:15:04 I will send out and email and coordinate with hogepodge: fungi: 19:15:32 luzC: sslypushenko_: meeting agenda and notes, https://etherpad.openstack.org/p/refstack-meeting-16-12-06 19:15:39 thx! 19:15:45 thanks :) 19:16:16 we are on topic one ... we plan to update the site on Friday but it is kind of aggressive ... 19:16:32 thanks catherineD! 19:17:30 but I kind of like to update the webiste on a Friday and while a lot of us are still here ... I know that people in the US will start to take vacation on the second half of December 19:18:04 catherineD +1 19:19:30 the 2 patches that we will discuss next are needed for the website update 19:20:55 and we have 2 more patches to be submitted today soon ( 1 for doc and the other one for display on the test result) 19:21:19 moving on .. 19:21:53 #topic Pending reviews 19:22:12 #link https://review.openstack.org/#/c/405019/ ( Only Foundation admins can update the 'name' fields of official vendors ) 19:23:30 Please review 19:23:40 yes, I'll take a look today... 19:24:41 luzC: thx ... this patch just prevents people to change the name of the vendor after it is approved by the foundation ... 19:25:15 only foundation members can change the vendor names for an approved/public vendor 19:25:36 next .. 19:26:11 #link https://review.openstack.org/#/c/407268/ ( Add ability to edit test meta on report page ) 19:27:22 same-- I'll take a look... 19:27:53 This is an improvement to ease Foundation members' efforts in editing meta data of test results (especially the previous results ) 19:28:03 luzC: thanks again! 19:28:10 (parenthesis) I've been trying to setup my own openstackid server... right now I have a refstack test server (with no domain)... so I kind of fake the openstackid auth, any pointers/ how you test these changes is appreciated :) 19:29:04 luzC: sure that is great ... let's discuss this after the meeting ... 19:30:28 ok 19:30:34 #topic Open discussion 19:31:25 hogepodge: for the 503 errors .. both pvaneck: and I have tested with no error 19:31:47 catherineD: I'm guessing the user is inducing an error with bad data 19:32:01 I have respondeded to the user on the email ... asking her to get onto #refstack for interactive section 19:32:28 hogepodge: I think so ... my plan is to give a fake RSA key that we use for unit test 19:32:50 and ask her to import this key to eliminate key error first .. 19:32:59 then go o nwith the next step .. 19:33:37 I have not heard back from her but will follow to see whether she still jhas the issue 19:34:43 anything else for discussion ? 19:37:06 if not, we can end the meeting early .... 19:37:25 luzC: we can discuss your env on #refstack 19:37:39 yes, thank you 19:38:14 alright thank you all for attending the meeting! bye ! 19:38:25 #endmeeting