Thursday, 2014-08-28

*** bkopilov has joined #openstack-swift00:10
*** dmsimard_away is now known as dmsimard00:22
*** tumf has joined #openstack-swift00:30
*** tkay has quit IRC00:32
zaitcevhttp://homepage.ntlworld.com/jonathan.deboynepollard/FGA/smtp-spf-is-harmful.html00:33
zaitcevhttp://david.woodhou.se/why-not-spf.html00:33
*** dmorita has joined #openstack-swift00:33
zaitcevhttp://www.ietf.org/mail-archive/web/ietf/current/msg87153.html00:33
openstackgerritJesse J. Cook proposed a change to openstack/python-swiftclient: Python sessions, streaming, and increased pool  https://review.openstack.org/11606500:34
*** tumf has quit IRC00:35
*** dmsimard is now known as dmsimard_away00:42
*** shri has left #openstack-swift00:43
mattoliveraunotmyname: is the email address on your github correct? I'm bcc'ing you in.00:48
*** mwstorer has quit IRC00:58
*** kevinc_ has quit IRC00:59
*** Edward-Zhang has quit IRC00:59
*** addnull has joined #openstack-swift01:00
*** Edward-Zhang has joined #openstack-swift01:14
mattoliverauSwift abandoner has gone live. The script is scripted to check every 15 minutes. Sorry if you just got spammed by donotreply@oliver.net.au01:17
pelusecool!01:25
*** tumf has joined #openstack-swift01:32
*** gyee has quit IRC01:32
*** Edward-Zhang has quit IRC01:36
*** tumf has quit IRC01:37
*** addnull has quit IRC01:45
*** nosnos has joined #openstack-swift01:49
*** openstackgerrit has quit IRC02:02
*** openstackgerrit has joined #openstack-swift02:03
*** occup4nt has quit IRC02:09
*** addnull has joined #openstack-swift02:19
*** haomaiwa_ has quit IRC02:25
*** 7YUAAI27X has joined #openstack-swift02:25
*** Edward-Zhang has joined #openstack-swift02:28
*** tumf has joined #openstack-swift02:33
*** tumf has quit IRC02:37
*** haomaiwang has joined #openstack-swift02:41
*** 7YUAAI27X has quit IRC02:43
*** nosnos has quit IRC03:26
*** nosnos has joined #openstack-swift03:27
*** nosnos has quit IRC03:32
*** sungju has quit IRC03:34
*** tumf has joined #openstack-swift03:34
*** sungju has joined #openstack-swift03:34
*** tumf has quit IRC03:38
*** Edward-Zhang has quit IRC03:50
*** mitz_ has quit IRC03:59
*** mitz has joined #openstack-swift03:59
*** addnull has quit IRC04:05
*** mahatic has quit IRC04:11
*** nosnos has joined #openstack-swift04:27
*** tumf has joined #openstack-swift04:35
*** Edward-Zhang has joined #openstack-swift04:37
*** echevemaster has joined #openstack-swift04:37
*** tumf has quit IRC04:39
*** zaitcev has quit IRC04:59
*** addnull has joined #openstack-swift05:05
*** nshaikh has joined #openstack-swift05:16
*** kopparam has joined #openstack-swift05:26
*** otoolee- is now known as otoolee05:28
*** DisneyRicky has quit IRC05:29
*** mikehn_ has quit IRC05:32
*** tumf has joined #openstack-swift05:35
*** mikehn has joined #openstack-swift05:39
*** tumf has quit IRC05:41
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925005:42
*** ppai has joined #openstack-swift05:50
*** kopparam has quit IRC05:53
*** kopparam has joined #openstack-swift05:53
*** kopparam has quit IRC05:58
*** k4n0 has joined #openstack-swift06:03
*** foexle has joined #openstack-swift06:17
*** bkopilov has quit IRC06:22
*** kopparam has joined #openstack-swift06:25
*** dmorita has quit IRC06:30
*** tumf has joined #openstack-swift06:37
*** foexle_ has joined #openstack-swift06:40
*** foexle_ has quit IRC06:40
*** mahatic has joined #openstack-swift06:43
*** jokke__ is now known as jokke_06:44
mahatichi, can someone please point me to a guide which lists out how to go about testing swift and thereafter?06:47
Edward-Zhangwhat do you want to test on Swift? the API?06:55
mahaticEdward-Zhang, yup06:55
mahaticputting objects/containers, building rings06:56
mahaticetcc06:56
Edward-Zhanghttp://docs.openstack.org/developer/swift/admin_guide.html06:58
Edward-Zhanghttp://docs.openstack.org/api/openstack-object-storage/1.0/content/06:59
Edward-Zhanghttp://docs.openstack.org/cli-reference/content/swiftclient_commands.html07:00
Edward-Zhangthese docs should cover your needs.07:01
mahaticEdward-Zhang, great, yes they should. Thank you!07:02
Edward-Zhangmahatic: welcomed!07:03
mahaticEdward-Zhang, I just roughly went through what they cover. But I also want to know how to create an account, after the set up, i see there is a test account. But how do i go about creating new one?07:03
*** tumf has quit IRC07:10
*** kopparam has quit IRC07:17
*** kopparam has joined #openstack-swift07:17
Edward-Zhangmahitic: The account  can not be created by the API. if you are using keystone as authentication,  the account will be created automatically by swift when your request has  been authenticated.07:20
*** kopparam has quit IRC07:22
*** bvandenh has joined #openstack-swift07:26
*** tkay has joined #openstack-swift07:29
*** sungju has quit IRC07:30
*** tkay has quit IRC07:32
slo_07:37
mahaticEdward-Zhang, oh okay. Thanks for the info. One more question, If i use Keystone, will i be able to create multiple accounts? (I can as well refer the doc maybe. But was just wondering)07:39
Edward-Zhangmahatic: sure. you can create any new account you want.07:42
Edward-Zhanghttp://docs.openstack.org/developer/keystone/configuringservices.html07:42
*** echevemaster has quit IRC07:46
mahaticEdward-Zhang, great. Thank you so much again! :)07:48
Edward-Zhang:-)07:48
*** kopparam has joined #openstack-swift07:55
*** tumf has joined #openstack-swift07:56
*** tumf has quit IRC07:56
*** tumf has joined #openstack-swift07:57
*** Midnightmyth has joined #openstack-swift08:14
*** mahatic has quit IRC08:19
*** tumf has quit IRC08:38
*** geaaru has joined #openstack-swift08:38
*** sungju has joined #openstack-swift08:41
*** mahatic has joined #openstack-swift08:45
*** nosnos has quit IRC08:47
*** nosnos has joined #openstack-swift08:47
*** bkopilov has joined #openstack-swift08:48
*** kopparam has quit IRC08:50
*** joeljwright has joined #openstack-swift08:50
*** kopparam has joined #openstack-swift08:51
*** nosnos has quit IRC08:52
*** kopparam has quit IRC08:56
*** sungju has quit IRC08:56
*** tumf has joined #openstack-swift09:09
*** Edward-Zhang has quit IRC09:12
*** tumf has quit IRC09:22
*** nosnos has joined #openstack-swift09:24
*** nshaikh has left #openstack-swift09:28
*** kopparam has joined #openstack-swift09:32
*** kopparam has quit IRC09:44
*** kopparam has joined #openstack-swift09:45
*** kopparam has quit IRC09:49
*** haomaiwang has quit IRC10:00
*** haomaiwang has joined #openstack-swift10:01
*** haomaiw__ has joined #openstack-swift10:07
*** haomaiwang has quit IRC10:10
*** kopparam has joined #openstack-swift10:10
openstackgerritChristian Schwede proposed a change to openstack/swift: Add option to log container metadata  https://review.openstack.org/6728210:17
*** tumf has joined #openstack-swift10:18
*** nosnos has quit IRC10:20
*** nosnos has joined #openstack-swift10:21
*** tumf has quit IRC10:22
*** nosnos has quit IRC10:25
*** Edward-Zhang has joined #openstack-swift10:28
*** nosnos has joined #openstack-swift10:34
*** mkollaro has joined #openstack-swift10:36
*** ppai has quit IRC10:38
*** HenryG has quit IRC10:43
*** ppai has joined #openstack-swift10:52
*** aix has joined #openstack-swift10:52
*** tumf has joined #openstack-swift10:56
*** Edward-Zhang has quit IRC10:57
*** tumf has quit IRC11:01
*** kopparam has quit IRC11:11
*** kopparam has joined #openstack-swift11:11
*** nosnos has quit IRC11:18
*** nosnos has joined #openstack-swift11:20
*** mkollaro1 has joined #openstack-swift11:31
*** mkollaro has quit IRC11:33
*** marcusvrn has joined #openstack-swift11:42
*** kopparam has quit IRC11:42
*** kopparam has joined #openstack-swift11:43
*** kopparam has quit IRC11:48
*** HenryG has joined #openstack-swift11:52
*** tumf has joined #openstack-swift11:57
openstackgerritYuan Zhou proposed a change to openstack/swift-specs: Initial draft for high level EC Get flow  https://review.openstack.org/11749212:00
*** tumf has quit IRC12:02
*** kopparam has joined #openstack-swift12:14
*** kopparam has quit IRC12:20
*** nosnos has quit IRC12:22
*** nosnos has joined #openstack-swift12:23
*** kopparam has joined #openstack-swift12:23
*** nosnos has quit IRC12:27
*** kopparam has quit IRC12:34
*** kopparam has joined #openstack-swift12:35
*** judd7 has quit IRC12:38
*** kopparam has quit IRC12:39
*** nmap911 has joined #openstack-swift12:43
*** ppai has quit IRC12:44
nmap911hi there. having some weirdness with a swift deployment. My proxy servers use keystone for authentication - I've made a container publically accessible for reads & listing - however when trying to access it I get 401 authentication errors. proxy server logs indicates missing authentication headers in the http request. what the?12:44
nmap911I found the problem x)12:49
nmap911forgive my foolishness12:49
nmap911incase this chat history gets archived somehwere and 10 million years from now someone needs to know, i had to add the following line to my proxy config file : delay_auth_decision = 112:50
nmap911l8a12:51
*** nmap911 has left #openstack-swift12:51
*** addnull has quit IRC12:57
*** tumf has joined #openstack-swift12:58
*** jasondotstar has joined #openstack-swift13:00
*** tumf has quit IRC13:03
*** mkollaro has joined #openstack-swift13:05
*** mkollaro1 has quit IRC13:07
*** k4n0 has quit IRC13:10
*** DisneyRicky has joined #openstack-swift13:16
*** pberis has joined #openstack-swift13:19
*** joeljwright has quit IRC13:23
*** joeljwright has joined #openstack-swift13:25
*** joeljwright has quit IRC13:28
*** Midnightmyth has quit IRC13:31
*** tdasilva has joined #openstack-swift13:34
*** Edward-Zhang has joined #openstack-swift13:47
*** joeljwright has joined #openstack-swift13:53
*** tumf has joined #openstack-swift13:59
openstackgerritA change was merged to openstack/python-swiftclient: Adds console script entry point  https://review.openstack.org/11578214:03
*** tumf has quit IRC14:04
*** annegent_ has joined #openstack-swift14:08
*** dmsimard_away is now known as dmsimard14:15
*** annegent_ has quit IRC14:23
*** annegent_ has joined #openstack-swift14:24
*** akp has quit IRC14:27
*** astellwag has quit IRC14:28
*** annegent_ has quit IRC14:34
*** astellwag has joined #openstack-swift14:35
*** akp has joined #openstack-swift14:38
*** annegent_ has joined #openstack-swift14:49
*** tumf has joined #openstack-swift15:00
*** joeljwright has quit IRC15:01
*** Edward-Zhang has quit IRC15:03
*** tumf has quit IRC15:05
*** jyoti-ranjan has joined #openstack-swift15:09
*** __lgw4__ has joined #openstack-swift15:20
*** kevinc_ has joined #openstack-swift15:22
*** HenryG has quit IRC15:28
*** annegent_ has quit IRC15:32
*** foexle has quit IRC15:35
*** annegent_ has joined #openstack-swift15:42
*** gyee has joined #openstack-swift15:47
*** annegent_ has quit IRC15:47
*** bkopilov has quit IRC15:49
*** zaitcev has joined #openstack-swift15:51
*** ChanServ sets mode: +v zaitcev15:51
jyoti-ranjanOne basic question: does Swift by default creates d1, d2 folder, if /srv/node is there15:55
jyoti-ranjanif yes, can you point me to swift code15:55
*** tumf has joined #openstack-swift16:01
*** annegent_ has joined #openstack-swift16:01
*** mwstorer has joined #openstack-swift16:04
*** tumf has quit IRC16:05
notmynamegood morning16:06
notmynamethanks mattoliverau16:06
*** Midnightmyth has joined #openstack-swift16:09
*** Slo__ has joined #openstack-swift16:09
*** annegent_ has quit IRC16:12
*** foexle has joined #openstack-swift16:14
notmynamemattoliverau: instead of having me on the bcc, can I be on the cc so there is at least some small chance that someone who has questions can have a contact point?16:17
*** mahatic has quit IRC16:19
*** annegent_ has joined #openstack-swift16:21
claygjyoti-ranjan: no it won't create the device mount points16:24
notmynamewhy did global requirements get bumped "for python swiftclient"?16:24
notmynamehttps://review.openstack.org/#/c/117216/116:24
clayglol16:25
claygso the requirement *was* for the version that ships with precise16:25
claygwe're so dysfunctional16:25
notmynameno, actually it was for the version after precise16:25
claygoh i thought when i checked precise was 2.1.316:26
notmynameprecise is 2.1.2. we landed one with 2.1.316:26
notmynamenow I'm looking at that linked bug16:26
notmynamehmm...so running with futures==2.1.3 works on my saio.16:29
*** annegent_ has quit IRC16:30
notmynamelooks like it might jsut be that it wasn't installed?16:32
claygyeah i don't get it...16:35
*** mahatic has joined #openstack-swift16:36
claygi don't get this section, it looks like it installs the latest version of swiftclient with the old depends -> http://logs.openstack.org/91/116991/1/check/check-grenade-dsvm/682b033/logs/grenade.sh.txt.gz#_2014-08-26_22_51_00_69716:37
notmynameclayg: ya. I was just talking to sdague about it in -infra16:38
notmynameclayg: I don't get the logic (actually I just disagree with it), but the way forward is to add the new dependency to the old stable branch. that's what has to happen for all new dependencies since the old reqs file is used to test the upgrade from old to new16:39
*** aix has quit IRC16:40
claygwhat the fuck?16:43
*** bvandenh has quit IRC16:43
claygnotmyname: so does grenade not run on client changes then I guess?16:44
notmyname????16:45
* notmyname doesn't know how to type the "I have no idea" sound16:45
claygso this is the change that merged, and all the gate tests ran just fine -> https://review.openstack.org/#/c/85453/2716:46
notmynameright, and grenade doesn't run.16:46
notmynameso that's the simple answer, I guess16:47
claygno it did run, and i'm totally confused by the output -> http://logs.openstack.org/53/85453/30/check/check-grenade-dsvm/acc74de/logs/grenade.sh.txt.gz#_2014-08-26_14_20_51_45516:47
notmynameoh16:47
claygwhere as in the one that was reported as the bug the "old requirements file" just didn't even mention that we needed futures16:48
*** tkay has joined #openstack-swift16:48
claygthen in the change that *added* futures the "old requirements file" not only required it, a compatible version was already installed16:48
*** gyee has quit IRC16:51
*** tumf has joined #openstack-swift17:02
*** annegent_ has joined #openstack-swift17:03
*** geaaru has quit IRC17:04
*** tumf has quit IRC17:07
*** annegent_ has quit IRC17:14
notmynamehttp://lists.openstack.org/pipermail/openstack-operators/2014-August/005017.html <-- question about swift-init reload17:28
*** jyoti-ranjan has quit IRC17:35
*** zul has quit IRC17:37
zaitcevNot sure what he's concerned about. Does he run out of processes or fds, or does he not. Surely doubling the numbers is expected, for a while. If they never finish, that is a problem.17:39
*** shakamunyi has joined #openstack-swift17:40
openstackgerritSamuel Merritt proposed a change to openstack/swift: Reject overly-taxing ranged-GET requests  https://review.openstack.org/11757917:41
claygnormally bc just hands out in here?  how am i supposed to even reply to that mailing list?17:48
claygzaitcev: is right of course, 1) yeah double 2) max_upload_time is configurable17:49
*** zul has joined #openstack-swift17:50
*** echevemaster has joined #openstack-swift17:53
*** morganfainberg is now known as morganfainberg_Z17:57
claygok, that's sorta trixy, the thing that lets the children exit after the parent hups is the handling of EINVAL around the wsgi.server call in run_server18:02
claygbasically it looks like the next time the child comes around and tries to accept a new conn it blows up cause the parent already closed the accepting socket before it shutdown - pretty neato18:02
*** tumf has joined #openstack-swift18:03
*** annegent_ has joined #openstack-swift18:03
*** fifieldt has joined #openstack-swift18:04
claygnotmyname: so it seems like the plan for testing havana upgrades to new updates going into stable/icehouse is 1) use the latest version of the clients 2) use the dependencies from havana 3) update the dependencies of havana to match the requirements of the clients18:05
*** tumf has quit IRC18:07
*** annegent_ has quit IRC18:07
notmynameclayg: which seems weird to me, since it means that "stable" keeps changing18:10
notmynameclayg: but yes, I have the same understanding18:10
* notmyname is on a defcore phone call where they are talking about "designated sections" of code required to use the openstack trademark18:10
*** Midnightmyth has quit IRC18:17
*** annegent_ has joined #openstack-swift18:19
*** gyee has joined #openstack-swift18:21
torgomaticnotmyname: shall I send in the emergency whiskey?18:23
zaitcevAnita must be trying hard to earn her bread.18:26
claygzaitcev: ?18:30
*** annegent_ has quit IRC18:33
*** annegent_ has joined #openstack-swift18:33
*** mkollaro has quit IRC18:52
*** mkollaro has joined #openstack-swift19:00
*** tumf has joined #openstack-swift19:03
*** tumf has quit IRC19:08
*** fifieldt has quit IRC19:08
*** occup4nt has joined #openstack-swift19:10
*** chuck_ has joined #openstack-swift19:14
*** zul has quit IRC19:16
*** mkollaro has quit IRC19:17
*** chuck_ has quit IRC19:20
*** zul has joined #openstack-swift19:20
*** openstackgerrit has quit IRC19:31
*** openstackgerrit has joined #openstack-swift19:33
portantepeluse: hi19:45
portantesaw your question from the swift team meeting yesterday19:45
portanteregarding the keystone ACL patch19:45
*** __lgw4__ has quit IRC19:54
*** tdasilva has quit IRC19:57
*** tumf has joined #openstack-swift20:05
*** tumf has quit IRC20:09
*** annegent_ has quit IRC20:10
*** fifieldt has joined #openstack-swift20:17
*** Dafna has quit IRC20:23
*** foexle has quit IRC20:32
*** echevemaster has quit IRC20:32
*** shri has joined #openstack-swift20:32
peluseportante:  howdy!20:36
*** occup4nt has quit IRC20:38
*** occup4nt has joined #openstack-swift20:38
*** fifieldt_ has quit IRC20:42
*** mahatic has quit IRC20:56
*** fifieldt_ has joined #openstack-swift20:59
*** annegent_ has joined #openstack-swift21:04
*** joeljwright has joined #openstack-swift21:05
*** tumf has joined #openstack-swift21:06
*** occup4nt is now known as occupant21:07
*** annegent_ has quit IRC21:09
*** tumf has quit IRC21:10
*** annegent_ has joined #openstack-swift21:14
*** foexle has joined #openstack-swift21:15
*** Slo__ has quit IRC21:35
notmynamewhooo! I love twitter21:41
* notmyname doesn't actually always love twitter21:41
openstackgerritJesse J. Cook proposed a change to openstack/python-swiftclient: Python sessions, streaming, and increased pool  https://review.openstack.org/11606521:44
*** annegent_ has quit IRC21:49
claygnotmyname: well it's not *that* awesome, it'd be great to leverage virtual box support to provision extra drives instead of loopback (at least optionally)21:52
claygnotmyname: at least I *think* vagrant knows how to do that21:52
*** joeljwright has quit IRC21:53
notmynameclayg: sure. in this case, someone is asking about using swift on loopback mounts, and it's easy to point to VSAIO and say "see!"21:53
claygnotmyname: I think maybe it does a mount point per device tho, so maybe it doesn't need to have the mount_check = false - maybe that's something21:53
claygnotmyname: well how lucky21:53
notmyname:-)21:53
*** swift_developer has joined #openstack-swift21:54
swift_developerHi21:54
claygoh, it looks like it does mount_check = false - so probably does do a single mount with dir per device21:54
notmynamewhoa. I love swift_developers21:55
swift_developerI am trying to configure the account and container services on a separate disk on the same node.21:55
claygswift_developer: great handle!  unless you're an "apple swift" developer - in which case wrong channel ;)21:55
notmynameheh21:55
notmynametaylor swift developer21:55
claygwhoa21:55
claygvery popular these days as I understand it21:55
swift_developerDoes anyone have any instructions on how to do this?21:55
notmynameswift_developer: yup. what are you doing now21:56
claygacorwin is acctually both a swift developer and an apple swift develop - we're not exclusionary21:56
notmynamedoes acorwin also listen to taylor swift?21:56
acorwinnotmyname: you know it21:56
swift_developerbasically, I'd like to have my account/container services to be on the SSD for my node.21:57
notmynameswift_developer: yup, that's a great idea. everyone should do that21:57
notmynameswift_developer: to do that, you add only the ssd mount points to your account and container rings and leave them out of your object ring21:57
swift_developerOr actually, I was wondering which files I would need to place on the SSD.21:59
swift_developerI'm not trying to include the SSDs as searchable devices for the rings, but rather to have the account and container services be run by the SSDs.22:00
notmynameswift_developer: not sure I follow. you shouldn't need to place any files on drives that swift manages. but eg you'd have the account and container processes running on the server where those drives live22:00
swift_developerOk, so my configuration is having all services (proxy, account, container, object), all on 1 node.22:01
swift_developerAnd I just want to place the account and container services on the SSD that's in that node.22:02
swift_developerObjects, though, are going to be stored in the other drives (which are all HDDs).22:03
torgomaticright, so when you set up the rings, you're going to run "swift-ring-builder blah.builder add blahblahblah" a bunch of times22:03
*** dmsimard is now known as dmsimard_away22:03
torgomaticwhen you're looking at account.builder and container.builder, only add SSDs22:04
torgomaticwhen you're looking at object.builder, only add spinning HDDs22:04
torgomaticif there's any HDDs in account.builder or container.builder, take them out, and do likewise for SSDs in object.builder22:04
swift_developerOk, so do you know when/where the account and container DBs get created, so that we can verify that they're being created the right way?22:05
*** tumf has joined #openstack-swift22:06
notmynameswift_developer: `ls` on the drives (seriously)22:06
notmynamealso you can use `swift-get-nodes` to see where swift thinks the data should go22:07
mattoliverauMorning all22:07
mattoliveraunotmyname: sure I'll move you from bcc to cc22:08
*** tumf has quit IRC22:09
*** tumf has joined #openstack-swift22:09
notmynamemattoliverau: thanks22:09
*** tkay has left #openstack-swift22:11
swift_developerOkay, thank you!22:13
*** tumf has quit IRC22:13
notmynameswift_developer: under the mount point of the drive, you'll have a directory for accounts, container, and objects22:14
notmyname(technically, maybe more than one directory for objects if you're using multiple storage policies)22:14
notmynameswift_developer: but swift is putting the data (incuding account and container data) down on disk as files. so you can use normal filesystem tools to inspect it22:14
*** fifieldt has quit IRC22:17
swift_developerI take it that there is some difference between how the data is being put on the disk, for account/container vs objects, since account/container services use a DB.22:20
notmynameswift_developer: account and containers use sqlite, which is a DB engine, but it ends up "just" being a file on disk22:20
notmynamere my earlier comment about twitter: https://twitter.com/troytoman/status/50509994714267648022:20
*** sungju has joined #openstack-swift22:29
notmynamepeluse: when will tsg be around next? I had a question about the upstream eventlet patch22:32
*** morganfainberg_Z is now known as morganfainberg22:34
swift_developerIs xfs a good choice for partitioning the SSD that will host the account and container services?22:36
swift_developerI used xfs for my HDDs that will store Objects, but wasn't sure whether xfs is a good choice for the SSD that will host the account and container services22:37
notmynameswift_developer: yup. it's fine on ssd22:40
*** zaitcev has quit IRC22:41
swift_developerokay, thank you!22:41
*** tumf has joined #openstack-swift23:10
ahale_that tweet that says swift code quality is becoming more like openstack .. worrying23:13
notmynameahale_: ya, I'm not sure that's what was meant, but funny :-)23:13
ahale_very :)23:13
notmynameahale_: I think there was another one buried in there about log message formats. that's what he was looking for23:14
ahale_aha i didn't read them all23:15
notmynameahale_: ya, i'm not sure I did either. turns out, twitter is _terrible_ for a threaded conversation23:16
notmynameshocking, I know23:16
swifterdarrellnotmyname: I'd have stopped after the _terrible_ ;)23:19
notmynameswifterdarrell: heh23:19
*** annegent_ has joined #openstack-swift23:22
*** dmsimard_away is now known as dmsimard23:23
*** annegent_ has quit IRC23:25
notmynamemy thoughts on the openstack ops meetup this week https://swiftstack.com/blog/2014/08/27/ops-meetup-refections/23:27
*** shakamunyi has quit IRC23:33
*** Edward-Zhang has joined #openstack-swift23:35
pelusenotmyname:  I'm not answering til I get my + back :)23:42
*** swift_developer has quit IRC23:42
notmynamepeluse: thanks for the reminder23:42
pelusenotmyname: he should be lurking... I'm working from home today so haven't seen anyone23:43
peluseI'll ping him23:43
*** tumf has quit IRC23:43
*** ChanServ sets mode: +o notmyname23:44
peluseOK, pinged.... should shoul hear from him next time he looks at his computer23:44
*** notmyname sets mode: +v peluse23:44
*** notmyname sets mode: -o notmyname23:44
peluseahh, that felt good23:44
notmynamenow I gotta remember my question23:45
notmynamesomething about when it's released, and then we gotta figure out when to get it in to openstack's global requirements23:46
notmynameand that affects distros, so there are cutoff dates.23:46
peluseit was committed:  https://github.com/eventlet/eventlet/commits/master which is all I know23:46
*** openstackgerrit has quit IRC23:46
*** openstackgerrit has joined #openstack-swift23:48
*** tsg has joined #openstack-swift23:51
tsgnotmyname: ping23:51
tsgnotmyname: peluse mentioned that you had a question about the upstream eventlet patch23:53
pelusetsg: see above, do you know when it will be released or can you ask?23:56
tsgnotmyname, peluse: the next scheduled eventlet release is 0.16, to go out on 9/1123:56
tsgI am trying to convince the author to cut a 0.15.2 for us23:57
tsgif that goes well, should be this weekend23:57
peluseway cool23:57

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!