Thursday, 2014-06-26

*** kevinc_ has quit IRC00:01
*** sileht has quit IRC00:06
*** kenhui has joined #openstack-swift00:12
*** lpabon has quit IRC00:19
*** lpabon has joined #openstack-swift00:20
notmynameanyone here who know's about sphinx?00:20
torgomaticif you get its riddles wrong, it eats you00:20
notmynameI'm being eaten. It's a riddle to figure out how to reference files not in the docs/source dir00:21
*** dmorita has joined #openstack-swift00:22
*** lpabon has quit IRC00:24
*** matsuhashi has joined #openstack-swift00:24
*** jamiehannaford has quit IRC00:24
notmynameacoles: portante: I'm just about done with getting swift-specs set up. fighting one sphinx error now00:25
notmynameacoles: FYI, you'll have to do more than rebase your change. the dir structure I'm setting up will mean your spec file needs to move00:25
notmyname(it will be obvious to where)00:25
*** mwstorer has quit IRC00:31
zaitcevthe problem is, once the manual is processed, it's not in docs/source dir. You can always refer to file:///, but...00:34
notmynamezaitcev: so it needs to be in both locations?00:35
notmynamezaitcev: specifically in this case it's the project README.rst file and others like that00:35
zaitcevnotmyname: I mean that manual is supposed to be delivered somewhere, deployed on a server, etc. It makes no sense for it to refer to a file. Someone may be reading it on an iPad. So... Refer to http://gitrub.com/openstack/swift/README.rst at best.00:36
notmynamehmm00:36
*** kota_ has joined #openstack-swift00:37
notmynamethat makes sense for the final build/html/* files, but not for the `python ./setup.py build_sphinx` step00:37
notmynameeg in swift-specs, it would be nice that the generated docs include the contents of README, CONTRIBUTING, and the example template00:38
zaitcevI see00:38
notmynamebuild_sphinx should pull that in to build/html00:38
notmynamewhich can be shipped around00:38
zaitcevright, makes sense00:38
notmynamebut I can't find how to reference those high-level files (And it seems weird to include them twice)00:38
mattoliveraunotmyname: I don't know sphinx but with some google foo can't you just use the reletive path and the include? http://reinout.vanrees.org/weblog/2010/12/08/include-external-in-sphinx.html or there is this method http://stackoverflow.com/questions/10199233/can-sphinx-link-to-documents-that-are-not-located-in-directories-below-the-root (the non-symlink answer)00:41
notmynamemattoliverau: it seems you have better google-fu than me ;-)00:43
*** kenhui1 has joined #openstack-swift00:43
mattoliveraunotmyname: lol, the google-fu is string with this one :P00:44
notmynamestring, yarn. whatever ;-)00:44
*** kenhui has quit IRC00:44
*** shri has left #openstack-swift00:45
*** kopparam has joined #openstack-swift00:49
notmynamemattoliverau: it works!!! thanks00:49
mattoliverauwoo!00:49
openstackgerritJohn Dickinson proposed a change to openstack/swift-specs: Add the initial specs framework  https://review.openstack.org/10241700:51
notmynamemordred: FYI ^^00:52
zaitcevbut you added README.rst copy00:53
zaitcevignore that00:53
openstackgerritSamuel Merritt proposed a change to openstack/swift: Zero-copy object-server GET responses with splice()  https://review.openstack.org/10260900:53
notmynameacoles: portante: clayg: so that's the proposed swift-specs repo. check it out, especially the structure in README00:53
notmynamezaitcev: :-)00:53
*** kopparam has quit IRC00:53
*** baojg has joined #openstack-swift00:53
notmyname(I'd love comments from everyone, just those 3 have been bugging me about it)00:53
*** baojg_ has joined #openstack-swift01:01
*** baojg has quit IRC01:02
*** baojg_ has quit IRC01:05
*** kenhui1 has quit IRC01:17
*** mkollaro has quit IRC01:25
anticwdoes anyone here know if swift.common.internal_client is overly robust?01:35
anticwi'm asking because delete_object throws exceptions when it encouters a 404 ... which isn't something i expect or can see why at a glance from the code01:35
anticwwhat's more ... it throws urllib2.HTTPError not .ClientException ...01:36
*** nosnos has joined #openstack-swift01:47
*** mlipchuk has quit IRC02:11
*** nsquare has quit IRC02:21
*** bkopilov has quit IRC02:24
*** dmsimard_away is now known as dmsimard02:34
*** cm2 has quit IRC02:37
*** baojg has joined #openstack-swift02:45
*** kopparam has joined #openstack-swift02:52
*** kopparam has quit IRC02:57
*** mhu has quit IRC03:05
*** gvernik has joined #openstack-swift03:05
*** jyoti-ranjan has joined #openstack-swift03:07
yuanzaitcev: met some PasteDepoly issue on CentOS6.5. w/ PasteDepoly 1.5.2, swift refuses to start: Error trying to load config from /etc/swift/proxy-server.conf: pastedeploy>=1.3.3. but w/ PasteDeploy 1.5.0 everything seems OK03:08
*** mhu has joined #openstack-swift03:10
*** gvernik has quit IRC03:11
zaitcevyuan: try to download http://people.redhat.com/zaitcev/tmp/xattr_load.py and run python xattr_load.py| grep -i paste03:24
zaitcevyuan: honestly I have no idea what the problem may be, especially since we don't know where the offending PasteDeploy originates, if you corrupted anything with pip, etc.03:26
zaitcevConsidering that F20 has python-paste-deploy-1.5.0-10.fc20.noarch, I would suspect it's something CentOS people screwed up, or you picked it at any other rogue repo.03:27
zaitcev(or worse, installed with pip)03:27
yuanoh yes, i used 'pip install -r requirements'03:28
zaitcevso, what does the command above say?03:29
zaitcevon my system it's03:29
zaitcevPasteDeploy(pastedeploy) 1.5.0 /usr/lib/python2.7/site-packages03:29
zaitcevPaste(paste) 1.7.5.1 /usr/lib/python2.7/site-packages03:29
yuanno outputs but pip list can see PasteDeploy03:33
zaitcevThat doesn't count, obviously, because everyone else's loadapp() ends in pkg_resources. If they can't find what they need, the can't import anything.03:36
zaitcevWell, they probably could if they just... I dunno... used the right path or something.03:37
yuanhmm, should be something wrong with pip. let have a try again. thanks a lot03:37
zaitcevnp. Sadly I don't understand how the whole machinery works.03:38
portantenotmyname: looking ...03:38
zaitcevBut you can keep re-running the script I wrote and tweak things until it works.03:38
*** Kbee has joined #openstack-swift03:40
portantejust found out that you can add comments in gerrit to a whole file, not just a specific line03:42
anticwzaitcev: RHEL 6.x has python 2.7 available?03:47
*** dmsimard is now known as dmsimard_away03:47
zaitcevanticw: It should... RHEL 6 GA shipped with 2.6, but I think it moved to 2.7.03:48
zaitcevgo go gadget Koji03:48
anticwyum would find/install that right?  and if i don't see it then it's because i starting drinking earlier tonight?03:48
*** jkelly has joined #openstack-swift03:49
zaitcevhmm03:50
*** baojg has quit IRC03:50
zaitcevlooks like it's still 2.6, at python-2.6.6-53.el6 currently03:50
*** baojg has joined #openstack-swift03:50
zaitcevLast build was in January03:51
anticwupgrade to rhel7!03:53
anticwzaitcev: actually, i looked at rdo+selinux ... and comments there on what selinux brings to the table?03:53
*** kopparam has joined #openstack-swift03:53
*** matsuhashi has quit IRC03:54
*** zhiyan_ is now known as zhiyan03:55
*** baojg has quit IRC03:55
*** matsuhashi has joined #openstack-swift03:55
*** kopparam has quit IRC03:58
*** bkopilov has joined #openstack-swift03:59
*** matsuhashi has quit IRC03:59
*** Italux has joined #openstack-swift04:02
*** Italux has quit IRC04:02
*** jonkelly has joined #openstack-swift04:05
*** jkelly has quit IRC04:05
*** jonkelly is now known as jkelly04:05
*** baojg has joined #openstack-swift04:08
*** baojg has quit IRC04:08
*** baojg has joined #openstack-swift04:08
*** nosnos has quit IRC04:09
*** jyoti-ranjan has quit IRC04:22
*** nshaikh has joined #openstack-swift04:27
zaitcevanticw: I think SElinux does very little for proxy and nothing for a/c/o. We didn't have a proper remote exploit in years in Swift.04:29
*** jyoti-ranjan has joined #openstack-swift04:29
zaitcevanticw: the whole value is in need-based access, which mitigates security issues in apps. Very valuable for something like Firefox.04:30
*** matsuhashi has joined #openstack-swift04:37
*** nosnos has joined #openstack-swift04:37
*** kopparam has joined #openstack-swift04:44
jkellyit’s more useful where you are running many apps with different roles on the same server… basically its value is predicated on the fact that once a service on the system has been compromised that that service can be leveraged to access other data on the same system04:53
*** kopparam has quit IRC04:54
jkellyin a ‘cloudy’ system where servers/vms are more single-purpose, much of the value is eliminated04:54
jkellyone of the primary problems is that its utility is predicated upon a service being compromised in the first place… typically you are better of focusing on your front-line (firewall rules, network security, patching strategy) before worrying about something like SELinux.  Not to say there’s no value there, but I do question its off-the-shelf utility as RedHat implements it04:55
*** ajc_ has joined #openstack-swift04:59
*** psharma has joined #openstack-swift05:00
*** ppai has joined #openstack-swift05:10
*** ppai has quit IRC05:15
*** kopparam has joined #openstack-swift05:16
*** kopparam_ has joined #openstack-swift05:19
*** kopparam has quit IRC05:19
*** zaitcev has quit IRC05:20
*** jkelly has quit IRC05:22
*** gyee has quit IRC05:22
*** ppai has joined #openstack-swift05:28
*** kopparam_ has quit IRC05:33
*** kopparam has joined #openstack-swift05:33
*** kopparam has quit IRC05:40
*** kopparam has joined #openstack-swift05:44
*** jyoti-ranjan has quit IRC05:55
*** kota_ has quit IRC05:56
*** Kbee has quit IRC05:57
*** Kbee has joined #openstack-swift05:57
*** jyoti-ranjan has joined #openstack-swift06:00
*** jyoti-ranjan has quit IRC06:03
*** jyoti-ranjan has joined #openstack-swift06:06
*** jyoti-ranjan has quit IRC06:07
*** jyoti-ranjan has joined #openstack-swift06:09
*** matsuhashi has quit IRC06:13
*** zhiyan is now known as zhiyan_06:13
*** matsuhashi has joined #openstack-swift06:13
*** zhiyan_ is now known as zhiyan06:14
*** matsuhashi has quit IRC06:18
*** matsuhashi has joined #openstack-swift06:18
*** jyoti-ranjan has quit IRC06:18
*** jyoti-ranjan has joined #openstack-swift06:23
*** matsuhashi has quit IRC06:24
*** matsuhashi has joined #openstack-swift06:24
*** kopparam has quit IRC06:30
*** matsuhashi has quit IRC06:31
*** matsuhashi has joined #openstack-swift06:32
*** baojg has quit IRC06:34
*** matsuhas_ has joined #openstack-swift06:34
goodespeluse_: any hints where I can find specs for erasure coding support?06:35
*** baojg has joined #openstack-swift06:36
*** matsuhashi has quit IRC06:37
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix double request in simple client  https://review.openstack.org/10274606:42
*** sileht has joined #openstack-swift06:44
*** chandan_kumar has joined #openstack-swift06:47
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix KeyError on Storage Policy Container Sync  https://review.openstack.org/10274706:55
*** tsg has quit IRC06:56
*** jamiehannaford has joined #openstack-swift06:57
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix KeyError on Storage Policy Container Sync  https://review.openstack.org/10274706:58
*** haomaiwa_ has joined #openstack-swift07:04
bkopilovHi , Question about swift cross_domain07:04
bkopilovI am running automation and one of the swift tests fails  ( tempest upstream code )07:04
bkopilovfails on get_crossdomain_policy07:05
*** openstackgerrit has quit IRC07:07
*** haomaiw__ has joined #openstack-swift07:08
*** haomaiwa_ has quit IRC07:08
*** kopparam has joined #openstack-swift07:11
*** mmcardle has joined #openstack-swift07:14
*** kopparam has quit IRC07:15
*** kopparam has joined #openstack-swift07:16
*** kopparam has quit IRC07:16
*** jamiehannaford has quit IRC07:17
*** jamiehannaford has joined #openstack-swift07:18
*** foexle has joined #openstack-swift07:19
*** jamiehan_ has joined #openstack-swift07:26
*** jamiehannaford has quit IRC07:30
*** eglynn has quit IRC07:31
*** jamiehan_ has quit IRC07:33
*** jamiehannaford has joined #openstack-swift07:39
*** mlipchuk has joined #openstack-swift07:44
*** Kbee has quit IRC07:45
*** Kbee has joined #openstack-swift07:45
*** kopparam has joined #openstack-swift07:47
*** pconstantine_ has joined #openstack-swift07:51
*** kopparam has quit IRC07:52
*** nsquare has joined #openstack-swift07:55
*** joeljwright has joined #openstack-swift07:58
*** nsquare_ has joined #openstack-swift08:01
*** nsquare has quit IRC08:04
*** nacim has joined #openstack-swift08:05
*** eglynn has joined #openstack-swift08:20
cschwedeacoles: Good Morning Alistair! I reviewed your Keystone V3 swiftclient patch (https://review.openstack.org/#/c/91788/), looks good to me so far, just a minor nitpick. Let me know what you think about it08:22
*** kopparam has joined #openstack-swift08:23
*** jyoti-ranjan has quit IRC08:30
*** jyoti-ranjan has joined #openstack-swift08:39
*** matsuhas_ has quit IRC08:56
*** matsuhashi has joined #openstack-swift08:57
*** matsuhashi has quit IRC09:01
*** matsuhashi has joined #openstack-swift09:01
*** matsuhashi has quit IRC09:07
*** matsuhashi has joined #openstack-swift09:08
*** matsuhashi has quit IRC09:08
*** matsuhashi has joined #openstack-swift09:09
*** pconstantine_ has quit IRC09:10
*** mkerrin has quit IRC09:18
*** kopparam has quit IRC09:22
*** mkerrin has joined #openstack-swift09:25
*** dANOKELOFF has joined #openstack-swift09:37
*** kopparam has joined #openstack-swift09:37
*** dmorita has quit IRC09:40
*** nosnos has quit IRC09:52
*** baojg has quit IRC10:05
*** baojg has joined #openstack-swift10:06
*** matsuhashi has quit IRC10:09
*** mkollaro has joined #openstack-swift10:09
*** matsuhashi has joined #openstack-swift10:09
*** matsuhashi has quit IRC10:10
*** matsuhashi has joined #openstack-swift10:11
*** mkollaro has quit IRC10:14
*** mkollaro has joined #openstack-swift10:15
*** matsuhashi has quit IRC10:16
*** matsuhashi has joined #openstack-swift10:17
*** matsuhas_ has joined #openstack-swift10:20
*** matsuhashi has quit IRC10:21
*** kopparam has quit IRC10:25
*** matsuhas_ has quit IRC10:26
*** matsuhashi has joined #openstack-swift10:26
*** matsuhashi has quit IRC10:35
*** matsuhashi has joined #openstack-swift10:35
*** matsuhashi has quit IRC10:35
*** matsuhashi has joined #openstack-swift10:36
*** dANOKELOFF has quit IRC10:37
*** Kbee has quit IRC10:48
*** chandan_kumar is now known as chkumar24610:51
*** chkumar246 is now known as chandan_kumar10:53
*** chandan_kumar has quit IRC10:54
*** chandan_kumar has joined #openstack-swift10:54
*** kopparam has joined #openstack-swift10:56
*** kopparam has quit IRC11:03
*** matsuhashi has quit IRC11:05
*** matsuhashi has joined #openstack-swift11:05
*** haomaiw__ has quit IRC11:05
*** haomaiwang has joined #openstack-swift11:06
*** kopparam has joined #openstack-swift11:09
*** matsuhashi has quit IRC11:10
*** nsquare_ has quit IRC11:14
*** nsquare has joined #openstack-swift11:17
*** cm2 has joined #openstack-swift11:22
*** nsquare has quit IRC11:22
*** dANOKELOFF has joined #openstack-swift11:30
*** haomaiwang has quit IRC11:58
*** marcusvrn has joined #openstack-swift11:59
*** ppai has quit IRC12:02
*** baojg has quit IRC12:02
*** baojg has joined #openstack-swift12:03
*** mmcardle has quit IRC12:03
*** baojg_ has joined #openstack-swift12:05
*** baojg_ has quit IRC12:05
*** baojg_ has joined #openstack-swift12:06
*** baojg has quit IRC12:06
*** baojg_ has quit IRC12:10
*** ppai has joined #openstack-swift12:18
*** mmcardle has joined #openstack-swift12:21
*** kopparam has quit IRC12:21
jyoti-ranjanI have question related to Swift namespace of region and zone.12:23
jyoti-ranjanAs per my understanding, Swift region and zone are different from nova availability zone and keystone region. Am I correct?12:24
jyoti-ranjanCertainly, we can leverage nova availability zone to mape to Swift zone but I believe that these nsamespaces are different.12:24
*** openstackgerrit has joined #openstack-swift12:26
cschwedejyoti-ranjan: yes, these are different - in fact Swift regions and zones are completely independet and configured in the rings12:29
cschwedes/independet/independent/12:29
jyoti-ranjanI was just having idea of mapping nova availability zone to Swift zone. I was thinking of flow like this:12:30
jyoti-ranjan1) User creates 3 nova availability zone for Swift12:30
jyoti-ranjan2) Swift goes and provision node from that zone and expand ring if required12:31
jyoti-ranjanFor provisioning, we can use Ironic or something12:31
jyoti-ranjanDoes it make sense to do something like this as it will assist operator to use nova tags itself to define Swift zones12:32
jyoti-ranjanCertainly, it is not a good idea if customer wants to deploy only Swift12:32
jyoti-ranjanBut many installation has nova as well.12:33
jyoti-ranjanAny thoughts?12:33
*** kopparam has joined #openstack-swift12:33
*** bkopilov has quit IRC12:34
*** tdasilva has joined #openstack-swift12:34
cschwede2) would not be done by Swift; in fact all ring building is currently done either manually or by tools (puppet, chef, ansible, …).12:39
cschwedethus i think this is more a task outside of Swift - making it suitable for deployments with or without Nova12:40
cschwedeso where do you want to have this tool? In Horizon, or on the command line?12:41
cschwedejyoti-ranjan: ^^12:41
*** mkollaro1 has joined #openstack-swift12:43
*** mkollaro has quit IRC12:43
*** annegent_ has joined #openstack-swift12:44
*** annegent_ is now known as annegentle_12:44
*** eglynn is now known as eglynn-lunch-afk12:49
*** eglynn-lunch-afk has quit IRC12:54
*** baojg has joined #openstack-swift12:56
*** ajc_ has quit IRC13:00
*** Kbee has joined #openstack-swift13:05
*** annegentle_ has quit IRC13:06
*** ppai has quit IRC13:06
jyoti-ranjan<cschwede>We wanted to run that tool in separate node13:11
*** miqui has joined #openstack-swift13:11
jyoti-ranjancalling it as Swift controller13:11
jyoti-ranjanYes, you are very right that provisioning zone nodes can not be scopt of Swift. I wanted your advice on whether marrying nova availability zone with Swift zone is good idea or not.13:12
cschwedejyoti-ranjan: i think most deployments will use different zones for Nova and Swift, because you need different kind of hardware for the zones13:13
cschwedeand also different kind of backend network traffic13:13
cschwedeso i think mapping a Nova zone to a Swift zone is a special case, most likely they are different13:13
jyoti-ranjanI see13:14
jyoti-ranjanIt makes sense13:14
jyoti-ranjan<cschwede> Thank you very much.13:19
cschwedejyoti-ranjan: you’re welcome, let me know if you have more questions!13:19
*** kopparam has quit IRC13:25
*** kopparam has joined #openstack-swift13:25
*** zz_wasmum is now known as wasmum13:27
*** rook_ has joined #openstack-swift13:28
*** kopparam has quit IRC13:30
*** shausy has joined #openstack-swift13:30
peluse_goodes:  There's some design notes attached to one of the discussions on our discussion board: https://trello.com/c/t1lud5iA/3-ec-reconstructor-general-design-discussion13:36
* peluse_ forgot to mention yesterday - on vacation Wed-Fri this week13:38
peluse_goodes:  let me know if you have specific questions, others can help too.  I'll be more offline than online for the next two days though :)13:38
*** joeljwright has left #openstack-swift13:38
*** psharma has quit IRC13:40
rook_administering swift question for you guys:  would it "hurt" anything to set all the files in /etc/swift to root:swift ownership and 0640 permission ?13:41
*** eglynn-lunch-afk has joined #openstack-swift13:46
*** mkollaro has joined #openstack-swift13:46
*** mkollaro1 has quit IRC13:50
*** annegent_ has joined #openstack-swift13:55
*** jasond has left #openstack-swift13:56
*** dmsimard_away is now known as dmsimard14:00
*** annegent_ has quit IRC14:01
*** dmsimard is now known as dmsimard_away14:02
*** nacim has quit IRC14:04
*** zaitcev has joined #openstack-swift14:06
*** ChanServ sets mode: +v zaitcev14:06
*** annegent_ has joined #openstack-swift14:06
*** dmsimard_away has quit IRC14:08
*** dmsimard has joined #openstack-swift14:11
*** kenhui has joined #openstack-swift14:19
*** eglynn-lunch-afk is now known as eglynn14:22
*** mhu has quit IRC14:27
*** mhu has joined #openstack-swift14:28
wasmumgood morning14:30
wasmumanyone have some swift3 keystone time?14:30
*** jamiehannaford has quit IRC14:36
*** baojg has quit IRC14:39
peluse_goodes:  also, there's a lot more EC specific infomation at https://bitbucket.org/kmgreen2/pyeclib where the library that we'll be using is being developed14:42
*** nacim has joined #openstack-swift14:50
*** annegent_ has quit IRC14:52
*** annegent_ has joined #openstack-swift14:53
*** bkopilov has joined #openstack-swift14:53
*** tongli has joined #openstack-swift14:56
*** Kbee has quit IRC14:59
*** nshaikh has left #openstack-swift15:02
*** nshaikh has joined #openstack-swift15:07
*** annegent_ has quit IRC15:08
*** kevinc_ has joined #openstack-swift15:12
*** shausy has quit IRC15:24
*** JelleB is now known as a1|away15:26
*** lpabon has joined #openstack-swift15:29
*** annegent_ has joined #openstack-swift15:30
*** nacim has quit IRC15:30
*** mkollaro has quit IRC15:34
*** lpabon has quit IRC15:39
*** mkollaro has joined #openstack-swift15:40
*** annegent_ has quit IRC15:40
*** kopparam has joined #openstack-swift15:41
*** nacim has joined #openstack-swift15:43
*** jyoti-ranjan has quit IRC15:43
*** lpabon has joined #openstack-swift15:48
*** lpabon has quit IRC15:49
*** lpabon has joined #openstack-swift15:53
claygrook_: do you run processes as root or swift?  should be fine, nothing gets written into /etc/swift afaik.15:54
*** kopparam has quit IRC15:55
*** kopparam has joined #openstack-swift15:55
rook_clayg: I thought it would be fine too, however, when the workers fork under the swift user they can't read their conf file  (even though they are group readable) -- strange15:55
claygrook_: some instructions put the .builder files in /etc/swift and to write out new .ring.gz's if you're in /etc/swift looks like you'd have to run swift-ring-builder as root - but you should really be managing your .builder's on a seperate box and pushing the ring.gz's out - so as long as they end up readable it should be fine..15:56
claygawww man i thought all that permissions drop group shiz got fixed - what version are you running?15:57
rook_1.1015:57
claygso the commit that fixed that was c656e18; oh there's a bug #126947315:59
*** bvandenh has joined #openstack-swift15:59
clayglooks like that would be in ~1.1215:59
*** annegent_ has joined #openstack-swift15:59
claygwhich is not as long ago as I thought, current is 1.13 with 2.0 rc out16:00
*** kopparam has quit IRC16:00
*** chandan_kumar has quit IRC16:02
*** bvandenh has quit IRC16:04
claygrook_: ps no fair asking "would this work" if you've already tested it :P16:04
zaitcevI didn't notice that regression because I scp *.ring.gz16:05
*** gyee has joined #openstack-swift16:05
*** mwstorer has joined #openstack-swift16:11
*** gyee has quit IRC16:11
*** dANOKELOFF has quit IRC16:14
*** annegent_ has quit IRC16:15
*** annegent_ has joined #openstack-swift16:16
*** kenhui has quit IRC16:19
*** gyee has joined #openstack-swift16:20
*** lpabon_test has joined #openstack-swift16:23
*** kenhui has joined #openstack-swift16:24
*** kevinc_ has quit IRC16:31
*** kevinc_ has joined #openstack-swift16:31
*** zhiyan is now known as zhiyan_16:32
*** nacim has quit IRC16:34
goodespeluse_: I was wondering regarding meta data for ec objects - is the plan to store them with xattr with all the parts or store the meta data out-of-band in a seperate file?16:40
rook_clayg: :)16:41
*** lpabon_test has quit IRC16:47
*** pberis has joined #openstack-swift16:48
*** mmcardle has quit IRC16:48
goodespeluse_: i.e. will the performance of updating metadata on ec vs ring objects being slower/same/faster?16:55
*** AdnanCloud1 has joined #openstack-swift17:00
AdnanCloud1hello!17:01
AdnanCloud1this the right room for swift programming?17:01
cschwedeAdnanCloud1: Hello! Programming for Openstack Swift (the object storage) or Apple Swift?17:01
peluse_goodes:  there's no change to how obj metadata is managed wrt EC; there are a few additional items that are stored in xattrs though.  Details of the current plan are in that trello card attachment I mention ealier17:01
AdnanCloud1apple swift17:02
AdnanCloud1openstack swift.. never heard of this actually.. what is it17:03
cschwedeAdnanCloud1: No, this is for Openstack Swift, the object storage system.17:03
AdnanCloud1where is this used17:03
AdnanCloud1amazon?17:03
cschwedeAdnanCloud1: HP, Rackspacke, Disney, Cloudwatt, to name just a few big installations17:03
AdnanCloud1right okay..hmm let me google this17:04
cschwedeAdnanCloud1: http://docs.openstack.org/developer/swift/17:04
*** lpabon has quit IRC17:04
AdnanCloud1okay looks interesting... but i can only learn so much :) this will have to wait for another time17:05
*** lpabon has joined #openstack-swift17:06
Alex_Gaynorcschwede: Don't forget Wikipedia!17:06
cschwedeAlex_Gaynor: oh yes, probably one of the most widely used installations!17:07
notmynameAdnanCloud1: good morning (just got out of a meeting)17:08
notmynameAdnanCloud1: I think the apple swift language stuff is #swift-lang (or maybe that's the other swift programming language)17:08
notmynameAdnanCloud1: this swift that we work on--openstack swift--is a storage system. you can think of it like "S3 in your own datacenter"17:08
*** AdnanCloud1 has quit IRC17:09
*** AdnanCloud1 has joined #openstack-swift17:09
chmouelwe *should* really implement openstack swift in swift to make it not confusing17:09
notmynamechmouel: right ;-)17:10
*** annegent_ has quit IRC17:12
chmouelcschwede: nice goal :)17:13
*** annegent_ has joined #openstack-swift17:13
*** annegent_ has quit IRC17:18
* peluse_ out for most of the rest of the day....17:19
notmynameportante: thanks for looking at the specs repo proposal17:23
portantenotmyname: welcome17:24
notmynameclayg: have you taken a look at the specs repo proposal yet? how much do you care?17:24
notmynameportante: you think the proposed repo structure makes sense?17:24
portanteseems fine to be to start. I think we should get it in place and let folks starting working with it so we can tweak it sooner than later17:25
notmynameya. I definitely think it's a living thing17:25
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545317:27
*** kenhui has quit IRC17:29
*** kevinc_ has quit IRC17:32
*** kenhui has joined #openstack-swift17:38
*** kevinc_ has joined #openstack-swift17:39
claygnotmyname: i'm not sure exactly what i should be looking for?  I commit .rst docs when I want design feedback - seems stright forward.  I really just want to look at acoles docs for fast-post17:39
notmynameclayg: the proposed structure in the README is IMO the only real thing. and that the generate sphinx docs actually work (they do, I checked)17:40
*** mlipchuk has quit IRC17:40
*** chandan_kumar has joined #openstack-swift17:41
*** nsquare has joined #openstack-swift17:42
*** shri has joined #openstack-swift17:42
*** pberis has quit IRC17:45
*** annegent_ has joined #openstack-swift17:55
notmynameclayg: if you're ok with it (or don't care too much yet), then I'll go ahead an land it. if you want changes, let me know17:56
claygnotmyname: the .gitreview change s/object/swift is sorta annoying17:58
notmynameclayg: that it's called swift-specs instead of object-specs?17:58
*** mmcardle has joined #openstack-swift17:59
*** annegent_ has quit IRC18:00
claygnotmyname: running tox to build docs the first time fails -> https://gist.github.com/clayg/a5317b40563a5931e16e18:00
notmynameclayg: that's the pattern being adopted across openstack. eg nova-specs, keystone-specs, etc. not compute-specs, bare-metal-deployment-specs, identity-management-specs, etc18:00
notmynameclayg: and works the second time?18:01
claygnotmyname: yup, you can make it fail by 'rm -fr doc/build'18:01
claygnotmyname: run it twice and it's good to go18:01
claygmordred: ^ dunno why, probably not a big deal18:02
notmynameclayg: WOMM: https://gist.github.com/notmyname/b313913998bf2913ad2d18:02
claygnotmyname: yeah so i normally checkout from github and then git review and the one in github has object-specs so i had to fix it by hand (and remove the broken gerrit remtoe) to make git review work18:02
claygnotmyname: weird, git clean -fd too maybe?18:03
notmynamenope. works18:03
claygnotmyname: maybe i broke something trying to rebase acoles change onto the initial?18:04
notmynamemaybe a requirements thing. I removed some requirements as I was working on it but maybe got something installed?18:04
notmynamestill works if I `rm -rf .tox/`18:04
claygnotmyname: yeah that was me doing something stupid with like... monty's patchset 1 or something, i did the rebase right this time and it builds w/o errors everytime - sorry18:05
notmynameclayg: no worries. thanks for looking18:05
notmynameclayg: can you +2/+1 one it (are you logged in to gerrit?) if not, I'll push the button18:06
*** wasmum is now known as zz_wasmum18:07
*** AdnanCloud1 has left #openstack-swift18:08
*** kenhui has quit IRC18:16
*** kenhui has joined #openstack-swift18:17
*** openstackgerrit has quit IRC18:20
*** mlipchuk has joined #openstack-swift18:28
*** shri1 has joined #openstack-swift18:33
*** kenhui has quit IRC18:33
*** shri has quit IRC18:34
*** zz_wasmum is now known as wasmum18:35
*** pconstantine_ has joined #openstack-swift18:37
*** openstackgerrit has joined #openstack-swift18:38
*** openstackstatus has joined #openstack-swift18:43
*** ChanServ sets mode: +v openstackstatus18:43
*** shri1 has quit IRC18:46
*** mlipchuk has quit IRC18:46
*** nsquare has quit IRC18:46
*** lpabon has quit IRC18:46
*** tdasilva has quit IRC18:46
*** redbo has quit IRC18:46
*** charz has quit IRC18:46
*** MooingLemur has quit IRC18:46
*** annegentle has quit IRC18:46
*** infotection has quit IRC18:46
*** ekarlso has quit IRC18:46
*** chandan_kumar has quit IRC18:46
*** bkopilov has quit IRC18:46
*** miqui has quit IRC18:46
*** swat30 has quit IRC18:46
*** j_king has quit IRC18:46
*** mitz has quit IRC18:46
*** yuan has quit IRC18:46
*** zhiyan_ has quit IRC18:46
*** wer has quit IRC18:46
*** torgomatic has quit IRC18:46
*** hurricanerix has quit IRC18:46
*** jd__ has quit IRC18:46
*** portante has quit IRC18:46
*** briancline has quit IRC18:46
*** openstackgerrit has quit IRC18:46
*** mhu has quit IRC18:46
*** zaitcev has quit IRC18:46
*** goodes has quit IRC18:46
*** occupant has quit IRC18:46
*** DisneyRicky has quit IRC18:46
*** pandemicsyn has quit IRC18:46
*** mlanner has quit IRC18:46
*** zacksh has quit IRC18:46
*** bgmccollum has quit IRC18:46
*** zigo has quit IRC18:46
*** notmyname has quit IRC18:46
*** anderstj has quit IRC18:46
*** joearnold has quit IRC18:46
*** glange has quit IRC18:46
*** pconstantine_ is now known as pconstantine18:46
*** pconstantine is now known as 18WAABF3U18:46
*** openstackgerrit has joined #openstack-swift18:46
*** shri1 has joined #openstack-swift18:46
*** mlipchuk has joined #openstack-swift18:46
*** nsquare has joined #openstack-swift18:46
*** chandan_kumar has joined #openstack-swift18:46
*** lpabon has joined #openstack-swift18:46
*** bkopilov has joined #openstack-swift18:46
*** mhu has joined #openstack-swift18:46
*** zaitcev has joined #openstack-swift18:46
*** miqui has joined #openstack-swift18:46
*** tdasilva has joined #openstack-swift18:46
*** goodes has joined #openstack-swift18:46
*** swat30 has joined #openstack-swift18:46
*** redbo has joined #openstack-swift18:46
*** charz has joined #openstack-swift18:46
*** occupant has joined #openstack-swift18:46
*** j_king has joined #openstack-swift18:46
*** MooingLemur has joined #openstack-swift18:46
*** mitz has joined #openstack-swift18:46
*** yuan has joined #openstack-swift18:46
*** annegentle has joined #openstack-swift18:46
*** infotection has joined #openstack-swift18:46
*** DisneyRicky has joined #openstack-swift18:46
*** zhiyan_ has joined #openstack-swift18:46
*** ekarlso has joined #openstack-swift18:46
*** wer has joined #openstack-swift18:46
*** torgomatic has joined #openstack-swift18:46
*** pandemicsyn has joined #openstack-swift18:46
*** hurricanerix has joined #openstack-swift18:46
*** mlanner has joined #openstack-swift18:46
*** jd__ has joined #openstack-swift18:46
*** portante has joined #openstack-swift18:46
*** dickson.freenode.net sets mode: +vvvv zaitcev redbo torgomatic portante18:46
*** briancline has joined #openstack-swift18:46
*** joearnold has joined #openstack-swift18:46
*** glange has joined #openstack-swift18:46
*** anderstj has joined #openstack-swift18:46
*** notmyname has joined #openstack-swift18:46
*** zigo has joined #openstack-swift18:46
*** bgmccollum has joined #openstack-swift18:46
*** zacksh has joined #openstack-swift18:46
*** dickson.freenode.net sets mode: +vv glange notmyname18:46
*** mitz has quit IRC18:46
*** mitz- has joined #openstack-swift18:47
*** cschwede has quit IRC18:48
*** tanee has quit IRC18:48
*** dfg has quit IRC18:48
*** jeblair has quit IRC18:48
*** wkelly has quit IRC18:48
*** anticw has quit IRC18:48
*** zackmdavis has quit IRC18:48
*** creiht has quit IRC18:48
*** amandap has quit IRC18:48
*** mtreinish has quit IRC18:48
*** creiht has joined #openstack-swift18:48
*** ChanServ sets mode: +v creiht18:48
*** anticw has joined #openstack-swift18:48
*** dfg has joined #openstack-swift18:48
*** jeblair has joined #openstack-swift18:48
*** cschwede has joined #openstack-swift18:48
*** tanee has joined #openstack-swift18:48
*** amandap has joined #openstack-swift18:48
*** wkelly has joined #openstack-swift18:49
*** zackmdavis has joined #openstack-swift18:50
*** mtreinish has joined #openstack-swift18:50
*** openstackgerrit has quit IRC18:51
*** redbo_ has joined #openstack-swift18:51
*** openstackgerrit has joined #openstack-swift18:51
*** MooingLe1ur has joined #openstack-swift18:51
*** kevinc_ has quit IRC18:54
*** shri1 has quit IRC18:56
*** mlipchuk has quit IRC18:56
*** nsquare has quit IRC18:56
*** lpabon has quit IRC18:56
*** tdasilva has quit IRC18:56
*** redbo has quit IRC18:56
*** charz has quit IRC18:56
*** MooingLemur has quit IRC18:56
*** annegentle has quit IRC18:56
*** infotection has quit IRC18:56
*** ekarlso has quit IRC18:56
*** MooingLe1ur is now known as MooingLemur18:57
*** tdasilva has joined #openstack-swift19:00
openstackgerritClay Gerrard proposed a change to openstack/swift-specs: fix missing link for py-modules on index  https://review.openstack.org/10291319:03
openstackgerritClay Gerrard proposed a change to openstack/swift-specs: Updating containers on object fast-POST  https://review.openstack.org/10259219:03
*** kenhui has joined #openstack-swift19:04
*** rook_ has quit IRC19:08
*** kenhui has quit IRC19:11
*** shri1 has joined #openstack-swift19:19
*** mlipchuk has joined #openstack-swift19:19
*** nsquare has joined #openstack-swift19:19
*** lpabon has joined #openstack-swift19:19
*** charz has joined #openstack-swift19:19
*** annegentle has joined #openstack-swift19:19
*** infotection has joined #openstack-swift19:19
*** ekarlso has joined #openstack-swift19:19
*** joeljwright has joined #openstack-swift19:24
*** kevinc_ has joined #openstack-swift19:24
anticwso, in debugging hell i noticed something else ... if i delete an object ... and then check the container db --- the action there is not reflected19:27
anticwthe object itself looks deleted, there is a tombstone .... but the row in the container is untouched19:27
anticwa second delect, which gives 204 from the container server does what's expected ... and in this case the object server sees a tombstone and returns 404 not 20x ...  which the proxy reflects19:28
notmynameanticw: did you find a corresponding async pending file?19:28
anticwthere isn't one19:28
anticw100% sure of it19:28
anticwthis is 1.13.1 from RDO19:28
anticwit might be zaitcev ruined it :)19:29
notmynameanticw: just performed a PUT/DELETE/listing series on my box. works properly from what I can see19:31
notmynametombstone is created and it's not in the listing results anymore19:31
anticwnotmyname: did you check the deleted flag in the db?19:31
anticwactually, i didn't list ... i just did a delete then checked the db from another process (which is what container-sync is)19:32
anticwlet me put a list in there in case it's doing some 'flushing' in some unexpected way19:32
anticwyes ... doing a list causes it to flush19:32
anticwso it's a coherency issue with the sqlite3 code19:32
anticwand if i stop/kill the swift process it seems to not update the flag19:33
anticwlet me replace the list with a container-server restart ... arguably that should cause anything pending to get flushed19:33
anticwa process restart won't update the db (from another process PoV) but restart + list does19:35
anticwthis means if you do deletes, etc ... and then don't list from the container server, other processes won't see those most recent changes19:35
anticwthe swift cli is super chatty and so are a lot of clients, i suspect they mask this in many cases19:36
notmynameanticw: are you talking about the .pending file getting folded in?19:36
anticwyes19:36
anticw.pending is updated19:36
anticwnot the db19:36
anticwthe issue is when is .pending 'flushed' to the db19:36
*** kevinc_ has quit IRC19:37
anticw... why this matters is container-sync doesn't see the pending state19:37
*** wasmum is now known as zz_wasmum19:38
notmynameall updates to the db are put into the pending file. nothing is directly put in the db (normal read/write paths). .pending is flushed on some normal read/write paths, but is also update by a background daemon (checking which one...)19:38
*** annegent_ has joined #openstack-swift19:39
notmynameprobably the container-updator. still following code paths19:39
notmynames/or/er/19:39
*** kenhui has joined #openstack-swift19:39
anticwyeah, i see if i run the updater before container-sync it reacts19:40
anticwi though .pending was only used if the db was locked?19:41
anticwdid that change?19:41
notmynamewell, lots of things end up calling .merge_items(). listings, puts, reclaim, is_deleted checks, etc19:41
notmynameanticw: nope. been that way for a long time. all writes are written to the .pending record, then they are merged as a group19:41
anticwmakes sense ... but i'm sure in the past db updates were more timely other than db locks19:43
*** kenhui has quit IRC19:43
*** kenhui has joined #openstack-swift19:49
openstackgerritNirmal Thacker proposed a change to openstack/swift: If the devices path configured in container-server.conf contains a file then an uncaught exception is seen in the logs. For example if file foo exists as such /srv/1/node/foo then when the container-auditor runs, the exception that foo/containers is not a  https://review.openstack.org/9714819:51
*** kevinc_ has joined #openstack-swift19:52
*** mmcardle has quit IRC19:52
*** ChanServ sets mode: +v dfg19:53
*** pberis has joined #openstack-swift19:56
*** mlipchuk has left #openstack-swift19:58
*** kenhui has quit IRC20:04
notmynamejust found a new Swift user: http://www.razyr.net  (see https://twitter.com/RazyrOps/status/482250873658040321)20:06
*** tdasilva has quit IRC20:28
*** zz_wasmum is now known as wasmum20:34
anticwhttp://pastebin.com/p8sBfmMF20:37
anticwhas me scratching my head20:37
anticwcouple of issues, first is swift.common.internal_client.delete_oebject barfs had on 404s ...  the second is that when it does we get urllib2.HTTPError not .ClientException ... the third is that I can't catch urllib2.HTTPError20:38
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545320:39
*** wasmum is now known as zz_wasmum20:46
*** tongli has quit IRC20:54
*** pberis has quit IRC20:57
*** mmcardle has joined #openstack-swift20:59
*** cath6184 has joined #openstack-swift21:01
*** DisneyRicky has quit IRC21:03
*** DisneyRicky has joined #openstack-swift21:15
*** nthacker has joined #openstack-swift21:20
*** mmcardle1 has joined #openstack-swift21:21
*** mmcardle has quit IRC21:23
*** cath6184 has quit IRC21:24
*** annegent_ has quit IRC21:35
clayganyone know how to use keystone?  I have some swiftusertestX users, and some swifttenanttestX teants - but i'm not sure which user is in which tenant21:36
*** joeljwright has left #openstack-swift21:36
claygI *thought* user-role-list would tell me the answer, it seems to join the demo user to the demo tenant - but it's comin' up empty for these other swiftusertestX users21:37
claygoh hold the phone now, user-role-list seems to like me better when I pass --user AND --tenant21:39
claygoh yeah, looks like it's my test:tester test2:tester2 test:tester3 accounts :D21:40
claygBAM!  swift stat -v --os-username swiftusertest1 --os-tenant-name swifttenanttest1 --os-password testing21:41
*** kenhui has joined #openstack-swift21:45
*** shri has joined #openstack-swift21:46
*** shri1 has quit IRC21:46
*** redbo_ has quit IRC21:49
*** redbo has joined #openstack-swift21:49
*** ChanServ sets mode: +v redbo21:49
openstackgerritNirmal Thacker proposed a change to openstack/swift: If the devices path configured in container-server.conf contains a file then an uncaught exception is seen in the logs. For example if file foo exists as such /srv/1/node/foo then when the container-auditor runs, the exception that foo/containers is not a  https://review.openstack.org/9714821:55
*** mmcardle1 has quit IRC22:02
claygacoles: well, i tried :'(22:02
claygnotmyname: do we need to file a bug or something wrt to anne's email on the undoced options in swift?  i.e. http://docs.openstack.org/trunk/config-reference/content/container-sync-realms-configuration.html22:05
notmynameclayg: I must have missed that email. but if there are config options that aren't doc'd, then that should be a bug in LP to track it, I think. probably affecting both swift and docs22:06
notmynameannegentle: ^^??22:07
notmynamein case you missed it (like I did), the -infra team has changed the base image for all the gate jobs. it's now running ubuntu 12.04. the mailing list subject from 2 days ago was "Tempest testing for master is now running on Trusty"22:13
torgomaticso does this mean Swift is no longer tested on Precise or Lucid?22:19
*** kenhui has quit IRC22:20
claygtorgomatic: i test it on precise, lucid sometimes even22:22
claygtorgomatic: oh and cent sometimes too!22:22
notmynametorgomatic: sortof. stable releases (havana and icehouse) are still tested on precise. and oy26 tests are done on ceton622:22
torgomaticclayg: Sure; my all-in-one is precise right now. I'm just wondering about the gate stuff.22:22
notmynamebut for normal new code, trusty is the thing now22:22
claygyay the new thing!22:22
notmynames/yay//22:23
*** chandan_kumar has quit IRC22:24
notmyname"we are doing this because openstack TC has said we will target latest red hat and ubuntu and not break latest LTS"  <-- so any change in this practice will need to involve long-term discussions with the TC22:30
mattoliverauMorning22:31
notmynamemattoliverau: hi22:31
mattoliveraunotmyname: I watched your PTL presentation last night, nice work :) Must be wierd when your not in control of the slides.22:33
notmynamemattoliverau: ya, it's always been weird doing web-based presentations. the slide control and not seeing the audience are both pretty challenging, It hink22:34
*** annegent_ has joined #openstack-swift22:36
mattoliveraunotmyname: I bet, well you did well. Mikal has his today, I think, I should go and heckle :P22:36
notmyname:-)22:37
*** annegent_ has quit IRC22:42
openstackgerritMatthew Oliver proposed a change to openstack/swift: When a filesystem does't support xattr return a 507  https://review.openstack.org/9988322:42
*** kenhui has joined #openstack-swift22:45
*** annegent_ has joined #openstack-swift22:46
*** kenhui has quit IRC22:46
*** kenhui has joined #openstack-swift22:47
*** cm2 has quit IRC22:49
*** kenhui has quit IRC22:49
*** dmsimard is now known as dmsimard_away22:51
*** cm2 has joined #openstack-swift22:53
zaitcevmattoliverau: did you test the xattr thing 99883 on a real cluster using a wrong filesystem?22:57
zaitcevmattoliverau: I'm curious if _failsafe_read_metadata plugs your exceptions22:58
*** kevinc_ has quit IRC23:00
*** annegent_ has quit IRC23:09
openstackgerritSamuel Merritt proposed a change to openstack/swift: Zero-copy object-server GET responses with splice()  https://review.openstack.org/10260923:09
*** rpedde has quit IRC23:11
*** zz_wasmum has quit IRC23:11
*** rpedde has joined #openstack-swift23:11
*** zz_wasmum has joined #openstack-swift23:32
*** cm2 has quit IRC23:32
mattoliverauzaitcev: Sorry was tied up in a meeting.. I tested it briefly on my SAIO, and it logged 'ERROR:root:Filesystem does not support xattr...' to the storageN.error log. But it may need more testing, now that there are storage policies I can change replicas and see if a can get a 507 because qorum wont be reached.23:33
torgomaticyou'll never get a 507 from the object server due to quorum; object servers don't know about quorums23:34
*** kevinc_ has joined #openstack-swift23:34
mattoliverauwell there you go, well it errors to the log file then.23:34
*** eglynn has quit IRC23:42
*** mwstorer has quit IRC23:46

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