19:00:24 <catherine_d|1> #startmeeting refstack
19:00:25 <openstack> Meeting started Tue Oct  4 19:00:24 2016 UTC and is due to finish in 60 minutes.  The chair is catherine_d|1. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:28 <openstack> The meeting name has been set to 'refstack'
19:00:37 <pvaneck> o/
19:00:39 <hogepodge> o/
19:00:56 <catherine_d|1> #link meeting agenda and notes, please feel free to add items https://etherpad.openstack.org/p/refstack-meeting-16-10-04
19:02:08 <sslypushenko> o/
19:03:17 <catherine_d|1> agenda https://etherpad.openstack.org/p/refstack-meeting-16-10-04
19:03:42 <catherine_d|1> Let's start
19:04:01 <catherine_d|1> #topic Barcelona summit working session
19:04:11 <Rockyg> o/
19:04:40 <catherine_d|1> Rockyg: did you get the agenda link above?
19:04:54 <Rockyg> yup.
19:04:55 <catherine_d|1> #link     Please add your topics to the etherpad (  https://etherpad.openstack.org/p/refstack-ocata-summit  )
19:06:20 <catherine_d|1> right now we have 3 topics on the agenda for the summit. Please add yours if there is any!
19:06:28 <catherine_d|1> moving on ...
19:06:52 <catherine_d|1> #topic RefStack client  whitelist (test list)
19:07:52 <catherine_d|1> #link The whitelist conversation started from this patch https://review.openstack.org/#/c/381232/
19:08:17 <catherine_d|1> background information ..
19:08:41 <catherine_d|1> refstack-client whitelist was created before ostestr was in place
19:09:27 <catherine_d|1> ostestr now does provide whitelist ... question is :  does refstack-client still need to create the list or can we use the ostestr whitelist?
19:10:10 <Rockyg> good question!
19:10:50 <catherine_d|1> Lucz: may be most familiar with ostestr .. she is not here .. I will contact her ...
19:11:14 <sslypushenko> I guess for now there is no reason to migrate to ostestr
19:11:31 <sslypushenko> *ostestr whitelisting
19:11:36 <hogepodge> catherine_d|1: I think that the new tempest test runner can do that, and mtreinish would really like refstack to move to using it
19:11:38 <catherine_d|1> sslypushenko: we already did from testing point of view ..
19:11:54 <catherine_d|1> hogepodge: that is my intention ..
19:12:01 <sslypushenko> yeap... I meant whitelist thing
19:13:06 <sslypushenko> https://review.openstack.org/#/c/381232/ looks good enough just need some testing
19:13:07 <catherine_d|1> we would like to use whatever tempest provides to minimize maintenant on our side too ,,, whitelist was not provided earlier that is why refstack-client created it ..
19:14:11 <sslypushenko> but if it just works... why we should change things?
19:15:09 <hogepodge> sslypushenko: for features and support from qa team
19:15:20 <catherine_d|1> sslypushenko: to avoid further maintenance ..
19:15:40 <sslypushenko> but then we should maintain our docs
19:15:56 <sslypushenko> because if ostestr change API docs should be updated
19:15:58 <catherine_d|1> but we need to first of all findout whether ther whitelist provides by Tempest is suitable for our use.
19:16:05 <Rockyg> ++ to docs maintenance
19:16:40 <sslypushenko> in other hand... while we use our implementation - docs are up to date)
19:17:09 <catherine_d|1> there is no doc update from our side because the implementation is a black box to RefStack users
19:17:43 <catherine_d|1> it is just code update whether we use our code or ostestr
19:17:59 <sslypushenko> I guess ostestr use a bit different formart
19:18:00 <catherine_d|1> but first of call we need to make sure that we can use ostestr ..
19:18:05 <sslypushenko> then we are using
19:18:41 <catherine_d|1> sslypushenko: that is what we need to find out ... if it does not meet our spec we still need to use ours
19:18:51 <catherine_d|1> I will check with Lucz:
19:19:05 <sslypushenko> http://docs.openstack.org/developer/os-testr/ostestr.html
19:19:19 <sslypushenko> https://www.irccloud.com/pastebin/Y5ipvqxT/
19:19:24 <catherine_d|1> #action catherine_d|1: to check with Lucz: on whitelist in ostestr vs refstack-client
19:19:30 <sslypushenko> so yes... it has different format
19:19:50 <catherine_d|1> sslypushenko: thx
19:20:05 <catherine_d|1> we will revisit this topic next week
19:20:41 <catherine_d|1> hogepodge: the intention is if there is any feature provides  by tempest we will make sure to use it if we can
19:21:20 <catherine_d|1> anything else on this topic ...
19:21:35 <catherine_d|1> moving on ...
19:21:42 <catherine_d|1> #topic Taget to merge feature/vendor to master
19:22:17 <catherine_d|1> right now all the vendor and product registration patches reside in the feature./vendor branch
19:22:35 <catherine_d|1> we want to merge this branch to master before the summit ...
19:22:53 <catherine_d|1> the target dates are list in the agenda ..
19:23:06 <catherine_d|1> we have a very tight schedule ...
19:23:53 <catherine_d|1> pvaneck: how many more pathes do you think we need ?
19:24:28 <pvaneck> catherine_d|1, hard to say exactly, but for essentials, i have 2-3 more coming up
19:24:47 <catherine_d|1> pvaneck: thx
19:25:04 <catherine_d|1> according to the schedule on the agenda
19:25:18 <catherine_d|1> Target date to merge all pending patches to feature/vendor branch:  Oct 12, 2016
19:25:58 <catherine_d|1> in order to meet the Oct 12 target dates ... we need your help to review the patches as soon as it appears on the system
19:27:00 <catherine_d|1> sslypushenko: I would probably bother you and Andrey a lot during this time ....
19:27:28 <sslypushenko> me - definitely not)
19:28:11 <catherine_d|1> sslypushenko: thx ... we just want a last push to achieve what we set forward for this cycle
19:28:33 <sslypushenko> yeap... this thing is very important
19:28:39 <catherine_d|1> it would be our significant accomplishment once we have vendor/product registraton on line ...
19:29:06 <sslypushenko> +
19:29:17 <catherine_d|1> after all we have been work on this for at least 3 cycle (from discussion to implemenation ...)
19:29:26 <catherine_d|1> thank you all ...
19:29:37 <catherine_d|1> too bad Alex and Andrey is noit here today ...
19:29:55 <catherine_d|1> they are a big part for this implemenation
19:30:35 <catherine_d|1> so according to the schedule ... if we have all the patches merge to feature/vendor on Oct 12
19:31:03 <catherine_d|1> we would be able to release the change to the refstack server Oct 17 ...
19:31:11 <sslypushenko> I'd also like to see vendor guidelines... but at least registration is good too
19:31:24 <catherine_d|1> sslypushenko: definitely ...
19:31:34 <catherine_d|1> that would be our Ocata priority
19:32:36 <catherine_d|1> the feature we have today are the fundation for the customized guidelines
19:33:56 <sslypushenko> I have a good example here in Mirantis)) One of our QA teams tries reinvent tempest because of lack of custom guidelines ))) it looks pretty funny)
19:34:15 <catherine_d|1> I just add the guideline topic to the summit etherpad
19:34:23 <catherine_d|1> sslypushenko: that is good
19:34:52 <sslypushenko> will see))
19:35:09 <catherine_d|1> anything else?
19:35:31 <catherine_d|1> moving on then ..
19:35:35 <catherine_d|1> #topic Pending reviews
19:35:46 <catherine_d|1> waiver patches
19:36:01 <catherine_d|1> #link   Spec:   Implement additional properties Defcore waiver   https://review.openstack.org/#/c/349213/
19:36:46 <catherine_d|1> hogepodge: and catherine_d|1: have reviewed ... sslypushenko: pvaneck: please review ... I think this patch is ready to merge
19:37:59 <catherine_d|1> #action sslypushenko: pvaneck: to review https://review.openstack.org/#/c/349213/
19:38:16 <pvaneck> okay
19:38:26 <catherine_d|1> once this spec is merge we then can review the implementatiom
19:38:50 <catherine_d|1> #action everyone please review     Implemenation: Added Defcore additional properties waiver  https://review.openstack.org/#/c/370534/
19:39:14 <catherine_d|1> next
19:39:19 <catherine_d|1> #link     Add verification_status field to test   https://review.openstack.org/#/c/379839/
19:39:51 <catherine_d|1> I guess pvaneck: will push an update and we will review again?
19:40:03 <pvaneck> yep, working on it now
19:40:15 <catherine_d|1> pvaneck: thx
19:40:30 <catherine_d|1> next
19:40:34 <catherine_d|1> #link     Fix regex to find test id  (  https://review.openstack.org/#/c/381232/  )
19:40:40 <catherine_d|1> we talked about this
19:41:12 <catherine_d|1> if the whitelist from ostestr and refstack-client are differenet ... we will review and merge this patch
19:41:51 <catherine_d|1> I will check with luxC as stated earlier ....  I can also review the link provided by sslypushenko: earlier
19:42:11 <luzC> hello... sorry to be so late...
19:42:52 <catherine_d|1> luzC: np  it is ealiser to assign work to you while you are not here :-)
19:43:10 <luzC> :-)
19:43:43 <catherine_d|1> just kidding pls review the log essentially we want to check whether the whitelist provides by ostestr can be used by refstack-client
19:44:28 <catherine_d|1> so refstack-client does not duplicated the feature that is now provided by ostestr ... you and I can discuss offline
19:44:44 <catherine_d|1> moving on
19:44:50 <catherine_d|1> #link     Fix missing dependency in refstack-client  (  https://review.openstack.org/#/c/361189/  )
19:44:57 <catherine_d|1> I have +2 this path ...
19:45:18 <catherine_d|1> basically it is a nice to have package ...
19:46:27 <catherine_d|1> refstack-client has been able to run without it ,,, but it does not hurt to include this package
19:47:03 <catherine_d|1> #action sslypushenko: pvaneck: luzC: to review and merge https://review.openstack.org/#/c/361189/
19:47:35 <catherine_d|1> anything else?
19:48:19 <catherine_d|1> if not we can end the meeting 12 mins early today :-)
19:48:25 <luzC> about the whitelist... I added that method (list_parser.create_whitelist) in the patch when using ostestr...
19:49:23 <luzC> basically instead of a file with a list of names... it use a file with a list of test ids
19:49:42 <catherine_d|1> luzC: could you check whether this whitelist can be used for testing>
19:50:24 <catherine_d|1> list of id is not good for refstrack test
19:50:50 <catherine_d|1> since we know that test id is not unique for test
19:50:51 <luzC> yes, this is the list that it is used in refstack and ostestr and the new "tempest run" command...
19:51:17 <luzC> each test case has this unique id
19:51:34 <catherine_d|1> luzC: it does not
19:51:52 <luzC> how come?
19:52:03 <catherine_d|1> each test method has unique id ...
19:52:49 <catherine_d|1> but each test case which is identified with fully qualified test name can be referred to the same test id
19:53:04 <catherine_d|1> luzC: let's discuss this at #refstack
19:53:15 <luzC> ok
19:53:25 <catherine_d|1> anything else beside whitelist?
19:54:05 <catherine_d|1> thank you everyone!
19:54:16 <catherine_d|1> #endmeeting