Tuesday, 2014-06-17

*** mmcardle1 has quit IRC00:01
zaitcevSome of the stuff in SP kinda makes my blood pressure raise. Or maybe I ate too much chocolate today.00:21
zaitcevportante noticed too00:21
zaitcevwhere is_deleted() added into .merge_timestamps(), but there were others like that00:22
portanteyes, agreed, seems like we are just opening up race conditions00:24
*** matsuhashi has joined #openstack-swift00:24
portantezaitcev: ^00:25
*** dmorita has joined #openstack-swift00:28
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988300:30
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988300:31
notmynamelooks like I'll be talking to some people about Swift on all SSDs tomorrow. should be interesting to listen and learn00:47
*** scohen has joined #openstack-swift00:48
*** scohen has quit IRC00:50
*** haomaiwa_ has joined #openstack-swift00:54
*** kopparam has joined #openstack-swift00:55
*** kopparam has quit IRC01:01
portantenotmyname: do we really support floating point number of replicas?01:25
mattoliveraunotmyname: cool01:26
portantelooking at the documentation for set_replicas of swift-ring-builder command01:26
*** nosnos has joined #openstack-swift01:26
*** kenhui has joined #openstack-swift01:29
portantewe apparently do at least that we can set a replica count of 3.2501:29
portanteon my01:29
portanteoh, that is01:30
*** kenhui1 has joined #openstack-swift01:30
mattoliverauIs anyone here coming to pyconau this year? There will be a Openstack miniconf segment. I was thinking about proposing a short talk on storage policies in swift (which should be in master by then), to make sure swift gets some time on the day. That is if no one objects :) Unless someone else more qaulified then me is coming of course.01:32
*** kenhui has quit IRC01:32
*** kenhui1 has quit IRC01:32
*** kenhui1 has joined #openstack-swift01:35
*** kenhui has joined #openstack-swift01:35
*** charz has joined #openstack-swift01:36
*** kenhui1 has quit IRC01:36
*** nsquare has quit IRC01:37
*** kenhui has quit IRC01:38
*** haomaiwa_ has quit IRC01:43
*** foexle_ has joined #openstack-swift01:48
*** foexle has quit IRC01:51
*** asdfsf has joined #openstack-swift01:55
*** lpabon has joined #openstack-swift02:02
*** kenhui has joined #openstack-swift02:02
portantepeluse_, notmyname, creiht: http://techreport.com/review/26523/the-ssd-endurance-experiment-casualties-on-the-way-to-a-petabyte02:09
*** kenhui has quit IRC02:14
pandemicsynheh we did some wear leveling tests when we deployed Intel 320's at Rackspace. Wonder if I still have those anywhere.02:17
pandemicsynkinda curious to see how older generations of SSD's hold up02:17
notmynameportante: yes. but it's not completely straightforward. 3.25 replicas means that everything has 3 replicas and 25% (.25) has 4 replicas02:19
portantewhoa02:22
portantesounds complicated02:22
notmynameportante: think of it as the sane migration story that allows you to change the replication factor without rebuilding the whole cluster from scratch02:23
portantethe code supports arbitrary floats, so 3.0001 is a valid replica count02:23
notmynameya02:23
portanteokay, I'll just ignore that part of swift for now. :)02:23
notmynamelol02:23
notmynameportante: the user story is when you have a one region cluster (3 replicas) and you want to move to two regions and 4 replicas02:24
portanteI am gonna go back to my world of integer replicas so that I can think about all this storage policies without exploding02:24
notmynameya, it's orthogonal to the policies.02:24
portanteagreed02:24
notmynameportante: and, for your sanity, each partition in the ring will only have an integer number of replicas02:24
notmynameand also don't assume things :-)02:25
portanteI was trying to update the in-process functional tests with one 3-replica ring and one 2-replica ring, but I am failing to do so for some reason that says I don't really understand what I am doing02:25
portante:)02:26
notmynameportante: good ssd article02:28
notmynameportante: seems to confirm my guess that one of the hardest part of SSDs in Swift is doing good management of them. eg figuring out more than just fullness, but current health and expected lifetime02:29
zaitcevSo... Apparently the account maintains status_changed_at, but it's never used for anything.02:29
notmynameother important parts, based on my reading, is getting read buffers configured properly all the way through the stack so that performance is correct02:30
notmynamezaitcev: wasn't that used for direct account management? like with PUT/DELETE to an account?02:30
notmynameie predates autocreated accounts02:30
pandemicsynnotmyname: re: ssd's...yeah....you wanna keep rebalancing to a minimum if you run object storage on ssd's too otherwise your churning data like crazy02:31
zaitcevI think it just goes into account_stat table to die. I don't see a select that fetches it out, ever (on both SP and current truck). But I may be mistaken.02:32
notmynamepandemicsyn: ya. we've also been looking at some things related to TRIM. turns out that's a good idea too :-)02:32
zaitcevAnyhow...02:32
pandemicsynfor the best performance when it comes to SSD's you'll wanna run Swift on Windows 7 Ultimate02:33
notmynamepandemicsyn: and it's that sort of thing (less rebalancing) that is something I'm very curious about and how much that can be set in Swift. ie can we have some config that keeps data less balanced because SSD? maybe in the ring-builder?02:33
notmynamepandemicsyn: naturally02:33
notmynameactually, the "less balanced but also less transfer" might be good in the non-SSD case with eg power management. peluse_, you're interested in that02:37
notmynamesome sort of backblaze-style "fill up the jbod and turn it off" sort of storage. would be pretty distinct02:38
* notmyname is imagining selecting storage policies based on durability schemes and power management schemes02:39
* pandemicsyn shudders02:39
pandemicsynnotmyname: thats kinda how NAST worked02:40
pandemicsynwell as far as not using the drives that often that is02:41
notmynamepandemicsyn: ya. and there's a reason swift exists today :-)02:41
*** foexle_ has quit IRC02:41
*** bkopilov_ has quit IRC02:41
notmynameI'd much prefer to tackle any power concerns by first looking at overall efficiency and density02:42
*** Midnightmyth has joined #openstack-swift02:45
*** kopparam has joined #openstack-swift03:00
*** kopparam has quit IRC03:05
peluse_portante:  you there?03:18
portanteyes03:19
portantewell, at least I am typing here, not sure how much thought I can pull off at this point03:19
peluse_wrt the failing probe test, did you see the 2 updates I put in there?03:20
portantenot yet03:20
peluse_ahh OK, they're after Sam's comment but before yours03:20
portantewas just working with the tip of the sp chain, and did NOT see a failure on my two SAIOs, FWIW03:20
portanteI don't have torgomatic's configuration, though03:20
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988303:21
*** dmsimard_away is now known as dmsimard03:21
portantepeluse_: I see them now, yes, I started to debug it, but gave up after I could not keep focused on this longer than a minute or two03:22
*** dmsimard is now known as dmsimard_away03:22
peluse_yeah, OK.  Getting a bead on it sort of... and you do have to have the config he mentions in there.  Non-0 default and rsync.  I know what's happening but can't explain why ssync works and can't find what I think would be obvisouly wrong (using 0 insetad of the specified default)...03:23
portanteI'd be happy to look at it tomorrow03:24
portantein the mean time, here is a simple patch to skip container-reconciler probe tests when no container-reconciler.conf file is present in a SAIO: https://gist.github.com/portante/6ab72faa6db065d32a8e03:25
peluse_cool, thanks.  doubt I'll resolve it here in the short amount of time I plan on spending for the rest of the eve :)03:25
portanteOne of my two SAIOs was in that state, and the errors from the probe tests were non-obvious what was happening03:25
portantepeluse_: also, working on adding a storage-policy configuration for the in-process functional tests03:26
peluse_cool03:26
*** zhiyan_ is now known as zhiyan03:28
*** Midnightmyth has quit IRC03:30
*** matsuhashi has quit IRC03:30
peluse_portante:  hmm, know off the top of your head if ssync's use of DiskFile would cause the creation of the policy specific tmp file?  (self._tmpdir).  Looking... if so that would explain it03:33
*** matsuhashi has joined #openstack-swift03:37
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988303:38
*** nosnos has quit IRC03:41
*** matsuhashi has quit IRC03:44
*** matsuhashi has joined #openstack-swift03:45
*** matsuhashi has quit IRC03:49
*** Kbee has joined #openstack-swift03:53
portantepeluse_: I think so, because the tmpdir is created when the DiskFile object's .create() method is invoked03:54
*** matsuhashi has joined #openstack-swift03:57
peluse_portante: yeah, that is probably part of it.  Just updated gerrit... this is an annoying piss-ant little thing if nothing else...04:00
portantepeluse_: but also the nature of having two sync methods. :)04:01
portanteone that uses the DiskFile backend, and one that assumes it knows what the on-disk layout looks like. :)04:01
*** matsuhashi has quit IRC04:03
*** matsuhashi has joined #openstack-swift04:04
*** bkopilov_ has joined #openstack-swift04:12
*** ppai has joined #openstack-swift04:21
*** nosnos has joined #openstack-swift04:30
*** matsuhashi has quit IRC04:36
*** matsuhas_ has joined #openstack-swift04:37
*** haomaiwa_ has joined #openstack-swift04:39
openstackgerritZhang Hua proposed a change to openstack/swift: Add distributed tracing capablities in logging.  https://review.openstack.org/9367704:43
*** gyee has quit IRC04:51
*** scohen has joined #openstack-swift04:53
*** haomaiw__ has joined #openstack-swift04:54
*** haomaiwa_ has quit IRC04:56
*** psharma has joined #openstack-swift05:01
*** nshaikh has joined #openstack-swift05:08
*** bkopilov_ has quit IRC05:16
*** bkopilov has joined #openstack-swift05:17
*** zhiyan is now known as zhiyan_05:20
*** zaitcev has quit IRC05:23
*** mlipchuk has joined #openstack-swift05:24
*** mlipchuk has quit IRC05:28
*** kopparam has joined #openstack-swift05:39
*** mlipchuk has joined #openstack-swift05:42
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988305:47
*** scohen has joined #openstack-swift05:55
*** scohen has quit IRC05:55
*** zhiyan_ is now known as zhiyan06:02
*** kopparam has quit IRC06:05
*** kopparam has joined #openstack-swift06:05
*** kopparam has quit IRC06:10
Kbeenotmyname, Solved it.. there were conflicting ports assigned to account and object servers.. correcting that resolved the issue06:34
*** asdfsf has quit IRC06:37
*** chandan_kumar has quit IRC06:38
*** scohen has joined #openstack-swift06:51
* hugokuo hurray06:51
mattoliverauI'm calling it day, have a great night/day depending on where you are in the world :)06:53
hugokuobye06:58
*** foexle has joined #openstack-swift07:00
*** joeljwright has joined #openstack-swift07:05
*** kopparam has joined #openstack-swift07:11
*** kopparam_ has joined #openstack-swift07:15
*** kopparam has quit IRC07:16
*** ujjain has quit IRC07:20
*** itarchitectkev_ has joined #openstack-swift07:21
*** mmcardle has joined #openstack-swift07:39
*** ujjain2 has joined #openstack-swift07:40
*** ujjain2 has quit IRC07:41
*** ujjain has joined #openstack-swift07:41
*** ujjain has quit IRC07:43
*** ujjain has joined #openstack-swift07:43
*** matsuhas_ has quit IRC07:49
*** matsuhashi has joined #openstack-swift07:51
*** mkollaro has joined #openstack-swift07:53
*** nacim has joined #openstack-swift07:58
*** nacim has quit IRC07:59
*** mmcardle has quit IRC08:16
*** nosnos has quit IRC08:16
*** judd7 has quit IRC08:16
*** rieglflo has quit IRC08:16
*** ahale has quit IRC08:16
*** itarchitectkev_ has quit IRC08:16
*** haomaiw__ has quit IRC08:16
*** wer has quit IRC08:16
*** AbyssOne_ has quit IRC08:16
*** torgomatic has quit IRC08:16
*** d0ugal has quit IRC08:16
*** hurricanerix has quit IRC08:16
*** jd__ has quit IRC08:16
*** fbo has quit IRC08:16
*** portante has quit IRC08:16
*** russell_h has quit IRC08:16
*** briancline has quit IRC08:16
*** pandemicsyn has quit IRC08:16
*** sileht has quit IRC08:16
*** mlanner has quit IRC08:16
*** occupant has quit IRC08:16
*** zacksh has quit IRC08:16
*** mhu has quit IRC08:16
*** bgmccollum has quit IRC08:16
*** zigo has quit IRC08:16
*** notmyname has quit IRC08:16
*** zhiyan has quit IRC08:16
*** chmouel has quit IRC08:16
*** anderstj has quit IRC08:16
*** joearnold has quit IRC08:16
*** glange has quit IRC08:16
*** mkollaro has quit IRC08:16
*** ujjain has quit IRC08:16
*** foexle has quit IRC08:16
*** bkopilov has quit IRC08:16
*** psharma has quit IRC08:16
*** acoles has quit IRC08:16
*** miqui has quit IRC08:16
*** zul has quit IRC08:16
*** AbyssOne has quit IRC08:16
*** mattoliverau has quit IRC08:16
*** zz_wasmum has quit IRC08:16
*** nshaikh has quit IRC08:16
*** Kbee has quit IRC08:16
*** openstackgerrit has quit IRC08:16
*** fifieldt has quit IRC08:16
*** IRTermite has quit IRC08:16
*** omame has quit IRC08:16
*** matsuhashi has quit IRC08:16
*** joeljwright has quit IRC08:16
*** dmorita has quit IRC08:16
*** ondergetekende has quit IRC08:16
*** openfly has quit IRC08:16
*** ppai has quit IRC08:16
*** Dieterbe has quit IRC08:16
*** dosaboy has quit IRC08:16
*** DisneyRicky has quit IRC08:16
*** JoshNang has quit IRC08:16
*** scohen has quit IRC08:16
*** mlipchuk has quit IRC08:16
*** mkerrin has quit IRC08:16
*** jokke_ has quit IRC08:16
*** ekarlso has quit IRC08:16
*** charz has quit IRC08:16
*** madhuri has quit IRC08:16
*** StevenK has quit IRC08:16
*** byeager_away has quit IRC08:16
*** rpedde has quit IRC08:16
*** thurloat has quit IRC08:16
*** otherjon has quit IRC08:16
*** kragniz has quit IRC08:16
*** serverascode has quit IRC08:16
*** CybergeekDK has quit IRC08:16
*** ChanServ has quit IRC08:16
*** swat30 has quit IRC08:16
*** cschwede has quit IRC08:16
*** tanee has quit IRC08:16
*** ezml has quit IRC08:16
*** dfg has quit IRC08:16
*** sts has quit IRC08:16
*** jeblair has quit IRC08:16
*** wkelly has quit IRC08:16
*** anticw has quit IRC08:16
*** zackmdavis has quit IRC08:16
*** creiht has quit IRC08:16
*** amandap has quit IRC08:16
*** mtreinish has quit IRC08:17
*** redbo has quit IRC08:17
*** kopparam_ has quit IRC08:17
*** kevinc_ has quit IRC08:17
*** sandywalsh has quit IRC08:17
*** nthacker__ has quit IRC08:17
*** patchbot has quit IRC08:17
*** bobby_ has quit IRC08:17
*** flowouffff has quit IRC08:17
*** ctennis has quit IRC08:17
*** acorwin has quit IRC08:17
*** clayg has quit IRC08:17
*** goneri has quit IRC08:17
*** Anticimex has quit IRC08:17
*** grapsus_ has quit IRC08:17
*** Mikalv has quit IRC08:17
*** goodes has quit IRC08:17
*** MooingLemur has quit IRC08:17
*** esmute has quit IRC08:17
*** peluse_ has quit IRC08:17
*** joearnold has joined #openstack-swift08:22
*** glange has joined #openstack-swift08:22
*** anderstj has joined #openstack-swift08:22
*** chmouel has joined #openstack-swift08:22
*** notmyname has joined #openstack-swift08:22
*** zigo has joined #openstack-swift08:22
*** zhiyan has joined #openstack-swift08:22
*** bgmccollum has joined #openstack-swift08:22
*** mhu has joined #openstack-swift08:22
*** zacksh has joined #openstack-swift08:22
*** briancline has joined #openstack-swift08:22
*** russell_h has joined #openstack-swift08:22
*** occupant has joined #openstack-swift08:22
*** portante has joined #openstack-swift08:22
*** dickson.freenode.net sets mode: +vvvv glange chmouel notmyname portante08:22
*** jd__ has joined #openstack-swift08:22
*** fbo has joined #openstack-swift08:22
*** mlanner has joined #openstack-swift08:22
*** hurricanerix has joined #openstack-swift08:22
*** sileht has joined #openstack-swift08:22
*** ahale has joined #openstack-swift08:22
*** pandemicsyn has joined #openstack-swift08:22
*** d0ugal has joined #openstack-swift08:22
*** torgomatic has joined #openstack-swift08:22
*** rieglflo has joined #openstack-swift08:22
*** AbyssOne_ has joined #openstack-swift08:22
*** wer has joined #openstack-swift08:22
*** judd7 has joined #openstack-swift08:22
*** nosnos has joined #openstack-swift08:22
*** haomaiw__ has joined #openstack-swift08:22
*** itarchitectkev_ has joined #openstack-swift08:22
*** mmcardle has joined #openstack-swift08:22
*** mkollaro has joined #openstack-swift08:22
*** matsuhashi has joined #openstack-swift08:22
*** ujjain has joined #openstack-swift08:22
*** joeljwright has joined #openstack-swift08:22
*** foexle has joined #openstack-swift08:22
*** scohen has joined #openstack-swift08:22
*** mlipchuk has joined #openstack-swift08:22
*** bkopilov has joined #openstack-swift08:22
*** nshaikh has joined #openstack-swift08:22
*** psharma has joined #openstack-swift08:22
*** ppai has joined #openstack-swift08:22
*** Kbee has joined #openstack-swift08:22
*** dmorita has joined #openstack-swift08:22
*** acoles has joined #openstack-swift08:22
*** dickson.freenode.net sets mode: +vv torgomatic acoles08:22
*** kevinc_ has joined #openstack-swift08:22
*** miqui has joined #openstack-swift08:22
*** zul has joined #openstack-swift08:22
*** sts has joined #openstack-swift08:22
*** sandywalsh has joined #openstack-swift08:22
*** openstackgerrit has joined #openstack-swift08:22
*** ondergetekende has joined #openstack-swift08:22
*** madhuri has joined #openstack-swift08:22
*** AbyssOne has joined #openstack-swift08:22
*** fifieldt has joined #openstack-swift08:22
*** Dieterbe has joined #openstack-swift08:22
*** dosaboy has joined #openstack-swift08:22
*** mattoliverau has joined #openstack-swift08:22
*** DisneyRicky has joined #openstack-swift08:22
*** nthacker__ has joined #openstack-swift08:22
*** IRTermite has joined #openstack-swift08:22
*** omame has joined #openstack-swift08:22
*** mkerrin has joined #openstack-swift08:22
*** openfly has joined #openstack-swift08:22
*** zz_wasmum has joined #openstack-swift08:22
*** flowouffff has joined #openstack-swift08:22
*** StevenK has joined #openstack-swift08:22
*** goodes has joined #openstack-swift08:22
*** patchbot has joined #openstack-swift08:22
*** bobby_ has joined #openstack-swift08:22
*** JoshNang has joined #openstack-swift08:22
*** jokke_ has joined #openstack-swift08:22
*** swat30 has joined #openstack-swift08:22
*** thurloat has joined #openstack-swift08:22
*** cschwede has joined #openstack-swift08:22
*** MooingLemur has joined #openstack-swift08:22
*** esmute has joined #openstack-swift08:22
*** ekarlso has joined #openstack-swift08:22
*** tanee has joined #openstack-swift08:22
*** byeager_away has joined #openstack-swift08:22
*** ezml has joined #openstack-swift08:22
*** dfg has joined #openstack-swift08:22
*** rpedde has joined #openstack-swift08:22
*** goneri has joined #openstack-swift08:22
*** otherjon has joined #openstack-swift08:22
*** peluse_ has joined #openstack-swift08:22
*** kragniz has joined #openstack-swift08:22
*** jeblair has joined #openstack-swift08:22
*** Anticimex has joined #openstack-swift08:22
*** grapsus_ has joined #openstack-swift08:22
*** serverascode has joined #openstack-swift08:22
*** dickson.freenode.net sets mode: +v dfg08:22
*** wkelly has joined #openstack-swift08:22
*** Mikalv has joined #openstack-swift08:22
*** anticw has joined #openstack-swift08:22
*** zackmdavis has joined #openstack-swift08:22
*** CybergeekDK has joined #openstack-swift08:22
*** creiht has joined #openstack-swift08:22
*** amandap has joined #openstack-swift08:22
*** mtreinish has joined #openstack-swift08:22
*** ChanServ has joined #openstack-swift08:22
*** ctennis has joined #openstack-swift08:22
*** redbo has joined #openstack-swift08:22
*** acorwin has joined #openstack-swift08:22
*** clayg has joined #openstack-swift08:22
*** dickson.freenode.net sets mode: +vovv creiht ChanServ redbo clayg08:22
*** d0ugal has quit IRC08:24
*** d0ugal_ has joined #openstack-swift08:24
*** d0ugal_ is now known as d0ugal08:25
*** d0ugal has quit IRC08:25
*** d0ugal has joined #openstack-swift08:25
*** fifieldt has quit IRC08:27
*** fifieldt has joined #openstack-swift08:28
*** mmcardle has quit IRC08:33
*** nosnos has quit IRC08:33
*** judd7 has quit IRC08:33
*** rieglflo has quit IRC08:33
*** ahale has quit IRC08:33
*** itarchitectkev_ has quit IRC08:33
*** haomaiw__ has quit IRC08:33
*** wer has quit IRC08:33
*** AbyssOne_ has quit IRC08:33
*** torgomatic has quit IRC08:33
*** hurricanerix has quit IRC08:33
*** jd__ has quit IRC08:33
*** fbo has quit IRC08:33
*** portante has quit IRC08:33
*** russell_h has quit IRC08:33
*** briancline has quit IRC08:33
*** pandemicsyn has quit IRC08:33
*** sileht has quit IRC08:33
*** mlanner has quit IRC08:33
*** occupant has quit IRC08:33
*** zacksh has quit IRC08:33
*** mhu has quit IRC08:33
*** bgmccollum has quit IRC08:33
*** zigo has quit IRC08:33
*** notmyname has quit IRC08:33
*** zhiyan has quit IRC08:33
*** chmouel has quit IRC08:33
*** anderstj has quit IRC08:33
*** joearnold has quit IRC08:33
*** glange has quit IRC08:33
*** kopparam has joined #openstack-swift08:40
*** mmcardle has joined #openstack-swift08:43
*** itarchitectkev_ has joined #openstack-swift08:43
*** haomaiw__ has joined #openstack-swift08:43
*** nosnos has joined #openstack-swift08:43
*** judd7 has joined #openstack-swift08:43
*** wer has joined #openstack-swift08:43
*** AbyssOne_ has joined #openstack-swift08:43
*** rieglflo has joined #openstack-swift08:43
*** torgomatic has joined #openstack-swift08:43
*** pandemicsyn has joined #openstack-swift08:43
*** ahale has joined #openstack-swift08:43
*** sileht has joined #openstack-swift08:43
*** zacksh has joined #openstack-swift08:43
*** mhu has joined #openstack-swift08:43
*** bgmccollum has joined #openstack-swift08:43
*** zhiyan has joined #openstack-swift08:43
*** zigo has joined #openstack-swift08:43
*** notmyname has joined #openstack-swift08:43
*** chmouel has joined #openstack-swift08:43
*** anderstj has joined #openstack-swift08:43
*** glange has joined #openstack-swift08:43
*** dickson.freenode.net sets mode: +vvvv torgomatic notmyname chmouel glange08:43
*** joearnold has joined #openstack-swift08:43
*** briancline has joined #openstack-swift08:43
*** russell_h has joined #openstack-swift08:43
*** occupant has joined #openstack-swift08:43
*** portante has joined #openstack-swift08:43
*** jd__ has joined #openstack-swift08:43
*** fbo_away has joined #openstack-swift08:43
*** mlanner has joined #openstack-swift08:43
*** hurricanerix has joined #openstack-swift08:43
*** dickson.freenode.net sets mode: +v portante08:43
*** nosnos has quit IRC08:54
*** nosnos has joined #openstack-swift08:55
*** kopparam has quit IRC08:56
*** kopparam has joined #openstack-swift08:56
*** IRTermite has quit IRC08:59
*** Kbee has quit IRC09:01
*** kopparam has quit IRC09:01
*** mkollaro has quit IRC09:01
*** IRTermite has joined #openstack-swift09:03
*** kopparam has joined #openstack-swift09:03
*** kopparam has quit IRC09:04
*** Kbee has joined #openstack-swift09:09
*** jamiehannaford has joined #openstack-swift09:12
joeljwrightHi everyone, the review process for the patch I proposed to add an additional high-level API for the python-swiftclient library (https://review.openstack.org/#/c/85453/) seems to have stalled09:18
*** Kbee has quit IRC09:18
*** jamiehannaford has quit IRC09:19
joeljwrightThis update aims to make a lot of the high-level, multithreaded logic in shell.py available to developers using python-swiftclient in their own projects09:19
joeljwrightto try to help get the review process going again I have written a short design document that hopefully makes the motivation and changes more clear https://github.com/joel-wright/openstack-notes/blob/master/swift-service/design.md09:20
*** pberis has quit IRC09:21
*** matsuhashi has quit IRC09:22
*** pberis has joined #openstack-swift09:23
*** matsuhashi has joined #openstack-swift09:24
*** matsuhashi has quit IRC09:30
*** matsuhashi has joined #openstack-swift09:30
*** pberis has quit IRC09:30
*** Kbee has joined #openstack-swift09:31
*** pberis has joined #openstack-swift09:33
*** matsuhashi has quit IRC09:34
acolesjoeljwright: thanks. suggest you link to that doc from the blueprint if you haven't already.09:36
joeljwrightI added it to the review, will add a link from the blueprint now09:36
acolesjoeljwright: ah, yes, just saw it on review. thx09:37
*** matsuhashi has joined #openstack-swift09:37
*** goneri has quit IRC09:39
*** nshaikh has quit IRC09:41
*** nshaikh has joined #openstack-swift09:41
*** pberis has quit IRC09:41
*** openstackgerrit_ has joined #openstack-swift09:43
*** matsuhashi has quit IRC09:48
*** matsuhashi has joined #openstack-swift09:50
*** kopparam has joined #openstack-swift09:53
*** kopparam_ has joined #openstack-swift09:53
*** kopparam has quit IRC09:57
*** jamiehannaford has joined #openstack-swift10:01
*** jamiehannaford has quit IRC10:02
*** matsuhashi has quit IRC10:03
*** matsuhashi has joined #openstack-swift10:03
*** matsuhashi has quit IRC10:04
*** matsuhashi has joined #openstack-swift10:04
*** dmorita has quit IRC10:13
*** matsuhashi has quit IRC10:14
*** matsuhashi has joined #openstack-swift10:21
*** matsuhashi has quit IRC10:35
*** matsuhashi has joined #openstack-swift10:36
*** matsuhashi has quit IRC10:40
rieglflohi everyone. i'm authenticated via keystone as admin. i create a user + tenant + root container (within swift). i set the read and write acl for the new user on the root container. why does a following list container request, authenticated as the newly created user, not show the container? because the owner is the admin user? can i change that?10:43
*** Kbee has quit IRC10:52
rieglflomaybe i'm an impasse here. what is the default role i have to assign a user + tenant so he is able to list his containers, create new ones and create objects? swiftoperator works fine, but is too much i think?11:00
*** sombrafam has joined #openstack-swift11:24
acolesrieglflo: the default role required for a user to create containers & objects is admin or swiftoperator11:31
*** joeljwright1 has joined #openstack-swift11:32
acolesrieglflo: i.e. in keystone the user must have role admin or swiftoperator on the tenant11:32
*** joeljwright2 has joined #openstack-swift11:35
*** joeljwright has quit IRC11:36
*** joeljwright1 has quit IRC11:37
*** mkollaro has joined #openstack-swift11:42
*** kopparam_ has quit IRC12:11
*** kopparam has joined #openstack-swift12:12
rieglfloacoles: is there no way to create a container as admin, set quotas and acl read/write for another user and set the new user as new owner?12:13
*** kopparam has quit IRC12:16
acolesrieglflo: a user with admin role on the tenant can create a container and set ACLs on that container to grant access to another user12:18
acolesrieglflo: where 'access'=list container and create/delete objects12:19
*** joeljwright has joined #openstack-swift12:19
acolesrieglflo: but ACL does not grant right to delete the container or change the ACL, if that is what you mean by set other user as 'owner'12:19
acolesrieglflo: looks like the container-quotas middleware takes care of setting a quota12:20
*** ahale has quit IRC12:20
*** joeljwright1 has joined #openstack-swift12:21
*** joeljwright2 has quit IRC12:22
*** joeljwright has quit IRC12:23
rieglfloacoles: but the container will never show up in the list of the containers the user owns a.k. via GET /v1/AUTH_b7f1cad131474e01a7305c5122d1bc72?delimiter=%2F&limit=100&format=json if the user-id is b7f1cad131474e01a7305c5122d1bc72 when the container has been created as another user(admin)12:23
rieglfloacoles: thats an issue because already existing clients, work that way on listing a users containers12:28
*** ppai has quit IRC12:28
*** annegentle has joined #openstack-swift12:30
acolesrieglflo: the piece b7f1cad131474e01a7305c5122d1bc72 after AUTH_ is usually the tenant id , not the user id. It defines the account in swift within which containers are created. So containers in one tenant/account AUTH_X will never list under another account AUTH_Y.12:30
*** zul has quit IRC12:31
*** zul has joined #openstack-swift12:31
acolesrieglflo: but more than one user can access the same tenant/account AUTH_X is each user has admin role on that tenant, or via an ACL.12:31
acolesrieglflo: /is/if/12:32
acolesrieglflo: sorry i have to got to a meeting.12:33
rieglfloacoles: thanks for your clarifcations and time12:33
*** mmcardle has quit IRC12:36
*** nacim has joined #openstack-swift12:41
*** mmcardle has joined #openstack-swift12:42
*** haomaiw__ has quit IRC12:43
*** haomaiwang has joined #openstack-swift12:43
*** haomaiwang has quit IRC12:46
*** haomaiwang has joined #openstack-swift12:47
*** haomaiw__ has joined #openstack-swift12:52
*** haomaiwang has quit IRC12:53
*** nosnos has quit IRC12:53
*** bkopilov has quit IRC12:54
*** annegentle has quit IRC12:58
peluse_portante:  FYI just updated the probe test failure thingy we were talking about that Sam reported, root cuased it finally13:01
rieglflois there a way to restrict the max expire seconds on the tempurl plugin on the server side, without patching the plugin?13:05
portantepeluse_: cool I'll take a look when I get into the office in a bit13:07
*** zul has quit IRC13:08
*** zul has joined #openstack-swift13:08
*** psharma has quit IRC13:12
acolespeluse_: i was just looking at that. reached the same conclusion i think... tmp dir is created by the db replicator, tmp-N dirs shouldn't be expected.13:15
*** zhiyan is now known as zhiyan_13:17
*** uksysadmin has joined #openstack-swift13:25
*** itarchitectkev_ has quit IRC13:28
*** itarchitectkev_ has joined #openstack-swift13:33
peluse_acoles:  yup, thanks13:34
*** uksysadmin has quit IRC13:36
peluse_acoles:  and that tmp creation in db repl feels like a bit of a hack...13:36
*** pberis has joined #openstack-swift13:42
*** pberis has quit IRC13:42
*** pberis has joined #openstack-swift13:42
*** nacim has quit IRC13:51
*** kopparam has joined #openstack-swift13:55
*** 77CAADKRD has joined #openstack-swift13:56
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873613:57
*** scohen has quit IRC13:59
*** scohen_ has joined #openstack-swift13:59
*** kopparam has quit IRC14:00
*** lpabon has joined #openstack-swift14:01
*** kopparam has joined #openstack-swift14:04
*** nshaikh has quit IRC14:16
*** zhiyan_ is now known as zhiyan14:16
*** mwstorer has joined #openstack-swift14:21
*** uksysadmin has joined #openstack-swift14:23
*** agentleone has joined #openstack-swift14:24
*** itarchitectkev_ has quit IRC14:26
*** haomaiw__ has quit IRC14:27
*** haomaiwa_ has joined #openstack-swift14:28
*** zhiyan is now known as zhiyan_14:35
*** zhiyan_ is now known as zhiyan14:36
*** zhiyan is now known as zhiyan_14:37
*** zhiyan_ is now known as zhiyan14:37
*** tdasilva has joined #openstack-swift14:40
*** agentleone has quit IRC14:42
*** haomai___ has joined #openstack-swift14:43
*** haomaiwa_ has quit IRC14:46
*** thiago has joined #openstack-swift14:51
*** thiago is now known as Guest6734114:51
*** agentleone has joined #openstack-swift14:53
*** Guest67341 has quit IRC14:55
openstackgerritAlistair Coles proposed a change to openstack/swift: Restrict keystone cross-tenant ACLs to IDs  https://review.openstack.org/8643014:59
*** Krazy has joined #openstack-swift15:01
Krazywhat is the recommended backend for storing keystone token? mysql or memcached?15:01
*** tdasilva has left #openstack-swift15:04
*** chandan_kumar has joined #openstack-swift15:04
*** tdasilva_ has joined #openstack-swift15:04
*** nacim has joined #openstack-swift15:05
*** uksysadmin has quit IRC15:05
*** uksysadmin has joined #openstack-swift15:06
*** kopparam has quit IRC15:08
*** kopparam has joined #openstack-swift15:09
*** kopparam has quit IRC15:13
*** tdasilva_ is now known as tdasilva15:15
*** zhiyan is now known as zhiyan_15:32
*** uksysadmin has quit IRC15:32
*** mlipchuk has quit IRC15:43
*** nacim has quit IRC15:49
*** judd7 has quit IRC15:52
*** agentleone has quit IRC15:53
acolesKrazy: you may be best off asking in #openstack-keystone15:56
claygfinished sifting through review comments from yesterday15:57
Krazycool thanks16:03
*** Krazy has left #openstack-swift16:03
*** scohen_ has quit IRC16:03
peluse_clayg: awesome, there's a few more you up there as I'm sure you've noticed :)16:04
claygpeluse_: so the final patch you came up with for the db/rsync tmpdir thing was on gerrit or email?16:09
claygpeluse_: i don't get it, containers don't use per-policy tmp dirs...16:14
*** joeljwright1 has left #openstack-swift16:14
claygoh well, i'll look at it when i get in, bbiab16:15
peluse_clayg:  gerrit comment but I also sent patch via email.  You'll get it when you look at it...16:16
*** foexle has quit IRC16:19
*** gyee has joined #openstack-swift16:20
*** bkopilov has joined #openstack-swift16:29
*** Midnightmyth has joined #openstack-swift16:31
*** agentleone has joined #openstack-swift16:38
*** pberis has quit IRC16:42
*** zaitcev has joined #openstack-swift16:47
*** ChanServ sets mode: +v zaitcev16:47
*** pberis has joined #openstack-swift16:48
zaitcevclayg, peluse_: What's the best way to deliver fix-ups for SP? I thought I better show something rather than carping in comments.16:56
zaitcevI mean re-upload a patch in the middle of the chain or tuck a new one at the back?16:57
peluse_zaitcev:  clayg has preferred sending him stuff or comments (but not pushing directly) to make management of the chain, well, manageable.16:58
zaitcevpeluse_: got it16:58
*** agentleone has quit IRC16:59
*** agentleone has joined #openstack-swift17:02
*** agentleone has quit IRC17:07
*** shri has joined #openstack-swift17:08
*** nsquare has joined #openstack-swift17:13
*** mmcardle has quit IRC17:22
*** kopparam has joined #openstack-swift17:27
*** kevinc_ has quit IRC17:27
*** agentleone has joined #openstack-swift17:30
*** kevinc_ has joined #openstack-swift17:31
*** kopparam has quit IRC17:31
*** agentleone has quit IRC17:31
*** agentleone has joined #openstack-swift17:32
*** agentleone has quit IRC17:33
*** agentleone has joined #openstack-swift17:33
*** agentleone has quit IRC17:38
*** foexle has joined #openstack-swift17:44
claygpeluse_: i only really see that the patch goes out of it's way not to delete some dirs on the receiving end - but that doesn't seem like something that should be required17:55
claygpeluse_: if you stuff an empty disk back into a container server replication should do what it needs to do receive data from the other container nodes17:55
claygzaitcev: something that applies on 96026 would be ideal17:56
zaitcevclayg: will do17:56
*** chuck__ has joined #openstack-swift18:25
*** zul has quit IRC18:25
*** chuck__ has quit IRC18:26
*** zul has joined #openstack-swift18:26
*** sandywalsh has quit IRC18:30
*** grapsus_ has quit IRC18:30
*** gholt has joined #openstack-swift18:32
*** ChanServ sets mode: +v gholt18:32
*** sandywalsh has joined #openstack-swift18:32
*** agentleone has joined #openstack-swift18:32
*** agentleone has quit IRC18:37
*** foexle has quit IRC18:37
*** agentleone has joined #openstack-swift18:39
*** agentleone has quit IRC18:40
*** mkollaro has quit IRC18:46
peluse_clayg:  the problem is that test deletes the entire tree from suffix dir on down and then compares it to what it was after replciation runs.  Any dir other than accounts, conainters, objects-n or tmp that doesn't exist after repl runs will cause the assert.  The only reason tmp dir doesn't is because its created by the db repl18:46
peluse_clayg:  so yo could eiher create tmp-N in the repl every time, which makes little sense as its only needed to pass a probe test, or you can modify the test not to epxect dirs that have no reason to get created after wiping the tree out to somehow get created again...18:47
*** CaioBrentano has quit IRC18:48
*** mkollaro has joined #openstack-swift18:48
claygpeluse_: ok, I think i'm getting closer, but I like the part where the test delete's the entire tree from suffix on down - and the part where it validates the directories are what it expects18:50
claygso why doesn't it just expect the tmp-N dir?  Any why do only probetests need the tmp-N dir?18:50
peluse_clayg:  oops, not suffix dir, node level dir or whatever we call the level where accounts/containers/object--n live :)  Also the repl isn't recreating those others either, the test blindlyh waits 60 secs so the other services are re-creating their dirs respectively...18:57
peluse_clayg:  it doesn't expect tmp-N because rsync doesn't create it becuase it doesn't use diskFile, ssync creates it via DiskFile18:57
*** annegentle has joined #openstack-swift18:57
claygso the test only fails with ssync?  ssync always fails probetests for me because of the x-static-large-object thing...18:58
peluse_hmmm, the specific test that failed for me only failed for rsync, passes for ssync18:58
claygpeluse_: i'm sure it will all be clear once I manged to duplicate it - i'm only half way paying attention to the other window thats running probetests (first it failed because of ssync, then passed because default was 0, maybe this time...)18:58
claygpeluse_: yeah ok, i don't think that test uses object metadata18:59
peluse_:)  cool.  Here's the test that fails for me: test_replication_servers_working.py:TestReplicatorFunctions.test_main18:59
claygk18:59
peluse_driving into work so will be offline for 45 min or so...18:59
* peluse_ is getting off to a late start today :)18:59
*** annegentle has quit IRC18:59
*** tdasilva_ has joined #openstack-swift19:04
*** tdasilva has quit IRC19:05
*** foexle has joined #openstack-swift19:06
*** tdasilva_ is now known as tdasilva19:09
*** foexle has quit IRC19:13
*** DisneyRicky has quit IRC19:14
*** otoolee has quit IRC19:15
*** gholt has quit IRC19:23
*** gholt has joined #openstack-swift19:24
*** ChanServ sets mode: +v gholt19:24
*** kopparam has joined #openstack-swift19:30
notmynamegood morning, everyone. I was in an interesting meeting all morning, but I'm online now19:33
notmynameclayg: welcome back19:34
*** kopparam has quit IRC19:34
*** DisneyRicky has joined #openstack-swift19:36
*** ahale has joined #openstack-swift19:41
*** Midnightmyth has quit IRC19:43
*** gyee has quit IRC19:43
peluse_notmyname:  morning, anything interesting you can share?19:44
claygnotmyname: hi19:47
notmynamepeluse_: in general, it's all about getting very dense and efficient storage. there's a lot of parts to that, of course, but some of the maybe-not-so-crazy crazy ideas to explore have to do with exploring RDMA19:48
ahalei was hoping you had typo'd rDNA, as that would be really awesome but I guess you didn't :(19:52
notmynameahale: now I'm imagining creating synthetic organisms with a swift cluster (hey! it's already used to store genenome sequences)19:53
portantenotmyname: cool19:54
notmynameahale: imagine if you had a high-powered CPU that could deal with replication for a whole zone of object servers. especially if it could use RDMA to get the NIC to talk directly to the drive without needing to do even copy-to-kernel memory management or spend CPU cycles on it19:55
notmynamejust some long-term stuff to thing about19:55
portanteclayg: have you seen the comment I made about the container code using "is_deleted, then a sql statement, then another is_deleted call, then the update_change_at thingy"19:55
portantethinging about it now ...19:55
ahalenotmyname: pure, awesome, scifi stuff19:56
notmynameahale: or to rephrase, Swift being awesomer :-)19:56
portantewhen swift is that awesome we won't need spelling anymore19:57
ahaleyou say that but imagine the headache multi galactic replication would be over multi-region19:57
portanteahale: all we need is that flux capacitor ...19:58
notmynameahale: ya, there may also need to be a few improvements there :-)19:58
ahaleheheh19:58
*** annegentle has joined #openstack-swift19:58
notmynamebut kota has all that figured out already :-)19:58
ahalei look forward to that! :)19:58
peluse_notmyname:  that meeting wasn't with some of our guys was it??20:00
portanteI think he had his people talk to their people20:01
notmynamepeluse_: no, but I wouldn't be surprised if y'all are tangentally involved20:01
peluse_notmyname:  heh, its something we need to talk about for sure20:02
peluse_portante:  check your IRC pm20:02
portanteIRC pm?20:03
peluse_private messsage / chat whateever its called20:03
notmynameportante: I think he means check it tomorrow afternoon20:03
peluse_huh?  no, trying to ping portante now and not sure its working20:04
notmynamelol20:04
portante:)20:04
notmynamepeluse_: maybe he doesn't want to talk to you ;-)20:04
portanteI use emacs' "erc" client, and that appears to be a bit challenged in this area20:04
peluse_story of my life :)20:05
portantetry using "/query portante" and see if that works20:05
portanteeverybody is well to do so as well, don't want to exclude anyone. :)20:05
notmynameso what's up with storage policies today? will we be able to merge it this evening?20:08
portanteI am not comfortable with the container sql query stuff20:08
claygportante: sure i saw that20:10
zaitcevportante: in theory I'm working on that is_deleted and there's related thing I want to fix TODAY20:10
portantek20:10
*** elmiko has joined #openstack-swift20:17
elmikohey all, i've got a question or two about the TempAuth middleware. is that just for testing?20:17
*** wer has quit IRC20:19
*** AbyssOne_ has quit IRC20:19
*** torgomatic has quit IRC20:19
*** hurricanerix has quit IRC20:19
*** jd__ has quit IRC20:19
*** fbo_away has quit IRC20:19
*** portante has quit IRC20:19
*** russell_h has quit IRC20:19
*** briancline has quit IRC20:19
*** zaitcev has quit IRC20:19
*** pandemicsyn has quit IRC20:19
*** sileht has quit IRC20:19
*** mlanner has quit IRC20:19
*** occupant has quit IRC20:19
*** zacksh has quit IRC20:19
*** mhu has quit IRC20:19
*** bgmccollum has quit IRC20:19
*** zigo has quit IRC20:19
*** notmyname has quit IRC20:19
*** zhiyan_ has quit IRC20:19
*** chmouel has quit IRC20:19
*** anderstj has quit IRC20:19
*** joearnold has quit IRC20:19
*** glange has quit IRC20:19
*** sombrafam has quit IRC20:19
*** zaitcev has joined #openstack-swift20:20
*** wer has joined #openstack-swift20:20
*** AbyssOne_ has joined #openstack-swift20:20
*** torgomatic has joined #openstack-swift20:20
*** pandemicsyn has joined #openstack-swift20:20
*** sileht has joined #openstack-swift20:20
*** hurricanerix has joined #openstack-swift20:20
*** mlanner has joined #openstack-swift20:20
*** fbo_away has joined #openstack-swift20:20
*** jd__ has joined #openstack-swift20:20
*** portante has joined #openstack-swift20:20
*** occupant has joined #openstack-swift20:20
*** russell_h has joined #openstack-swift20:20
*** briancline has joined #openstack-swift20:20
*** joearnold has joined #openstack-swift20:20
*** glange has joined #openstack-swift20:20
*** dickson.freenode.net sets mode: +vvvv zaitcev torgomatic portante glange20:20
*** anderstj has joined #openstack-swift20:20
*** chmouel has joined #openstack-swift20:20
*** notmyname has joined #openstack-swift20:20
*** zigo has joined #openstack-swift20:20
*** zhiyan_ has joined #openstack-swift20:20
*** bgmccollum has joined #openstack-swift20:20
*** mhu has joined #openstack-swift20:20
*** zacksh has joined #openstack-swift20:20
*** dickson.freenode.net sets mode: +vv chmouel notmyname20:20
portanteelmiko: yes20:21
portantethere are brave souls that use it in production20:21
portanteat least, I have heard of a few in the past20:21
elmikoportante: ok, thanks. i was having a little trouble understanding the documentation but that clears it up :)20:21
*** Midnightmyth has joined #openstack-swift20:23
creihtyes please only use it for testing :)20:24
*** pberis has quit IRC20:24
*** chandan_kumar has quit IRC20:24
*** rieglflo has quit IRC20:24
elmikocreiht: i had a basic flaw in my understanding of how it worked. i thought it might be akin to a TempURL for an object.20:25
claygcreiht: well even then really only for development testing - it suck to bechmark your storage cluster then turn on auth for realzy and find out token validation is eating 10% of your request rate (or worse)20:25
creihtclayg: indeed20:26
*** chandan_kumar has joined #openstack-swift20:33
*** pberis has joined #openstack-swift20:36
*** rieglflo has joined #openstack-swift20:36
*** Midnightmyth has quit IRC20:54
*** tdasilva has quit IRC21:02
*** gyee has joined #openstack-swift21:04
*** lpabon has quit IRC21:05
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925021:06
*** scohen has joined #openstack-swift21:08
*** scohen has quit IRC21:09
*** annegentle has quit IRC21:13
*** foexle has joined #openstack-swift21:23
*** elmiko is now known as _elmiko21:27
claygtorgomatic: the line in the release notes to "turn on v2 endpoints responses" is sorta opposed to the comment "make v2 the default"21:28
torgomaticclayg: yeah, that's cause I'm stupid. I meant "turn off v2 endpoints responses"21:28
torgomaticso on by default with a note that says "if you're actually using this thing, set this variable to keep it working like before"21:29
claygtorgomatic: i guess what I sorta think I should do is make /endpoints/v1 and /endpoints/v2 both work then the config option is which one you get if you just say /endpoints21:29
*** _elmiko has left #openstack-swift21:29
claygtorgomatic: where "keep it working like before" ~= "doesn't provide all needed info on to work with storage policies"21:30
torgomaticclayg: yup, so it'll only work (i.e. provide all you need) if you haven't defined new storage policies yet21:30
claygtorgomatic: but that sounds like an argument to not go changing the default response unless we have to?21:32
*** kopparam has joined #openstack-swift21:33
torgomaticclayg: it's a tradeoff; if we set v1 by default, then upgrades are painless21:33
torgomaticif we set v2 by default, then new installs are painless21:33
*** kevinc_ has quit IRC21:33
torgomaticand there's a lot more Swift installs in the future than there are today21:36
Alex_GaynorSo teh swift docs say, about DLO: "It is best to upload all the segments first and then create or update the manifest. In this way, the full object won’t be available for downloading until the upload is complete."21:36
Alex_GaynorIf I /want/ the object to be downloadable when only some of the segments are uploaded, is ti fine to create the manifest and then start uploading segments?21:36
*** mkollaro has quit IRC21:36
torgomaticAlex_Gaynor: yeah, it won't break anything21:36
Alex_Gaynortorgomatic: perfect, thanks21:36
notmynameAlex_Gaynor: yes. but in both cases you are subject to the container listings21:36
Alex_Gaynornotmyname: meaning what?21:37
torgomaticit's not like Swift can tell when you're done uploading segments unless you've got it hooked up to a crystal ball ;)21:37
Alex_GaynorOh. Yeah, that's fine, that'll be the applications responsibility in my case21:38
notmynameAlex_Gaynor: if the container listings are taking a long time to be updated (eg in large or busy containers) the DLO manifest won't "work" until the listing is up to date. and that can take a while21:38
*** kopparam has quit IRC21:38
claygtorgomatic: well I think either default is fine if there's a way for the client to decide when it wants the storage_policy_index key - but I couldn't think of an obviously correct way to decide if /endpoints/v2.0 was asking for a v2 response or the account named "v2.0"21:38
Alex_Gaynormeaning, if I'm building a multi-tenanted system I probably want to give each tenant it's own container?21:38
torgomaticclayg: oh yeah, it's not just objects is it...21:39
notmynameAlex_Gaynor: is there a reason you wouldn't give each tenant it's own swift account?21:39
Alex_Gaynornotmyname: because I'm deploying this on top of an existing swift deployment in a large public cloud21:39
notmynameclayg: torgomatic: v1_endpoints/ and /endpoints21:39
notmyname?21:39
torgomaticnotmyname: maybe? now it's even more namespace devoted to this little niche middleware21:40
notmynameAlex_Gaynor: it's always a good idea to use many containers when storing application data in swift21:40
notmynametorgomatic: I'm jsut throwing stuff on the wall :-)21:40
torgomatic:)21:40
notmynameAFAIK zerovm are the only ones to use the endpoints middleware. I haven't seen anyone else talking about it. of course, somebody probably is somewhere21:41
torgomaticnotmyname: good point; any zerovm guys in here?21:43
notmynamenot that are speaking, and the #zerovm channel is very quiet21:43
*** kevinc_ has joined #openstack-swift21:43
torgomaticwell, so much for just asking them21:43
*** nsquare has quit IRC21:44
notmynamebut also looking at a swift release being with SP and being a major version bump, I'm much more ok with doing something backwards incompatible than eg on a 2.0->2.1 release or 1.12->1.13 release21:45
*** nsquare has joined #openstack-swift21:46
claygnotmyname: torgomatic: I don't think it needs to be backwards incompatible if I can come up with a good path parsing schema - would be trivial if it was versioned from the start...21:46
claygmaybe the option is just path_has_version and if you say no then you get v1 responses, if you say yes then you clients can either add /v1/ or parse 'endpoints' out of the dict21:47
claygstill no good way to update cluster and clients except at the same time21:48
claygbah21:48
claygI think some sort of goofy account_part_looks_like_a_version_if_you_squint method would probably good enough21:49
notmynameclayg: what about checking if the first split part has a reseller. or more simply, an underscore?21:50
*** pberis has quit IRC21:54
peluse_notmyname: I'm still learning to speak clayg but I kinda thought that's what he meant :)21:54
notmynamepeluse_: ya, he's a pretty smart guy21:54
claygnotmyname: well you'd either have to make list endpoints take a configurable list of reseller bits but underscore might work21:56
notmynameclayg: I think that's where the _if_you_squint part of your method comes in ;-)21:57
claygnotmyname: alright, that'll probably work21:59
portantenotmyname, creiht: your favorite topic, pbr: https://bugs.launchpad.net/keystone/+bug/133077122:25
notmynameportante: oh yes. that was a fun thing to read this morning. (turns out I'm subscribed to all things PBR in LP)22:26
torgomaticportante: notmyname: does this mean swift devs are Thought Leaders(tm)?22:30
claygtorgomatic: so the object server was already using per-policy tmpdirs in the rsync commands?22:31
torgomaticclayg: I think so?22:31
claygheh22:32
torgomaticlike I said, perhaps in the vicinity of a fix :)22:32
torgomaticclayg: although now that I look at it more, it seems like rsync drops temp files in the same dir as the destination, at least by default22:36
claygtorgomatic: idk, why would that be there in the replicator instead of the obj server?22:36
torgomaticand I don't see us setting -T or --temp-dir anywhere in obj/replicator.py22:36
torgomaticor the obj server22:36
claygtorgomatic: yeah i'm applying the patch and seeing if it fixes the failure OMM too22:37
torgomaticthis patch may be entirely the wrong way to go; it might be the case that enforcing the presence of a tmp-1 directory is the wrong thing for the probe test to do22:38
torgomaticand I'm just making a bogus directory to satisfy a bogus check22:39
claygtorgomatic: is that all peluse_'s change did?  was make the test not give a shit if rsync needs a tmp dir to sync objects or not?22:39
torgomaticclayg: I think so; let me go read it again22:39
torgomaticclayg: no, his patch changes the setup from nuking /srv/node/sdblah/* to nuking only /srv/node/sdblah/(accounts|containers|objects)22:41
torgomaticwhich would have the effect of leaving tmp-1 around so the later assertion is satisfied22:41
claygtorgomatic: looks like there's a bit before the delete that gets a list of shit on the existing node, and it explicitly excludes .pending files cause it don't care if the recieving end needs those - probably do the same for tmpdirs and call it a day22:43
torgomaticclayg: yeah, that sounds like a better fix22:43
*** nsquare has quit IRC22:44
*** nsquare has joined #openstack-swift22:45
claygtorgomatic: can you test this one -> https://gist.github.com/clayg/858efb1f472d72a472cc22:46
claygtorgomatic: WOMM22:46
torgomaticclayg: heh, I had almost that exact same diff written out over here, only I had a call to os.path.basename that you don't :)22:48
* torgomatic goes to try clayg's patch22:48
torgomaticclayg: works for me. Ship it!22:50
claygtorgomatic: oh i think i like the basename bit22:51
claygtorgomatic: oh well i guess that's from os.walk so they're not really full paths22:51
torgomaticclayg: yeah, exactly. I wasn't sure, so I put it in there out of paranoia with a note to see if it was really necessary22:52
torgomaticturns out it's not22:52
* clayg is really glad this wasn't a 4th bug related to the per-policy tmpdirs22:52
torgomaticseriously22:52
*** kevinc_ has quit IRC22:56
*** foexle has quit IRC23:03
*** kevinc_ has joined #openstack-swift23:05
mattoliverauMorning all23:07
*** scohen has joined #openstack-swift23:10
*** scohen has quit IRC23:11
shrihey all… have a quick question. Is there any such thing as Swift regions *without* keystone?23:13
torgomaticshri: Swift regions and Keystone regions have nothing to do with one another, so yes23:15
peluse_clayg:  just looked at the tmp dir patch above, looks good to me too!23:15
shritorgomatic : Thanks!23:15
torgomaticnp23:15
*** kopparam has joined #openstack-swift23:37
torgomaticis there a way to ask Gerrit for patches that I haven't reviewed the latest change set on?23:40
torgomaticI found reviewer:self, but that seems to apply to any change set23:41
*** kopparam has quit IRC23:43
*** openfly has quit IRC23:44
mattoliverautorgomatic: I use a search string: status:open project:openstack/swift NOT label:Code-Review>=0 label:Verified>=1,jenkins NOT label:Code-Review<=-1   NOT label:Workflow<=-123:48
mattoliverauYou can see if that helps, I have another more detailed for infra reviews, if you want that. :)23:49
torgomaticmattoliverau: thanks, I'll play with those search params23:49
mattoliverautorgomatic: this might be useful, its a blog entry written by Sean: http://is.gd/vN5k1q23:57

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