Friday, 2015-12-11

hogood morning!00:00
*** esker has quit IRC00:00
*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-swift00:01
mattoliveraunotmyname: lol00:01
mattoliveraunotmyname: at least you tried00:01
*** ianbrown__ has quit IRC00:10
*** ianbrown_ has joined #openstack-swift00:10
*** ianbrown_ has quit IRC00:16
*** ianbrown_ has joined #openstack-swift00:17
*** Jeffrey4l has quit IRC00:17
*** dmorita has quit IRC00:19
*** dmorita has joined #openstack-swift00:20
*** ianbrown_ has quit IRC00:21
*** ianbrown_ has joined #openstack-swift00:22
*** dslevin has joined #openstack-swift00:23
*** dmorita_ has joined #openstack-swift00:23
*** dmorita has quit IRC00:24
*** dslevin has quit IRC00:27
*** Guest35433 has quit IRC00:29
*** km has joined #openstack-swift00:29
*** km is now known as Guest601900:29
*** pgbridge has quit IRC00:38
*** thumpba has joined #openstack-swift00:45
*** thumpba has quit IRC00:45
openstackgerritHisashi Osanai proposed openstack/swift: Add X-Delete-After and X-Delete-At functional test  https://review.openstack.org/25562600:47
*** chlong has joined #openstack-swift00:52
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
*** dslevin has joined #openstack-swift01:17
*** dslevin has quit IRC01:21
*** ianbrown_ has quit IRC01:32
*** ianbrown_ has joined #openstack-swift01:32
*** david-lyle has joined #openstack-swift01:37
*** dmorita_ has quit IRC01:38
*** dmorita has joined #openstack-swift01:40
*** zhill has quit IRC01:41
*** janonymous_ has quit IRC01:58
*** noark9 has joined #openstack-swift02:00
*** haomaiwang has quit IRC02:01
*** haomaiwang has joined #openstack-swift02:01
*** jamielennox is now known as jamielennox|away02:01
*** ianbrown_ is now known as ianbrown02:05
*** Jeffrey4l has joined #openstack-swift02:07
*** lyrrad has quit IRC02:08
*** ianbrown has quit IRC02:15
*** ianbrown has joined #openstack-swift02:15
*** petertr7_away is now known as petertr702:17
*** dmorita has quit IRC02:23
*** dmorita has joined #openstack-swift02:26
*** jamielennox|away is now known as jamielennox02:29
*** dewsday has quit IRC02:57
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** sanchitmalhotra has joined #openstack-swift03:03
*** bill_az has joined #openstack-swift03:12
openstackgerritMerged openstack/swift: Unification of manpages and conf-samples (default values, etc)  https://review.openstack.org/25139603:20
openstackgerrithgangwx@cn.ibm.com proposed openstack/swift: Fix some inconsistency in docstrings  https://review.openstack.org/25619703:38
*** links has joined #openstack-swift03:42
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
*** trifon has joined #openstack-swift04:01
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620104:04
*** trifon has quit IRC04:07
*** trifon has joined #openstack-swift04:10
mahaticnotmyname: hi. Is it worth updating that, after DELETE, the older version is gone from versions container and back in the actual container, indicating with a curl command? Here: http://docs.openstack.org/developer/swift/overview_object_versioning.html#examples-using-curl04:13
mahaticit just says the older version is gone, and I wondered why until I checked that it is back in the (original) container after a DELETE04:14
*** trifon has quit IRC04:15
*** trifon has joined #openstack-swift04:25
*** yatin has joined #openstack-swift04:28
yatinHello Folks04:29
yatinI'm new to swift, read swift docs, got one query04:29
yatinafter the ring datastructure decides which drive to find the object on..how does it go further from there?04:30
*** ppai has joined #openstack-swift04:34
*** garthb has quit IRC04:34
*** esker has joined #openstack-swift04:41
*** proteusguy_ has quit IRC04:45
*** trifon has quit IRC04:46
*** sgundur has left #openstack-swift04:47
*** proteusguy_ has joined #openstack-swift04:58
*** haomaiwang has quit IRC05:01
*** haomaiwang has joined #openstack-swift05:01
*** esker has joined #openstack-swift05:02
*** dmorita has quit IRC05:03
*** dmorita has joined #openstack-swift05:07
*** esker has quit IRC05:08
notmynamemahatic: yeah, it could be more specific05:13
notmynameyatin: still here? still wondering about how swift works? :-)05:14
yatinnotmyname: yes.. having some in between gaps05:14
mahaticnotmyname: okay, thanks. will update05:14
notmynamemahatic: cool. thanks05:14
notmynameyatin: where are you at now?05:14
*** ig0r__ has joined #openstack-swift05:15
notmyname(in your understanding)05:15
yatinnotmyname: so, two datastructures , device dict, and replica2devpart05:16
yatinnotmyname: the arrays of arrays stores device-ids05:16
yatinnotmyname: this device id is key into devices dict, where it gets ip and drive name05:17
notmynamering05:17
yatinnotmyname: so, after that what happens?05:17
notmynameerr...right05:17
notmynameok, so you've gotten really deep into the ring sturcture05:17
notmyname*structure05:17
notmynamethat's great05:18
yatinnotmyname: not feeling that great yet, my understanding has landed me into service with specific drive, how to locate object?05:18
notmynamebasically, all that is called from the ring class's get_nodes() and get_more_nodes()05:19
notmynameheh05:19
yatinnotmyname: *server05:19
*** ig0r_ has quit IRC05:19
notmynameok, backing up a little more05:19
yatinnotmyname: ok. please05:19
notmynamegiven a path to something in swift, eg /account/container/object, that info (the account, container, and object parts) are passed to the ring05:20
notmynamethe ring hashes those parts (along with some salts) and gets a hash value05:20
yatinnotmyname: right05:20
*** klrmn has quit IRC05:20
notmynamesome number of prefix bits of the resulting hash are used as the "partion"05:20
notmynamethe number of bits is the part power number. or actually 2**part_power05:21
yatinnotmyname: yes.. md5 bits - part_power.. some formula there05:21
notmynameso essentially, part = hasher(path_parts) << 2**part_power05:21
yatinnotmyname: to get hash05:21
notmynamering05:21
*** ig0r__ has quit IRC05:21
notmynameright05:22
notmynamesorry. muscle memory on my fingers ;-)05:22
notmynameok, so you get a partition05:22
notmynamepartitons are mapped to devices in the cluster05:22
yatinnotmyname: :) yes05:22
notmynameso given a partition, you can find where that *should* be stored in the cluster05:23
notmynameand that mapping is The Ring (tm)05:23
yatinnotmyname: correct05:23
notmynamewith the various data structures you mentioned05:23
notmynameok05:23
yatinnotmyname: 2D array of [replica][partions]05:23
notmynameso the 2 key parts of the ring data structure are the mapping from partition to device (dev_id) and the mapping of device ids05:24
*** esker has joined #openstack-swift05:24
*** venkatesh has joined #openstack-swift05:24
notmynamea device is identified by (IP, port, mount point)05:24
yatinnotmyname: true05:25
notmynameso eg if you hash /a/c/cat.jpg, and you get partition 42, partion 42 might be mapped to devices 3, 5, and 705:25
notmynameand device 3 is identified as 10.0.1.34:6001/sdf105:25
notmynameIP:port/mount05:26
notmynameand that's what's returned to the proxy when it calls the ring with a given URL (or the URL parts)05:26
notmynameso therefore the proxy connects to the given IP:port and sends the mountpoint and the URL and the object server translates that to the on-disk filename05:27
notmynameand, ta-da, you can read and write your objects05:27
yatinnotmyname: so, so proxy-server sends ip:port/mount and object name too?05:28
yatinnotmyname: because on sdf1, here may be many more objects?05:28
notmynameright05:28
notmynamein fact, many partitions will be assigned to whatever device is mounted ad sdf105:28
yatinnotmyname: and could be from different containers too,05:29
notmynameabsolutely05:29
yatinnotmyname: two contrainer can have same objects name05:29
notmynameright05:29
notmynameand 2 different accounts can have the same contaienr name (with objects of the same name too)05:29
yatinnotmyname: worst case, could go on same sdf1,05:30
*** esker has quit IRC05:30
notmynameno, that's ok. since the on-disk filename has to do with the hash of "account + contaienr + object"05:30
yatinnotmyname: ook...now, its clear05:31
yatinnotmyname: thanks a ton05:31
venkateshHi all,05:31
notmynamewhile not *exactly* related to your question, this is a link to a talk I gave a few years ago about how swift deals with failures. it shows some of the on-disk files and how that works. https://www.youtube.com/watch?v=_sUvfGKhaMo05:31
venkateshis proxy-server sends account HEAD/GET/POST request to every account-server?05:32
yatinnotmyname: great! thanks for the url05:32
notmynameit might provides some additional details for you05:32
*** Trixboxer has quit IRC05:33
yatinnotmyname: this would really help further to gain deeper understanding. :)05:33
notmynameyatin: happy to help.05:33
notmynameyatin: it's getting late in my timezone, and I'm stepping away now, but please feel free to ask more questions. there's other pople online now, and I'll definitely be back on later05:34
venkateshHi all05:34
venkateshCan someone tell05:35
venkateshis proxy-server sends account HEAD/GET/POST request to every account-server?05:35
*** SkyRocknRoll has joined #openstack-swift05:36
*** petertr7 is now known as petertr7_away05:36
yatinnotmyname: thanks. good night05:38
*** Trixboxer has joined #openstack-swift05:42
*** esker has joined #openstack-swift05:46
notmynamevenkatesh: if by "every" you mean all servers in the cluster, it depends on how big your cluster is. but assuming you have a large cluster with many servers, no, requests are not sent to every server05:51
*** esker has quit IRC05:52
venkateshnotmyname: In saio setup, it goes to every server right?05:53
venkatesh*account05:54
notmynamethe saio simulates 4 servers. if you have a 3 replica policy and you haven't failed any of the servers, then it will only go to the 3 servers that are handling the request05:54
notmynamefor a write (eg PUT/POST)05:54
*** bill_az has quit IRC05:55
notmynamefor a read (GET/HEAD), it will only go to one05:55
venkateshnotmyname: I assumed every server handles separate replica, is that correct05:57
notmynameyes05:57
*** dmorita has quit IRC05:57
venkatesh4 servers, 3 replicas are possible?05:58
venkateshHow the account-db new entries are replicated across multiple account-servers?05:59
venkateshfrom the code I understood as make_requests, which sends request to every account-server06:00
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-swift06:01
*** Trixboxer has quit IRC06:01
notmynamevenkatesh: you should talk to yatin, who was just going through this too :-)06:01
venkateshOk, Thanks for your help06:02
venkateshyatin:06:02
venkateshHi06:02
*** trifon has joined #openstack-swift06:03
yatinvenkatesh: Hi06:05
venkatesh 4 accountservers, 3 replicas are possible?06:07
yatinvenkatesh: yes06:07
venkateshyatin : can I repost the above 2 questions?06:07
yatinvenkatesh: accountservers has nothing to do with replicas06:08
venkateshaccount-server mainatins separate db's right?06:08
yatinvenkatesh: i did read your question, as i'm new to swift, don't know what's the exact answer06:08
yatinvenkatesh: but you can check api guide06:08
yatinvenkatesh: yes..06:09
*** Trixboxer has joined #openstack-swift06:09
yatinvenkatesh: swift calls it metadata, use to get container list06:09
venkateshhere replica means I am saying account-db replica06:10
yatinvenkatesh: it;s not replica, it has to distribute account ring to all servers which having accont-server running06:10
yatinvenkatesh: use word replica for objects06:11
venkateshOk,06:11
yatinvenkatesh: do you have setup, if not get swift AIO to begin with..06:11
venkateshI installed SAIO and  devstack and separate VM's06:12
venkateshI went through the swift code06:12
yatinvenkatesh: nice06:12
venkateshI will ask my exact doubt w.r.t code06:12
yatinvenkatesh: I yet to go through code...i'm just new here...but you can shoot question06:13
yatinvenkatesh: i will try06:13
venkateshhttps://github.com/openstack/swift/blob/master/swift/proxy/controllers/account.py#L12706:13
venkateshthis is sending the request to every account-server right?06:13
*** chlong has quit IRC06:15
*** bill_az has joined #openstack-swift06:16
* yatin checking code06:16
venkateshOk06:17
yatinvenkatesh: yes.. you are right06:20
venkateshOk, thanks06:20
*** ChubYann has quit IRC06:21
yatinvenkatesh: it gets unique devices, via using seen_ids06:22
yatinvenkatesh: def _get_part_nodes() in ring.py06:23
*** ppai is now known as ppai|afk06:30
venkateshOk, Thanks, I will check06:31
*** esker has joined #openstack-swift06:31
*** jamielennox is now known as jamielennox|away06:33
*** bill_az has quit IRC06:36
*** esker has quit IRC06:36
*** gyee has quit IRC06:38
*** bill_az has joined #openstack-swift06:43
*** silor has joined #openstack-swift06:53
openstackgerritMahati Chamarthy proposed openstack/swift: Update versioned_writes doc  https://review.openstack.org/25625006:57
*** bill_az has quit IRC06:59
*** silor has quit IRC07:00
*** haomaiwang has quit IRC07:01
*** silor has joined #openstack-swift07:01
*** haomaiwa_ has joined #openstack-swift07:01
*** silor1 has joined #openstack-swift07:03
*** silor has quit IRC07:05
*** silor1 is now known as silor07:05
*** bill_az has joined #openstack-swift07:07
*** zhill has joined #openstack-swift07:07
*** SkyRocknRoll has quit IRC07:16
*** zaitcev has quit IRC07:22
*** takashi has joined #openstack-swift07:27
*** ig0r_ has joined #openstack-swift07:32
*** bill_az has quit IRC07:52
*** takashi has quit IRC07:57
*** haomaiwa_ has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** ppai|afk is now known as ppai08:04
*** arnox has joined #openstack-swift08:05
*** rledisez has joined #openstack-swift08:08
*** ig0r_ has quit IRC08:11
kota_takashi?08:12
*** arnox has quit IRC08:15
*** esker has joined #openstack-swift08:18
*** ig0r_ has joined #openstack-swift08:19
*** SkyRocknRoll has joined #openstack-swift08:20
*** esker has quit IRC08:23
*** arnox has joined #openstack-swift08:35
*** arnox has quit IRC08:40
*** esker has joined #openstack-swift08:40
*** arnox has joined #openstack-swift08:43
*** rcernin has joined #openstack-swift08:44
*** esker has quit IRC08:46
*** ig0r_ has quit IRC08:53
openstackgerritPeter Lisák proposed openstack/swift: Unification of manpages and swift-* --help  https://review.openstack.org/25139708:59
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
openstackgerritPeter Lisák proposed openstack/swift: Change schedule priority of daemon/server in config  https://review.openstack.org/23879909:14
*** acoles_ is now known as acoles09:19
*** ig0r_ has joined #openstack-swift09:19
*** Zyric1 has quit IRC09:24
mahatickota_: hi, would you happen to know if I should be updating something else for this patch (256250)? the rst picks up from doc string - I remember you mentioning about  sphinx build last time on a doc patch09:32
*** zhill has quit IRC09:32
openstackgerritHisashi Osanai proposed openstack/swift: Fix ClientException handling in Container Sync  https://review.openstack.org/25630609:37
*** jordanP has joined #openstack-swift09:38
*** aix has joined #openstack-swift09:42
*** ig0r_ has quit IRC09:47
acoleseranrom: re. your question on patch 205803, see http://www.ktcdigital.com/2012/07/whats-up-with-all-the-symbols/ :)09:54
patchbotacoles: https://review.openstack.org/#/c/205803/ - Container-Sync to iterate only over synced containers09:54
*** jistr has joined #openstack-swift09:55
tdasilvagood morning09:59
*** haomaiwang has quit IRC10:01
mahaticmorning already?10:01
*** haomaiwang has joined #openstack-swift10:01
acolestdasilva: good morning. you're up early!10:01
tdasilvaacoles: 8am here ;)10:02
tdasilvaacoles: i'm in Brasil10:03
mahaticoh well, morning!10:03
mahatic:)10:03
acolestdasilva: now i'm confused. Brasil is only UTC-2 ?10:03
janonymoustdasilva: o/10:04
acolesi thought it was UTC-410:04
tdasilvayeah..BRST is UTC-2. (Brasilia Summer Time)10:04
tdasilvaBRT is UTC-310:05
acolestdasilva: oh yeah its summer there :)10:05
tdasilvaacoles: yes!!! :-)10:05
kota_mahatic: i think you need just recheck. Other patches also got similar issue,10:06
tdasilvawow, even kota_ is still around!! I like this time10:06
mahatickota_: yeah, thanks. I just noticed some email about gate failure10:06
kota_tdasilva: yeah10:07
kota_tdasilva : yeah but unfortunately i'm heading for a pub today :P10:08
tdasilvakota_: nice! no worries, enjoy the pub, it's friday night!10:09
kota_                Usually i'm on this time10:09
tdasilvajanonymous: o/ hello10:09
*** esker has joined #openstack-swift10:27
*** esker has quit IRC10:32
*** hseipp has joined #openstack-swift10:33
*** aix has quit IRC10:36
*** ho has quit IRC10:42
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620110:43
* mahatic is ooo until wednesday10:44
*** Jeffrey4l has quit IRC10:45
*** esker has joined #openstack-swift10:48
tdasilvamahatic: enjoy!10:50
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925010:51
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873610:51
mahatictdasilva: thanks! you too in brasil10:51
tdasilvamahatic: thx :)10:52
tdasilvamahatic: btw, your changes to the obj. versioning doc look good10:53
*** esker has quit IRC10:54
mahatictdasilva: ok, apparently the gate is fixed and i left a recheck10:56
mahaticand added you a reviewer too10:56
tdasilvamahatic: ok, cool10:56
*** SkyRocknRoll has quit IRC10:58
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620111:00
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:01
*** ppai has quit IRC11:02
openstackgerritMerged openstack/swift: fix mock and assert in test_direct_client  https://review.openstack.org/25434111:05
openstackgerritTakashi Kajinami proposed openstack/swift: Fix proxy-server's support for chunked transferring in GET object  https://review.openstack.org/25620111:06
*** ig0r_ has joined #openstack-swift11:08
*** esker has joined #openstack-swift11:11
*** aix has joined #openstack-swift11:12
*** esker has quit IRC11:17
*** noark9 has quit IRC11:19
*** manous has joined #openstack-swift11:22
*** chlong has joined #openstack-swift11:32
*** jmccarthy has quit IRC11:34
*** jmccarthy has joined #openstack-swift11:34
*** sanchitmalhotra has quit IRC11:34
*** ig0r_ has quit IRC11:46
*** Guest6019 has quit IRC11:51
*** yatin has quit IRC11:57
*** kei_yama has quit IRC11:58
*** haomaiwang has quit IRC12:01
*** haomaiwang has joined #openstack-swift12:01
*** SkyRocknRoll has joined #openstack-swift12:04
*** changbl has quit IRC12:04
openstackgerritStuart McLaren proposed openstack/python-swiftclient: Retry download of object body  https://review.openstack.org/15920812:07
*** ig0r_ has joined #openstack-swift12:14
*** rcernin has quit IRC12:18
*** links has quit IRC12:19
*** ig0r_ has quit IRC12:24
*** janonymous_ has joined #openstack-swift12:27
*** janonymous_ has quit IRC12:28
*** janonymous_ has joined #openstack-swift12:28
*** [1]eranrom has joined #openstack-swift12:29
*** eranrom has quit IRC12:29
*** [1]eranrom is now known as eranrom12:29
*** petertr7_away is now known as petertr712:30
janonymous_kota_ : hey, u around?12:30
*** petertr7 is now known as petertr7_away12:39
*** cdelatte has joined #openstack-swift12:49
*** esker has joined #openstack-swift12:59
*** dslevin has joined #openstack-swift13:00
*** haomaiwang has quit IRC13:01
*** haomaiwang has joined #openstack-swift13:01
*** esker has quit IRC13:03
*** jistr is now known as jistr|biab13:10
*** ig0r_ has joined #openstack-swift13:16
*** esker has joined #openstack-swift13:19
*** ig0r_ has quit IRC13:25
*** esker has quit IRC13:26
*** venkatesh has quit IRC13:36
*** haomaiwang has quit IRC13:41
*** haomaiw__ has joined #openstack-swift13:41
*** esker has joined #openstack-swift13:44
*** janonymous_ has quit IRC13:44
*** esker has quit IRC13:48
*** haomaiw__ has quit IRC13:52
*** esker has joined #openstack-swift14:04
*** jistr|biab is now known as jistr14:09
*** esker has quit IRC14:09
*** haomaiwang has joined #openstack-swift14:10
*** CaioBrentano has joined #openstack-swift14:10
*** haomaiwang has quit IRC14:11
*** haomaiwa_ has joined #openstack-swift14:11
*** haomaiwa_ has quit IRC14:12
*** acoles is now known as acoles_14:12
*** 18WABFL3O has joined #openstack-swift14:12
*** 18WABFL3O has quit IRC14:13
*** haomaiwang has joined #openstack-swift14:13
*** haomaiwang has quit IRC14:14
*** haomaiwa_ has joined #openstack-swift14:14
*** haomaiwa_ has quit IRC14:15
*** haomaiwang has joined #openstack-swift14:15
*** haomaiwang has quit IRC14:16
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873614:16
*** haomaiwang has joined #openstack-swift14:16
*** changbl has joined #openstack-swift14:16
*** haomaiwang has quit IRC14:17
*** haomaiwang has joined #openstack-swift14:17
*** haomaiwang has quit IRC14:18
*** haomaiwang has joined #openstack-swift14:18
*** janonymous_ has joined #openstack-swift14:18
*** haomaiwang has quit IRC14:19
*** haomaiwang has joined #openstack-swift14:19
*** breitz has quit IRC14:19
*** breitz has joined #openstack-swift14:19
*** haomaiwang has quit IRC14:20
*** haomaiwang has joined #openstack-swift14:20
wbhubergood morning, my fellow swifters!14:20
*** haomaiwang has quit IRC14:21
janonymous_hey wbhuber14:21
wbhuberjust wanted to let you know jrichli did really awesome last night at the openstack meetup presenting on swift encryption: http://www.meetup.com/OpenStack-Austin/events/226421866/14:21
*** haomaiwa_ has joined #openstack-swift14:21
wbhubera lot of good questions being asked and she articulated at each one....14:21
*** haomaiwa_ has quit IRC14:22
*** 17WAA8LUI has joined #openstack-swift14:22
tdasilvawbhuber, jrichli: awesome, great job!14:22
wbhuberdo any of you guys know the purpose of swift_bytes in this string: 'content_type': 'application/json;swift_bytes=25'14:22
*** 17WAA8LUI has quit IRC14:23
tdasilvagot slides to share?14:23
wbhuberit's failling some of SLO unit test that i'm rewriting14:23
wbhuberwill ask jrichli to share when she gets on line14:23
*** haomaiwa_ has joined #openstack-swift14:23
*** haomaiwa_ has quit IRC14:24
*** 17WAA8LWI has joined #openstack-swift14:24
*** 17WAA8LWI has quit IRC14:25
*** 17WAA8LXI has joined #openstack-swift14:25
*** 17WAA8LXI has quit IRC14:26
*** haomaiwang has joined #openstack-swift14:26
*** haomaiwang has quit IRC14:27
*** haomaiwang has joined #openstack-swift14:27
*** haomaiwang has quit IRC14:28
*** haomaiwa_ has joined #openstack-swift14:28
*** haomaiwa_ has quit IRC14:29
*** haomaiwa_ has joined #openstack-swift14:29
*** haomaiwa_ has quit IRC14:30
*** haomaiwa_ has joined #openstack-swift14:30
*** haomaiwa_ has quit IRC14:31
*** haomaiwa_ has joined #openstack-swift14:31
*** haomaiwa_ has quit IRC14:32
*** haomaiwa_ has joined #openstack-swift14:32
*** haomaiwa_ has quit IRC14:33
*** haomaiwa_ has joined #openstack-swift14:33
*** haomaiwa_ has quit IRC14:34
*** haomaiwang has joined #openstack-swift14:34
*** haomaiwang has quit IRC14:35
*** haomaiwang has joined #openstack-swift14:35
*** haomaiwang has quit IRC14:36
*** haomaiwang has joined #openstack-swift14:36
*** haomaiwang has quit IRC14:37
*** 17WAA8MB6 has joined #openstack-swift14:37
*** 17WAA8MB6 has quit IRC14:38
*** haomaiwa_ has joined #openstack-swift14:38
*** haomaiwa_ has quit IRC14:39
*** 18WABFM0S has joined #openstack-swift14:39
*** 18WABFM0S has quit IRC14:40
*** haomaiwang has joined #openstack-swift14:40
*** haomaiwang has quit IRC14:41
*** ig0r_ has joined #openstack-swift14:41
*** haomaiwang has joined #openstack-swift14:41
*** haomaiwang has quit IRC14:42
*** haomaiwa_ has joined #openstack-swift14:42
*** haomaiwa_ has quit IRC14:43
*** haomaiwang has joined #openstack-swift14:43
*** ig0r_ has quit IRC14:43
*** haomaiwang has quit IRC14:44
*** haomaiwa_ has joined #openstack-swift14:44
*** haomaiwa_ has quit IRC14:45
*** 7F1AA7M98 has joined #openstack-swift14:45
*** 7F1AA7M98 has quit IRC14:46
*** 17WAA8MLS has joined #openstack-swift14:46
*** 17WAA8MLS has quit IRC14:47
*** haomaiwang has joined #openstack-swift14:47
*** diogogmt has quit IRC14:47
*** haomaiwang has quit IRC14:48
*** Jeffrey4l has joined #openstack-swift14:48
*** haomaiwang has joined #openstack-swift14:48
*** haomaiwang has quit IRC14:49
*** 17WAA8MN8 has joined #openstack-swift14:49
*** 17WAA8MN8 has quit IRC14:50
*** haomaiwa_ has joined #openstack-swift14:50
*** diogogmt has joined #openstack-swift14:51
*** haomaiwa_ has quit IRC14:51
*** blmartin has joined #openstack-swift14:51
*** haomaiwa_ has joined #openstack-swift14:51
*** haomaiwa_ has quit IRC14:52
*** haomaiwang has joined #openstack-swift14:52
*** haomaiwang has quit IRC14:53
*** haomaiwang has joined #openstack-swift14:53
*** haomaiwang has quit IRC14:54
*** haomaiwa_ has joined #openstack-swift14:54
*** haomaiwa_ has quit IRC14:55
*** haomaiwa_ has joined #openstack-swift14:55
*** haomaiwa_ has quit IRC14:56
*** haomaiwa_ has joined #openstack-swift14:56
*** haomaiwa_ has quit IRC14:57
*** haomaiwa_ has joined #openstack-swift14:57
*** ig0r_ has joined #openstack-swift15:01
*** haomaiwa_ has quit IRC15:04
*** haomaiwang has joined #openstack-swift15:04
*** ig0r_ has quit IRC15:06
*** sgundur has joined #openstack-swift15:06
*** esker has joined #openstack-swift15:07
*** diogogmt has quit IRC15:09
*** links has joined #openstack-swift15:11
*** diogogmt has joined #openstack-swift15:12
*** diogogmt has quit IRC15:13
*** tongli has joined #openstack-swift15:25
*** SkyRocknRoll has quit IRC15:30
*** tsg has joined #openstack-swift15:33
*** daddyjoseph97 has joined #openstack-swift15:33
*** diazjf has joined #openstack-swift15:36
*** pgbridge has joined #openstack-swift15:40
jrichligood morning.  wbhuber, tdasilva, thanks!  I will provide a link to the slides in a moment - they are really high level, though.  And not much without the spoken words.15:44
jrichliwbhuber: my understanding is that swift_bytes is used internally only for the container listing so that the total size of the large object is shown.15:44
jrichlialso, I am *technically* on vacation today.  but will be popping in occasionally15:45
*** lpabon has joined #openstack-swift15:46
*** diazjf has quit IRC15:48
jrichlimy presentation is here https://drive.google.com/file/d/0B-zpM_BFwU5ATWMxWXZWUzVJMkU/view?usp=sharing15:49
jrichliThe highlight was that at the end, somebody talked to me about how they want to start contributing to swift and asked for some advice :-)15:50
*** david-ly_ has joined #openstack-swift15:50
tdasilvajrichli: great slides15:53
*** david-lyle has quit IRC15:53
*** david-ly_ is now known as david-lyle15:53
jrichlitdasilva: thanks15:55
*** janonymous has quit IRC15:56
*** sgundur has quit IRC15:57
janonymous_nice slides15:57
jrichlijanonymous_: thanks15:59
*** diazjf has joined #openstack-swift16:01
*** changbl has quit IRC16:03
wbhuberjrichi: thumbs up! :)16:09
*** links has quit IRC16:09
jrichliwbhuber: he he, like the monkey16:11
wbhuberyes, fonze the monkey :)16:11
janonymous_Haha, yes i was thinking of what the monkey in last slide means :P16:12
jrichlithe last slide wasn't shown - Resources slide was really last16:12
*** diogogmt has joined #openstack-swift16:13
jrichlithe first slide is where I introduced "The Fonze" and a little story16:13
janonymous_Hahaa, cool :)16:14
*** changbl has joined #openstack-swift16:16
*** ig0r_ has joined #openstack-swift16:21
*** jlvillal has quit IRC16:22
*** jlvillal has joined #openstack-swift16:22
*** jlvillal has quit IRC16:24
*** lpabon has quit IRC16:24
*** hseipp has quit IRC16:24
*** jlvillal has joined #openstack-swift16:28
*** jlvillal has quit IRC16:30
*** jlvillal has joined #openstack-swift16:31
*** haomaiwang has quit IRC16:34
*** sgundur has joined #openstack-swift16:37
*** acoles_ is now known as acoles16:42
*** mfalatic has joined #openstack-swift16:42
*** mfalatic has quit IRC16:45
*** jordanP has quit IRC16:46
*** jordanP has joined #openstack-swift16:47
*** ig0r_ has quit IRC16:47
acolesjrichli: nice!16:48
jrichliacoles: thanks16:49
*** diazjf has quit IRC16:52
openstackgerritBill Huber proposed openstack/swift: SLO multipart-manfest=get call returns json in inconsistent format  https://review.openstack.org/25658016:52
*** dslevin has quit IRC16:52
wbhubertdasilva: timburke: ^^ feel free to make recommendation/feedback.16:53
*** dslevin has joined #openstack-swift16:56
*** garthb has joined #openstack-swift16:57
*** esker has quit IRC17:01
*** rledisez has quit IRC17:05
*** klrmn has joined #openstack-swift17:07
*** diazjf has joined #openstack-swift17:07
*** diazjf has quit IRC17:08
*** thumpba has joined #openstack-swift17:08
*** manous has quit IRC17:10
*** lyrrad has joined #openstack-swift17:11
*** gyee has joined #openstack-swift17:16
*** klrmn has quit IRC17:17
*** ianbrown has quit IRC17:19
*** ianbrown has joined #openstack-swift17:20
hroujrichli, that's really awesome !  What was the audience like ?  New'ish to swift / wanting to get involved (dev or ops side).17:21
jrichlihrou: thanks.  It is hard for me to say.  I only talked to a few of them.  I was advised that the general meetup audience would most likely be new to swift.  A couple security folks were there.17:23
jrichliBecause there was a "dojo" this week at IBM, a few people who work with Monty Taylor under Angel Diaz were there.  That was unexpected for me :-)17:23
openstackgerritOndřej Nový proposed openstack/swift: Removed deprecated tox -downloadcache option  https://review.openstack.org/25659717:24
hroujrichli, Ah Angel and Monty, nice :)   That's really great, is it like an openstack meetup with different people presenting about the various projects?17:25
jrichlihrou: well, Angel and Monty were not there :-) just people who work in their team17:25
hroujrichli, There loss, they should have attended ; )17:25
*** dmorita has joined #openstack-swift17:26
jrichlihrou:  I don't have a lot of experience with meetups, but I take it that the openstack meetups are pretty wide-ranged in topic.  As long as its under the openstack umbrella.17:27
*** dmorita has quit IRC17:27
hroujrichli, yea I just looked it up, interesting, they have them throughout !17:27
*** dmorita has joined #openstack-swift17:28
*** trifon has quit IRC17:30
*** esker has joined #openstack-swift17:36
*** esker has joined #openstack-swift17:36
*** daddyjoseph97 has quit IRC17:38
*** arnox has quit IRC17:44
*** daddyjoseph97 has joined #openstack-swift17:44
*** daddyjoseph97 has quit IRC17:45
*** esker has quit IRC17:47
*** sgundur has quit IRC17:47
*** sgundur1 has joined #openstack-swift17:47
*** esker has joined #openstack-swift17:48
*** robefran has joined #openstack-swift17:50
*** janonymous_ has quit IRC17:58
*** diazjf has joined #openstack-swift18:01
*** diazjf has quit IRC18:02
*** diazjf has joined #openstack-swift18:03
*** jordanP has quit IRC18:05
*** janonymous_ has joined #openstack-swift18:08
openstackgerritOndřej Nový proposed openstack/swift: Deprecated tox -downloadcache option removed  https://review.openstack.org/25659718:09
notmynamegood morning18:14
notmynamejrichli: that's great!18:14
*** klrmn has joined #openstack-swift18:16
jrichlinotmyname: :-)18:16
notmynamethe slides look great18:16
*** zaitcev has joined #openstack-swift18:16
*** ChanServ sets mode: +v zaitcev18:16
diazjfwhoop whoop jrichli :)18:18
jrichlinotmyname diazjf: thanks.  i got into a little more than what was on the slides.18:19
*** delattec has joined #openstack-swift18:20
*** cdelatte has quit IRC18:23
*** zhill has joined #openstack-swift18:28
*** nadeem has joined #openstack-swift18:29
* jrichli is stepping out18:31
*** janonymous__ has joined #openstack-swift18:34
*** haomaiwang has joined #openstack-swift18:37
*** acoles is now known as acoles_18:38
*** janonymous__ has quit IRC18:38
*** janonymous__ has joined #openstack-swift18:42
*** shakamunyi has quit IRC18:44
*** tamizh_geek has quit IRC18:45
*** jistr has quit IRC18:45
*** tamizh_geek has joined #openstack-swift18:47
*** janonymous__ has quit IRC18:48
*** tamizh_geek has quit IRC18:52
*** silor has quit IRC18:55
*** tamizh_geek has joined #openstack-swift18:56
*** robefran has quit IRC18:56
*** robefran has joined #openstack-swift18:57
*** blmartin has quit IRC19:00
*** sgundur1 has quit IRC19:02
*** robefran has quit IRC19:02
*** pberis has joined #openstack-swift19:06
*** sgundur has joined #openstack-swift19:07
*** nadeem has quit IRC19:12
*** hogepodge has quit IRC19:18
*** hogepodge has joined #openstack-swift19:18
*** hogepodge has quit IRC19:19
*** aix has quit IRC19:19
*** hogepodge has joined #openstack-swift19:19
*** diazjf has quit IRC19:19
*** changbl has quit IRC19:19
*** diazjf has joined #openstack-swift19:20
*** diazjf has quit IRC19:22
*** hogepodge has quit IRC19:23
*** hogepodge has joined #openstack-swift19:23
*** garthb_ has joined #openstack-swift19:28
*** garthb has quit IRC19:30
*** changbl has joined #openstack-swift19:39
*** esker has quit IRC19:48
*** shakamunyi has joined #openstack-swift19:48
wbhuberdfg: timburke: thanx for ur review.  im gonna look into a new query argument like get-formatted instead of breaking backward compatibility19:49
*** delatte has joined #openstack-swift19:52
*** shakamunyi has quit IRC19:55
*** delattec has quit IRC19:55
*** robefran has joined #openstack-swift19:58
*** diazjf has joined #openstack-swift20:02
*** tsg has quit IRC20:02
robefranA swift consistency question. Can a sequence of two PUTs followed by a POST (post-as-copy) eventually settle on the data from the first PUT ? I've created an etherpad https://etherpad.openstack.org/p/swift_consistency_questions with the details of the sequnce I'm worried about. Is this a known situation, or a violation of eventual consistency ?20:07
*** Zyric has joined #openstack-swift20:10
ZyricGood morning20:11
*** dmorita has quit IRC20:33
*** robefran has quit IRC20:35
*** ig0r_ has joined #openstack-swift20:37
*** hogepodge has quit IRC20:47
*** sgundur has quit IRC20:50
*** ChubYann has joined #openstack-swift20:51
*** sgundur has joined #openstack-swift20:53
*** sgundur1 has joined #openstack-swift20:54
*** rcernin has joined #openstack-swift20:56
*** sgundur1 has quit IRC20:56
*** lcurtis has joined #openstack-swift21:08
*** dewsday has joined #openstack-swift21:09
*** diazjf has quit IRC21:10
*** CaioBrentano has quit IRC21:10
*** hogepodge has joined #openstack-swift21:12
*** dmorita has joined #openstack-swift21:12
*** dewsday has quit IRC21:12
*** tsg has joined #openstack-swift21:14
*** diazjf has joined #openstack-swift21:26
notmynameI wishe robefran were still here21:31
hrounotmyname, feel free to answer ;) Here I'll relay the message we've been chatting about the subject the last week, or you could answer in the etherpad21:34
notmynameheh21:34
notmynameso the answer is "sortof"21:34
notmynameor rather, yes it might be possible, but it's very very unlikely21:34
notmynameso when swift does a server-side copy, it uses the x-newest:true header to get the source21:34
notmynamewhich means that it will query all the primaries and use the one with the biggest timestamp21:35
hrounotmyname, Yea we agree about the "that'll probably never" happen part - but to give some context this us trying to understand how things work so we can present a better way forward for symlink ;)21:35
*** then3rd has joined #openstack-swift21:35
hrounotmyname, yep!  But x-newest may not be able to find a handoff that's offline atm.21:35
notmynameso his example would only happen if all of the primary nodes with the newer data were unavailable21:35
notmynametotally21:35
notmynamex-newest isn't a guarantee, really. but it significantly reduces the possiblity of getting older data21:36
hrouyep, or if the primarys were down earlier and didn't have all the data in the first place?21:36
hrounotmyname, perfect yea that was our interpretation21:37
notmynameso yeah, we could come up with scenarios where that might happen. failures + ring rebalances + operators who are pushing new rings too fast + etc21:38
hrounotmyname, that's great;  That's what we expected and just wanted to ensure there wasn't something else we're missing that would handle it.21:39
hrouhrou, that's good though it'll help up frame what we're proposing with symlink given that's the case here.21:39
hrounotmyname, thanks!21:39
*** zhill has quit IRC21:42
*** robefran has joined #openstack-swift21:47
then3rdHey all, I have a dumb question I can't seem to find the answer for. I've only a few months experience with swift and am responsible for a previously configured cluster. So far, I haven't made any big changes to the existing environment.21:47
notmynamethen3rd: sure. what's up?21:48
then3rdOur current haproxy, swift-proxy, keystone, and storage nodes have both public and private IPs. The storage nodes communicate via a 10G private network that the proxies also have access to. I think it's all fairly standard. I'm going to soon be adding additional storage nodes located in a separate geographic region, so I'll be learning how to implement regions. I've read that generally you want to21:48
then3rdconfigure either a VPN or MPLS/Ethernet circuit to connect the private networks. Here's my question: Since we already have public IPs, would changing the rsycnd config to bind to the public IPs enable me to synchronize between regions without the need for a vpn?21:48
notmynamethen3rd: the two regions need to be routable for each other. eg storage nodes in R1 need to be able to open a connection to nodes in R221:49
then3rdSo, internet-routable ips would count?21:50
notmynamethen3rd: but, and this is important, anything that can talk to the storage nodes directly, including via rsync, will be able to access any and all data on the node21:50
notmynameso you *really* don't want the storage nodes to be accessible by anything other than other trusted nodes in the cluster (eg proxies and maybe admin bastion servers)21:50
then3rdSo, a security vector. As long as we trust our keys, is that okay? I'm guessing that's why vpns are prefered.21:51
notmynametrust your keys? what keys?21:51
robefrannotmymame: I'm back, but hrou explained the motivation for the question (symlink POST)21:51
*** dustins is now known as dustins|out21:51
robefranbefore we get too complicated with symlink POST we just want to check that we are not trying to hard to close holes that exist anyways in regular POST21:52
then3rdHmm.. maybe I'm confused. I thought rsync used ssh keys.21:52
notmynamethen3rd: yeah, it can. but rsync isn't the only way nodes are talking to each other21:53
then3rdWhat other communication happens between them?21:53
notmynamethen3rd: there's an internal http api for node to node (or proxy to node) communication21:54
then3rdOkay. Can it be configured for tls like everything else?21:55
notmynamethen3rd: in addition to get/put/post/delete, there's also a replicate command21:55
then3rdI'm just trying to feel out my options in the event the boss doesn't want to pay for additional ASAs21:55
notmynamethen3rd: not directly. or rather, like the proxy, you really don't want to set it up to use ssl. you want to use something like stud or stunnel to do the TLS21:55
then3rdI think what I'm hearing is: make the private network work. have you heard of anyone trying to do it without?21:56
notmynamewithout a VPN between the regions?21:57
*** sgundur1 has joined #openstack-swift21:57
then3rdYeah.21:57
notmynameif you don't have your own connection between the regions, use a VPN21:58
then3rdCool. I value your time and input, thanks for answering!22:00
then3rdThe next step will be learing how to use reigons. The concept hasn't completely clicked with me yet. I need to get hands-on.22:01
notmynamesure22:04
notmynamethen3rd: our of curiosity, what are you using swift for?22:04
notmynameI like to hear how people are using swift and what they've done with it22:07
notmynamethen3rd: here's an older blog post on global clusters with swift https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/22:08
notmynamethen3rd: bah. looks like some images were lost in a blog reformat. here's an older cached one https://web.archive.org/web/20140429163105/https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/22:09
then3rdWe're running a CDN for a startup company that's building a media managment platform. Atlys.io and atlys MMP22:10
notmynamecool22:11
then3rdThey have their 1.0 client app is available to play with http://atlys.tv and you can mess with the mmp dash at https://atlysmmp.com.22:12
notmynamethen3rd: so it's video streaming from swift?22:12
notmynameoh yeah! that video looks like a swift url ;-)22:13
notmynamecool22:14
then3rdTheir 2.0 version is launching first quarter next year.. wayyy nicer interface and tons more features. Yep, all straight from swift. They're working on implimenting transcoding and a bunch of other stuff. They're interested in storlets and that terrifys me.22:14
notmynamelol22:14
then3rds/terrifys/terrifies/22:14
then3rdI'm like.. I don't do java, I won't write it. But I may be able to enable it.22:15
then3rdI think storlets might be overkill for what they want anyway. who knows.22:15
notmynamedepends on what they need22:16
notmynamethe main advantage of storlets over "normal" middleware in swift is that the storlet can change without having to restart any processes in the cluster22:17
then3rdI was on this channel a few months back asking how I could track bandwidth usage per-object. Thanks to someones advice here, I went with post-log analysis. logstash+elasticsearch let me pull all kinds of fun stats that we can use for billing.22:17
notmynameso you, in effect, get user-defined middleware22:17
notmynamenice22:18
notmynameyeah, that's the way to do it22:18
then3rdI still don't know what middleware is.22:18
then3rdI'm a noob man.. such noob.22:18
notmynamehttp://docs.openstack.org/developer/swift/development_middleware.html22:19
*** sgundur1 has quit IRC22:20
*** haomaiwang has quit IRC22:23
*** haomaiwang has joined #openstack-swift22:23
then3rdOkay. I'm still getting my feet wet with python (I don't know why it took me this long to realize how wonderufl it is) but if I understand right.. this lets us do things to the objects passing through the proxy. So I could write middleware to scan for viruses on the fly, or rewrite configurations as they're accessed.22:35
notmynameyeah, exactly22:36
notmynameyou can intercept and act on (including modify) the request on the way in and the response on the way out22:36
then3rdCould middleware do transcoding as a video is uploaded?22:36
notmynameabsolutely22:36
then3rdCrap, they're not gonna like to hear that.22:37
notmynamethe basic hello world version of middleware is resizing an image22:37
*** openstackgerrit has quit IRC22:37
notmynamenow, the reason you might not want to transcode on the fly on ingest is because transcoding might take a long time22:37
*** rcernin has quit IRC22:37
*** openstackgerrit has joined #openstack-swift22:37
then3rdi think they're pulling the files out, transcoding, and re-adding as a new object. Though, they want to keep archives of the original quality.22:38
notmynameand you might want to store the non-transcoded (original source format) in the cluster so you can re-transcode again later22:38
notmynameyeah22:38
then3rd^^]22:38
notmynameeither way is possible. depends on what the end goal is22:38
then3rdSo, the middleware could be cablable of writing both objects. That would be awesome.22:38
*** diazjf has quit IRC22:38
notmynameyeah, that's possible too22:39
notmynameI've used this use case as an example for storage polices before. one storage policy eg erasure coded or 3 or 4 replicas across multiple regions for the original format. then use something like a regional 2 replica policy for the transcoded version22:40
notmynameso you get full durability of the original that you don't want to replace. but cheaper (and potentially local) storage for the transcoded ones that people access22:40
openstackgerritMerged openstack/swift: Update versioned_writes doc  https://review.openstack.org/25625022:41
then3rdnotmyname: that's exactly what they want too. I knew I would have to figure out something like that.22:41
then3rdPolicies are also something I'm going to have to get familiar with22:42
notmynamethen3rd: do you have a copy of the oreilly swift book yet?22:42
*** thumpba has quit IRC22:43
*** diogogmt has quit IRC22:44
pdardeaunotmyname: yatin: your earlier discussion of swift ring was awesome22:45
pdardeaukeeping handy reference to that for future use22:45
notmynamepdardeau: oh, good. it's a pretty complex topic ;-)22:45
hrouthen3rd, I'd be curious about hearing more about their uses cases, there's talk (well there always talk ;-) of extending storlets beyond java if that's actually a blocking factor;  You're correct though storlets bring in an ecosystem (all the suden you're running docker on your proxy / object server) and all the fun that comes with that22:45
notmynamethen3rd: http://www.amazon.com/OpenStack-Swift-Administering-Developing-Storage/dp/1491900822/22:45
*** setmason has joined #openstack-swift22:46
notmynamethen3rd: or, if you want it for free (ie giving some contact details) https://swiftstack.com/books/22:46
then3rdI don't have the orriley book, though I've read a few chapters of the Sotware Defined Storage with swift by Joe Arnold.22:46
setmasonIn SSBench, is there docs on the output columns? I’m trying to understand what a backend_error is.22:47
*** Trixboxer has quit IRC22:49
*** tsg has quit IRC22:49
notmynamesetmason: yeah, I remember looking for that too22:49
then3rdhrou: One of the devs show me this and said it was what he wanted to do. I think the goal is basically transcoding on the storage nodes? http://superuser.openstack.org/articles/docker-meets-swift-a-broadcaster-s-experience22:50
*** shakamunyi has joined #openstack-swift22:51
hrouthen3rd, Yep!  That's essentially that use case, some transcoding on the way in or out of object storage22:52
then3rdSo, having just learned about middleware, why use storlets to accomplish that?22:52
notmynamesetmason: wait. backend_error? I can't find that string anywhere in the ssbench repo22:53
notmynamethen3rd: because you can update a storlet implementation without getitng the cluster operator to redeploy middleware and update configs (if necessary) and restart the servers22:54
hrouthen3rd, on paper you could indeed accomplish just about anything with middleware ;)  Heck storlets are middleware.  The project gives a mechanism for people to easily add the functionality though without having to get the operator to make any changes, or really be familiar with swift at all.22:54
hrouor what notmyname said ;)22:54
notmynamehrou: on the other hand, the operator overhead of managing the storlet stuff isn't zero either ;-)22:55
then3rdOh! I get it.. storlets are objects.. so they could just build and upload.22:55
notmynameright22:55
hrounotmyname, 100% agreed I think that's going to be one of the problems to overcome with storlets, it can get complex, there's thread managment to worry about, how to allocate resources between accounts, not free at all.22:55
hrounotmyname, then3rd one other very big point / advantage;22:55
hrouEven if the operator was expecting of generic python middleware code (scary thought), there are a lot security  concerns, storlets only allow you to mess with the input / output stream, you can't do anything else (no communication to any other part swift / outside world).22:56
notmynameright22:57
notmynamewhereas with middleware, you better trust the developer of that code. ie know what you're running22:57
hrounotmyname, yep exactly22:58
*** thumpba has joined #openstack-swift22:58
*** nadeem has joined #openstack-swift22:58
then3rdYou've both been enlightening.22:59
hrouthen3rd, shameless plug time, I'd be curious to here about more use cases, there's a storlet IRC channel btw ! #openstack-storlets, which is starting to get a bit more active as of late thanks to kota_ and other folks.23:00
*** shakamunyi has quit IRC23:00
then3rdI'm sure I'll be back soon23:00
then3rdCan't say I have a lot of info about use cases though.23:01
hrouthen3rd, oh no worries, thanks !23:01
then3rdWell, I've been up for at least 24 hours at this point. I think it's time to go home and start my (on-call) weekend.23:02
hrouthen3rd, "starting the weekend" always a good decision ;)23:02
hrousee ya23:02
*** bkmz_ has joined #openstack-swift23:02
then3rdBtw, any of you guys have friends at lehi Mirantis? I have some old bluehost buddies that all went and got jobs there.23:03
*** August1914 has joined #openstack-swift23:03
*** bkmz has quit IRC23:06
*** diogogmt has joined #openstack-swift23:07
notmynamethen3rd: I notice that you're running an older version of swift. (in addition to all the other good stuff added recently) you'll need to upgrade to take advantage of storage policies23:19
*** shakamunyi has joined #openstack-swift23:26
Zyricnotmyname: Speaking of new features/storage policies, is it possible to get eyes on https://review.openstack.org/#/c/241978/ ? I'm not sure what to do with it at this point, I know the goal was to have it done this week. From what I can tell the cluster failures aren't due to the patch code.23:27
*** thumpba has quit IRC23:28
notmynameZyric: I think you're good for now. it's up to torgomatic and tdasilva to look at it and come to an agreement. and I should look at it again to see if my previous +2 still should be there23:28
notmynameZyric: how's the rest of your first week? what do you need? what are you looking at?23:29
Zyricnotmyname: Cool. It's been quite slow going for me the past few days, mostly just reading code and docs and trying to wrap my head around A) How Swift works and B) How my project fits into it, much like we discussed in our start-of-project meeting. 23:29
ZyricI have a much better understanding of the system than I did a few days ago, but I'm still feeling pretty overwhelmed. 23:29
ZyricI noticed myself falling into a kind of trap where I'll be reading about something relevant to my project, discover terms or concepts I'm unfamiliar with so I'll Google those so I can understand the relevant content better, then find more things I don't know about those things and research those and on and on it goes23:30
notmynamefun!23:30
notmynameZyric: don't worry. that all sounds right :-)23:30
notmynameand don't try to understand everything 100% before trying to play with stuff.23:30
notmynameZyric: have you had a chance to look at the auditor hook patch or slogging?23:30
Zyricnotmyname: Yeah I have figured that out eventually. It's only the first week and a few days of learning and confusion are expected but it's still frustrating, The theory is also pretty dry so I think for the rest of the internship I'll do my best to learn what I need on the go as required so it's moving on time.23:31
*** thumpba_ has joined #openstack-swift23:31
*** shakamunyi has quit IRC23:32
Zyricnotmyname: Sort of, I have tried but ran into some problems setting up slogging - namely creating a new account. I have read the code for the patch and slogging respository but it hasn't quite clicked yet.23:32
notmynameZyric: maybe if he weren't such a jerk the maintainer of that repo would stop by and answer your questions ;-)23:33
Zyricnotmyname: Heh, that would be nice. Speaking of questions, I haven't been very good at asking them this week, somewhat due to shyness and somewhat due to the fact the docs are pretty good! Thanks for all the great docs and video tutorials Swift Community :)23:36
*** August1914 has quit IRC23:36
*** thumpba_ has quit IRC23:49
*** tongli has quit IRC23:50
gmmahanotmyname: i sent you an email about the testr patch. when you get a chance, your thoughts on it would be awesome.23:53
gmmahadefinitely not urgent. getting pulled down by end of the year administrative stuff.. :(23:53
notmynamegmmaha: actually that is pretty important. I do want to look at it again verys oon23:54
mattoliveraugmmaha: aren't we all :P23:54
*** Jeffrey4l has quit IRC23:54
gmmahanotmyname: :D23:54
notmynamealready 4pm here and I was looking at a couple of other things, but I hope to look at it before monday23:54
notmynamewe need it to land soon23:54
gmmahamattoliverau: :D that too with barely 3 weeks left to close of the year23:54
gmmahanotmyname: got it. thanks a lot.. and hope i am not being a pain :D23:55
*** setmason has quit IRC23:55
mattoliverauI'll spend my Monday (your Sunday) looking at it :)23:55
notmynamequite the opposite23:55
notmynamemattoliverau: thanks23:55
gmmahamattoliverau: woohoo.. awesome23:55
mattoliveraugmmaha: no thank you so much for all the awesome effort you've put it, it's been so usful!23:55
gmmahamattoliverau: thanks :) i have a strong feeling the solution is "duh, you did it wrong" but thats good23:56
gmmaha:D23:56
mattoliverauI'm just sorry I was pulled away for most of this week, when I was coming to the Sydney office, I suspected (like in the past) I'd still have a chance to do actualy work.. but that kinda failed.23:56
gmmahamattoliverau: aah travels are always fun!! never once have i gotten to do actual work when i travel23:57
mattoliveraulol23:57
gmmahayou are online and thats more than what i could have accomplished23:57
*** lcurtis has quit IRC23:57
mattoliverauwell I'm in a cafe in Sydney ATM waiting for my wife to arrive, so trying to get some work in beofre then ;)23:58
*** zhill has joined #openstack-swift23:58
gmmahathank god you dont have to sign into a VPN to work23:58
* gmmaha needs to get himself a VPS hosted znc23:59
*** zhill has quit IRC23:59
mattoliveraugmmaha: nah, I don't even use my rackspace email for openstack work. Everything in the open, just the way I like it :)23:59
gmmahaniceeee....23:59
notmynamemattoliverau: I don't use my rackspace email either23:59

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