19:01:29 <notmyname> #startmeeting swift
19:01:29 <openstack> Meeting started Wed May  7 19:01:29 2014 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:32 <openstack> The meeting name has been set to 'swift'
19:01:44 <notmyname> hello everyone. who's here for the swift meeting?
19:01:54 <cschwede> \o/
19:01:57 <donagh> hi
19:02:00 <otoolee> otoolee
19:02:22 <portante> o/
19:02:28 <tdasilva> hello
19:02:39 <peluse_> howdy
19:02:45 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
19:02:54 <Kota> ya
19:03:01 <notmyname> I wanted to talk about summit prep today
19:03:12 <notmyname> to make sure everyone is ready and has what they need
19:03:30 <portante> okay
19:03:41 <notmyname> #topic summit prep: conference
19:04:02 <notmyname> there are quite a few swift-related talks for the conference
19:04:17 <creiht> howdy
19:04:18 <notmyname> as a reminder, this is the "get up in front and give a presentation lecture" sort of thing
19:05:08 <notmyname> cschwede: chmouel: peluse_: mjseger: you guys and myself are giving talks. do you have any questions or need anything? how's your prep going?
19:05:26 <peluse_> ready and willing :)
19:05:41 <cschwede> nearly ready, excited :)
19:05:50 <notmyname> peluse_: I've got to get back with you for a couple of slide, but should be minor
19:05:56 <mjseger> Eamonn and I are doing a joint presentation at the main summit and have our slides ready to go....
19:06:06 <notmyname> great to hear
19:06:28 <peluse_> notmyname:  sounds good
19:06:52 <notmyname> anyone need any basic swift stuff? or bird images? :-)
19:07:20 <cschwede> heh, bird images are always welcome :)
19:07:21 <peluse_> yeah, would be cool if everyone used the same presentation theme (Swift)
19:07:32 <notmyname> peluse_: I'm going to break that rule :-)
19:07:45 <notmyname> I've got 4 presentations, each with a different presentation theme and tool
19:08:03 <peluse_> notmyname:  well, variety is the spice of life I guess
19:08:12 <notmyname> or something...
19:09:35 <notmyname> if anything comes up, please email me (me@not.mn). If you need to get in touch with me at the summit, my cell is 254-722-3321
19:09:59 <notmyname> #topic summit prep: project pod
19:10:10 <notmyname> we've got a table all week for us to use
19:10:26 <notmyname> I'm bringing a projector, in hopes we can shine it on the wall as needed
19:10:44 <notmyname> we'll be in the corner of the room and have plenty of space, I think
19:11:05 <notmyname> and I hope that we can use that time for stuff that wasn't able to be scheduled during the summit sessions
19:11:16 * lpabon here (a little late)
19:11:18 <notmyname> it will be a great place for ad-hoc swift conversations
19:11:43 <notmyname> lpabon: do you need anything for conference talk prep? (except my slides)
19:12:00 <lpabon> food? :-) .. no I don't think so
19:12:04 <notmyname> :-)
19:12:10 <notmyname> any questions about the swift project pod?
19:12:13 <cschwede> that sounds cool (pod). is there a schedule or anything else? so we know when to be there?
19:12:33 <notmyname> I think we should have some sort of paper/flipchart/whiteboard/link in IRC about a schedule
19:12:36 <notmyname> cschwede: +1
19:13:08 <clayg> notmyname: will there be punch and pie?
19:13:18 * clayg was lead to believe there would be punch and pie.
19:13:20 <notmyname> clayg: you signed up to bring that, right?
19:13:36 <notmyname> #action clayg to bring punch and pie
19:13:51 * notmyname doesn't know meetbot commands
19:14:03 <creiht> heh
19:14:21 <donagh> I had a prposed session -- that;s now in the cinder track
19:14:24 <notmyname> who can make sure there is a schedule sheet on the project pod sheet?
19:14:32 <notmyname> donagh: ya, that's next :-)
19:15:01 <donagh> its at 4:50 friday ... so some of you may have flown home
19:15:20 <portante> donagh: I'll still be there, with bells on
19:15:25 <portante> ;)
19:15:40 <donagh> ok. We HP guys thought we might be by ourselves
19:15:44 <notmyname> better yet, if you get to the swift table project pod thingy and there isn't a schedule sheet on the table, please take it upon yourself to make one
19:15:56 <portante> notmyname: k
19:15:59 <cschwede> donagh: will be there too
19:16:09 <cschwede> notmyname: l
19:16:12 <cschwede> eh, k
19:16:20 <donagh> I'm lokiing for a keystone person(s)
19:16:23 <notmyname> #topic summit prep: summit sessions
19:16:33 <notmyname> donagh: has a talk in the cinder track
19:17:12 <notmyname> I'm looking forward to it because of the integration with glance and cinder
19:17:18 <notmyname> #link http://junodesignsummit.sched.org/event/f9073c8f8e10731c299fab98eb67ba59#.U2pP3vldUjw
19:17:33 <notmyname> swift sessions:
19:17:35 <notmyname> #link http://junodesignsummit.sched.org/type/swift
19:17:55 <notmyname> all of the swift specific stuff is split over thursday pm and friday am
19:18:27 <notmyname> (so don't go home thursday night)
19:18:55 <notmyname> for the swift sessions, remember that this part of the conference is for facilitated discussions, not lecture presentations
19:19:34 <notmyname> I think there will be a projector there, but please don't give a 40 minute talk about your topic. better to have some high-level discussion things and let the conversation starty
19:20:11 <notmyname> those who are leading these sessions (ie those who submitted them), do you have any questions or need anything? how's your prep?
19:20:28 <peluse_> peluse:  good to go
19:20:36 <clayg> creiht: is gunna be busy!
19:20:39 * peluse_ is talking to himself again
19:20:39 <creiht> lol
19:20:40 <portante> notmyname: still workin a bit
19:20:44 <creiht> x2
19:20:50 <Kota> Kota: I'm in prep but nealy ready
19:20:52 <notmyname> note that your original submission may now be combined with another
19:21:31 <notmyname> I'm really looking forward to the sessions :-)
19:21:36 <notmyname> I think this is going to be a great summit
19:21:58 <creiht> notmyname: you say that about every summit :)
19:22:06 <Kota> I have a question in my session
19:22:14 <notmyname> creiht: and most summits are very good!
19:22:19 <notmyname> Kota: what's up?
19:22:23 <creiht> :)
19:22:49 <Kota> I proposed efficient replication but I found another performance issue for ssync replication.
19:23:29 <portante> bring it on!
19:23:35 <Kota> Ofcause I present proposed efficient replication but I'm not sure that issue I found.
19:24:00 <Kota> portante: Ok, I'll try to include the information.
19:24:07 <portante> sounds like it will be a good summit session, then
19:24:20 <notmyname> +1
19:24:22 <portante> I think you'll be able to get the discussion going
19:25:04 <notmyname> other summit tracks I'd love to have swift participation in are the cross project workshops and the ops workshop
19:25:09 <notmyname> #link http://junodesignsummit.sched.org/overview/type/cross-project+workshops
19:25:16 <notmyname> #link http://junodesignsummit.sched.org/overview/type/ops+meetup
19:25:45 <notmyname> both of those have topics that are relevant to us (cross project) and relevant to our users (ops meetup)
19:26:33 <notmyname> we have a reputation in the ops world as being the easiest openstack project to administer, so let's continue to listen to the feedback and ensure that we can make things better and help others where we can
19:27:11 <notmyname> any other questions on the summit sessions?
19:28:13 <notmyname> ok, let's move on to non-summit stuff
19:28:24 <notmyname> #topic functional tests
19:28:37 <notmyname> portante: you've been working on getting the in-process func tests running in the gate
19:28:41 <notmyname> what's the status?
19:28:42 <portante> yes
19:28:59 <portante> and it appears to be working, though waiting for the merge of master onto feature/ec for it to work there
19:29:10 <portante> once that happens, we can make it "voting"
19:29:15 <portante> right now, it is non-voting
19:29:16 <notmyname> ok
19:29:29 <notmyname> portante: what about the coverage report?
19:29:41 <portante> so the coverage report is going to be interesting
19:29:55 <portante> first, there is lots of code that are not covered by a strict run
19:30:02 <notmyname> "strict"?
19:30:14 <portante> meaning, just run the functional tests once and done
19:30:22 <portante> no unit tests (can't cheat)
19:31:01 <portante> the daemons are not covered
19:31:09 <portante> nor is the cli sub-tree
19:31:38 <notmyname> ok
19:31:49 <portante> there are two swift.common modules which are not inoked at all, and a bunch of middleware
19:31:59 <notmyname> the middleware doesn't surprise me
19:32:12 <notmyname> portante: where are we at now for percentage covered in functests?
19:32:12 <portante> the tact taking for the in-process functional tests was to follow the sample middleware from the conf file
19:32:32 <portante> I have not boiled it down to one number, yet
19:32:43 <portante> thought the raw number now is 54%
19:32:47 <notmyname> ok
19:33:15 <portante> gimme a sec, I'll post a link for folks ...
19:33:42 <notmyname> portante: do you expect to add the cli and daemon testing to the functional tests or improve probe tests to give similar reporting?
19:34:21 <notmyname> chmouel: cschwede (?) next question for you is about the swiftclient tests in devstack
19:34:24 <portante> I am not sure it is possible to get functional tests to cover cli
19:34:28 <notmyname> ok
19:34:44 <cschwede> portante: why not?
19:34:53 <portante> arguably, we'd apply this same tact to probetests, and the daemons would get covered
19:35:22 <portante> func tests are all about the REST API calls, the cli commands are more backend type stuff
19:35:49 <portante> swiftclient, etc. are the analogous front end cli, and that is, well, out of tree
19:35:56 * notmyname is "working" on getting the probetests to run against a non saio
19:36:11 <portante> cool, that would be a cool think to knock out over summit
19:36:11 <notmyname> well, perhaps "interested in" is a better way to say that :-/
19:36:16 <portante> or perhaps the hackathon
19:36:18 <notmyname> ya
19:37:10 <notmyname> tdasilva: portante: does the just-proposed patch to refactor functests affect the in-process at all? let me rephrase: are you two talking to one another?
19:37:25 <tdasilva> yes
19:37:33 <notmyname> ok :-)
19:37:34 <tdasilva> yes talking
19:37:36 <cschwede> portante: hmm, i need to think about that. i thought we could run functional tests for swiftclient on the gate s well
19:37:48 <portante> cschwede: what do you mean?
19:37:49 <tdasilva> no, it doesn affect the in-process
19:37:50 <notmyname> cschwede: well, that's what I was going to ask you about
19:38:19 <portante> are you saying, you want to use the in-process swift servers to run the swiftclient against?
19:38:24 <portante> that is doable
19:38:27 <cschwede> portante: no, one second
19:38:30 <portante> k
19:38:33 <portante> one
19:38:38 <cschwede> portante: there are now functional tests for swiftclient too
19:38:43 <portante> okay
19:38:45 <cschwede> merged… yesterda
19:38:46 <cschwede> y
19:38:54 <portante> okay
19:39:02 <cschwede> so the idea (from chmouel) was to run these on the gate too
19:39:42 <portante> okay, that is doable
19:40:02 <cschwede> so we need a saio for this, and then run swiftclient functional tests against it
19:40:08 <notmyname> cschwede: these functests test an arbitrary swift endpoint?
19:41:01 <cschwede> notmyname: yes, by using this: https://github.com/openstack/python-swiftclient/blob/master/tests/sample.conf
19:41:17 <notmyname> cschwede: ok, cool
19:41:20 <cschwede> i tried to do it the same way as for swift itself
19:41:22 <notmyname> cschwede: so SAIO or devstack
19:41:28 <notmyname> makes sense
19:41:33 <cschwede> yes, devstack is fine too i think
19:41:44 <notmyname> cschwede: which is where chmouel's comments about getting it in devstack comes from
19:41:53 <notmyname> cschwede: otherwise, it's hard to get in the gate
19:42:19 <lpabon> portante: on cli testing... our QA added funtional tests to cover cli in gluster-swift/swiftonfile
19:42:56 <cschwede> notmyname: ok, I will have a look at this and try to propose a solution
19:42:58 <portante> lpabon: okay, we can talk offline
19:43:29 <notmyname> cschwede: in general, if we have tests that provide value, we should do what's reasonable to get them included in the gate
19:43:40 <cschwede> notmyname: yes, fully agree!
19:43:42 <portante> in-process functional tests are all about running paco in the same process as the nose test runner to allow for coverage
19:44:16 <notmyname> and I was talking with mordred the other day about getting a better config for swift in devstack. better testing would help here, I think
19:44:18 <notmyname> cschwede: ^
19:44:38 <portante> adding functional tests for cli commands would be great to have, but I don't think will work with the in-process servers
19:45:06 <notmyname> cschwede: that is to say, if you (and chmouel?) are looking at getting the swiftclient tests in the gate, maybe that will also involve improving the swift devstack config
19:45:46 <notmyname> anything else to cover about testing here in the meeting?
19:45:54 <clayg> notmyname: the devstack config is probably fine for functional swiftclient tests
19:45:55 <portante> more of it
19:46:06 <notmyname> clayg: ah, cool
19:46:13 <notmyname> clayg: which makes sense, actually
19:46:36 <cschwede> clayg: yes, swiftclient functional should mainly require a basic swift installation, nothing special
19:47:53 <notmyname> #topic open discussion
19:48:01 <notmyname> anything else to cover here this week
19:48:18 <notmyname> also, as a logistics note, I propose we skip next week's meeting because of the summit
19:48:20 <portante> is there room at the summit for impromptu scheduled disscussions?
19:48:30 <cschwede> anyone attending the sunday afternoon hackathon?
19:48:34 <notmyname> portante: that would be the project pod, I think
19:48:39 <portante> k
19:48:44 <notmyname> cschwede: I'm going to stick my head in probably
19:48:45 <peluse_> the mother's day hackathon?
19:48:47 <zaitcev> how can "scheduled" be "impromptu"
19:48:49 <creiht> heh
19:49:10 <notmyname> sunday pm storage hackathon
19:49:11 <notmyname> #link
19:49:13 <notmyname> #link  http://osstorage-hack.eventbrite.com
19:49:26 <notmyname> wednesday pm swiftstack party
19:49:27 <notmyname> #link https://www.eventbrite.com/e/come-one-come-all-for-a-carnival-yall-tickets-11325708499
19:50:39 <notmyname> any other questions?
19:51:11 <zaitcev> storage thing looks interestin... I should review the enovance's patch before that
19:51:44 <portante> zaitcev: what patch are you referring to?
19:51:49 <cschwede> zaitcev: you mean for ceph?
19:51:52 <zaitcev> Swift-on-RADOS
19:52:07 <cschwede> i will try to move that to stackforge tomorrow
19:52:19 <tdasilva> link?
19:52:34 <cschwede> https://review.openstack.org/#/c/60215/
19:52:38 <peluse_> zaitcev:  yeah, we hjave some interest in that patch as well and will be looking more cloesly soon too
19:53:15 <cschwede> there will be a talk as well, and a part of it is related to that patch: http://openstacksummitmay2014atlanta.sched.org/event/33c0842a1270efb6df1960f19d996e40
19:54:32 <notmyname> that's during the swift summit sessions
19:54:43 <cschwede> yes :-/
19:55:34 <notmyname> thanks everyone for being here today. see you next week!
19:55:40 <notmyname> #endmeeting