19:02:44 <catherineD> #startmeeting refstack
19:02:45 <openstack> Meeting started Mon Jul 13 19:02:44 2015 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:02:49 <openstack> The meeting name has been set to 'refstack'
19:03:03 <catherineD> Roll call
19:03:16 <sslypushenko__> o/
19:03:17 <pvaneck> o/
19:03:21 <hogepodge> o/
19:03:30 <catherineD> agenda #link https://etherpad.openstack.org/p/refstack-meeting-15-07-13
19:04:03 <davidlenwell> o/
19:04:23 <catherineD> hello everyone ..
19:04:27 <davidlenwell> hi!
19:04:36 <catherineD> #topic Relocate RefStack Project
19:04:55 <davidlenwell> hi .. sorry .. that was my task.. and Akanda related work has consumed my entire week..
19:06:43 <pvaneck> This is just the project rename?
19:07:12 <catherineD> No this is moving our project to OpensStack-Infra
19:07:38 <catherineD> I believe we will need to submit patch(es) to Infra ...
19:08:10 <hogepodge> I'm not certain how to move the hosting forward now that the spec has been approved
19:09:02 <catherineD> davidlenwell: do you know what need to be done to go forward ?  Or do we need to find out?
19:09:31 <davidlenwell> fungi: can you answer the question from hogepodge ?
19:09:38 <pvaneck> so we do have this review up in system-config: #link https://review.openstack.org/#/c/198869/
19:10:06 <fungi> davidlenwell: hogepodge: i added a review to create the server, but it needs some more work and i'm in and out of availability since i just bought a house
19:10:12 <fungi> anyone is welcome to take over that review
19:10:26 * fungi digs up the link from last week
19:10:37 <catherineD> I https://review.openstack.org/#/c/198869/ is to create server ..
19:11:38 <catherineD> we are discussing moving Refstack project from stackforge to OpenStack-Infra
19:12:04 <davidlenwell> yes .. So I don't know the exact steps for this .. but I imagine its a governacne patch and a infra projects patch to make it sop
19:12:07 <davidlenwell> so
19:12:18 <fungi> yep, sorry that's the right one. i'm trying to internet from a wireless modem since this house has no internet hooked up yet
19:16:58 <catherineD> fungi: do you know the exact steps to move the Refstack project from stackforge to OpenStack_Infra?
19:17:13 <catherineD> fungi: or do you have a contact name?
19:18:00 <catherineD> I guess we can discuss with fungi: later ...
19:18:33 <fungi> catherineD: did the technical committee approve refstack as a new project, or was an existing official project team identified who will be responsible for it?
19:19:25 <catherineD> fungi: I don't think we have get the apporval from the technical committee yet ...
19:19:26 <davidlenwell> fungi: infra is the responsible team as far as I know
19:19:26 <fungi> the first step is to get it accepted by the technical committee into the list at http://governance.openstack.org/reference/projects/index.html
19:19:34 <catherineD> I guess that would be our next step ..
19:20:27 <fungi> oh, if refstack is going to be part of openstack-infra specifically then check with jeblair since he's the ptl of the project-team you say is adopting refstack
19:21:22 <catherineD> fungi: thx so checking with jeblair is our next step then?
19:21:23 <fungi> note that hosting the web service on our servers doesn't _necessarily_ mean that the software running that web service is governed by the infra project-team
19:22:11 <catherineD> davidlenwell: would you like to contact jeblair or I can help too ...
19:22:12 <fungi> catherineD: from what davidlenwell is saying, it sounds like there must have already been some existing conversation implying that refstack was going to become an openstack-infra repo rather than remaining a separate project-team
19:23:31 <catherineD> fungi: unless davidlenwell: had contacted jeblair else thus far the conversasions were among Refstack team ..
19:24:04 <davidlenwell> jeblair and I have had this discussion since the begining of refstack
19:24:15 <davidlenwell> it should come as a surprise to him
19:24:45 <catherineD> #action davidlenwell: catherineD: to contact jeblair for next steps to relocate Refstack to OpenStack-Infra
19:24:45 <fungi> anyway, those are the two options. either stackforge/refstack is adopted by an existing project-team recognized by the tc, or asks the tc to recognize it as a new project-team
19:25:07 <catherineD> fungi: thx ..
19:25:11 <davidlenwell> I think the plan was always to fall under infra
19:25:21 <lifeless> o/
19:25:23 <davidlenwell> not to be our own project
19:25:27 <davidlenwell> hi lifeless
19:25:30 <fungi> and then we have a change to the openstack/governance repo to indicate the change in namespace, and a corresponding change to openstack-infra/project-config to edit it in all the configuration files for the new name
19:25:33 <catherineD> davidlenwell: We have decided to move under Infra
19:25:49 <davidlenwell> catherineD: I'm aware of that .. im not talking abotu name space
19:25:53 <davidlenwell> im talking about goverance
19:25:59 <catherineD> davidlenwell: ic
19:26:14 <davidlenwell> if any project team should own refstack .. its infra
19:27:15 <catherineD> ready to move onto the next topic ?
19:27:52 <catherineD> #topic refstack.net Site
19:28:04 <davidlenwell> yes
19:28:32 <davidlenwell> So I've moved refstack.net to a dreamhost compute instance.. this instance is free for as long as we need it.. There will be no more 173 dollar bills
19:28:48 <catherineD> hogepodge: As discusse last week, David got a bill for $187 for refstack,net .. you were checking on whether OpenStack Foundation can sponsor and reimburse ?
19:28:50 <davidlenwell> hogepodge:  has already agreed to have the foundation reimburse me for the charges on the original
19:29:01 <catherineD> davidlenwell: wow
19:29:01 <davidlenwell> catherineD:  its done
19:29:19 <catherineD> hogepodge: thank you sooooo much!!!
19:29:31 <hogepodge> no problem
19:30:02 <catherineD> so refstack.net is now on DreamHost ...
19:30:17 <catherineD> #topic Infra Hosting
19:30:57 <catherineD> This is https://review.openstack.org/#/c/198869/  ...
19:32:02 <catherineD> lifeless: would you be able to help review https://review.openstack.org/#/c/198869/  ?
19:33:56 <pvaneck> the puppet repo is in infra as mentioned last week.
19:34:05 <pvaneck> i submitted a patch here: https://review.openstack.org/#/q/project:openstack-infra/puppet-refstack,n,z
19:34:17 <pvaneck> not sure who is core there
19:34:44 <catherineD> I guess we will need some help on  https://review.openstack.org/#/c/198869/ ...
19:35:06 <catherineD> and Paul's patch ....
19:37:31 <catherineD> #action Paul to find out core to approve https://review.openstack.org/#/c/198910/
19:39:23 <catherineD> #action checking on status of https://review.openstack.org/#/c/198869/ next week
19:39:49 <catherineD> #topic Set up eavesdrop for refstack channel
19:40:21 <catherineD> hogepodge: https://review.openstack.org/#/c/198621/   was merged ... any next steps ...?
19:40:42 <hogepodge> Nope, should be good to go.
19:40:55 <hogepodge> it's automated, so everything is in place
19:41:12 <catherineD> hogepodge: great .. thx a lot! ..
19:41:51 <catherineD> for taking care of this ... now we have our #refstack logs for review  ...
19:42:07 <catherineD> #topic Tokyo Refstack  sessions
19:43:03 <catherineD> hogepodge: It would be nice if we can have a formal schedule (time and room) for Refstack meeting at Tokyo ... do you know what we need to do to schedule?
19:43:25 <davidlenwell> There are usually open meeting rooms that people can use adhock
19:44:12 <hogepodge> I can ask around. The process behind the room selection for summits can be opaque to me. Room space is going to be really hard for Tokyo. We just don't have the room that we had in Vancouver
19:44:28 <catherineD> davidlenwell: yes that were what we did in the last 2 summit ...
19:44:37 <davidlenwell> usually there is a breakout room
19:44:50 <catherineD> hogepodge: ic ..
19:45:38 <catherineD> #action hogepodge: to try find out whether it is possible to schedule a room for Refstack meeting at Tokyo
19:46:28 <catherineD> we will  submit a speaker session for #refstack ... Could you please review https://etherpad.openstack.org/p/refstack_tokyo_speaker_session
19:46:55 <sslypushenko__> Looks good)
19:47:28 <catherineD> sslypushenko__: hope we can meet you at Tokyo
19:47:46 <catherineD> #topic OpenStackID integration
19:47:52 <sslypushenko__> I hope too)
19:48:34 <catherineD> OpenStackID integration is moving on welll ... sslypushenko__: has 2 WIP ...
19:48:52 <catherineD> sslypushenko__: is this https://docs.google.com/presentation/d/1v7exKKL1zSA102Xu8FkY1u9rMVUE6BjwUCoWGYYvbaI/edit#slide=id.g3005a843b_0_11
19:49:15 <sslypushenko__> It needs to be updated
19:49:19 <catherineD> still good ?  I want to add that doc to refstack wiki ..
19:49:54 <sslypushenko__> I'm planning to finish UI for uploading pubkeys
19:50:02 <catherineD> sslypushenko__: ok I will wait then ... Please let me know when you have the update ... no hurry we can work on merging the UI code first ...
19:50:26 <catherineD> #topic Refstack need SSL
19:50:29 <sslypushenko__> And than I'll update docs
19:50:46 <davidlenwell> catherineD:  isn't registering ssl for refstack.org part of the infra hosting thing?
19:50:47 <catherineD> sslypushenko__: great thx ..
19:51:27 <catherineD> davidlenwell: just want to see is there anything else?
19:51:28 <catherineD> if that is it then we have it cover ...
19:51:42 <davidlenwell> I believe they'll handle that
19:52:00 <catherineD> ok then that is good ...
19:52:56 <catherineD> #agree Refstack SSL will be handled with Refstack server hosting at Infra
19:53:06 <catherineD> #topic subunit2sql evaluation and adoption
19:53:35 <catherineD> sslypushenko__: you were looking at subunit2sql ...
19:53:37 <sslypushenko__> catherineD I have a bad new about subunit2sql
19:53:44 <sslypushenko__> *news
19:54:17 <sslypushenko__> It cann't be used by refstack right now
19:54:22 <catherineD> what is it?  We won't be able to adopt ...
19:54:39 <catherineD> yes .. I take a quick look and believe so too ..
19:55:00 <sslypushenko__> subunit2sql doesn't use idempotent ids is test unique indenifier
19:55:20 <davidlenwell> mtreinish: ^^
19:55:42 <sslypushenko__> davidlenwell He is on top of it
19:56:06 <sslypushenko__> We need to resolve uuid duplication issue first
19:56:08 <mtreinish> sslypushenko__: that shouldn't be a blocker for adoption
19:56:20 <sslypushenko__> But it is
19:56:35 <mtreinish> you just need to assign additional metadata to tests like I described in my email
19:57:05 <sslypushenko__> Right not any test move will broke test results
19:57:52 <sslypushenko__> So we need to track changes og test FQN to undestand the real results
19:58:12 <mtreinish> sslypushenko__: no it won't all the data is there it's just not the primary key
19:58:35 <catherineD> mtreinish: the other reason that I see we won't be able to adopt for now isfor refstack the subunit processing is done at server side ... and #resstack does not ship the subunit file only the pass tests... so the process had to ben done at the client side which has no DB ...
19:58:49 <sslypushenko__> It will be better finally solve issue with uuid duplication
19:59:38 <mtreinish> catherineD: well I've always found that model weird, but you don't actually have to use the subunit2sql utility. Just leverage the python api to handle writing to the db on the server side
19:59:55 <sslypushenko__> catherineD DB is not a big deal, we can you mysql-in-docker for that
20:00:24 <catherineD> Let's discuss this in #refstack
20:00:32 <sslypushenko__> +1
20:00:49 <catherineD> #endmeeting