Monday, 2014-08-25

*** annegentle has joined #openstack-swift00:10
*** dmorita has joined #openstack-swift00:24
*** tsg has quit IRC00:28
*** tgohad has quit IRC00:29
*** tgohad has joined #openstack-swift00:30
*** tsg has joined #openstack-swift00:30
*** annegentle has quit IRC00:31
*** mitz has joined #openstack-swift00:37
*** nosnos has joined #openstack-swift00:45
*** annegentle has joined #openstack-swift00:50
*** annegentle has quit IRC00:54
*** nosnos has quit IRC00:58
*** nosnos has joined #openstack-swift01:01
*** mitz has quit IRC01:01
*** annegentle has joined #openstack-swift01:02
*** mitz has joined #openstack-swift01:03
*** annegentle has quit IRC01:09
*** addnull has joined #openstack-swift01:13
*** mitz has quit IRC01:13
*** mitz has joined #openstack-swift01:16
*** nosnos has quit IRC01:19
*** nosnos has joined #openstack-swift01:22
*** nosnos has quit IRC01:24
*** elambert has quit IRC01:27
*** evanjfraser has joined #openstack-swift01:33
*** Edward-Zhang has joined #openstack-swift01:39
*** nosnos has joined #openstack-swift01:51
*** haomaiwang has joined #openstack-swift01:56
*** nosnos has quit IRC01:58
*** nosnos has joined #openstack-swift01:58
*** annegentle has joined #openstack-swift02:10
*** haomaiw__ has joined #openstack-swift02:12
*** haomaiwang has quit IRC02:13
*** annegentle has quit IRC02:15
*** annegentle has joined #openstack-swift02:18
*** tgohad has quit IRC02:33
*** tsg has quit IRC02:33
*** elambert has joined #openstack-swift03:05
*** elambert has quit IRC03:06
*** annegentle has quit IRC03:14
*** mrsnivvel has joined #openstack-swift03:23
*** jasondotstar has quit IRC03:26
*** elambert has joined #openstack-swift03:30
*** ppai has joined #openstack-swift03:40
*** Edward-Zhang has quit IRC03:43
*** atan8 has joined #openstack-swift03:45
*** tsg has joined #openstack-swift03:59
*** tgohad has joined #openstack-swift03:59
*** atan8_ has joined #openstack-swift04:00
*** atan8 has quit IRC04:00
openstackgerritpaul luse proposed a change to openstack/swift-specs: Updates to EC Design Spec  https://review.openstack.org/11648604:02
*** Edward-Zhang has joined #openstack-swift04:16
*** atan8_ has quit IRC04:25
*** nosnos has quit IRC04:32
*** nosnos has joined #openstack-swift04:33
*** kopparam has joined #openstack-swift04:57
*** tgohad has quit IRC05:05
*** tsg has quit IRC05:05
*** kopparam has quit IRC05:17
*** kopparam has joined #openstack-swift05:17
*** kopparam has quit IRC05:22
*** kopparam has joined #openstack-swift05:27
*** addnull has quit IRC05:41
*** addnull has joined #openstack-swift05:41
*** addnull has quit IRC05:43
*** addnull has joined #openstack-swift05:44
*** addnull_ has joined #openstack-swift05:46
*** addnull has quit IRC05:47
*** addnull_ has quit IRC05:47
*** addnull has joined #openstack-swift05:48
*** addnull has joined #openstack-swift05:50
*** miqui has quit IRC06:00
*** nshaikh has joined #openstack-swift06:02
*** k4n0 has joined #openstack-swift06:05
*** haomaiw__ has quit IRC06:08
*** haomaiwa_ has joined #openstack-swift06:08
*** haomaiw__ has joined #openstack-swift06:17
*** haomaiwa_ has quit IRC06:21
*** joeljwright has joined #openstack-swift06:57
ByteSoredoes someone know how to fix this? swift: ERROR Insufficient Storage 192.168.0.102:6002/accounts? i get it when i run swift list06:57
*** dvas has joined #openstack-swift07:00
*** sungju has quit IRC07:06
*** kopparam has quit IRC07:07
*** kopparam has joined #openstack-swift07:08
*** kopparam has quit IRC07:12
*** dvas has quit IRC07:19
*** dvas has joined #openstack-swift07:19
*** bkopilov has joined #openstack-swift07:20
*** dvas_ has joined #openstack-swift07:22
*** dvas has quit IRC07:24
*** jokke__ is now known as jokke_07:31
*** Midnightmyth has joined #openstack-swift07:34
*** bvandenh has joined #openstack-swift07:35
*** kopparam has joined #openstack-swift07:58
ByteSorenvm, found it. mount_check = false fixed it08:05
*** geaaru has joined #openstack-swift08:17
*** dvas_ has quit IRC08:25
*** dvas_ has joined #openstack-swift08:37
*** k4n0 has quit IRC08:39
*** kopparam has quit IRC08:41
*** nshaikh has quit IRC08:43
*** k4n0 has joined #openstack-swift08:53
*** mkollaro has joined #openstack-swift09:05
*** mkollaro has quit IRC09:09
*** mkollaro1 has joined #openstack-swift09:09
*** kopparam has joined #openstack-swift09:20
*** Edward-Zhang has quit IRC09:25
*** kopparam_ has joined #openstack-swift09:41
*** dvorkbjel has quit IRC09:42
*** kopparam has quit IRC09:44
*** koppara__ has joined #openstack-swift09:44
*** dvorkbjel has joined #openstack-swift09:45
*** koppar___ has joined #openstack-swift09:46
*** kopparam_ has quit IRC09:47
*** koppara__ has quit IRC09:49
*** dvas_ has quit IRC09:49
*** dvas_ has joined #openstack-swift09:49
*** ppai has quit IRC09:50
*** dvas_ has quit IRC09:54
*** dvas_ has joined #openstack-swift09:54
*** ppai has joined #openstack-swift10:06
*** koppar___ has quit IRC10:10
*** kopparam has joined #openstack-swift10:17
*** addnull has quit IRC10:44
*** nshaikh has joined #openstack-swift10:46
*** k4n0 has quit IRC10:47
*** addnull has joined #openstack-swift10:47
*** bkopilov has quit IRC10:48
*** bkopilov has joined #openstack-swift10:49
*** dmorita has quit IRC10:55
*** k4n0 has joined #openstack-swift10:59
*** tdasilva has quit IRC11:03
*** tdasilva has joined #openstack-swift11:05
*** addnull has quit IRC11:10
*** dvas_ has quit IRC11:20
*** dvas_ has joined #openstack-swift11:21
*** mkollaro has joined #openstack-swift11:22
*** mkollaro1 has quit IRC11:24
*** dvas_ has quit IRC11:25
*** ppai has quit IRC11:39
*** tdasilva has quit IRC11:43
*** ppai has joined #openstack-swift11:51
*** mkollaro has quit IRC12:14
*** mkollaro1 has joined #openstack-swift12:14
*** bvandenh has quit IRC12:18
*** bvandenh has joined #openstack-swift12:19
*** kopparam has quit IRC12:24
*** thomaschaaf has joined #openstack-swift12:30
thomaschaafhello i just upgraded from 1.13 to 2.0 and read acl seem to have been reset12:31
thomaschaafwhy could this be?12:31
*** jasondotstar has joined #openstack-swift12:34
thomaschaafhmm restarted swift services and now they are back12:36
thomaschaafweird..12:36
*** dvas_ has joined #openstack-swift12:47
*** kopparam has joined #openstack-swift12:55
*** ppai has quit IRC12:56
thomaschaafdo i actively have to enable xprofile?12:59
*** miqui has joined #openstack-swift13:08
*** dvas_ has quit IRC13:13
*** dvas_ has joined #openstack-swift13:14
*** dvas__ has joined #openstack-swift13:17
*** dvas_ has quit IRC13:18
*** chandankumar has joined #openstack-swift13:20
*** dvas___ has joined #openstack-swift13:20
*** dvas__ has quit IRC13:21
*** tdasilva has joined #openstack-swift13:23
*** mikehn_ is now known as mikehn13:24
*** k4n0 has quit IRC13:35
*** nosnos has quit IRC13:38
*** nosnos has joined #openstack-swift13:38
*** nosnos has quit IRC13:43
*** chandankumar has quit IRC13:46
*** bkopilov has quit IRC13:48
openstackgerritXiang Hui proposed a change to openstack/swift: Fix getaddrinfo if dnspython is installed.  https://review.openstack.org/11661813:51
openstackgerritXiang Hui proposed a change to openstack/swift: Fix getaddrinfo if dnspython is installed.  https://review.openstack.org/11661813:54
*** kopparam has quit IRC13:57
*** kopparam has joined #openstack-swift13:58
*** dmsimard_away is now known as dmsimard14:03
*** atan8 has joined #openstack-swift14:14
*** __lgw4__ has joined #openstack-swift14:23
notmynamegood morning world14:25
notmyname2.1.0.rc1 has been tagged. final release planned for next monday (sept 1)14:25
notmynameI'm at the openstack ops meetup in san antonio today and tomorrow, so I'll be in-and-out of IRC14:25
*** IRTermite has joined #openstack-swift14:27
notmynamethomaschaaf: what do you mean by "enable" xprofile? it does need to be added to the pipeline, but that's it IIRC14:28
notmynameByteSore: mount_check is important if you aren't using real devices (eg loopback). mount_check makes sure that the OS says it's mounted, and if not it returns a 50714:28
*** jdag_ has joined #openstack-swift14:29
*** bgmccollum_ has quit IRC14:32
*** pandemicsyn has quit IRC14:32
*** jdag has quit IRC14:32
*** mtreinish has quit IRC14:32
*** jroll has quit IRC14:32
*** zacksh has quit IRC14:32
*** zacksh has joined #openstack-swift14:32
*** mtreinish has joined #openstack-swift14:32
*** bgmccollum has joined #openstack-swift14:32
*** pandemicsyn has joined #openstack-swift14:33
*** jroll has joined #openstack-swift14:33
*** jdag_ is now known as jdag14:34
*** elambert has quit IRC14:36
*** judd7 has joined #openstack-swift14:37
*** thomaschaaf has quit IRC14:38
*** erlon has joined #openstack-swift14:40
*** erlon has quit IRC14:40
*** erlon has joined #openstack-swift14:40
*** mtreinish_ has joined #openstack-swift14:50
*** pandemicsyn has quit IRC14:50
*** bgmccollum has quit IRC14:50
*** zacksh has quit IRC14:50
*** mtreinish has quit IRC14:50
*** bgmccollum has joined #openstack-swift14:50
*** zacksh has joined #openstack-swift14:50
*** pandemicsyn has joined #openstack-swift14:50
*** mtreinish_ is now known as mtreinish14:51
*** tsg has joined #openstack-swift14:55
*** tgohad has joined #openstack-swift14:55
*** kopparam has quit IRC14:57
*** kopparam has joined #openstack-swift14:57
*** mwstorer has joined #openstack-swift14:59
*** kopparam has quit IRC15:00
*** annegentle has joined #openstack-swift15:00
*** dvas___ has quit IRC15:12
*** pconstantine has quit IRC15:12
*** dvas___ has joined #openstack-swift15:27
*** pconstantine has joined #openstack-swift15:31
*** atan8 has quit IRC15:36
*** dvas___ has quit IRC16:04
*** annegentle has quit IRC16:04
*** bvandenh has quit IRC16:04
*** dvas___ has joined #openstack-swift16:04
*** nshaikh has quit IRC16:07
*** dvas___ has quit IRC16:08
*** mahatic has joined #openstack-swift16:12
*** atan8 has joined #openstack-swift16:14
*** atan8 has quit IRC16:34
*** elambert has joined #openstack-swift16:55
*** openstackgerrit has quit IRC17:00
*** dvas___ has joined #openstack-swift17:05
*** dvas___ has quit IRC17:12
*** dvas___ has joined #openstack-swift17:12
*** openstackgerrit has joined #openstack-swift17:14
*** dvas___ has quit IRC17:15
*** dvas___ has joined #openstack-swift17:15
*** dvas___ has quit IRC17:19
*** geaaru has quit IRC17:21
*** esmute has quit IRC17:24
*** aix has quit IRC17:24
*** peluse has left #openstack-swift17:35
*** peluse has joined #openstack-swift17:35
*** esmute has joined #openstack-swift17:37
*** shri has joined #openstack-swift17:40
*** tsg has quit IRC17:40
*** tgohad has quit IRC17:41
*** gyee has joined #openstack-swift17:48
*** tsg has joined #openstack-swift17:55
*** tgohad has joined #openstack-swift17:55
*** esmute has quit IRC18:00
*** esmute has joined #openstack-swift18:00
occupantso I'm running on CentOS 6 and I thought I'd try using a elrepo 3.0 kernel on the storage nodes because I suspected my hardware was being held back by the CentOS kernel. Went from 40% idle to 4-5% idle.18:02
*** elambert has quit IRC18:02
*** elambert has joined #openstack-swift18:05
*** pconstantine has quit IRC18:18
*** jasondotstar has quit IRC18:30
*** jasondotstar has joined #openstack-swift18:31
*** gvernik has joined #openstack-swift18:32
*** pconstantine has joined #openstack-swift18:34
*** elmiko has joined #openstack-swift18:35
elmikohey folks, i'm looking for the preferred method to get the storageURL for Swift in a project. would i be better served creating a Connection and using get_auth or is there a way to query the service catalog from keystone?18:36
*** jasondotstar has quit IRC18:38
*** gvernik has quit IRC18:38
*** elambert has quit IRC18:39
*** marcusvrn has joined #openstack-swift18:44
*** haomaiwa_ has joined #openstack-swift18:46
*** haomaiw__ has quit IRC18:47
*** gvernik has joined #openstack-swift19:03
*** jasondotstar has joined #openstack-swift19:03
*** mahatic has quit IRC19:03
*** rick_ has joined #openstack-swift19:05
*** gvernik has quit IRC19:10
claygnotmyname: how's SA?19:11
rick_Let's say that we have 3 copies of data on three different disks within the same sotrage server or within cluster. On what basis does Swift decide from which disk it will read the data? Does it know which disk could serve data the fastest (based on disk utilization) or is there some other decision criteria?19:13
claygrick_: mostly it's random19:14
claygrick_: there's things like timing affinity that sorta act like huristics to sort things - but it's not so scientific19:15
claygelmiko: I'm sure you could get a catalog from keystone - but get_auth is generally recommeneded19:16
elmikoclayg: thanks, i can get it working either way, i was more curious if there was a "best practice" or some such19:16
rick_maybe also this question for you clayg. Is it already possible, with Swift-on-File as an open-source solution, to save/read objects to Swift backend through legacy NFS protocol?19:17
claygoccupant: and less idle is better in your case?  you've got some active load going at it?19:17
claygrick_: swift-on-file is other way - talk swift to a file system; not talk file system to swift19:18
claygrick_: i'm not aware of an opensource solution that let's you point legacy applications that talk file system to an nfs share to use object storage19:18
rick_maybe some FUSE solution could allow this? some aditional fs layer on top of object storage? I was loking this -> https://code.google.com/p/s3ql/wiki/other_s3_filesystems19:19
*** mahatic has joined #openstack-swift19:22
rick_I am looking Huawei UDS solution from SNIA conference, they are using s3fs, but I do not know possible hacks they made -> http://www.snia.org/sites/default/files2/SDC2013/presentations/ObjectStorage/QuingchaoLuo_Huawei%20SmartDisk_based_Object_Storage.pdf19:22
rick_You can see picture on S3 FS slide19:22
rick_slide number 1919:23
rick_So I am guessing possible Swiftstack is using something similar -> https://www.swiftstack.com/uploads/factsheets_pdf/swiftstack_filesystem_gateway.pdf19:24
*** occupant has quit IRC19:37
tdasilvarick_: swiftonfile currently supports only FS with xattr support. You can write a file and get it from swift, but you need to know the full path19:37
*** occupant has joined #openstack-swift19:38
rick_So currently there is only comercial sw from Swiftstack - Filesystem Gateway available that could do vice-versa manipulating data?19:39
claygrick_: another swiftstack employee who's also a swift core dev reminded me of https://github.com/redbo/cloudfuse19:42
claygrick_: redbo lurks in here sometimes - he may (or may not) comment on his opinion of how successful that might be on nfs19:43
clayger rather exposing the fuse file system to nfs19:43
rick_clayg, tdasilva: thank you for the comments provided. I will also check on cloudfuse.19:46
redbohmmm... I'm not sure.  nfs (as of v4) can export a fuse filesystem if you configure it right.  But I don't know if cloudfuse is correct enough for nfs.19:48
*** mahatic has quit IRC19:56
*** fifieldt_ has joined #openstack-swift20:03
*** fifieldt has quit IRC20:06
rick_Maybe this is interesting: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/chap-User_Guide-UFO.html20:07
*** annegentle has joined #openstack-swift20:08
tdasilvarick_: that's basically describing swiftonfile20:09
tdasilvathe project used to be called gluster-swift and we have now changed the name to swiftonfile. It allows for swift to access objects stored on a filesystem following the same path as the URL20:11
tdasilvaso if you store a file on /mnt/swiftonfile/acct/cont/obj, then you can GET the object  "acct/cont/obj" with swift and vice-versa20:12
rick_It says : "Unified File and Object Storage technology enables enterprises to adopt and deploy cloud storage solutions. It allows users to access and modify data as objects from a REST interface along with the ability to access and modify files from NAS interfaces including NFS and SMB. "20:13
tdasilvacorrect....i think some of the confusion is that earlier you asked if you could write object to swift backend throught nfs, which sounded like you wanted to migrate data from a legacy system to a swift cluster with its own backend....with swiftonfile your NFS mount point is your swift backend storage20:15
tdasilvawith the new storage policies, you could deploy a swift cluster with policies that use the default storage backend of swift and you could add another swiftonfile policy that access your objects over your fuse mount point20:17
rick_sri: thx for the link provided, please send me also your email.20:17
*** dvas___ has joined #openstack-swift20:18
shririck_: Sent it to you directly.20:19
rick_tdasilva: ok, so with swift-on-file , Swift object storage backend can be mounted somehow to be used together with legacy NFS/CIFS appication.... if i understad siwft-on-file is able to translate NFS/CIFS protocol to REST API/Swift API calls?20:22
rick_shri: thx for contact20:22
notmynameclayg: SA is hot!20:28
tdasilvarick_: swiftonfile allows you to write/read files through the swift rest interface as well as a NAS interface20:28
notmynameclayg: but they've got a nice new event center at rackspace to host the ops meetup20:29
tdasilvarick_: this doc is a bit more up to date then the previous one: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/chap-User_Guide-Object_Store.html20:29
rick_ok. let me check it out20:30
IRTermitenotmyname: indeed we do!20:31
tdasilvarick_: checkout the #swiftonfile channel...i have to get going, but other folks might be able to help20:31
rick_ok, no problem. thx for all the info!20:32
tdasilvaor feel free to post questions here: https://github.com/swiftonfile/swiftonfile/issues20:32
tdasilvano problem...good luck20:32
*** miqui has quit IRC20:33
*** tdasilva has quit IRC20:36
claygdfg: ok, I think i see the idea that you don't want to limit the node completely - but I thought that sliding time window would still do that - but you may have to convince sam to help me with the math as to why random.random() < weighted_average works out to letting 10% of requests go through and not... some fucking random amount of requests who happen to return a value less than weight_average go through...20:50
claygdfg: either way i'm glad your back and looking at that patch - i've been thinking about that patch a lot and i'm sorta getting a crush on it20:53
dfgum...20:53
dfgclayg: what do you mean?20:54
dfgby the "random.random() < weighted_average works out to letting 10% of requests" ?20:54
claygi was trying to interpret your comment on my comment about the coin flip?20:55
dfglike the weighted average gives the individual nodes kinda a score and then the proxy tries to limit based on that.20:55
dfgif, based on the history 90% of the requests resulted in a timeout then there will be a 90% chance that the node will be skipped20:56
claygdfg: yeah I think i get that... but I think i was looking for if weighted_average > "some known value at which i say screw this node" with maybe a tunable or something and instead i found a call to random and realized I have no idea what i'm looking at anymore :'(20:57
claygdfg: oh oh oh, ok gimme a second20:57
dfgoh- i don't do that.20:57
dfgi won't ever complete;y stop sending reqs (how would I know what that number is and how would i know when to try starting again)20:59
claygyeah yeah yeah; cool cool cool - i was just confused.  this stuff is hard.  you do like a fire-side chat where we can all just gather around and you beat stupid out of us21:00
claygor oh oh *I* know - you could come to a design summit or a hack-a-thon every once in a while21:00
clayg:P21:01
dfgya- of course the one i went to you weren't there21:01
claygfair :\21:02
dfganyway- i'm not saying that error limiting is the best or anything but i'm trying to ease into it. even a dumb limiting like I have should help a lot i think but i wrote it to be pretty lax i think (hope)21:02
dfgi mean i just don't want to just like break everything all at once :)21:04
claygdfg: I think what you have is pretty sophisticated and I definately think it would help (maybe *quite* a lot) - i'm really keen on this change; I'd be interested in ideas you have on how to test it out and what we can do to help21:04
dfgclayg: well to test it i have some crappy middleware in our local stuff that sits on the obj server and randomly slows crap down based on configs. the tests do fine but then i feel that i'm writing the test for the feature and it doesn't mean much. idk21:07
dfganyway- all that will have to be expanded on when its gets cooked more. but I'll keep y'all in the loop. i got kinda side tracked with a couple things recently21:16
claygI'm chatting across the table with swifterdarrell we also have some crappy "break some random stuff" middleware's lying about - you think we should try and gather requirements and do something more useful or just throw 'em out there (tcod?) and let everyone kinda just sorta hack around the edges on their own stuff?21:19
dfgclayg: that would be cool.21:22
swifterdarrelldfg: i haven't actually evolved to "middleware" yet--just a hacked-in latency injector... but what I actually *want* is a configurable layer like middleware suitable for fuzz-testing various failure modes (random latencies injected, random connection severing, etc.)21:23
swifterdarrelldfg: I think that could be useful for testing various Swift clients or applications... hard to shake that stuff out w/o a real cluster and who wants to have to twist their real cluster into the random weird shit that shows up under load?21:24
notmynameswifterdarrell: https://github.com/notmyname/latency_middleware (super old. should* still work)21:25
notmynamento as full featured as you are wanting, though21:26
*** acoles has quit IRC21:30
dfgswifterdarrell: that sounds cool. i'll clean up my stuff and show you want I have. it would be cool to have something simple / moderately put together that people can use to try this type of stuff out.21:30
claygnotmyname: it's a start?  but like with david's code we'd need something that would like sleep for >10s before responding and then go back to normal21:30
notmynameclayg: ya. for sure. I wrote that a long time ago when I was trying to debug something or other21:31
swifterdarrelldfg: ya, any kind of working skeleton would be a great start for me21:31
claygnotmyname: to use something like that in a probetest you might want to have the middleware do a reloading config trick (probably *not* the object-server.conf) where the test could control the values21:31
dfgclayg: thats basically what mine does. i works for PUTs and GETs and can read in some bytes before crapping out and stuff.21:32
notmynameah, that would be cool21:32
notmynameya, I totally expect whatever dfg has to be much better than mine21:32
swifterdarrelldfg: my main problem was that i could inject 16s latency where I knew some code had a 15s timeout, but it wasn't selective enough for initialization stuff to work, followed by later timeouts... I think a probabilistic latency would have been sufficient, perhaps with some ramp-up21:32
notmynamewhy should you use swift? this is why: http://d.not.mn/a-disk-in-the-SAN-is-about-to-fail.gif21:34
*** dvas___ has quit IRC21:35
*** dvas___ has joined #openstack-swift21:35
*** dvas___ has quit IRC21:40
*** dvas___ has joined #openstack-swift21:44
*** dvas____ has joined #openstack-swift21:47
*** dvas___ has quit IRC21:49
*** annegentle has quit IRC21:52
*** annegentle has joined #openstack-swift21:52
*** dvas____ has quit IRC21:53
*** dvas____ has joined #openstack-swift21:54
*** dvas____ has quit IRC21:59
*** occup4nt has joined #openstack-swift21:59
*** occupant has quit IRC22:01
*** serverascode has quit IRC22:01
*** hurricanerix has quit IRC22:01
*** hurricanerix_ has joined #openstack-swift22:01
*** dmsimard is now known as dmsimard_away22:02
*** jasondotstar is now known as jasondotstar|afk22:02
*** serverascode has joined #openstack-swift22:02
*** __lgw4__ has quit IRC22:05
*** occup4nt is now known as occupant22:06
*** mitz has quit IRC22:06
*** HenryG_ has joined #openstack-swift22:12
torgomaticnotmyname: there are more words on the internet for you to read now, particularly on https://review.openstack.org/#/c/111562/22:13
*** HenryG has quit IRC22:15
mattoliverauMorning all22:23
*** annegentle has quit IRC22:24
rick_maybe weird question, but how Swift writes data to disk. In how many steps is data written to disk. I know that account/container db file is updated and than data is written somewhere to the disk. Is this happening simultaneous or is there some waiting mechanisms....etc. I know that there is no journaling involved as it is in the case of Ceph, which wants to be stroingly consistent...22:29
*** shakamunyi has joined #openstack-swift22:31
*** elmiko is now known as _elmiko22:38
*** shakamunyi has quit IRC22:40
*** joeljwright has quit IRC22:42
*** joeljwright has joined #openstack-swift22:43
*** joeljwright has quit IRC22:43
*** Midnightmyth has quit IRC22:50
*** annegentle has joined #openstack-swift22:51
*** shakamunyi has joined #openstack-swift22:54
*** zul has quit IRC22:57
*** mwstorer has quit IRC22:58
*** annegentle has quit IRC23:06
*** zul has joined #openstack-swift23:09
*** erlon has quit IRC23:10
*** marcusvrn has quit IRC23:31
*** _elmiko is now known as elmiko23:31
*** annegentle has joined #openstack-swift23:36
*** annegentle has quit IRC23:43
*** sungju has joined #openstack-swift23:57
*** tgohad has quit IRC23:58
*** tsg has quit IRC23:58

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