17:00:15 <gema> #startmeeting tailgate
17:00:17 <openstack> Meeting started Thu Sep 10 17:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is gema. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:19 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:22 <openstack> The meeting name has been set to 'tailgate'
17:00:44 <gema> #link http://eavesdrop.openstack.org/meetings/tailgate/2015/tailgate.2015-09-03-17.00.html
17:00:58 <gema> #topic rollcall
17:01:10 <gema> hey, anyone around for the meeting today?
17:01:45 <jasonsb> hi gema
17:01:51 <gema> hi jasonsb
17:02:09 <gema> jose-idar: around?
17:02:19 <gema> let's give people some time to show up
17:02:51 <jasonsb> i think spyderdyne said he couldn't make today due to conflict
17:03:01 <gema> jasonsb: yep, I read that
17:04:47 <gema> alright, just you and me this time around it seems
17:04:54 <gema> #topic Last week's actions
17:05:15 <gema> jasonsb: you didn't get to the questionaire review, right?
17:05:34 <jasonsb> i can send you my draft this afternoon
17:05:40 <gema> sounds good
17:05:48 <gema> will keep  it on the log then
17:05:59 <gema> and we'll have something else to discuss next week
17:06:00 <jasonsb> then we can send to ml
17:06:09 <gema> coolio
17:06:13 <gema> #ACTION jasonb to initiate the review of the questionaire on the ML
17:06:31 <gema> the other action I have for you on the log is
17:06:39 <gema> jasonb to figure out the mechanics of getting endpoints and gurumeditationreport and maybe create a simple script that does this
17:06:51 <jasonsb> didn't get to it yet
17:07:00 <gema> alright, will carry it forward then
17:07:08 <gema> #ACTION jasonb to figure out the mechanics of getting endpoints and gurumeditationreport and maybe create a simple script that does this
17:07:09 <jasonsb> probably after sending out questionaire
17:07:11 <jasonsb> (its easy)
17:07:16 <gema> ok
17:07:22 <gema> malini: you around?
17:07:51 <gema> ok, let's go for mine next
17:08:01 <gema> they are all going to be carried over till after my holidays
17:08:18 <gema> or well, I can start the conversation about the new time slot before leaving
17:08:22 <gema> and you guys discuss it
17:08:31 <gema> #ACTION gema to continue with the strategy doc
17:08:31 <gema> #ACTION gema to write a blog post about refstack-client running
17:08:32 <gema> #ACTION gema to send out the defcore details on actionable gaps
17:08:47 <gema> #ACTION gema to initiate conversation on the mailing about a new time slot
17:08:55 <jasonsb> i'm starting to see your interest in defcore
17:09:07 <gema> jasonsb: they need tests and we should be writing them
17:09:09 <gema> :)
17:09:19 <jasonsb> its also not a thing so much as a process
17:09:19 <gema> they know where the gaps are, that's done for us
17:09:35 <jasonsb> a process where compatbility (forwards, backwards) becomes a concern
17:09:41 <gema> yep
17:09:50 <gema> let me finish with the actions
17:09:53 <jasonsb> or else you end up in the same pickle as keystone etc
17:09:56 <gema> and then we can discuss defcore
17:09:57 <jasonsb> sorry
17:10:06 <gema> #ACTION malini to try to write a test with tempest-lib that spins a VM and destroys is, as a POC
17:10:09 <gema> #ACTION jose-idar to start a spec for component tests for nova (user side, no admin), so we can all contribute cases and maybe implement them at some point , but at least start to get organised
17:10:13 <gema> ok
17:10:20 <gema> #topic defcore
17:10:44 <gema> you were talking about compatibility and some insight on what htey are doing
17:11:17 <jasonsb> please correct me
17:11:27 <malini> sorry - network worries
17:11:32 <jasonsb> but if you identify capabilities, then you need to determine which you can rely on
17:11:43 <jasonsb> which leads you directly to compatibility
17:11:53 <gema> well, capabilities are api calls
17:11:58 <gema> that give you some functionality
17:12:04 <gema> that are exposed to the user
17:12:13 <gema> so yes, yoou should be able to rely on them
17:12:23 <gema> and they should be consistent across clouds
17:12:35 <gema> for people to be able to develop stable apps on top of them
17:12:41 <jasonsb> so maybe defcore is about socializing that idea
17:13:00 <gema> defcore is about establishing that idea
17:13:09 <jasonsb> which is great
17:13:16 <gema> not sure about socializing although there will be part of it too I am sure
17:13:49 <gema> however as a project, I don't think openstack is there yet
17:14:03 <gema> this defcore conversations are just the beginning
17:14:04 <jasonsb> little bit early days for this
17:14:12 <gema> so it is a great time for us to start contributing
17:14:16 <gema> and get emmeshed in t he project
17:14:17 <gema> I think
17:14:24 <jasonsb> for example, keystone v3 is heir apparent
17:14:31 <gema> heir?
17:14:31 <jasonsb> but horizon does not support domain scoped tokens
17:15:07 <jasonsb> "a person who is most likely to succeed to the place of another."
17:15:20 <gema> ahh, ok
17:15:22 <jasonsb> sorry for oblique reference
17:15:27 <gema> it's alright xD
17:15:51 <jasonsb> so can you really write defcore around v3 yet?
17:15:55 <gema> yeah, but that is what I was trying to understand yesterday, because new apis should carry over the old ones functionality
17:16:05 <gema> sure you can, if v3 api is there now
17:16:12 <gema> and the test will mature with the api
17:16:23 <gema> and hopefully stay there for a long time
17:16:28 <gema> life long and prosper, as they say
17:17:27 <jasonsb> i think you said before that tailgate should view defcore tests as someting very central
17:17:47 <gema> I think it is a good starting point
17:17:48 <jasonsb> to tailgate interests.  i see that
17:17:58 <jasonsb> the testing concerns overlap alot
17:17:59 <gema> I think there will be more to us
17:18:04 <gema> like non-functional testing
17:18:13 <gema> but for functional I think their umbrella is ideal
17:19:01 <gema> jasonsb: so you have their meeting pinned in your calendar for next week then?
17:19:11 <jasonsb> i do not but i will :)
17:19:17 <gema> you should subscribe to their mailing which is where they send deviations like yesterday's
17:19:20 <gema> with invites
17:19:30 <jasonsb> will do
17:19:32 <gema> their meetings normally happen in meetingroom-4 on irc
17:19:52 <gema> ok, did anything else happen after I left yesterday that you want to share?
17:20:10 <jasonsb> nothing notable i think
17:20:23 <gema> ok
17:20:30 <gema> I made a note about a neutron test that is missing
17:20:54 <gema> #idea Add a new test for neutron that attaches a floating ip to a VM (see if it can be done without admin)
17:21:16 <jasonsb> #link https://docs.google.com/spreadsheets/d/15Fkt2n95WPPe7CYH-0WIKz3dhMeW3FW2gl5aSlamEeY/edit#gid=561264013
17:21:40 <gema> jasonsb: what is this document?
17:21:56 <jasonsb> defcore capabilities scoring
17:22:12 <gema> coolio
17:22:19 <gema> I am going to add it to the test strategy
17:22:27 <gema> will work on that side of things when I come back from holidays
17:22:33 <jasonsb> i think you gave it in irc yesterday?
17:22:43 <jasonsb> when is holidays for you?
17:22:44 <gema> no,, I don't think I had seen it
17:22:50 <gema> starts tomorrow until end of next week :D
17:22:56 <jasonsb> oh ok
17:24:14 <gema> I hope I come back fresh and centered
17:24:22 <jasonsb> me too :)
17:24:24 <gema> the works at my house were very distracting
17:25:23 <gema> anyway, anything else on defcore?
17:25:31 <jasonsb> i hope to be fresh enough to get a blog post done
17:25:38 <gema> :D
17:25:46 <jasonsb> like spyderydyne
17:25:50 <gema> yep, me too
17:25:59 <gema> #topic AOB
17:26:01 <jasonsb> can' think of anything on defcore
17:26:02 <gema> ok
17:26:11 <malini> what is AOB?
17:26:18 <gema> any other business
17:26:23 <malini> :D
17:26:24 <gema> malini: lol, you ask me every time
17:26:27 <gema> that's so cute x)
17:26:33 <malini> short term memory
17:26:37 <gema> haha, me too :D
17:26:43 <malini> any ideas for the summit?
17:26:58 <malini> At the minimum I wud like us to meet early on :D
17:27:01 <gema> we should start building a list of topics for you guys to work on
17:27:36 <malini> tht wud be neat
17:27:58 <jasonsb> gema did you have a topic for preparing the tokyo talk?
17:27:59 <gema> who wants so start that?
17:28:14 <gema> jasonsb: not really, I never added it
17:28:28 <gema> jasonsb: it all starts with the questionaire
17:28:33 <jasonsb> ah
17:28:34 <gema> and from that we can work on the talk
17:28:38 <jasonsb> ok!
17:28:44 <gema> jasonsb: so you are the bottleneck
17:28:46 <gema> how about that x D
17:29:01 <jasonsb> i knew there was a reason i didnt' ask before
17:29:20 <gema> j/k, we should whenever we get answers from the questionaire have at least a skeleton of the talk  in place
17:29:27 <gema> just in case the talk does finally happen
17:29:37 <gema> so that we are not rushed in that case
17:29:44 <jasonsb> true
17:29:57 <gema> do any of you have time to start thinking about that this week?
17:30:09 <gema> maybe put an empty slidedeck together with just an index
17:30:20 <malini> I can help some too
17:30:37 <gema> malini: do you want to think about the presentation, then?
17:30:50 <malini> yes
17:31:07 <malini> I will start a skeleton, so we can start poking around to add info
17:31:10 <gema> #action malini to start thinking about the presentation and a structure that would make sense in case it happens
17:31:19 <gema> malini: sounds good
17:31:30 <gema> malini: make sure jasonsb finishes the questionaire, lol
17:31:45 <malini> hopefully this will also help us gather our thoughts
17:31:50 <gema> yep
17:31:55 <gema> soul searching, like you said
17:32:10 <malini> tht soul is hard to find :/
17:32:15 <gema> I know
17:32:36 <gema> starting is always the most difficult part
17:32:46 <gema> I think we set up a too broad of a goal at the beginning
17:32:52 <gema> which is why we are still trying to find a way to start
17:33:24 <gema> and maybe why most of the people that started with us dropped from these calls
17:33:32 <gema> that or maybe they just lost interest
17:33:44 <gema> but there are still three players here
17:33:51 <gema> four, actually
17:34:00 <malini> unless we have something solid, its hard to justify spending time on this -rt?
17:34:02 <gema> rackspace, cisco, hitachi and canonical
17:34:21 <gema> malini: and unless we spend time on it and get organised there'll be nothing solid
17:34:26 <gema> it's a catch 22
17:34:43 <gema> but I agree with you
17:34:47 <gema> it has been difficult for me too
17:34:48 <malini> once we find tht soul, we'll gain momentum
17:34:55 <gema> agreed
17:35:23 <malini> we'll get there :)
17:35:28 <gema> sure thing
17:35:49 <gema> you guys take care of that this week and that'll give me some push when I come back to continue the defcore work
17:36:04 <malini> ok :)
17:36:09 <gema> I will need a volunteer to chair next week's meeting
17:36:09 <malini> enjoy ur time off
17:36:17 <gema> malini: thanks :D
17:36:27 <malini> I always screw up the tags
17:36:33 <gema> malini: who cares
17:36:37 <jasonsb> yes indeed enjoy your holidays
17:36:45 <malini> I can in tht case :)
17:36:50 <gema> :D
17:36:55 <malini> what is the name of our meeting again?
17:37:00 <malini> :d
17:37:10 <gema> haha you need to type: #startmeeting tailgate
17:37:15 <gema> without the ':'
17:37:21 <malini> ok :D
17:37:33 <gema> #action malini to chair next week's meeting
17:37:56 <gema> do we have anything else to discuss?
17:39:09 <gema> ok , ending meeting in
17:39:11 <gema> 3
17:39:12 <gema> 2
17:39:17 <gema> #endmeeting