19:01:25 <notmyname> #startmeeting swift
19:01:26 <openstack> Meeting started Wed Aug  7 19:01:25 2013 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:29 <openstack> The meeting name has been set to 'swift'
19:01:32 <notmyname> who's here for the swift team meeting?
19:01:38 <swifterdarrell> o/
19:01:39 <zaitcev> o7
19:01:45 <cschwede> o/
19:01:57 <peluse> o/
19:02:02 <portante> o/
19:02:09 * torgomatic is just here for the snacks
19:02:27 <notmyname> thanks everyone for joining. let's get started
19:02:28 * clayg was lead to believe there would be punch and pie?
19:02:36 <notmyname> topics: https://wiki.openstack.org/wiki/Meetings/Swift
19:02:44 <notmyname> #topic 1.9.1 release
19:02:56 <notmyname> so first up, notice that 1.9.1 RC was cut today
19:03:07 * portante yum, never thought irc meetings could be so tempting ...
19:03:08 <notmyname> this is primarily in response to the bug reported and patched by portante
19:03:27 <portante> thanks to zaitcev for asking the original question in a review
19:03:38 <notmyname> patches have been backported to folsom and grizzly
19:03:50 <notmyname> and merged into master
19:04:14 <peluse> there go my plans to take down the new Intel Swift cluster with delete commands
19:04:21 <portante> redbo also has a patch out based on this to remove unlinkold() calls
19:04:23 <notmyname> :-)
19:04:45 <notmyname> assuming nothing major is reported by people this week, the current RC will be the final 1.9.1 release
19:04:59 <notmyname> ttx will help formalize that on monday or tuesday, depending on your timezone
19:05:20 <notmyname> any questions about 1.9.1 or today's release?
19:05:54 <notmyname> ok, moving on to the schedule for the next one
19:06:00 <notmyname> #topic havana release schedule
19:06:15 <notmyname> the openstack-wide schedule for havana is at https://wiki.openstack.org/wiki/Havana_Release_Schedule
19:06:46 <notmyname> from that, you can see that oct 17 is the date for havana, and the RC for havana is sept 26 (ish)
19:07:18 <notmyname> which means that it's likely for us (ie swift) to have just one more release before then, and that release will be included in the openstack havana release
19:08:06 <zaitcev> Is this a good time to ask if LFS is makingit
19:08:11 * portante hopes to get diskfile refactoring and database db work from zaitcev in for that release
19:08:29 <portante> clayg has reviewed the latest diskfile proposal
19:08:29 <notmyname> so therefore the 1.9.2 milestone has been created and we'll shoot for the RC at sept 26 ish
19:08:42 <portante> great
19:08:43 <clayg> portante: what's next?!
19:08:43 <notmyname> zaitcev: portante: ya, I'd love to see it included
19:08:54 <notmyname> clayg just asked the right questions
19:08:57 <chmouel> would that be 2.0 if we get lfs?
19:08:58 <notmyname> zaitcev: what do you need next
19:09:22 * clayg guesses he needs to review some of zaitcev's patches too...
19:09:26 <notmyname> chmouel: probably not (my default answer is no)
19:09:33 <chmouel> :)
19:09:53 * chmouel guesses that question come up every release
19:09:58 <notmyname> it's likely that the next release will be 1.10.0 rather than 1.9.2 (either way, just a number)
19:10:15 <notmyname> current_version = uuid.uuid4().hex
19:10:18 <redbo> 1.A.0
19:10:26 <notmyname> redbo: :-)
19:10:33 <portante> yes!
19:10:41 <zaitcev> Peter asked me to take https://raw.github.com/zaitcev/swift-lfs/master/doc/source/lfs_plugin.rst and stuff it into... docstrings. Mostly. Some of it does not match docstrings entirely, so I'm going to keep that file, just make it very small. Include examples of configuration that GlusterFS/Ceph/HPSS can copy-paste.
19:11:23 <zaitcev> The "LFS planned changes" section is supposed to list all work items and reviews, which it mostly does.
19:12:11 <zaitcev> David was not happy about my renaming of broker.db_file, then I thought I'd help his ACL thing in exchange, then he suddenly disappeared.
19:12:12 <cschwede> @zaitcev: HPSS? Is someone working on this, are there any docs I didn't read yet?
19:12:52 <zaitcev> cschwede: A guy from IBM Federal poked me about doing it. Apparently its xattr is limited and Swift does not work right on top of it.
19:13:11 <yuan> zaitcev, will there be an example config for zfs?
19:13:13 <zaitcev> cschwede: So it would be Swift's essentially unchanged back-end but with some workarounds
19:13:20 <portante> clayg: I believe that for DiskFile, we need to grind out the changes to use the new open method and then from that work do the official API definition
19:13:44 <portante> with that, we'll apply a similar discipline to the database broker based on pete's work already
19:14:31 <clayg> portante: ok, feel free to ping me anytime you have a review up that I haven't looked at yet, or if you get a couple of changes going and you could use some help with one
19:14:31 <notmyname> zaitcev: portante: are you concerned with the ability to get changes proposed in time for inclusion in havana?
19:14:31 <cschwede> @zaitcev: thanks for the info. Nice to know as I know some other people interested in this
19:15:15 <portante> I think we can get DiskFile in on time, but we'll have work hard on the database db side
19:15:34 <notmyname> ok
19:15:42 <notmyname> let me know how I can help
19:16:05 <notmyname> anything else to discuss for the havana release?
19:16:15 <portante> and I think we need to realize that this won't be a completely polished interface, as we make changes, the ripple effects take time as folks start to see how these changes can be leveraged for other work
19:16:50 <notmyname> in general, the review queue has been getting really long. we all need to get better at staying on top of reviews
19:17:08 <notmyname> #topic swift hackathon
19:17:12 * portante has been off on perf testing for the last hour days, sorry
19:17:25 <notmyname> so we're going to do this :-)
19:17:32 <portante> yes
19:17:38 <cschwede> nice :)
19:17:39 <portante> hackathon is a good idea
19:17:43 <notmyname> the summit is in hong kong (and has a tendency to have lots of powerpoint
19:18:06 <notmyname> so for those who want to do code stuff with no powerpoint allowed, let's do a hackathon! :-)
19:18:17 <peluse> sounds good!
19:18:43 <notmyname> I'll make the invite public shortly (ie this afternoon or tomorrow), but here's the summary
19:18:50 <notmyname> Tuesday, October 15, 2013 at 9:00 AM - Thursday, October 17, 2013 at 7:00 PM in Austin Texas
19:18:57 <portante> venue?
19:19:07 <notmyname> we'll reserve a block of hotel rooms
19:19:14 <notmyname> the venue will be on the UT campus
19:19:21 <zaitcev> I replied, but feel free to bump me if you need "more core core" peope accomodated.
19:19:23 <notmyname> jsut north of downtown austin
19:19:23 <creiht> ahh nice
19:19:28 <creiht> notmyname: where at on campus?
19:20:27 <notmyname> creiht: in the UT commons center
19:20:39 <notmyname> sorry, had to find it in my email
19:20:44 <creiht> hehe cool
19:21:02 <creiht> http://www.utexas.edu/commons/
19:21:05 <creiht> that commons?
19:21:10 <notmyname> ya
19:21:23 <creiht> then that is at the JJ. Pickle Research center
19:21:25 <notmyname> http://www.utexas.edu/commons/rooms/commons/bevoroom.php
19:21:26 <creiht> not the UT campus
19:21:46 <creiht> but still a cool place
19:21:59 <notmyname> ah ok :-)
19:22:24 <dfg> isn't that place in way north austin?
19:22:33 <notmyname> dfg: http://www.utexas.edu/commons/maps/
19:22:54 <creiht> Nah, just North Austing
19:23:04 <creiht> I used to work across the street when IBM was there
19:23:14 <dfg> i still think of austin in terms of having to take the bus there...
19:23:19 <creiht> haha
19:23:33 <creiht> parking there will also be better than the normal campus :)
19:23:41 <zaitcev> "Drive via US-84 E ยท 698 mi	11 h 12 min" .. hmm. I think I'll have to fly in.
19:23:46 <notmyname> heh
19:23:57 <notmyname> I'll get the rest of the logistics info out ASAP
19:24:04 <creiht> lol
19:24:06 <notmyname> I'm looking forward to it
19:24:17 <notmyname> any other questions on that topic?
19:24:31 <cschwede> it should be no problem to join remote?
19:24:43 <notmyname> cschwede: not sure. we havent' discussed that yet
19:24:49 <cschwede> ok
19:24:49 <portante> do you know what hotel you are going to get a block of rooms at yet?
19:25:08 <notmyname> portante: not yet. that's next on the list fo things to do for it
19:25:11 <notmyname> any preferences?
19:25:36 <zaitcev> I was going to stay in the cheapest motel. At Havana summit FBI broke into the next room and arrested a dude at 4 a.m.
19:25:45 <portante> marriot
19:25:45 <creiht> lol
19:25:50 <peluse> marriott
19:25:52 <portante> red hat gets a discount there
19:26:03 <creiht> I'll probably just crash with family
19:26:05 <peluse> I store my points there :)
19:26:13 <Dieterbe> zaitcev: whoa
19:26:39 <notmyname> I'll look into the marriott
19:26:56 <notmyname> #topic erasure codes progress
19:27:04 <notmyname> torgomatic: peluse: can you give an update here?
19:27:07 <peluse> so I've got general multi-ring support up for review on the EC branch.  Covers proxy server only and test coded updated to support the plumbing but havne't added specitic unit tests yet.  Looking for feedback then will post similar changes to the replciator.
19:27:19 <notmyname> #link https://trello.com/b/LlvIFIQs/swift-erasure-codes
19:27:20 <peluse> lots more info on teh review page
19:27:29 <torgomatic> I provided a little feedback; I'll look more after this meeting
19:27:53 <peluse> cool, thanks
19:28:13 <peluse> I know Yuan has done a lot too, Yuan are you on?  Its 3am there so hard to say
19:28:27 <portante> notmyname: is this a community trello board, or only for swiftstack folks?
19:28:33 <notmyname> portante: public
19:28:38 <yuan> torgomatic, I made some early code here, c/39865/
19:28:54 <torgomatic> yuan: ok, I'll look at that too
19:28:58 <portante> I would not mind using this for tracking the work for DiskFile and DatabaseBroker and the rest of LFS
19:29:00 <peluse> Wrt Yuan's work - he posted a draft of the get/put path changes and the EC library framework.  When he cleans it up more he'll push it up for review on the EC branch
19:29:04 * torgomatic has been busy with internal SwiftStack work lately
19:29:13 <notmyname> portante: ok, let's talk after to get one set up
19:29:19 <portante> k thx
19:29:39 <peluse> Does Kevin know about the Swift meetings?
19:29:55 <notmyname> peluse: I'll make sure he does
19:30:36 <peluse> cool, I know he's made progress on his EC algorithms and on the algebraic signature stuff.  We at Intel are also looking to open source some low level code and will contriube that as as optional library as well.  Next month or so I think
19:30:43 <notmyname> cool
19:31:01 <notmyname> anything else need to be discussed on EC? any questions?
19:31:03 <peluse> clayg:  did you get a chance to look at the latest multi ring changes?
19:31:27 <yuan> question, we want a new eccontroller or some helper func
19:32:09 <torgomatic> whatever makes the code cleaner
19:32:12 <peluse> If you mena ECObjectController I think we settled on no new controller, just helper functions.  Or I read things that way anyway... torgomatic?
19:32:25 <portante> the LFS patch work at the controller level would help make this easier to do, would it not?
19:32:31 <clayg> peluse: not since sam's comments
19:32:48 <portante> zaitcev already has a tree with that work that folks might want to consider
19:33:00 <yuan> portante, yeah it does
19:33:01 <peluse> His comments were just today I think, patch 10 is the last update I made.  Lots of fun w/the test code :)
19:33:04 <notmyname> zaitcev: got a link for clicky goodness?
19:33:18 <clayg> peluse: I'll take another look then - thanks
19:33:40 <peluse> prtante:  can you send the link?
19:33:44 <zaitcev> The "big" LFS, which plugs Controller in proxy is here https://github.com/zaitcev/swift-lfs
19:33:55 <notmyname> thanks
19:34:01 <peluse> yeah, will check it out
19:34:13 <zaitcev> that said I'm not sure, I need to look at Paul's thing. I didn't know his "multi-ring" was baout EC
19:34:40 <peluse> So to be clear the multi-ring thing and the idea of using a separate ECObjectController are two different dsicussions
19:34:52 <zaitcev> oh
19:35:06 <peluse> The separate controller would be to not require different functions in the ObjectController for get/put/etc
19:35:17 <torgomatic> I'd kind of like to support multi-ring stuff completely before starting on EC, but that's just me
19:35:25 <peluse> multi-ring I'm trying to do as very generic to apply to Clayg's storage policies soln as well
19:35:50 <peluse> torgotmatic:  i agree which is why I jumped on it first :)
19:36:03 <torgomatic> i:)
19:36:12 <torgomatic> not sure what the i is for
19:36:20 <peluse> was wondering
19:36:23 * portante thought it was a solute
19:36:45 <notmyname> anything else on EC for now?
19:36:50 <peluse> not on my end
19:36:52 <notmyname> before moving to open discussion?
19:36:59 <torgomatic> nothing here
19:37:04 <notmyname> #topic open discussion
19:37:18 <notmyname> anything else to discuss in the meeting this week?
19:37:29 <peluse> anyone see my general question about debug prints in the unit test code?  (how to)
19:38:03 <portante> run ./.unittests --nocapture --nologcapture
19:38:08 <notmyname> peluse: is the problem that nose is grabbing the output streams and you aren't seeing it?
19:38:21 <notmyname> portante: ah, those are nice options to know
19:38:35 <peluse> problem is they're going somewhere and I don't know where :)
19:38:42 <peluse> I can try what portante suggests
19:39:13 <clayg> i think i do -vsx
19:39:21 <portante> does not work with tox, so use that with a virtualenv with the right dependencies if not on a release that supports the latest with openstack
19:39:28 <clayg> running one test at a time helps a lot too
19:39:33 <portante> yes
19:39:37 <portante> what is -vsx?
19:39:44 <clayg> portante: options for nose
19:39:46 <portante> oh, sorry
19:39:53 <peluse> and how do I run one test a time, that would be great
19:40:16 <clayg> nosetests path/to/the/test_file.py:TestCaseName.test_name
19:40:21 <clayg> -vsx
19:40:21 <clayg> :P
19:40:24 <peluse> swesome thanks
19:40:43 <notmyname> anything else?
19:41:13 <notmyname> thanks all for being here and for your work on swift
19:41:17 <notmyname> #endmeeting