Thursday, 2015-01-08

*** chlong has quit IRC00:01
*** chlong has joined #openstack-swift00:02
*** chlong has quit IRC00:06
hogood morning!00:10
hoclayg: thanks for the review. I will check your comments on it.00:11
claygho: yeah... at somepoint I realized I don't entirely understand the use case - so it may be better to start with some evangelizing00:11
claygit's much easier to get some reviews on a feature if we can get some people excited about the feature!00:11
hoclayg: thanks! in BP there is a link to a mail-list thread. In the thread i disccussed a use-case with notmyname. http://lists.openstack.org/pipermail/openstack-dev/2014-July/040948.html00:14
hoclayg: i see. i need some evangelizing first :)00:16
EmilienMI have a stupid question and I don't find the answer in the doc. With the API, can I get an object MD5 result?00:16
claygho: oh nice, very good then - maybe you just needed to smack me in the head for not reading carefully enough!00:17
EmilienMmaybe with ETag in fact.00:18
*** Masahiro has joined #openstack-swift00:20
notmynameEmilienM: the etag (md5 of the object contents) is returned with every read request00:20
EmilienMnotmyname: excellent, it helps me to do what I wanted, thanks for confirmation !00:22
claygho: ahh - this one is great!  include this link in the commit: http://lists.openstack.org/pipermail/openstack-dev/2014-July/041076.html, the following like 4 or 5 emails sum up the issues pretty well - although there was no obvious concensus in the thread :\00:22
claygI think maybe now that we have some code up it might be a good time to dust off the old thread and see if we can get anyone to bite - I think i have some questions and wouldn't mind some smart swift devs or other swift operaters with different experience to think about and chime in on00:23
*** Masahiro has quit IRC00:24
EmilienMnotmyname: I go for another stupid question. Does it work also for write requests?00:27
EmilienMIf-match -> upload00:27
hoclayg: thanks. i will summarize the thread as a lure for getting interest :)00:28
*** chlong has joined #openstack-swift00:29
hoclayg: i talked with operators for maintenance of swift nodes. i will write their concerns on it.00:38
*** km__ has joined #openstack-swift00:43
*** km has quit IRC00:43
*** addnull has joined #openstack-swift00:49
openstackgerritSamuel Merritt proposed openstack/swift: Make ThreadPools deallocatable.  https://review.openstack.org/14564700:55
torgomaticotherjon: swifterdarrell: ^^00:56
*** dank has quit IRC01:04
openstackgerritSamuel Merritt proposed openstack/swift: Make ThreadPools deallocatable.  https://review.openstack.org/14564701:16
openstackgerritClay Gerrard proposed openstack/swift: Fix large out of sync out of date containers  https://review.openstack.org/14101901:23
*** gyee has quit IRC01:36
*** nosnos has joined #openstack-swift01:54
openstackgerritClay Gerrard proposed openstack/swift: Remove the X-Newest pre-flight request on X-Timestamp  https://review.openstack.org/10377802:01
*** haomaiwang has joined #openstack-swift02:08
*** Masahiro has joined #openstack-swift02:09
openstackgerritMerged openstack/swift: Substituted object storage paragraph with simple definition  https://review.openstack.org/14529402:11
*** chlong has quit IRC02:11
*** SkyRocknRoll has joined #openstack-swift02:12
openstackgerritClay Gerrard proposed openstack/swift: Remove the X-Newest pre-flight request on X-Timestamp  https://review.openstack.org/10377802:16
openstackgerritClay Gerrard proposed openstack/swift: Add support for multiple container-reconciler  https://review.openstack.org/10377902:22
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873602:22
*** fandi has quit IRC02:42
*** lcurtis has joined #openstack-swift03:03
*** bill_az has quit IRC03:22
*** annegent_ has joined #openstack-swift03:24
*** reed has quit IRC03:38
*** nosnos has quit IRC03:43
*** mahatic has quit IRC03:44
*** lihkin has joined #openstack-swift03:45
*** chlong has joined #openstack-swift03:57
*** k_ has joined #openstack-swift03:59
*** bkopilov has quit IRC04:01
*** chlong has quit IRC04:02
*** ppai has joined #openstack-swift04:06
*** chlong has joined #openstack-swift04:18
*** fandi has joined #openstack-swift04:22
*** fandi has quit IRC04:23
*** fandi has joined #openstack-swift04:24
*** fandi has quit IRC04:24
*** fandi has joined #openstack-swift04:26
*** annegent_ has quit IRC04:32
*** nosnos has joined #openstack-swift04:36
*** lcurtis has quit IRC04:39
*** david-lyle has quit IRC04:50
notmynamegood evening04:53
honotmyname: hi!04:56
mattoliveraunotmyname: good evening05:05
*** annegent_ has joined #openstack-swift05:06
notmynamemattoliverau: good news! I have a the rough draft of my title slide done for my lca talk ;-)  (proof! http://d.not.mn/lca_prep_screenshot.png)05:09
notmynamemattoliverau: so you could say things are getting serious ;-)05:10
mattoliveraunotmyname: nice, good to see things are coming along and not last minute :P05:10
notmynamelol @ ~40 hours before my plane takes off being "not last minute"05:11
mattoliverauTrue, doing it during the openstack mini-conf is last minute :P05:12
zaitcevmake sure to pack earplugs05:12
mattoliverauzaitcev: what for the conference? us Aussies aren't that noisy.. ok maybe we are but still :P05:13
mattoliveraunotmyname: I don't know if I want to hear the answer to this but.. with cats in the title of a talk, how many lol cat references will there be :P05:14
notmynamemattoliverau: all of them05:16
notmynameobviously05:16
mattoliveraulol05:18
*** bill_az has joined #openstack-swift05:30
notmynamehmmm...organizing this talk isn't as easy as it has been for other talks05:35
*** nshaikh has joined #openstack-swift05:36
notmynamemattoliverau: we may need to visit http://mexico.net.nz/menu/tequila next week05:44
mattoliveraunotmyname: I'm sure we can find time for that ;)05:45
*** annegent_ has quit IRC05:52
hothe following url is the backgroud of the change https://review.openstack.org/#/c/133155/ (FQDN in Rings). i think this is a good enhancement for realization of swift system's DevOps05:52
hohttp://paste.openstack.org/show/155943/05:52
hoI would like to have your feedback!05:53
notmynamethat's a really big patch05:55
*** lihkin has quit IRC05:57
*** ppai has quit IRC05:58
*** addnull has quit IRC05:58
notmynameho: just curious, but emc was interested in this functionality a while back (identifying a node in a ring by hostname instead of IP). have you had any conversations with them about this?05:58
honotmyname: I talked with previous owner of this idea, he is an engineer of emc.06:00
notmynameah cool06:00
honotmyname: his name is  "Co-Authored-By: Alex Pecoraro <alex.pecoraro@emc.com>" in the commit message06:02
honotmyname: fyi.06:02
notmynameoh, yeah. missed that :-)06:03
notmynameho: is this something you've got interest in a fujitsu or ...? IOW, how did you get involved in writing this functionality? :-)06:09
*** ppai has joined #openstack-swift06:12
honotmyname: not decided yet. but i think i can offer this func for our users after i get approval :)06:12
notmyname:-)06:12
notmynameI actually didn't know that you were using swift at fujitsu. is it a public cloud? part of a storage product sold to companies? used internally for stuff?06:13
mattoliverauho: before I was at Rackspace I worked at Fujitsu (in Australia).. wish I knew I could have worked on swift back then!06:15
honotmyname: as for public cloud, we decided to use Openstack so we will use swift also.06:16
notmynamecool!06:16
notmynameho: are you in prod yet or are you still building out the product?06:16
honotmyname: really? you worked at FAST. sorry i dont understand prod mean...06:19
notmynameprod == production06:19
*** annegentle has joined #openstack-swift06:19
notmynameand that was mattoliverau who worked there06:19
mattoliverauho: yeah I worked there :) notmyname has never worked in Australia, but he would be very welcome too ;)06:21
honotmyname: under developing for public cloud not product yet06:21
notmynameho: ah ok. is it part of http://welcome.globalcloud.global.fujitsu.com/index.html ?06:21
notmynamemattoliverau: ya, but I hear your internet connections are pretty terrible. but I do like most things about australia that I've seen.... :-)06:22
*** lihkin has joined #openstack-swift06:22
honotmyname: i'm searching public info. wait a minutes06:23
*** addnull has joined #openstack-swift06:23
mattoliveraunotmyname: yeah, damn slow internet.. downside of being such a large country with so little people largely dispurst :(06:23
mattoliverausome places you can get decent speed.. but still rather evensive and limited. At least hwne compared to Japan and probably San Fran.06:25
mattoliverauWell I'm going to go make a start on dinner before the wife arrives home, still around if I'm needed. :)06:26
*** lihkin has quit IRC06:29
*** annegentle has quit IRC06:29
*** bkopilov has joined #openstack-swift06:33
*** nshaikh has quit IRC06:41
honotmyname: sorry. i'm not allowed to say plans for swift usage at this time. i only found the info. http://www.businesscloudnews.com/2014/07/14/fujitsu-announces-2bn-cloud-offensive/06:43
notmynamelol, ok :-)06:44
notmynamethanks06:44
honotmyname: sorry for that.06:47
notmynameho: no, I understand. and "Fujitsu has committed $2bn to build a cloud on openstack and is contributing to swift" is enough of a good story for now :-)06:48
honotmyname: thanks!06:50
*** silor has joined #openstack-swift06:57
notmynameok, ideas and rough outline transferred from notes to presentation. still a ton of work to do on this talk, but I'm done for today07:02
notmynamegood night07:02
notmynamewell, actually...07:02
honotmyname: good night!07:03
notmynameho: I'm really glad that you and, by proxy, fujitsu, are contributing to swift. that's really cool.07:03
notmynameho: I fully understand not being able to share details, so I'm not worried by that at all07:03
*** zaitcev has quit IRC07:03
notmynamebut please let us know how we can help and what you are seeing in you experience07:03
notmynamebecause even if I've seen different stuff and someone else has a few different experiences, yours will be unique and the whole community is better when we can understand your use case too07:04
notmynameand also, it's just really cool and motivating to hear about and see how others are using swift. so don't be shy :-)07:05
notmynamethe positive good stories are just as important (and maybe more so) than the bugs07:05
notmyname...and now I'm going to bed :-)07:07
honotmyname: thanks a lot! and good night!07:07
*** bill_az has quit IRC07:13
*** ppai has quit IRC07:23
*** annegent_ has joined #openstack-swift07:25
*** annegent_ has quit IRC07:31
*** addnull has quit IRC07:31
honotmyname: i try to dump my experience (background of my thought) thanks for advice:)07:31
*** ppai has joined #openstack-swift07:35
*** k4n0 has joined #openstack-swift07:38
*** k4n0 has quit IRC07:42
*** addnull has joined #openstack-swift07:43
*** chlong has quit IRC07:47
*** nshaikh has joined #openstack-swift07:51
*** rledisez has joined #openstack-swift08:14
*** delattec has joined #openstack-swift08:21
*** geaaru has joined #openstack-swift08:22
*** cdelatte has quit IRC08:23
*** ppai has quit IRC08:25
*** annegentle has joined #openstack-swift08:25
*** annegentle has quit IRC08:30
*** silor has quit IRC08:33
*** ppai has joined #openstack-swift08:37
openstackgerritPrashanth Pai proposed openstack/swift: fsync() on directories  https://review.openstack.org/12692308:47
*** addnull has quit IRC09:06
*** jistr has joined #openstack-swift09:10
*** acoles_away is now known as acoles09:11
*** jordanP has joined #openstack-swift09:12
*** addnull has joined #openstack-swift09:14
*** addnull has quit IRC09:20
*** annegentle has joined #openstack-swift09:25
*** ahonda has quit IRC09:28
*** annegentle has quit IRC09:30
*** nellysmitt has joined #openstack-swift09:45
*** jordanP has quit IRC09:45
*** jordanP has joined #openstack-swift09:45
*** silor has joined #openstack-swift10:04
*** silor has quit IRC10:09
openstackgerritMerged openstack/swift: Add tests for unavailability of `tee` and `splice` in `libc`  https://review.openstack.org/14283610:19
*** silor has joined #openstack-swift10:24
*** annegent_ has joined #openstack-swift10:25
*** Masahiro has quit IRC10:27
*** annegent_ has quit IRC10:30
*** haomaiwang has quit IRC10:56
*** annegent_ has joined #openstack-swift11:25
*** NM has joined #openstack-swift11:30
*** annegent_ has quit IRC11:30
*** mahatic has joined #openstack-swift11:31
*** mahatic has quit IRC11:41
*** chlong has joined #openstack-swift11:43
*** mahatic has joined #openstack-swift12:03
hogood night!12:08
*** ho has quit IRC12:08
*** silor has quit IRC12:16
*** Masahiro has joined #openstack-swift12:16
*** Masahiro has quit IRC12:20
*** ppai has quit IRC12:22
*** lucasagomes has joined #openstack-swift12:23
*** sandywalsh has quit IRC12:24
*** km__ has quit IRC12:25
*** k_ has quit IRC12:25
*** kei_yama has quit IRC12:27
*** nosnos has quit IRC12:30
*** ppai has joined #openstack-swift12:33
EmilienMcschwede: why PUT does not support If-None-Match ?12:38
EmilienMcschwede: because it's not implemented or it's a limitation of HTTP ?12:39
*** silor has joined #openstack-swift12:42
cschwedeEmilienM: it’s not fully implemented yet, there were some difficulties with it: https://review.openstack.org/#/c/81646/12:55
*** silor has quit IRC12:57
EmilienMcschwede: so what is missing here?12:57
cschwedeEmilienM: the part in the proxy. i think one of the problems is the eventual consistency, making this a little bit unreliable. for example, if the primary nodes are down and there is an older copy on a fallback node13:09
EmilienMcschwede: fair enough - thanks13:11
*** addnull has joined #openstack-swift13:22
*** annegentle has joined #openstack-swift13:25
*** bill_az has joined #openstack-swift13:29
*** addnull has quit IRC13:36
*** tdasilva has joined #openstack-swift13:36
*** Masahiro has joined #openstack-swift14:05
*** NM has quit IRC14:07
*** Masahiro has quit IRC14:09
*** annegentle has quit IRC14:25
*** annegentle has joined #openstack-swift14:25
*** ppai has quit IRC14:32
*** nshaikh has quit IRC14:33
*** lihkin has joined #openstack-swift14:39
*** SkyRocknRoll has quit IRC14:41
*** miqui_ has joined #openstack-swift14:41
*** lcurtis has joined #openstack-swift14:53
*** SkyRocknRoll has joined #openstack-swift14:54
openstackgerritRomain LE DISEZ proposed openstack/swift: Support of the Linux socket option SO_REUSEPORT  https://review.openstack.org/13765914:55
*** NM has joined #openstack-swift15:06
*** lpabon has joined #openstack-swift15:14
*** annegent_ has joined #openstack-swift15:14
*** annegentle has quit IRC15:14
*** lihkin has quit IRC15:32
openstackgerritpaul luse proposed openstack/swift: New hashes.pkl format and other reconstructor changes  https://review.openstack.org/13187215:42
peluseclayg, ^ removes the 'reconstruct before send' deal... all on the fly now :)15:43
*** annegent_ has quit IRC15:44
*** annegentle has joined #openstack-swift15:45
*** elambert has joined #openstack-swift15:50
tdasilvapeluse: hi, I remember that before storage policies was finalized there was an idea to have 'types' defined in swift.conf, which was then removed. Is that being brought back with EC?15:53
*** Masahiro has joined #openstack-swift15:53
*** annegent_ has joined #openstack-swift15:55
*** Masahiro has quit IRC15:58
*** annegentle has quit IRC16:00
tdasilvapeluse: got it, it's already there in the feature/ec branch, cool!16:11
*** nshaikh has joined #openstack-swift16:16
*** lpabon_ has joined #openstack-swift16:20
*** chlong has quit IRC16:34
thurloatnotmyname: where is the best place to run the object-expirer daemon?16:34
thurloatseparate service, or with the proxy server?16:35
pelusetdasilva, sorry, stepped away for a minute but you got the answer right :)16:36
*** gyee has joined #openstack-swift16:39
lcurtisquestion for swift experts. Have decided to go with swift on zfs, where each 'dev' will be a zfs dataset/volume. Should I treat each zfs dev as a single disk even though it will be ~ 100T in determine my part power?16:41
*** nellysmitt has quit IRC16:44
*** dmsimard_away is now known as dmsimard16:45
*** lpabon_ has quit IRC16:51
*** reed has joined #openstack-swift16:55
*** EmilienM is now known as EmilienM|afk17:15
*** nshaikh has quit IRC17:18
ahale_I havent used zfs with swift lcurtis but have been thinking about it recently, I was tending towards lots of zpools each of single devices.. otherwise with any kind of raid it gets expensive or complicated by storage policy.. i think..17:28
notmynamegood morning17:28
openstackgerritRomain LE DISEZ proposed openstack/swift: Support of the Linux socket option SO_REUSEPORT  https://review.openstack.org/13765917:29
*** rledisez has quit IRC17:29
*** pberis has quit IRC17:30
*** pberis has joined #openstack-swift17:30
*** SkyRocknRoll has quit IRC17:34
lcurtisahale...interesting thought17:34
lcurtiswhy do you say it gets expensive17:34
notmynameraid rebuild (or zpool repairs) really kill performance17:35
lcurtisokay...understood17:36
lcurtisyeah that makes sense17:36
*** jistr has quit IRC17:43
*** Masahiro has joined #openstack-swift17:43
ahale_yeah that and as well if you're making a big raid volume you're using more disks for the same replicas, or drop replica count but then you lose some availability when stuffs down17:47
*** Masahiro has quit IRC17:48
ahale_we were discussing zfs for its "not xfs" features rather than any of the cool stuff17:48
notmynameahale_: xfs: the worst filesystem for swift except for all the others?17:49
ahale_:)17:49
notmynameahale_: have you played with running on object server per drive?17:50
*** fandi has quit IRC17:50
ahale_nope - thought about it a bit but its a lot of processes17:50
*** annegent_ has quit IRC17:51
ahale_daniele was playing with reproducing some of the nasty hangs we get when umounting horribly broken filesystems, we ended up in https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/fs/xfs/xfs_trans_ail.c?id=refs/tags/v3.18.1#n59217:53
swifterdarrellahale_: notmyname: seems like you can choose between A) blocking I/O syscalls interfering with eventlet's hub; or B) lots of OS threads or processes to at least isolate the stalls to requests depending on the same source of blocking (physical device)17:53
ahale_interestingly zfs was able to umount without sending everything uninteruptable17:54
ahale_yeah - what a choice :)17:54
lcurtison that note....if you made big volume and treated it as a drive, would swift therefore NOT place 2 replicas on same drive?17:54
notmynamelcurtis: ya, swift actually maps objects to a particular mount point. but we often say "drives" cause that's the strongly recommended way to do it in almost every situation17:55
notmynamelcurtis: but technically, it's "storage volume at a mount point"17:55
swifterdarrellahale_: notmyname: i haven't been able to put my money where my mouth is, but I think:   normal deployment << one-obj-server-per-disk << thread-pool-per-disk17:56
swifterdarrellahale_: notmyname: IOW, extra processes involved would still be better than the standard deployment17:56
lcurtisnotmyname: thank you17:57
swifterdarrellahale_: notmyname: I know the thread-pool-per-disk has overhead that doesn't really make it worthwhile :-/17:59
ahale_can't be sure, but I have a funny recollection we already looked at the thread pool and it didn't work out well or something ..17:59
swifterdarrellahale_: notmyname: wouldn't surprise me ;)18:00
notmynameahale_: probably not with you 90 drive servers ;-)18:00
ahale_yeah :)18:00
swifterdarrellahale_: notmyname: there, you get obj-serv-count * disk-count * threads-per-disk number of OS threads... to keep that sane, it drives down the other two factors with dense servers :(18:00
swifterdarrellahale_: notmyname: and even if you don't have >1k OS threads, the per-I/O-request overhead is higher going through Queues.18:01
*** jordanP has quit IRC18:01
*** geaaru has quit IRC18:01
*** fandi has joined #openstack-swift18:02
*** gyee has quit IRC18:08
*** elambert has quit IRC18:12
*** EmilienM|afk is now known as EmilienM18:14
*** elambert has joined #openstack-swift18:15
lcurtisas far as partition power goes...say if I do 2^18...that is 262144 partitions...then say 100 partitions per 'volume', would be enough for 2600 servers18:22
lcurtis?18:22
lcurtis261218:22
*** elambert has quit IRC18:24
*** acoles is now known as acoles_away18:26
*** elambert has joined #openstack-swift18:26
notmynamelcurtis: servers or drives?18:28
notmynamedrive count is what matters18:28
lcurtissorry...drives18:30
lcurtisaka the zfs conundrum18:30
mahaticnotmyname, good morning18:33
mahaticnotmyname, where do i find what replication server's allowed headers are?18:35
mahaticis there any code that says so?18:35
notmynamelcurtis: part power of 16 or 17 would be fine with 2600 drives18:35
lcurtisdo replicas play into the equation?18:36
notmynamemahatic: look in the __call__ method to see when HTTPMethodNotAllowed is returned18:36
lcurtisis it literally 2^x /100 / # drives18:36
notmynamelcurtis: ya. 2**<part power> * <replica count> / <drives>18:37
lcurtisokay...thanks so much...reading various docs and still struggling to understand it all18:37
*** lpabon has quit IRC18:39
mahaticnotmyname, ah okay, thanks!18:40
lcurtisor 2^16 * 3 replicas / 100 partitions = 1966 drives?18:42
notmynameya. but the point is to have the ability to spread out partitions so that a partition is a small percentage of the total drive space. so 100 partitions on a drive means each partition is about 1% of the space. part power of 16 with 2600 drives is about 75 parts per drive18:44
*** nellysmitt has joined #openstack-swift18:45
lcurtisokay..that makes sense18:46
notmynamelcurtis: the risk is that if you have a too high part power, especially if you have a smaller cluster (eg initially), you'll end up with 10k or more directories on a drive. and that's really bad for performance and efficient use of the space18:49
lcurtisyes exactly18:49
lcurtisi get that18:49
*** nellysmitt has quit IRC18:50
lcurtisbut for some reason i dont get if you have fewer partitions 'your data distribution will be more uneven than you want. You'll have to keep more free space on your disks in order to avoid their getting full.'18:50
*** elambert has quit IRC18:51
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873618:51
notmynamelcurtis: objects are placed based on the hash of their name18:55
notmynamewhich means that for a lot of objects and with a good hash function (which swift uses) you'll get roughly the same number of objects in each partition18:55
notmynameand the placement isn't to a drive. objects are mapped to a partition and the partitions are assigned to drives18:56
notmynamenote that the size of the object doesn't factor into the placement at all18:56
notmynameso if you are terribly unlucky, you could end up with all of your 2-byte objects mapping to the partitions assigned to drive A, but all of your 5GB objects mapping to the partitions assigned to drive B18:57
notmynamewhich would result in uneven filling18:57
notmynameof the drive space (ie as reported by df)18:57
notmynamenow, it's probably more likely that you'll win ever state's lottery every week for the rest of your life than that happening, but you know, technically it's possible18:58
ahale_i would love if you could double the total partition count18:58
notmynameahale_: yes, that would be nice18:58
notmynamelcurtis: so if you have a few number of partitions on a drive, it means that each partitions size (ie what's reported by du for that directory) is more impactful for the drive's fullness18:59
notmynameand if you have fewer partitions overall, they will be more uneven in capacity used, based on how homogenous the size objects in your clusters are19:00
notmynameso all that works out to: less partitions on a drive can make the relative drive fullness more uneven.19:01
lcurtissigh of relief...19:01
lcurtisyep...okay...got it19:01
notmynameit also works out to: swift is better the bigger it gets19:01
lcurtisyou seriously rock...have not had much sleep in trying to set this all up...lol..so having hard time grasping the why19:04
mahaticnotmyname, I'm not sure if you are following the mail thread (OPW meeting), but tomorrow 5pm UTC there is a meeting update scheduled. You can drop by if you are free/possible.19:06
mahaticin #openstack-opw19:07
notmynamemahatic: ah, no I hadn't seen that19:08
notmynamemahatic: I'm not sure if I'll make it. hard to say at this point. I'm flying out tomorrow night, so I'll be doing a lot of last minute prep tomorrow19:09
mahaticnotmyname, ah okay. linuxcon I believe? No problem19:09
notmynameya. LCA in new zealand19:10
mahaticokay no, linuxcon is at the end of the month. My bad19:10
mahaticoh okay. great19:10
*** elambert has joined #openstack-swift19:15
notmynameah. 5pm UTC19:16
mahaticyup19:17
*** elambert has quit IRC19:18
*** elambert has joined #openstack-swift19:19
lcurtisand min_part_hours can be changed?19:19
*** Masahiro has joined #openstack-swift19:31
torgomaticlcurtis: yes19:32
lcurtisthanks!19:33
lcurtisokay...pushing <enter>19:33
lcurtisor at least having one of my guys do the puppet run19:34
lcurtis;)19:34
*** Masahiro has quit IRC19:35
*** mahatic has quit IRC19:42
*** fandi has quit IRC20:13
*** zaitcev has joined #openstack-swift20:19
*** ChanServ sets mode: +v zaitcev20:19
*** fifieldt_ has quit IRC20:32
*** fifieldt_ has joined #openstack-swift20:33
*** nellysmitt has joined #openstack-swift20:46
*** nellysmitt has quit IRC20:51
openstackgerritClay Gerrard proposed openstack/swift: Add dispersion command to swift-ring-builder  https://review.openstack.org/14443220:52
*** david-lyle has joined #openstack-swift20:54
*** lpabon has joined #openstack-swift20:58
*** rdaly2 has joined #openstack-swift20:59
*** NM has quit IRC21:01
*** mariusv__ is now known as mariusv21:12
*** mariusv is now known as Guest3366521:13
*** Masahiro has joined #openstack-swift21:20
*** Masahiro has quit IRC21:25
mattoliverauMorning21:25
*** angelastreeter has joined #openstack-swift21:27
notmynamehi21:27
notmynamemattoliverau: any chance that AU and NZ currency are the same?21:28
* notmyname has some AU$ from the last trip...21:28
*** gyee has joined #openstack-swift21:28
mattoliveraunotmyname: nope, unfortunately not.. Its come up many times over the decades but NZ would never do it. You'll just have to come back to Oz at a later time ;)21:31
notmynameheh ok21:32
*** lpabon has quit IRC21:32
notmynamealso, why is Oz a nickname/abbreviation for Australia? I've always wondered that21:32
notmynameis it from aussie? shortened to oz?21:33
claygnotmyname: it's because it's so fucking weird and trippy down there21:33
claygnotmyname: you know they have the only mammels that lay eggs right?21:33
mattoliverauclay one lays eggs and has venom21:37
mattoliveraunotmyname: short of Aussie... We're just lazy, if we could shortening even more we would :p21:38
clayglol21:39
claygcschwede: idk, i keep trying to make set_overload take a % but I'm not really liking how it's turning out21:40
claygcschwede: but since the dispersion graph talks about dispersion as a % it seems like allowing the operator to set overload as a percent makes sense21:41
*** takotuesday has joined #openstack-swift22:05
takotuesdayhey guys, is anyone familiar with swiftclient api for python?22:05
notmynametakotuesday: ya, what's up?22:05
takotuesdaynotmyname: awesome, Im looking for some examples of usage. Im wanting to have my app save some generated files to a swift container22:07
notmynameok, cool. what have you tried so far?22:07
takotuesdayjust reading through the api22:07
claygfrom swiftclient.client import get_auth, put_object; token, url = get_auth(**creds); put_object(token, url, container_name, open_file_like_object_string_or_generator)22:08
clayghrmm... no there's probably a object_name param in there somewhere22:09
claygbut that's the general idea22:09
claygif you use a Connection object there's automatic retries and stuff22:09
claygoh, this isn't terrible -> http://docs.openstack.org/developer/python-swiftclient/swiftclient.html#module-swiftclient.client22:10
*** angelastreeter has quit IRC22:11
takotuesdayso im relatively new to python22:13
takotuesdayhere let me type up some code of what im thinking22:13
torgomatictakotuesday: in case you're new to IRC as well, let me advise you to use gist.github.com or pastebin.com or any other such thing instead of pasting multiline code in the channel22:14
claygtorgomatic: what are you saying?22:15
clayg:P22:15
* clayg is new to irc22:16
* torgomatic whistles innocently ;)22:16
*** EmilienM is now known as EmilienM|afk22:17
claygwhy is so hard to just calculate what overload would need to be to solve the ring?!22:18
takotuesdayhttp://paste.debian.net/hidden/711d8860/22:19
claygi hate math, computers are stupid22:19
takotuesdaythis is where im starting22:19
takotuesdaydoesnt make sense to store the swiftclient obj in a variable22:19
notmynametakotuesday: here's a small script I wrote recently using python-swiftclient https://github.com/notmyname/directory_uploader/blob/master/uploader.py22:20
takotuesdaynotmyname: thanks, that really helps22:22
openstackgerritClay Gerrard proposed openstack/swift: Add dispersion command to swift-ring-builder  https://review.openstack.org/14443222:23
*** lcurtis has quit IRC22:26
*** david-lyle has quit IRC22:28
*** delattec has quit IRC22:43
*** nellysmitt has joined #openstack-swift22:47
takotuesdaycan you send a path to put_object22:48
takotuesdayfor obj, or do you have to send individual files22:49
*** nellysmitt has quit IRC22:51
*** rdaly2 has quit IRC22:57
*** Masahiro has joined #openstack-swift23:09
*** Masahiro has quit IRC23:13
*** IRTermite has quit IRC23:15
*** tdasilva has quit IRC23:21
zaitcevhttps://review.openstack.org/145809 what madness is this23:22
zaitcev"The implementation is fairly straightforward with the exception of building the ring. I've followed an upstream TripleO model here where we build the actual ring on each node (rather than build once and rsync). This works because Heat will always know all the devices ahead of time."23:22
zaitcevwell, as long as it works23:22
torgomaticas long as they set the same random seed on each node, it'll be okay23:23
torgomaticif they've forgotten that, then hilarity will ensue23:24
mattoliverautakotuesday: looking at the code, you pass it a file like object or the contents of the file.23:27
*** takotuesday has quit IRC23:31
openstackgerritClay Gerrard proposed openstack/swift: Add some input options for set_overload  https://review.openstack.org/14597023:34
*** erlon_ has quit IRC23:40
notmynamezaitcev: I see you left a comment. I just did too23:41
zaitcevnotmyname: thanks23:41
notmynamezaitcev: thanks for bringing it up23:41
zaitcevI'm not convinced it's ideal, out of the general principle where automation is doing something different from what we expect an administrator to do. But I do not have a reasoned objection.23:42
zaitcev notmyname: I appropriated your explanation yesterday here - http://zaitcev.livejournal.com/226242.html - and wasn't sure what to use as your Internet URL identity, so I used Swiftstack's blog23:43
notmynamePiston was the one who first wanted that feature. they were wanting to build rings concurrently on their different servers. (....then they stopped using swift altogether.....but that's a different story)23:44
zaitcevsad_panda.png23:44
notmynamezaitcev: ah you used some author id I have with openstack.org. If you can change it, I'd prefer http://not.mn23:45
zaitcevexcellent, thank you23:45
*** dmsimard is now known as dmsimard_away23:50
zaitcevhttp://programmerthoughts.com/programming/deleted-file-recovery/ - oh good lord, this reminded me about our yesterday conversation23:52
zaitcevWhy is it that we want to move those to special containers. Can't we simply write .ts, but do not unlink and let auditor do it with a special API call at a configurable interval?23:53
zaitcevSeems like almost zero effort, except the actual undelete that requires work. But it should be bug-free.23:54

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