18:56:18 <davidlenwell> #startmeeting refstack
18:56:19 <openstack> Meeting started Mon Dec 15 18:56:18 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:56:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:56:23 <openstack> The meeting name has been set to 'refstack'
18:57:07 <hogepodge> o/
18:58:58 <davidlenwell> I was a little early.. we'll give folks a few minutes ..
18:59:07 <davidlenwell> I heard back from rocky.. she probably won't be joining us
19:02:00 <zehicle> o/
19:02:07 <_0x44> o/
19:02:11 <zehicle> sorry, I've been absent
19:02:18 * _0x44 is only here to point at zehicle.
19:02:20 <davidlenwell> you're here now .. thats what matters
19:02:48 <sslypushenko__> o/
19:03:07 <rockyg> O/
19:03:22 <davidlenwell> yay rocky made it
19:03:39 <zehicle> _0x44, changing all my action items over to you :)
19:03:49 <davidlenwell> ha ha
19:04:20 <davidlenwell> alright .. lets get started ..
19:04:30 <davidlenwell> So the first item I'd like to discuss is this.. https://review.openstack.org/#/c/132583/
19:04:37 <_0x44> zehicle: :(
19:04:56 <davidlenwell> hogepodge: that is the review that will fix the problem that we are installing tempest from trunk
19:05:13 <davidlenwell> I'd like some more reviews on it before we think about merging
19:05:29 <davidlenwell> sadly I think catherine is out until jan 5
19:06:03 <davidlenwell> is hogepodge and I can give it a good once over I think we can get it to a mergable place before then.
19:06:17 <sslypushenko__> I tested it on containers with Ubuntu, Centos and Fedora, but additional testinf will be good
19:07:21 <hogepodge> added to the top of my list
19:07:37 <davidlenwell> thanks hogepodge
19:08:19 <davidlenwell> about half my other agenda items are dependant on ibm employees to which catherine has been the conduit .. so I'll table them till I hear back from her.
19:08:36 <davidlenwell> lets go ahead and talk about our plans for a mid-cycle meetup in january
19:10:20 <davidlenwell> #topic mid-cycle meetup
19:10:51 <davidlenwell> I'd like to do a 2-3 day kind of a thing.. rockyg you previously mentioned you could get us space?
19:11:02 <rockyg> Oh darn.forgot to talk to boss but don't see a problem with housing and lunch.
19:11:45 <davidlenwell> so there is an action item for rockyg then
19:11:57 <rockyg> We should announce on mailing list in case others want to participate.
19:12:14 <hogepodge> rockyg If we want to order in for lunch I have a commitment for funding for that.
19:12:31 <rockyg> S/housing/hosting
19:12:50 <davidlenwell> maybe we can do cafateria lunch and use your funding hogepodge for a dinner ?
19:12:52 <rockyg> Kewl. It's a backup plan
19:13:15 <rockyg> That would work, too
19:13:20 <davidlenwell> awesome
19:13:33 <rockyg> Dates?
19:13:34 <hogepodge> I'll have to check on dinner.
19:13:38 <zehicle> when
19:13:44 <davidlenwell> mid january
19:13:51 <zehicle> when is the tempest meetup?  can that be coordinated w/ this?
19:13:56 <zehicle> since that seems gating
19:14:15 <rockyg> That would be great.
19:14:19 <hogepodge> I am on travel 18th - 23rd
19:14:22 <davidlenwell> same
19:14:29 <davidlenwell> 18-25th
19:14:58 <davidlenwell> maybe 14-16
19:15:04 <davidlenwell> would be good dates
19:15:08 <davidlenwell> or earier in that week
19:15:47 <rockyg> Okay by me
19:15:55 <davidlenwell> any objections to those dates?
19:16:04 <davidlenwell> zehicle: it would be awesome if you could make it
19:16:33 <rockyg> When is tempest mid cycle?
19:16:35 <hogepodge> I prefer 12-14, but 14-16 works for me too.
19:16:40 <davidlenwell> okay
19:16:51 <davidlenwell> _0x44 thinks the southbay is mexico .. so he may not attend ;)
19:17:13 <davidlenwell> I think we have enough to do indipendant of their meetup
19:17:21 <zehicle> I'll see what I can do.  Would love to do it but...
19:17:23 <davidlenwell> as long as we aren't conflicting I think it shouldn't matter
19:18:04 * zehicle has to make plans in case I don't make it to the board
19:18:11 <sslypushenko__> What about Mirantis team? May we can attend meetup remotely?
19:19:08 <hogepodge> there is no tempest mid-cycle meetup this time around.
19:19:15 <rockyg> We should be able to arrange a feed. Skype or hangout or something
19:19:58 <rockyg> Kewl.maybe we can get a qa rep to come
19:20:25 <sslypushenko__> Video records would be good
19:20:42 <davidlenwell> yeah .. for sure .. ghang for the win
19:20:59 <davidlenwell> we'll plan an agenda leading up to the event
19:21:19 <davidlenwell> okay .. next topic
19:21:39 <sslypushenko__> I guess your time will not be comfortable for us to join you directly (
19:22:23 <davidlenwell> #topic uuid in tempest spec
19:22:57 <_0x44> The South Bay isn't Mexico, it's just slightly north of Mexico. :)
19:24:03 <davidlenwell> So I'm reworking my original spec to include the meta data in both decorators and doc string
19:24:32 <davidlenwell> I have a feeling some bike shedding will happen once I submit it for review..
19:24:54 <hogepodge> Can we get a draft up in gerrit? I think it's important we we get this out in the open. I'm very worried about the delays.
19:24:55 <davidlenwell> int he mean time we need to land the tagged release review that is out right now so we have a static test path to keep track of
19:25:10 <davidlenwell> hogepodge: I'll throw it at gerrit
19:25:14 <hogepodge> ty
19:25:32 <sslypushenko__> I think decorator - is more preferable
19:25:54 <hogepodge> I think mtreinish and sdague are debating this right now in #openstack-qa
19:25:56 <davidlenwell> hogepodge: said that mtreinish said he wants both
19:26:37 <sslypushenko__> I finished prototype with docstrings - I looks not very good
19:27:06 <rockyg> Hogepodge, I think you're right.
19:27:51 <rockyg> They're talking sphinx
19:28:59 <hogepodge> oh yeah, I see.
19:29:01 <davidlenwell> I'm joining their conversation about this in qa
19:29:09 <_0x44> Why not something like: https://gist.github.com/ChristopherMacGown/d3f02c1cb2e115cf2ed6 ?
19:29:16 <hogepodge> Yes, both places, with validation to make sure they're consistent.
19:29:21 <rockyg> Ah, Davidlenwell is time sharing
19:30:07 <davidlenwell> _0x44: thats essentially the plan
19:30:18 <_0x44> davidlenwell: Right, but the plan is to put it into docstring
19:30:27 <davidlenwell> lets stop bikeshedding on this issue right now and lets work it out with qa ..
19:30:42 <davidlenwell> we cannot decide this without them
19:30:52 <rockyg> ++
19:32:03 <davidlenwell> I'm going to spend some time talking to them this afternoon and we'll come up with the thing.. I'll put it in the spec I've already started and throw it at the wall later today
19:32:10 <hogepodge> This is why the spec needs to be up for comment.
19:32:20 <davidlenwell> agreed
19:32:20 <sslypushenko__> +1
19:32:26 <davidlenwell> we'll get it there today
19:33:37 <davidlenwell> everything else I wanted to talk about depends on people who are not here.. so lets go into pending open reviews
19:34:11 <hogepodge> I'd like to open up the topic for refstack ui and api
19:34:14 <davidlenwell> sslypushenko__: the plan is for hogepodge and I to review your tempest tag review today and land it if its ready
19:34:30 <sslypushenko__> Good!
19:34:34 <hogepodge> Just to get a sense of what we need to get that in a deployable place, even if the implementors aren't here.
19:34:44 <davidlenwell> hogepodge: okay.. the plan was to pass off the development of the api to one of catherines underlings
19:34:58 <davidlenwell> we just need someone to spend a week on it
19:35:00 <zehicle> I've been gone.  I'd love to hear status updates on client, API too
19:35:05 <davidlenwell> I have a good start and the spec is clear
19:35:09 <zehicle> sslypushenko__, did good work on visualizations
19:35:12 <davidlenwell> but I have not had the bandwidth to finish it
19:35:18 <sslypushenko__> Thx
19:35:25 <davidlenwell> the missing piece is the data collection
19:35:27 <davidlenwell> and hosting it
19:35:32 <hogepodge> davidlenwell link to the spec?
19:35:37 <davidlenwell> its in the repo
19:35:54 <sslypushenko__> Yep, We need API thing move forward
19:36:02 <davidlenwell> https://github.com/stackforge/refstack/blob/master/specs/approved/api-v1.md
19:36:19 <davidlenwell> minus the event handing methods
19:36:32 <sslypushenko__> May Vlad and I can help you with API
19:36:35 <sslypushenko__> ?
19:36:35 <davidlenwell> I'll make that another action item for me today
19:36:41 <hogepodge> as far as hosting goes, we can do it, but the faulty UI needs to be removed. As is we can't run it in the namespace
19:36:44 <davidlenwell> of course .. that would be great sslypushenko__
19:37:10 <davidlenwell> hogepodge:  all the ui needs to be removed from the refstack repo
19:37:17 <davidlenwell> with the exception of the score card
19:37:22 <davidlenwell> as that will be an api call
19:37:27 <sslypushenko__> Good, let talk about it in refstack channel later
19:37:31 <davidlenwell> great
19:37:47 <davidlenwell> I'll update the spec and pass development of that piece off to the marantis folks
19:38:29 <davidlenwell> hogepodge: the refstack website itself I've got a single page info thing written and done.. I just need a place to put it
19:38:53 <davidlenwell> zehicle and rockyg and I worked on copy at the summit
19:39:07 <hogepodge> Ok, is it in gerrit?
19:39:16 <rockyg> I'll give it one last pass.
19:39:20 <davidlenwell> no .. we have to decide where it would go in gerrit
19:39:24 <zehicle> even a static page would let us get the process running
19:39:36 <davidlenwell> exactly its all we need
19:39:39 <zehicle> since we could test changes to it via gerrit
19:39:49 <davidlenwell> we just need to work out how we're hosting a single page website .. and how that sits in with the api
19:40:24 <davidlenwell> I'd like api.refstack.org to be different from www.refstack.org which will host this single page
19:40:47 <davidlenwell> and right now they are all kinda mixed up into the same flask app that joshua mkkenty wrote while drunk
19:41:22 <rockyg> Hmm.flask, drunk......
19:41:36 <davidlenwell> So .. sslypushenko__ when we make the new api.. I'd like to just ditch flask all together and make a pecan api like all the other projects have.. then we have have a "static"  folder that has the static website folders in it.
19:42:03 <davidlenwell> lets discuss that in detail in #refstack later today when you are ready
19:42:21 <zehicle> new api?
19:42:28 <davidlenwell> the v1 api
19:42:32 <zehicle> ok
19:42:33 <sslypushenko__> We can start right now)
19:42:54 <sslypushenko__> pecan - is not bad choose)
19:42:57 <davidlenwell> right after the meeting jump in #refstack with me and I'll get you started
19:43:35 <sslypushenko__> ok
19:43:54 <davidlenwell> hogepodge: does this plan of action sound good?
19:44:11 <hogepodge> Yes.
19:44:18 <davidlenwell> cool ..
19:44:21 <rockyg> +1
19:44:32 <davidlenwell> any other items that need discussion?
19:44:52 <hogepodge> I've put together a rough timeline of where we need to be for testing production deployments.
19:45:51 <rockyg> Where is it? It'd like to review.
19:45:57 <hogepodge> I'm scheduling client and api work to be done by end of January so that we can spend February making sure the tests are sound.
19:46:34 <hogepodge> https://etherpad.openstack.org/p/refstack-timeline
19:47:00 <rockyg> Thanks
19:49:52 <hogepodge> That's about it for me.
19:51:38 <davidlenwell> okay .. rockyg lets try to see if you can nail down a commitment for a room for january
19:51:45 <davidlenwell> we'll check in on that next week
19:52:03 <rockyg> Will do.I'll work on it today.
19:52:32 <davidlenwell> excelent
19:55:00 <davidlenwell> `see you guys next time.. sslypushenko__ lets talk api in channel
19:55:17 <rockyg> Bye!
19:55:22 <davidlenwell> #endmeeting