Saturday, 2016-07-16

*** asettle has joined #openstack-swift00:22
*** asettle has quit IRC00:27
*** _JZ_ has quit IRC00:46
*** klrmn has quit IRC01:07
*** chromatin has joined #openstack-swift01:19
chromatinHas anyone deployed Seagate Kinetic drives in production with Swift ?01:22
*** asettle has joined #openstack-swift01:32
*** asettle has quit IRC01:37
*** klrmn has joined #openstack-swift02:21
*** asettle has joined #openstack-swift03:12
*** asettle has quit IRC03:16
*** adu has joined #openstack-swift03:24
*** acoles_ has quit IRC03:49
*** asettle has joined #openstack-swift04:02
*** asettle has quit IRC04:07
*** adu has quit IRC04:27
*** vills has joined #openstack-swift04:34
villsHi guys! Maybe someone know existed solution or have some thoughts of implementing so. What i want is to move old objects (like older than 7 days) to another container. And i want it work on servers side, not on client. Any ideas?04:36
*** Dragon535 has joined #openstack-swift04:39
*** acoles has joined #openstack-swift04:49
*** ChanServ sets mode: +v acoles04:49
*** nadeem has joined #openstack-swift04:49
*** vills has quit IRC04:55
*** nadeem has quit IRC05:01
*** rickflare2 has joined #openstack-swift05:02
*** rickflare has quit IRC05:04
*** rickflare2 is now known as rickflare05:04
*** chromatin has quit IRC05:16
*** Dragon535 has left #openstack-swift05:24
*** nadeem has joined #openstack-swift05:25
*** rcernin has joined #openstack-swift05:32
*** psachin has joined #openstack-swift05:33
*** d0ugal has joined #openstack-swift05:50
*** psachin has quit IRC05:55
*** itlinux has quit IRC06:01
*** garthb has joined #openstack-swift06:04
*** chsc has joined #openstack-swift06:08
*** chsc has joined #openstack-swift06:08
*** zaitcev has quit IRC06:09
*** klrmn has quit IRC06:09
*** d0ugal has quit IRC06:09
*** chsc has quit IRC06:14
*** nadeem has quit IRC06:17
*** psachin has joined #openstack-swift06:25
*** SkyRocknRoll has joined #openstack-swift06:32
*** rcernin has quit IRC06:42
*** rcernin has joined #openstack-swift06:42
*** natarej_ has joined #openstack-swift06:51
*** silor has joined #openstack-swift06:51
*** SkyRocknRoll has quit IRC06:54
*** natarej has quit IRC06:54
*** silor1 has joined #openstack-swift06:57
*** silor has quit IRC06:59
*** silor1 is now known as silor06:59
*** asettle has joined #openstack-swift07:35
*** asettle has quit IRC07:40
*** mmcardle has joined #openstack-swift08:00
*** mmcardle has quit IRC08:13
*** Jeffrey4l has joined #openstack-swift08:25
*** garthb has quit IRC08:26
*** d0ugal has joined #openstack-swift08:43
*** siva_krish has joined #openstack-swift08:48
*** d0ugal has quit IRC08:53
*** ouchkernel has quit IRC09:04
*** ouchkernel has joined #openstack-swift09:09
*** Vr__ has joined #openstack-swift09:19
*** Vr__ has quit IRC09:24
*** siva_krish has quit IRC09:34
*** pcaruana has joined #openstack-swift09:43
*** abhitechie has quit IRC10:29
*** joeljwright has joined #openstack-swift10:30
*** ChanServ sets mode: +v joeljwright10:30
acolestdasilva: jrichli timburke I added my notes from symlinks discussion here https://etherpad.openstack.org/p/swift_symlinks11:10
*** oshritf has joined #openstack-swift11:17
acolestimburke: I didn't take any notes about object versioning w/ symlinks so that section is blank :) all I remembered was that symlinks had to be left of encryption :)11:17
* acoles afk til weds11:18
*** acoles is now known as acoles_11:19
*** oshritf has quit IRC11:32
*** asettle has joined #openstack-swift11:41
*** _JZ_ has joined #openstack-swift11:45
*** asettle has quit IRC11:45
kota_acoles: nice! thanks!12:04
*** joeljwright1 has joined #openstack-swift12:15
*** joeljwright has quit IRC12:19
*** Jeffrey4l has quit IRC12:33
*** Jeffrey4l has joined #openstack-swift12:33
*** mmcardle has joined #openstack-swift12:34
*** vint_bra has joined #openstack-swift12:47
*** vint_bra has quit IRC12:47
*** chromatin has joined #openstack-swift13:11
*** SkyRocknRoll has joined #openstack-swift13:30
*** SkyRocknRoll has quit IRC14:11
*** mmcardle has quit IRC14:28
*** mmcardle has joined #openstack-swift14:31
*** nottrobin has quit IRC14:38
*** nottrobin has joined #openstack-swift14:40
*** adu has joined #openstack-swift15:04
*** adu has quit IRC15:28
*** ozialien10 has quit IRC15:53
*** ozialien10 has joined #openstack-swift15:53
*** chromatin has quit IRC15:53
*** SkyRocknRoll has joined #openstack-swift16:07
*** psachin has quit IRC16:38
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873616:53
*** chromatin has joined #openstack-swift17:22
openstackgerritNandini Tata proposed openstack/swift: swift-ring-builder output corrected for ipv6  https://review.openstack.org/31938717:25
*** adu has joined #openstack-swift17:28
*** manous has joined #openstack-swift17:30
*** adu has quit IRC17:33
*** jmccarthy has quit IRC17:37
*** jmccarthy has joined #openstack-swift17:38
chromatinDoes the use of erasure coding obviate the need to split large files , if splitting is done for parallel read reasons?17:49
*** klrmn has joined #openstack-swift17:52
*** psachin has joined #openstack-swift18:04
timburkeclayg: so you might be right that a py3 migration might just take a weekend (or week) and a bottle of whiskey. waiting for my plane, i at least got the proxy-server to start and respond to /info -- it wasn't as bad i i feared https://github.com/openstack/swift/compare/master...tipabu:py3-proxy18:24
timburkestill can't get it to talk to the backend servers, and at least one header was coming out with b'...' around it, but it's a start18:26
notmynamechromatin: no. erasure coding (EC) is related to how durability is done. large files (ie SLO and DLO) are from the end-user perspective. they're different things18:28
notmynamechromatin: were you asking about using swift for genomics the other day?18:28
chromatinnotmyname: Yes, that was me, and I am not sure I agree with your first answer. THat is to say, I understand EC is for durability, and I understand multipart uploads are performed on client end. I am asking about the functional consequences of each achieving a common goal18:29
notmynameright18:29
notmynamechromatin: oh, if you're interested in genomics stuff with swift, you might be interested in https://www.swiftstack.com/resources18:30
chromatinThanks for the link!18:30
notmynamechromatin: so if an object is stored with EC, that doesn't affect the client-perspective size of the object18:30
notmynamechromatin: if you store a 1GB BAM file, the client will see 1GB, regardless of how is stored--EC or replicas18:31
notmynamejust internally, the data will be split up differently with replication and EC18:31
notmynames/split up/persisted/18:32
chromatinnotmyname: Agree, and perhaps this is covered in the book, but genomics use case is less focused on many-clients parallel reading smaller objects, but few users reading large files. Even 200 MB/sec (single disk throughput) is unacceptable. I see both EC as well as splitting large files on the client end as both achieving the goal of increasing read throughput to a single client for a large object18:32
chromatin(but that is my naive, uninformed view, so welcome criticism)18:35
notmynameyeah, that makes sense. I'm thinking about it18:36
notmynameI think my answer is "maybe" ;-)18:37
chromatin=) I will do some reading on my end18:37
notmynamebut you can tell from that answer that the overall throughput for a single stream isn't the primary design goal of EC18:37
notmynamewhat's your use case? how are you looking to use swift (or using it today)?18:39
chromatinAm not using yet (currently using a couple of NAS without a distributed file system). Recognized that most of our data is rarely accessed / archive and I think object storage makes sense as our growth is still high (maybe not exponential). Right now very small, ~50 TB, but expect to increase by at least that much yearly18:40
notmynamechromatin: very cool :-)18:41
notmynamechromatin: definitely check out that genomics book from the link. it covers a lot of workflows and how swift can fit in18:42
chromatinWill definitely do, thanks again18:42
*** hogepodge has quit IRC19:04
*** hogepodge has joined #openstack-swift19:05
*** klrmn1 has joined #openstack-swift19:17
*** klrmn has quit IRC19:19
*** Jeffrey4l_ has joined #openstack-swift19:32
*** Jeffrey4l has quit IRC19:34
jrichliacoles: excellent symlink write-up.  thank you!19:38
*** chromatin has quit IRC19:42
*** _JZ_ has quit IRC19:56
*** manous has quit IRC20:04
*** garthb has joined #openstack-swift20:07
openstackgerritChristian Schwede proposed openstack/swift: Add support to increase object ring partition power  https://review.openstack.org/33729720:12
*** joeljwright1 has quit IRC20:19
*** SkyRocknRoll has quit IRC20:20
*** chromatin has joined #openstack-swift20:21
*** manous has joined #openstack-swift20:29
*** manous has quit IRC20:36
*** manous has joined #openstack-swift20:49
*** garthb has quit IRC20:51
*** silor has quit IRC21:06
manoushi21:42
*** manous has quit IRC22:02
*** _JZ_ has joined #openstack-swift22:27
*** manous has joined #openstack-swift22:32
*** Raymii has quit IRC23:01
*** Raymii has joined #openstack-swift23:05
*** vinsh has quit IRC23:06

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