19:00:15 <catherineD> #startmeeting refstack 19:00:16 <openstack> Meeting started Tue Dec 13 19:00:15 2016 UTC and is due to finish in 60 minutes. The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:20 <openstack> The meeting name has been set to 'refstack' 19:01:00 <sslypushenko_> o/ 19:01:14 <catherineD> sslypushenko_: hello 19:01:29 <sslypushenko_> catherineD: Hi! 19:01:43 <catherineD> #link meeting agenda and notes, https://etherpad.openstack.org/p/refstack-meeting-16-12-13 19:01:58 <pvaneck> o/ 19:02:39 <catherineD> let's wait for a few minutes for other to join ... 19:04:39 <catherineD> alright .. let's start .. 19:04:58 <catherineD> meeting agenda and notes, https://etherpad.openstack.org/p/refstack-meeting-16-12-13 19:05:25 <catherineD> #topic Update RefStack website with code in master 19:05:39 <luzC> o/ 19:05:56 <Rockyg> o/ 19:06:22 <catherineD> We made it!!!! The website was updated with the latest code on master on Dec 19, 2016. 19:06:30 <Rockyg> yay! 19:06:47 <hogepodge> o/ 19:07:03 <catherineD> now vendor/product registration is available so people can associate test results to vendor/product 19:07:41 <catherineD> thank everyone for working together to make this date before the holidays ... 19:07:56 <catherineD> these are big changes ... 19:09:08 <catherineD> however, there was issues that the website was down for a couple hours after the updates 19:09:43 <catherineD> #topic Issue encountered during the update 19:10:18 <catherineD> The issue seems to be caused by pyOpenSSL package being updated and not related to the RefStack code itself. 19:11:47 <sslypushenko_> This issue can be mitigated by fixing upper version in requirements.txt 19:12:15 <sslypushenko_> but it is a partial fix 19:12:48 <catherineD> jeblair and mordred helped to investigate and fix to bring our website up ... Thanks so much!!! 19:13:37 <catherineD> sslypushenko_: yea we need to investigate this issue before the next update to the website 19:13:38 <sslypushenko_> RefStack definitely should align requirements management process with common community process 19:13:49 <catherineD> sslypushenko_: ++ 19:14:32 <catherineD> my fundamental question is : do we need this package ( pyOpenSSL) in our requirements.txt? 19:14:50 <catherineD> now that our site is running without it 19:14:55 <sslypushenko_> I guess it is nice to have it... but with fixed version 19:15:35 <catherineD> sslypushenko_: we are not using it though ... 19:15:44 <catherineD> anywhere in our code 19:15:57 <sslypushenko_> in RefStack code - yes 19:16:25 <sslypushenko_> but it if someone wonats to setup development version of RefStack with https 19:16:28 <catherineD> we did a search and could not detect that 19:16:52 <sslypushenko_> then this package is necessary 19:17:45 <catherineD> is https://refstack.openstack.org/#/ and SSL env? 19:18:25 <sslypushenko_> yeap, but here https is handled by nginx 19:18:34 <luzC> also on the conversation mordred mentioned it is needed to talk to openstackid, right? 19:19:25 <sslypushenko_> catherineD: let me investigate this issue a bit, I'll inform you about results tomorrow, ok? 19:19:26 <catherineD> luzC: it does not seems so because our login is by talking with openstackid .. 19:19:44 <sslypushenko_> luzC: I don't think, so 19:19:45 <catherineD> sslypushenko_: great! Thanks a lot!!!! 19:20:27 <catherineD> if we do not fix this (by removing it or some other action ...) we will face the same issue on the next update 19:21:46 <catherineD> we maynot be as lucky last time with the in time help from mordred and jeblair .. out website could be down for a while ... 19:22:23 <Rockyg> Do we have a rollback method? That would be useful. 19:23:23 <catherineD> Rockyg: yea with this lesson learned .. we need to investigate a rollback methog 19:23:48 <catherineD> method or strategy ... 19:24:10 <sslypushenko_> Without having staging server - we will hit similar problems again, some day) 19:24:19 <catherineD> I will table that for our coming meeting 19:25:06 <sslypushenko_> And also rollback will be nice to have 19:25:07 <catherineD> sslypushenko_: exactly .. it was nerveracking last Friday 19:26:09 <catherineD> I am not sure how to get a staging env ... it kinds of go against the CI/CD practice? 19:26:56 <catherineD> anyway ... these are the decision and strategy we need to make ... 19:28:07 <catherineD> for now let's pat ourself on the back for delivering these new features ... we have been working on these for the last 2 cycles 19:28:49 <catherineD> good job everyone ... 19:28:59 <catherineD> that brings us to the next topic 19:29:06 <catherineD> #topic Working with DefCore to advertise this features 19:29:26 <catherineD> how do we advertise these new features to the users ... 19:29:56 <catherineD> I will bring this topic to DefCore meeting ... 19:30:47 <luzC> a how-to article on the super user would be good too 19:31:27 <catherineD> luzC: good idea ... the about link now have some info 19:31:49 <catherineD> that is what we should do 19:32:30 <catherineD> the most features are available to Foundation admin ... 19:33:11 <catherineD> hogepodge: at the minimum you can mark the links that vendor sent to you for Powered Logo application as verified 19:34:01 <catherineD> by marking those links (results) as verified these test records are protected .. noone can delete them until they are unmark by foundation admins 19:34:39 <catherineD> this also open the door for us to discable anonymous data upload in 2017 19:35:17 <catherineD> any other discussion on this one 19:35:19 <catherineD> ? 19:36:00 <catherineD> hearing nothing. I think we can move to the next topic .. 19:36:26 <catherineD> #topic IRC meetings for the next 2 weeks 19:36:58 <catherineD> I will be out of the office for the next 2 weeks... 19:37:59 <catherineD> does anyone want to run the meeting or should we cancel ? 19:38:14 <sslypushenko_> +1 for cancel 19:38:44 <Rockyg> +1 19:39:09 <luzC> +1 for cancel 19:39:46 <catherineD> alright, I will send out an email to cancel 19:39:56 <catherineD> moving on .. 19:40:07 <catherineD> #topic Pending reviews 19:40:22 <catherineD> #link https://review.openstack.org/#/c/409357/ ( Replace mention of easy_install with pip ) 19:43:53 <sslypushenko_> Good catch 19:44:18 <sslypushenko_> if author will not update the patch I will do it 19:44:54 <sslypushenko_> but patch definitely needs to be updated) 19:45:23 <catherineD> ok do we want to merge this one and then follow up with the next one? or you just update this one? 19:45:31 <catherineD> sslypushenko_: ++ 19:46:25 <luzC> +1 to update this one... also note that package from apt might be a very old version... is that enough for refstack? 19:48:39 <catherineD> I am not sure that we need that latest one ... but if we do then what being proposed without using apt-get will get us the latest one ... 19:49:23 <sslypushenko_> luzC: for ubuntu 14.04 and 16.04 it is pretty fresh 19:49:54 <catherineD> Is there a standard in OpenStack? Noted that this only affects new build of RefStack server ... which should mostly in development env 19:50:58 <catherineD> I have tested either ways .. as expected both works ... 19:51:20 <catherineD> moving on ... 19:51:48 <catherineD> #link https://review.openstack.org/#/c/403017/ ( Show team and repo badges on README ) Refstack 19:52:04 <catherineD> #link https://review.openstack.org/#/c/409975/ ( Show team and repo badges on README ) Refstack-client 19:52:31 <catherineD> I will take a look at the doc created by these two before merging them ... 19:52:57 <catherineD> now that our about link does link to the rst doc in the refstack repository 19:54:33 <catherineD> #link https://review.openstack.org/#/c/396700/ ( Add authentication with Json Web Tokens ) and https://review.openstack.org/#/c/410271/ ( Add tool for coverage check ) 19:54:54 <catherineD> sslypushenko_: thanks for working on these two patches ... we really need them 19:55:09 <catherineD> everyone please review ... 19:55:26 <sslypushenko_> yeap it should be ready for review 19:55:29 <catherineD> I will review and test them too 19:56:31 <catherineD> sslypushenko_: question do you expect to have them update on the website as soon as possible? if so we need to make an other update the the website 19:57:20 <sslypushenko_> this patch does not affect website 19:57:56 <luzC> I'll take a look... 19:58:12 <sslypushenko_> it introduce auth method usable by CLI tools 19:59:10 <sslypushenko_> so update of refstack.org it not necessary 19:59:16 <catherineD> https://review.openstack.org/#/c/396700/ change the API ... if we want those available at https://refstack.openstack.org/api we will need to update the site right? 19:59:31 <sslypushenko_> right 20:00:06 <catherineD> sslypushenko_: ok that is good ... we will test it and plan for update this feature to the website in 2017. Is that OK? 20:00:17 <sslypushenko_> absolutely 20:00:24 <sslypushenko_> My goal is to remove pubkey signature during upload of new pubkey 20:00:45 <sslypushenko_> then site will need to be update 20:01:09 <catherineD> Thank you so much ... it was so stressful last Friday that I did not want to go thru that again in a short time :-) 20:01:19 <catherineD> sslypushenko_: ++ totally agree. 20:01:39 <catherineD> we are out of time ... 20:02:07 <catherineD> but we have discuss the Aligned RefStack with openstack-requirements (openstack/global-requirements) topic briefly 20:02:17 <catherineD> let's discuss more next time 20:02:29 <catherineD> well this is the last meeting of the year .. 20:03:04 <catherineD> I want to THANK YOU all for your hardwork and contribution to the RefStack project ... 20:03:30 <catherineD> need to end the meeting now ... 20:03:36 <catherineD> bye everyone 20:03:46 <catherineD> #endmeeting