19:00:17 <catherineD> #startmeeting refstack
19:00:18 <openstack> Meeting started Tue Apr 18 19:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:22 <openstack> The meeting name has been set to 'refstack'
19:01:52 <pvaneck> o/
19:02:29 <mguiney> o/
19:02:48 <catherineD> hello
19:03:04 <catherineD> #link meeting agenda and notes,  https://etherpad.openstack.org/p/refstack-meeting-17-04-18
19:05:32 <catherineD> alright, let's start
19:05:44 <catherineD> #topic Displaying RefStack documentation
19:06:21 <pvaneck> did not quite have time to work on it last week, but should be able to this week
19:06:42 <sslypushenko_> o/
19:06:42 <catherineD> pvaneck: sure .. thanks!
19:06:53 <catherineD> sslypushenko_: hello
19:07:26 <catherineD> agenda https://etherpad.openstack.org/p/refstack-meeting-17-04-18
19:07:43 <catherineD> #topic Update existing certified data with the verified flag
19:08:37 <catherineD> pvaneck: sslypushenko_: could you take a look at the comments on https://review.openstack.org/#/c/452518/  ...
19:09:15 <mguiney> I think that you were definitely on point on those, and I can get that adjusted
19:09:29 <catherineD> mguiney: thx for agreeing to work on a new version
19:09:47 <catherineD> since mguiney: going it work on a new version ...
19:10:25 <catherineD> it would be nice of we give any inputs you have in mind ... it may reduce the number of revision
19:10:28 <mguiney> It should be a nice simplification. I wrote the current version assuming that people would try and put multiple result links on hte same line, but I think it is fair to make them do one link per entry
19:11:08 <catherineD> mguiney: I think so .. on test_id (test link) per link is a good assumption
19:11:47 <catherineD> also there should be no duplicate test link ... that is one test id can not be used for verification more than one time
19:12:26 <sslypushenko_> I fully support idea of using API instead of direct DB quires.
19:12:32 <mguiney> ah. So adding a check for uniqueness would also be beneficial
19:13:14 <sslypushenko_> If there is some missing points in API then it is better to adjust API then do DB quires
19:13:39 <catherineD> also I think you need to authenticate before sending the POST/PUT request .. see the example in https://review.openstack.org/#/c/396700/
19:13:59 <catherineD> sslypushenko_: ++
19:14:03 <mguiney> sslypushenko_: I removed direct queries in the last patch, I believe, in favor of using the API. It had previously been used in one spot to get a type of ID from the db that, on closer inspection, was not strictly required.
19:14:14 <mguiney> I will check this out
19:14:23 <mguiney> apologies for how drawn out this process has been
19:14:31 <catherineD> mguiney: not at all ...
19:14:37 <rockyg> o/
19:14:52 * catherineD waves at rockyg:
19:15:31 <catherineD> mguiney: this is the beauty of open source and benefit of code review
19:15:48 <sslypushenko_> mguiney:  it looks you are on the right way now) I hope new auth system will help you
19:17:08 <catherineD> sslypushenko_: definitely without your auth patches .. this would not be possible .. because the script really need to be run by a user belong to openstack foundation ... autth is needed
19:17:15 <rockyg> mguiney, ++  always slow to get started in getting patches merged
19:17:33 <mguiney> it should be helpful, thank you sslypushenko_ !
19:17:45 <catherineD> This question is for everyone ...
19:18:20 <catherineD> our server is right now running with python 2.7 .. do we need the script to run with 2.7 or do we care which version it should be run on?
19:19:02 <pvaneck> dont care
19:19:34 <rockyg> agree.
19:19:38 <sslypushenko_> as long as script is consuming API it can be run with any version of python
19:19:52 <rockyg> That's at least 2.7
19:20:15 <catherineD> alright... do we need to speciy which version it run on or do we let the user to find out?
19:20:25 <pvaneck> the script already specifies python 3
19:20:43 <mguiney> If it would be helpful, i can add that explicitly into the doc rst for the script
19:21:14 <catherineD> mguiney: thank you!
19:21:58 <catherineD> any other thoughts on this subject?
19:22:04 <mguiney> excellent. Thank you all for the feedback!
19:22:37 <catherineD> moving on ...
19:23:13 <catherineD> #topic Pending reviews
19:23:17 <catherineD> #link     Change doc references from DefCore to Interop Working Group  (  https://review.openstack.org/#/c/390881/  )
19:23:52 <catherineD> For this patch, we are still waiting for https://review.openstack.org/#/c/433414/ to merge
19:24:10 <catherineD> until then nothing we can do
19:24:34 <catherineD> #link     Add scripts for running refstack-client in docker (  https://review.openstack.org/#/c/430701/  )
19:24:42 <catherineD> sslypushenko_: thanks for the new patch ..
19:24:55 <catherineD> I did not have time to test it yesterday ..
19:25:12 <sslypushenko_> good) I hope it will work now
19:25:13 <catherineD> will run some test soon ..
19:25:39 <catherineD> everyone  please review https://review.openstack.org/#/c/430701/
19:25:48 <sslypushenko_> I just need provide one more patch with minor fixes regarding Luz's comments
19:26:18 <catherineD> sslypushenko_: ok great ..
19:26:19 <sslypushenko_> But it already should works fine
19:26:56 <catherineD> #topic     Open discussion
19:29:11 <catherineD> The OPNFV certification team is thinking about working with our team to reuse the tool-chain that we already have. Since they need to run more tests other than tempest, they wasn�t sure if they  could reuse our schema.
19:29:51 <catherineD> it is nice to see that the RefStack resouce can be used somewhere else ..
19:30:07 <rockyg> ++
19:30:08 <catherineD> So I will inivite them to our meeting sometime ...
19:30:45 <sslypushenko_> That is awesome !
19:30:55 <catherineD> yea I think so ...
19:31:25 <catherineD> For schema, DefCore (Chris) is working on a more flexible version https://review.openstack.org/#/c/430556/
19:32:06 <catherineD> so that may make RefStack become a general certification tools (framework ?)
19:32:10 <catherineD> we will see
19:32:31 <catherineD> I am happy to hear that someone is interesting in our work ..
19:32:39 <rockyg> ++
19:32:42 <mguiney> nice!
19:33:02 <rockyg> maybe now we can also get the other test sets in, too.
19:33:10 <catherineD> kudo to the RefStack team ... let's make this happens
19:33:21 <catherineD> rockyg: yup
19:33:34 <sslypushenko_> at least someone is interesting in our work... again)
19:33:45 <catherineD> sslypushenko_: exactly!!
19:33:56 <rockyg> yes!
19:34:00 <sslypushenko_> I hope we are more ready for cooperation )
19:34:22 <sslypushenko_> New schema looks very promising )
19:34:36 <mguiney> ++
19:34:40 <catherineD> sslypushenko_: yea .. I know that Kubernetes is working on conformance test too ... we have a lot of experiences to share
19:35:08 <catherineD> that is all the topics for to day ...
19:35:31 <rockyg> Plus, much of the networking open source projects rely on OpenStack, so more might be interested in using our platform.
19:36:11 <mguiney> nice!
19:36:13 <catherineD> rockyg: good to hear
19:36:28 <catherineD> anything else to discuss today?
19:37:03 <rockyg> I'll see if we can start a conversation with ODL
19:37:13 <catherineD> ODL?
19:37:32 <rockyg> Open Daylight.  SDN project.  runs on OpenStack.
19:37:57 <catherineD> ic
19:38:16 <catherineD> that would be nice since OPNFV is doing that already ..
19:38:27 <rockyg> #link https://www.opendaylight.org/
19:39:11 <catherineD> alright .. anything else?
19:39:47 <catherineD> if not let's end early today ...
19:39:53 <catherineD> thank you all!
19:39:58 <catherineD> bye!
19:40:00 <mguiney> have a good day!
19:40:10 <sslypushenko_> bye!
19:40:14 <rockyg> Enjoy Spring!
19:40:15 <catherineD> mguiney: you too!
19:40:47 <catherineD> rockyg: and allergy :-(
19:41:04 <catherineD> #endmeeting