19:00:59 <catherineD> #startmeeting refstack 19:01:00 <openstack> Meeting started Tue Nov 22 19:00:59 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:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:04 <openstack> The meeting name has been set to 'refstack' 19:01:51 <pvaneck> o/ 19:02:22 <catherineD> #link meeting agenda and notes, https://etherpad.openstack.org/p/refstack-meeting-16-11-22 19:02:56 <catherineD> pvaneck: Hi... I expect it will be a quick meeting today .. Let's wait for a few minutes 19:03:03 <pvaneck> catherineD: sure 19:05:18 <sslypushenko_> o/ 19:05:38 <sslypushenko_> Hi, folks! 19:06:24 <catherineD> sslypushenko_: Hi ... 19:06:59 <catherineD> thx for joining .. we can use this meeting to discuss your patch ... 19:07:28 <catherineD> let go thru the agenda real quick ... https://etherpad.openstack.org/p/refstack-meeting-16-11-22 19:07:34 <sslypushenko_> yeap sure) 19:07:48 <catherineD> #topic Project Team Gathering (PTG) 19:08:16 <catherineD> RefStack team will not participate at the PTG ... 19:08:27 <catherineD> sslypushenko_: will you join PTC? 19:08:31 <catherineD> PTG 19:08:47 <sslypushenko_> No 19:09:05 <catherineD> yea we do not either ... 19:09:27 <catherineD> #topic Pending review 19:09:46 <catherineD> #link https://review.openstack.org/#/c/396700/ ( Authenticate user for with public key and signature ) 19:10:13 <sslypushenko_> I should put it in WIP again 19:10:28 <sslypushenko_> Looks like it needs some work work 19:10:35 <sslypushenko_> but I have a good news) 19:10:38 <catherineD> sslypushenko_: First of all .. I want to think you for this patch ,... we have been talking about this but never implement ... thx so much for working on it 19:10:52 <sslypushenko_> we can depricate publick key signature during uplaod 19:10:59 <sslypushenko_> *upload 19:11:16 <catherineD> that would make thing eaiser .. 19:11:20 <sslypushenko_> catherineD: it is my pleasure) 19:11:49 <sslypushenko_> also I will add some docs how to test it 19:12:11 <sslypushenko_> because it is not a piece of cake with postman) 19:12:13 <catherineD> I did some more test http://paste.openstack.org/show/590121/ but I guess without the signature with upload we may not need to work on this problem any more .. 19:12:35 <sslypushenko_> it is true 19:12:57 <luzC> o/ sorry to be late 19:13:14 <catherineD> so in the latest test I use curl and the fake pub key .. that way all of us can use the same key to test 19:13:50 <catherineD> luzC: no problem at all ... thx for joining ... agenda https://etherpad.openstack.org/p/refstack-meeting-16-11-22 19:13:58 <sslypushenko_> catherineD: I'll provide some script for signature generation 19:14:11 <sslypushenko_> then you can use postman easily 19:14:27 <catherineD> great .. but with no signature for upload ... we do not need it anymore right? 19:14:32 <pvaneck> yea, i think a utility/script for that would be useful 19:15:05 <catherineD> actually curl will be good because other people can easily duplicate the tests .. 19:15:22 <sslypushenko_> it is a bit different things 19:16:00 <sslypushenko_> signature during upload pubkey become optional 19:16:43 <catherineD> sslypushenko_: do we worry about upload data tempering ? that is the reason why we add signature right? 19:16:43 <sslypushenko_> but each request should be signed with signature in order to provide user auth 19:17:40 <sslypushenko_> pubkey signature it is a way how to prevent duplication of pubkeys 19:18:07 <catherineD> sslypushenko_: I think that is fine .. because key are lot upload frequently 19:18:11 <sslypushenko_> it was a way... 19:18:40 <sslypushenko_> but now I found a way how to make it optional 19:18:54 <catherineD> by now RefStack users are accustomed to upload key with signature 19:19:04 <catherineD> sslypushenko_: oh that is great 19:19:39 <catherineD> I will wait for your update for any further test then ... 19:20:18 <catherineD> any thing else on this topic? 19:20:24 <sslypushenko_> yeap, I'll ping you as far as it become ready 19:20:54 <sslypushenko_> I have nothing to add 19:21:13 <catherineD> sslypushenko_: again thank you so much for working on this very needed feature .. 19:21:21 <catherineD> moving on .. 19:21:28 <catherineD> #topic https://review.openstack.org/#/c/398633/ ( Rename key name from 'reason' to 'registration_decline_reason' ) 19:21:52 <catherineD> luzC: sslypushenko_: could you please review this patch ... 19:22:40 <catherineD> basically the change there is to just use a more descripted name for a free-from key/value info ... no database or business logic change at all ... 19:23:07 <sslypushenko_> catherineD: LGTM 19:23:10 <catherineD> I realize that further work are needed .. but I think this is good for now ... 19:23:11 <sslypushenko_> merged 19:23:22 <catherineD> sslypushenko_: thx ... 19:23:26 <luzC> I already review it, code looks good, 19:23:39 <catherineD> luzC: thx .. 19:24:57 <catherineD> As you know we have been working on vendor/product feature for about 1 and a half cycle now ... we have all the code merged to the master branch before the summit but we still have not update the code on the RefStack site 19:25:41 <catherineD> since we have time now ... that is why we review all the the details .. .this is one of the things that we want to update before the merge ... 19:26:10 <catherineD> we target to update the website during the first week of December .. 19:26:55 <catherineD> Hopefully we can make it so we will wrap up 2016 with Vendor/Product feature published on the RefStack website 19:27:08 <catherineD> that is our target 19:27:14 <catherineD> moving on .. 19:27:32 <catherineD> #topic https://review.openstack.org/#/c/400432/ ( Show vendor products on vendor page ) 19:28:05 <pvaneck> looks like andrey already reviewed. so will take a look 19:28:07 <catherineD> every one please review 19:28:30 <catherineD> pvaneck: ok that is good ... 19:29:22 <sslypushenko_> catherineD: ok 19:29:34 <catherineD> moving on .. 19:29:38 <catherineD> #topic Tempest config script 19:30:43 <catherineD> so this effort was leading by dmellado: and gema: 19:31:14 <luzC> is this related to the hangout from last week? 19:31:22 <catherineD> #link Tempest config working document ( https://docs.google.com/document/d/1UCtpUfZBDBecRKzBwbko8PWmXz3T2UQ5QV4dL1G-5lE/edit ) 19:31:31 <catherineD> luzC: yes .. 19:32:07 <catherineD> just want to post the link here 19:33:01 <catherineD> luzC: so we decided that the script and code will be reside in a separated github repository to begin with 19:33:02 <sslypushenko_> catherineD: it is awesome! 19:33:16 <catherineD> and later move to refstack-client if needed 19:33:49 <luzC> cool 19:33:56 <sslypushenko_> maybe we can just put in refstack-client / tools 19:34:00 <catherineD> sslypushenko_: yea dmellado: had the script already ... once he publishes the location we call can test 19:34:12 <catherineD> sslypushenko_: yup 19:34:38 <catherineD> I will inivte them to our meeting next week if possible 19:35:03 <catherineD> #topic Open discussion 19:35:56 <catherineD> any topic we want to to discuss ? 19:36:31 <luzC> I have a WIP patch 19:36:50 <luzC> related for the renaming of Defcore 19:36:51 <catherineD> luzC: yea the Defcore name change .. 19:36:56 <catherineD> :-) 19:37:26 <luzC> yes, but so, should "Defcore guideline" be changed to "Interop Guideline" 19:37:27 <luzC> ? 19:37:30 <catherineD> so my suggestion is wait until DefCore complete their change and then we will update our site 19:38:21 <catherineD> luzC: yea that is something that we should discuss ... 19:39:03 <luzC> ok, sounds good to me :) but the process is first changing the code via a patch merge it into master and last step moving latest branch into the site? 19:39:23 <catherineD> to me "Interop Guideline" has a bigger scope ... where DefCore guideline is very precise that this is the guideline for Defcore purpose 19:40:29 <sslypushenko_> Interop guideline sounds good 19:40:32 <catherineD> so customized guideline that Andrey were targeting be would be one type of guildeline and defcore guildeline is an other type ... but all of them are for interop purpise 19:40:54 <catherineD> purposes ... 19:41:01 <sslypushenko_> I gives a chance for non-Defcore guidelines ) 19:41:21 <catherineD> sslypushenko_: absolutely .. 19:42:10 <catherineD> so I kind of hesitate to call DefCore Guideline --> Interop Guideline ... as I said before Interop Guideline would be something wth a bigger scope 19:42:32 <luzC> mmm I see... so ultimately is defcore group defining the "public name" for the guideline, right? I mean keep calling it defcore guideline vs something else? 19:43:12 <catherineD> so today you pass the DefCore guideline you can be verified for OpenStack Logo ... but it does not mean that those cloud are interop (at least not yet). 19:44:38 <catherineD> we still far away from setting a guideline that guarantee interop .. that is the target but we (DefCore) are not there yet ... 19:45:46 <luzC> ok, I'll hold on the changes until the other changes land on defcore 19:46:13 <catherineD> yea we should give some thought on this ...once we allow Andrey's customized guidelines in ... we need someway to differentiate ... the name DefCore Guideline was perfect and prescise ... but they change their name 19:46:29 <catherineD> luzC: yup ...thx 19:46:57 <catherineD> anything else? 19:47:17 <catherineD> luzC: thx for bringing up the guideline topic 19:48:33 <catherineD> sslypushenko_: this is US Thanksgiving Holidays week ... for IBM at my location we have Thurs and Friday off ... 19:48:45 <catherineD> luzC: How about you? 19:48:59 <catherineD> do you have Friday off as well? 19:49:04 <luzC> yes, me too 19:49:24 <luzC> both days off :) 19:49:56 <catherineD> nice 19:50:11 <catherineD> I guess only sslypushenko_: need to still working :-) 19:51:21 <catherineD> if there is nothing else ... let's end the meeting ... Thank you all! Bye 19:51:47 <catherineD> #endmeeting