19:00:49 <catherineD> #startmeeting refstack
19:00:50 <openstack> Meeting started Tue May 30 19:00:49 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:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:53 <openstack> The meeting name has been set to 'refstack'
19:00:56 <mguiney> o/
19:01:14 <pvaneck> o/
19:01:28 <catherineD> #link meeting agenda and notes,  https://etherpad.openstack.org/p/refstack-meeting-17-05-30
19:01:52 <catherineD> let's wait for a couple mins
19:02:56 <rockyg> o/
19:03:34 <catherineD> let's start
19:03:49 <rockyg> brb
19:04:19 <catherineD> https://etherpad.openstack.org/p/refstack-meeting-17-05-30
19:04:46 <catherineD> #topic Catherine will be away for 2 weeks in June
19:05:26 <catherineD> pvaneck: do you mind running the meeting on June 13 and 20?
19:05:44 <pvaneck> catherineD: sure, though they will likely be brief meetings
19:05:46 <sslypushenko_> o/
19:06:11 <mguiney> o/
19:06:13 <catherineD> pvaneck: I think so ...
19:06:47 <catherineD> pvaneck: Thanks!
19:06:58 <catherineD> #topic Displaying RefStack documentation
19:07:47 <catherineD> Finally https://review.openstack.org/#/c/460787/ was merged last week ...
19:08:07 <mguiney> \o/
19:08:08 <hogepodge> o/
19:08:12 <catherineD> so now we are ready to review https://review.openstack.org/#/c/460746/
19:08:57 <rockyg> o/
19:09:02 <catherineD> everyone please review https://review.openstack.org/#/c/460746/   this would be the last one for this series of patch to render the doc in HTML at the RefStack website
19:10:46 <catherineD> pvaneck: do you have any other thoughts on this topic?
19:11:21 <pvaneck> catherineD: eh not really. Will ask infra to review later to speed up the merging process
19:12:06 <catherineD> pvaneck: ok thx
19:12:21 <rockyg> ++
19:12:40 <catherineD> #topic Update existing certified data with the verified flag
19:13:20 <catherineD> The Add a script to update the internal RefStack DB  (  https://review.openstack.org/#/c/452518/ )  was merged May 22
19:14:45 <catherineD> hogepodge: mguiney: before we run this scripts ... I feel like we need one more tool as suggested in the next item .. we also need to coordinate to have a backup of the db before running the script
19:15:10 <catherineD> because the script will make update the the db
19:15:11 <hogepodge> ok
19:15:34 <catherineD> Let's discuss the additional tool in the next item
19:15:49 <catherineD> #topic Tools to check whether test links in a spreadsheet are marked as verified in RefStack
19:16:50 <catherineD> Based on the testing experiences so far, some of the test record may not have the verification flag update.  We need a tool to chech that ..
19:17:00 <catherineD> this is my suggestion ..
19:17:43 <mguiney> to check if the results have previously been verified?
19:17:46 <catherineD> question: should this be a stand-alone script or should it be part of the update-rs-db.py?
19:17:53 <catherineD> mguiney: yes
19:18:12 <mguiney> that strikes me as as something that would be fairly simple to implement as a part of the original script
19:18:39 <catherineD> the main reason is to check what are the records that should be verified but are not
19:18:56 <mguiney> ahhh... interesting
19:19:09 <mguiney> hogepodge: what are your thoughts on the matter?
19:19:27 <catherineD> so the output would be another csv file ..
19:19:43 <mguiney> of results that still need verification
19:19:57 <hogepodge> I don't think I entirely understand.
19:21:19 <hogepodge> so it's hard for me to say exactly what my thoughts are
19:21:54 <catherineD> So you have an original spreadsheet with all the links that you want to have the verification flag set as true (verify) by the update-rs-db script
19:23:10 <hogepodge> yes, it's being maintained by us. There are a lot of new entries over the last few months
19:23:30 <hogepodge> as entries are added or updated
19:23:41 <catherineD> but for some reason the update is not done because it failed one of the many checking step before the verification flag can be altered
19:24:03 <catherineD> You need to be able to identify those records (links)
19:24:33 <mguiney> ahhhh so a list of tests that failed due to the records being incomplete
19:24:44 <hogepodge> How much of that can be automated? What's the workflow we're talking about here, and the action that I or mguiney need to take?
19:24:57 <catherineD> mguiney: no just failed the complete list ...
19:25:07 <catherineD> of pass and fail
19:25:44 <catherineD> hogepodge: it is automated right now with the update-rs-db script
19:25:49 <catherineD> this is just a safety check
19:26:05 <hogepodge> ok
19:27:13 <catherineD> mguiney: do you think you can take the task to create this checking feature?
19:27:41 <mguiney> I think I can, but I am still not sure exactly what the csv would hold, ideally
19:28:05 <mguiney> would it be all of the records from the original that failed for any given reason?
19:28:54 <catherineD> the columns described in ron 26-29 of all records ...
19:29:21 * mguiney nods
19:29:24 <mguiney> ok, can do
19:29:59 <catherineD> there are not pass or fail here ... you just take a test link from the input files and get the records from (26 - 29) and write it out to a csv.
19:30:29 <mguiney> ok, I can do that
19:31:02 <catherineD> if all the value in the verication column is true then the automation is 100% sucsses ... else need to investigate the failure reason
19:31:48 <catherineD> mguiney: it is up to you whether you want it to be a new script or a sub command of the existing script
19:32:30 <mguiney> ok. I will poke around at that and try to get a patch pushed shortly
19:33:04 <catherineD> mguiney: thank you!  refstack-client should have sample on subcommand
19:33:26 <catherineD> anything else on this topic?
19:34:00 <catherineD> moving on ...
19:34:05 <hogepodge> I have questions, but I don't know how to articulate them, so mguiney can help me understand better this afternoon.
19:34:43 <catherineD> hogepodge: sure ... we can discuss more later ..
19:34:59 <catherineD> #topic Pending reviews
19:35:17 <catherineD> #link Add scripts for running refstack-client in docker (  https://review.openstack.org/#/c/430701/  )
19:35:39 <catherineD> sslypushenko_: I have request Ann to review ...
19:36:16 <catherineD> mguiney: and I have reviewed and it looks good to us ..
19:36:55 <mguiney> i think the previous issue was with it running on mac, though, and I tested against ubuntu
19:37:18 <sslypushenko_> It doesn't cover all  possible cases, but should be suitable
19:37:25 * mguiney nods
19:37:36 <catherineD> I also tested it on Ubuntu ...Anne is testing on Mac
19:37:38 <sslypushenko_> at least for development on Linux)
19:38:16 <catherineD> let wait for Anne's response ... then I think this patch is ready for merging
19:38:29 <sslypushenko_> I can't test it on Mac)
19:38:59 <catherineD> I know
19:39:04 <catherineD> ok moving on ...
19:39:04 <hogepodge> I can test on mac too
19:39:13 <sslypushenko_> so will see what Anne says
19:39:17 <catherineD> hogepodge: what would be great
19:39:26 <hogepodge> (not that I've ever run docker on mac, I just do it on linux, but I have a mac)
19:39:54 <catherineD> moving on ..
19:40:18 <catherineD> #link Add 'rm -f .testrepository/times.dbm' command in testenv ( https://review.openstack.org/#/c/459634/ )
19:40:55 <catherineD> pvaneck: I guess we are waiting for response to your review?
19:41:29 <pvaneck> yes, seems so.
19:42:12 <catherineD> Let me try to ping him offline ..
19:42:47 <catherineD> That is all the topics we have for today ...
19:42:52 <catherineD> #Open discussion
19:43:11 <catherineD> #topic Open discussion
19:44:15 <catherineD> sslypushenko_: hogepodge: mguiney: pvaneck: rockyg: Is there any other topic we should discuss today?
19:44:35 <sslypushenko_> nothing from me
19:44:45 <rockyg> none from me
19:44:54 <mguiney> noop!
19:45:25 <hogepodge> I'm good
19:45:29 <hogepodge> Thanks catherineD
19:45:39 <catherineD> Alright ... we can end the meeting early then ...
19:45:46 <catherineD> thank you all!
19:45:51 <mguiney> have a good day!
19:46:01 <catherineD> #endmeeting