Thursday, 2014-05-08

portanteperhaps that patchbot could be modified to say something like "Clay Gerrard proposed a patch chain to openstack/swift, the first link is ..."00:00
portantewho maintains that patchbot?00:00
portantenotmyname:00:00
notmynameportante: https://github.com/notmyname/Patches00:01
*** fifieldt has joined #openstack-swift00:03
*** bach has quit IRC00:03
*** mwstorer has quit IRC00:04
*** matsuhashi has joined #openstack-swift00:07
*** bach has joined #openstack-swift00:07
*** bach has quit IRC00:07
*** bach has joined #openstack-swift00:08
portanteis that the one that does the announcements in the IRC for gerrit review posts?00:20
*** dmorita has joined #openstack-swift00:26
*** bach has quit IRC00:26
*** bach has joined #openstack-swift00:26
*** matsuhashi has quit IRC00:28
*** bach has quit IRC00:31
*** matsuhas_ has joined #openstack-swift00:31
*** bach has joined #openstack-swift00:32
*** bach has quit IRC00:34
*** matsuhas_ has quit IRC00:40
*** matsuhashi has joined #openstack-swift00:41
*** kevinc_ has quit IRC00:42
*** shri has quit IRC00:46
*** jasondotstar has joined #openstack-swift00:50
*** nacim has quit IRC01:05
*** Honghui has joined #openstack-swift01:21
*** alexpec has joined #openstack-swift01:24
*** shakamunyi has joined #openstack-swift01:26
*** keving has quit IRC01:29
ophukare we allowed to ask questions for help in here? I keep getting a unit test that fails. I've installed twice and it fails on the same step every time01:34
*** K_ has joined #openstack-swift01:37
*** K_ is now known as Kota01:40
portanteophuk: can you share a gist of the failure?01:41
portanteor pastebin or something?01:41
portanteand what version of swift you are installing?01:41
ophukportante: yup - one sec01:41
portantePerhaps if you are following the SAIO setup or not?01:41
*** shakamunyi has quit IRC01:42
ophukportante: here is the gist and the steps I took. The output of the unit tests is in unittest.log and every step I took to install it is in the first one. I had this problem earlier and they suggest a few commands for me to run so I have those there as well.01:43
ophukportante: https://gist.github.com/shade34321/2101c077430cd8b7516001:44
ophukportante: I am using the SAIO setup located here, http://docs.openstack.org/developer/swift/development_saio.html#common-dev-section01:44
*** nosnos has joined #openstack-swift01:44
ophukportante: I believe the problem is because the folder it's looking for doesn't exist and therefore neither does the file but I'm not sure why they don't exist01:45
*** BAKfr has quit IRC01:45
ophukportante: I have to leave work now - security guard is here. I'll be back on in a bit if you're still on and know of a solution.01:46
*** ophuk has left #openstack-swift01:46
portanteokay01:47
*** jasondotstar has quit IRC01:50
*** judd7_ has joined #openstack-swift01:55
*** judd7 has quit IRC01:56
*** shakamunyi has joined #openstack-swift01:57
*** keving has joined #openstack-swift01:59
*** elambert has quit IRC02:01
*** ophuk has joined #openstack-swift02:05
*** keving has quit IRC02:07
*** bach has joined #openstack-swift02:10
*** shakayumi has joined #openstack-swift02:15
*** zhiyan_ is now known as zhiyan02:17
*** shakamunyi has quit IRC02:19
ophukportante, I'm back02:31
peluse_ophuk:  Just looking at what you posted, I've run into that before due to running as root and simply stopped doing that :)02:35
ophukpeluse_, bah..ok. I'll create a swift user and a swift group and change the permissions for everything to swift:swift. and I think that's it off the top of my head02:36
ophukI should just be able to move the git clones over to the swift user's home directory but if not and I reclone them would i have to run setup.py again?02:37
peluse_ophuk:  yeah, every once in a while I forget I'm root and run tox and screw up /tmp permissions and have to go fix them...02:38
peluse_ophuk:  I'd just re-clone in your user dir and re-run, that's the easiest I think02:38
ophukpeluse_, ok, will that mess up the config files as well?02:38
ophukor those should be fine02:38
peluse_ophuk:  if you mean the swift.conf files, they will be OK02:39
ophukpeluse_, yeah - feel like I edited another file as well but I might be going crazy02:40
*** NM1 has joined #openstack-swift02:40
peluse_:)02:40
ophukthanks for the help! I'll do it in the morning and get back on and let you know if that solved my issue, hopefully it does and then I can start playing:D02:40
peluse_you bet, I'll be on as well as many others that would be happy to help02:41
ophukpeluse_, sounds good. Once again thank you for the help! Have a great night/day02:41
*** ophuk has quit IRC02:46
*** gmonkey has joined #openstack-swift02:50
*** Honghui has quit IRC02:54
*** shakayumi has quit IRC03:01
*** keving has joined #openstack-swift03:04
*** praveenkumar has joined #openstack-swift03:07
openstackgerritClark Boylan proposed a change to openstack/python-swiftclient: Use correct test command  https://review.openstack.org/9276003:07
*** elambert has joined #openstack-swift03:08
*** keving has quit IRC03:12
openstackgerritClark Boylan proposed a change to openstack/python-swiftclient: Use correct test command  https://review.openstack.org/9276003:12
*** Honghui has joined #openstack-swift03:18
*** matsuhashi has quit IRC03:24
*** shakayumi has joined #openstack-swift03:30
*** krtaylor has joined #openstack-swift03:33
*** bach has quit IRC03:40
*** nosnos has quit IRC03:41
*** ams0 has quit IRC03:44
*** ams0 has joined #openstack-swift03:44
*** Honghui has quit IRC04:05
*** shakayumi has quit IRC04:08
*** keving has joined #openstack-swift04:09
*** tzumainn has quit IRC04:10
*** gvernik has joined #openstack-swift04:13
*** gvernik has quit IRC04:14
*** Kota has quit IRC04:14
*** keving has quit IRC04:17
*** NM1 has quit IRC04:19
*** gmonkey has quit IRC04:24
*** zaitcev has quit IRC04:24
*** nosnos has joined #openstack-swift04:29
*** matsuhashi has joined #openstack-swift04:37
*** Honghui has joined #openstack-swift04:40
*** zhiyan is now known as zhiyan_04:46
*** haomaiwa_ has joined #openstack-swift04:52
*** ppai has joined #openstack-swift05:06
*** ams0 has quit IRC05:10
*** saurabh_ has joined #openstack-swift05:10
*** judd7_ has quit IRC05:11
*** keving has joined #openstack-swift05:14
*** ams0 has joined #openstack-swift05:14
*** ams0 has quit IRC05:14
*** ams0 has joined #openstack-swift05:16
*** ams0 has quit IRC05:16
*** keving has quit IRC05:18
*** ams0 has joined #openstack-swift05:19
*** matsuhashi has quit IRC05:19
*** ams0 has quit IRC05:20
*** matsuhashi has joined #openstack-swift05:20
*** ams0 has joined #openstack-swift05:21
*** ams0 has quit IRC05:21
*** ams0 has joined #openstack-swift05:22
*** ams0 has quit IRC05:22
*** gvernik has joined #openstack-swift05:22
*** ams0 has joined #openstack-swift05:27
*** ams0 has quit IRC05:27
*** ams0 has joined #openstack-swift05:28
*** otoolee has quit IRC05:29
*** ams0 has quit IRC05:29
*** nshaikh has joined #openstack-swift05:33
*** chandan_kumar has joined #openstack-swift05:37
*** Midnightmyth has joined #openstack-swift05:40
*** keving has joined #openstack-swift05:44
*** mlipchuk has joined #openstack-swift05:49
*** shakayumi has joined #openstack-swift05:52
*** keving has quit IRC05:52
*** mlipchuk has quit IRC05:54
*** shakayumi has quit IRC05:57
*** zhiyan_ is now known as zhiyan05:59
openstackgerritA change was merged to openstack/python-swiftclient: Make the function tests Python3-import friendly  https://review.openstack.org/9259306:04
*** zhiyan is now known as zhiyan_06:05
*** gyee has quit IRC06:06
*** zhiyan_ is now known as zhiyan06:08
*** zhiyan has left #openstack-swift06:08
*** mlipchuk has joined #openstack-swift06:09
*** Midnightmyth has quit IRC06:33
*** keving has joined #openstack-swift06:49
*** shakayumi has joined #openstack-swift06:53
*** keving has quit IRC06:57
*** shakayumi has quit IRC06:58
*** mkollaro has joined #openstack-swift07:07
*** elambert has quit IRC07:13
*** mmcardle has joined #openstack-swift07:19
mattoliverauI'm calling it a day, night all07:31
*** psharma has joined #openstack-swift07:37
openstackgerritYuan Zhou proposed a change to openstack/swift: Allow to deprecate policy  https://review.openstack.org/8682707:49
*** shakayumi has joined #openstack-swift07:54
*** keving has joined #openstack-swift07:54
*** matsuhashi has quit IRC07:54
*** matsuhashi has joined #openstack-swift07:55
*** shakayumi has quit IRC07:58
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix cross policy versioning DELETE  https://review.openstack.org/9150308:00
*** [1]gvernik has joined #openstack-swift08:01
*** gvernik has quit IRC08:02
*** [1]gvernik is now known as gvernik08:02
*** keving has quit IRC08:02
*** zzanc has joined #openstack-swift08:06
*** zzanc has left #openstack-swift08:13
*** acoles_ has joined #openstack-swift08:25
*** ChanServ sets mode: +v acoles_08:25
*** jamie_h has joined #openstack-swift08:32
acoles_chmouel: you around?08:37
chmouelacoles_: yes hello08:40
acoles_hi. thanks for taking a look at the keystone v3 swiftclient patch08:40
acoles_about reworking the interface - what did you have in mind?08:40
acoles_chmouel:^^08:42
chmoueli was thinking of at least splitting the auth functions08:42
chmouelhave an interface with abc perhaps08:43
chmouelthere is a lot i'd like to rework on swiftclient but unfortunately don't think that would be doable08:43
acoles_chmouel: so you mean the client.py interface? get_auth(), get_auth_v2(), get_auth_v3()?08:45
chmouelacoles_: are you going to be at the summit next week?08:46
acoles_chmouel: yes. and i was just thinking this may need a conversation there?08:46
chmouelacoles_: yeah that would be easier :)08:46
acoles_chmouel: also i think you suggested on openstack-dev getting folks together about keystoneauth changes (poilcy file etc). i'd like to join that discussion, and other hp guys.08:48
chmouelacoles_: yep, I didn't organise anything I was thinking we (enovance) and you guys (HP) talk together about it since i think we are the one most interested by it08:49
chmouelother are welcome obv08:49
acoles_chmouel: sounds good. we have the swift pod area all week i think.08:51
chmouelyes08:51
acoles_chmouel: so back to the v3 patch ... do you want this to wait and include any interface refactoring? its just i have this other patch to fix the ACL problem, and it depends on v3 in swiftclient for a functional test https://review.openstack.org/#/c/86430/508:53
chmouelacoles_: i think for now it get_auth_v3 should make a litlle bit cleaner even if it's a bit more duplication08:54
*** shakayumi has joined #openstack-swift08:54
acoles_chmouel: ok. i'll take a look at how that could work.08:55
acoles_chmouel: and speak next week, are you there mon-fri?08:56
chmouelacoles_: i have a few sessions (three) yeah between DS and the normal speak but need to check the times08:56
chmoueli think friday i have two fwo of them08:56
chmouelacoles_: i have to go afk now, ttyl08:59
acoles_chmouel: if you find a good free time then drop me email, or write on the pod signup.08:59
acoles_chmouel: ok, thanks08:59
*** shakayumi has quit IRC08:59
*** keving has joined #openstack-swift08:59
*** gvernik has quit IRC09:03
*** keving has quit IRC09:07
*** gvernik has joined #openstack-swift09:22
openstackgerritZhang Hua proposed a change to openstack/swift: Add profiling middleware in Swift  https://review.openstack.org/5327009:23
*** jasondotstar has joined #openstack-swift09:28
*** tzumainn has joined #openstack-swift09:35
*** Honghui has quit IRC09:36
*** jasondotstar has quit IRC09:46
*** jasondotstar has joined #openstack-swift09:50
*** zanc has quit IRC09:55
*** shakayumi has joined #openstack-swift09:55
*** shakayumi has quit IRC10:00
*** keving has joined #openstack-swift10:04
*** keving has quit IRC10:13
*** matsuhashi has quit IRC10:27
openstackgerritA change was merged to openstack/swift: Additional functional tests for Storage Policies  https://review.openstack.org/9150210:38
*** matsuhashi has joined #openstack-swift10:40
*** jasondotstar has quit IRC10:41
openstackgerritA change was merged to openstack/swift: Add write_fake_ring helper to test.unit  https://review.openstack.org/8815110:46
*** corrigac has quit IRC10:48
*** acoles has joined #openstack-swift10:48
*** ChanServ sets mode: +v acoles10:48
*** j_king_ has joined #openstack-swift10:50
*** fin1te_ has joined #openstack-swift10:53
*** cschwede_ has joined #openstack-swift10:54
*** j_king has quit IRC10:55
*** fin1te has quit IRC10:55
*** wkelly has quit IRC10:55
*** cschwede has quit IRC10:55
*** fin1te_ is now known as fin1te10:57
*** acoles_ has left #openstack-swift10:57
*** wkelly has joined #openstack-swift10:57
*** Honghui has joined #openstack-swift11:05
*** fin1te_ has joined #openstack-swift11:07
*** keving has joined #openstack-swift11:09
*** keving has quit IRC11:18
*** mmcardle has quit IRC11:21
*** matsuhas_ has joined #openstack-swift11:22
*** fin1te has quit IRC11:23
*** matsuhashi has quit IRC11:23
*** mkollaro has quit IRC11:23
*** omame has quit IRC11:23
*** fin1te_ is now known as fin1te11:23
*** haomai___ has joined #openstack-swift11:33
*** haomaiwa_ has quit IRC11:34
*** Honghui has quit IRC11:37
*** Honghui has joined #openstack-swift11:38
*** Trixboxer has joined #openstack-swift11:42
*** mkollaro has joined #openstack-swift11:42
*** ophuk has joined #openstack-swift11:59
*** foexle has joined #openstack-swift12:03
*** ppai has quit IRC12:03
ophukWhile running the unittest for swift during the SAIO installation instructions I'm getting a IOError, permission denied. Here is the output of the unittest run - http://pastebin.com/7YkgD8ft12:04
*** ondergetekende has quit IRC12:04
*** mmcardle has joined #openstack-swift12:05
*** keving has joined #openstack-swift12:14
*** ondergetekende has joined #openstack-swift12:18
*** ppai has joined #openstack-swift12:21
openstackgerritA change was merged to openstack/python-swiftclient: Only encode metadata for user customed headers  https://review.openstack.org/8835112:21
*** dmorita has quit IRC12:22
*** keving has quit IRC12:22
*** mkollaro has quit IRC12:36
*** mlipchuk has quit IRC12:36
*** Honghui has quit IRC12:37
*** PradeepChandani has quit IRC12:38
*** mlipchuk has joined #openstack-swift12:54
*** NM1 has joined #openstack-swift12:58
*** fifieldt has quit IRC13:06
*** tdasilva has joined #openstack-swift13:12
*** ppai has quit IRC13:12
portantehmm, who owns /tmp/backups and what is in it?13:13
portanteophuk: ^^^13:14
ophukportante: sorry - walked away for a second13:14
ophukportante: one sec13:14
ophukportante, drwxr-xr-x  2 root  root  4.0K May  7 17:55 backups13:14
portanteand the contents?13:14
portanteempty?13:14
portantemy guess is that there is a test bug where it expects to create /tmp/backups or something and that directory previously existed.13:15
portantethe test probably needs to be fixed to address that13:15
ophukportante: there is stuff inside of it...let me try to delete and rerun it then13:15
ophukportante: I completely missed the backup part of the path - I was still drinking my first cup of coffee when it ran:/13:16
portante:)13:16
portanteno problem13:16
portantevery understandable13:16
ophukportante: I am now working on my monster after finished my second cup of coffee...meeting in 5 minutes and it is very likely I'll fall asleep:)13:17
ophukso far so good:D13:17
ophukportante: that was the problem...passed this time:)13:19
ophuknow to see if I can finish setting this up and write a quick script to demo it during the meeting13:19
ophuklol13:19
ophukthanks for the help!13:19
*** keving has joined #openstack-swift13:19
*** gvernik has quit IRC13:20
portantewelcome13:21
ophukportante: nope...no demo today. Function tests failed - lol13:23
portantewhat is the failure?13:23
portantepropably an easy fix13:23
portanteb13:23
portanteophuk:13:24
*** tdasilva has quit IRC13:27
*** chandan_kumar has quit IRC13:28
*** tdasilva has joined #openstack-swift13:28
*** keving has quit IRC13:29
*** nosnos has quit IRC13:38
*** zanc has joined #openstack-swift13:38
*** chandan_kumar has joined #openstack-swift13:45
*** omame has joined #openstack-swift13:49
*** zul has joined #openstack-swift13:49
openstackgerritAlex Gaynor proposed a change to openstack/python-swiftclient: Declare that we support Python 3  https://review.openstack.org/9283113:52
*** mlipchuk has quit IRC13:53
*** bach has joined #openstack-swift14:02
*** bsdkurt has quit IRC14:10
*** tdasilva has left #openstack-swift14:10
*** psharma has quit IRC14:12
*** keving has joined #openstack-swift14:24
*** bsdkurt has joined #openstack-swift14:27
*** keving has quit IRC14:33
*** chandan_kumar has quit IRC14:34
*** gholt has quit IRC14:34
*** chandan_kumar has joined #openstack-swift14:34
*** gholt has joined #openstack-swift14:35
*** ChanServ sets mode: +v gholt14:35
*** judd7 has joined #openstack-swift14:40
*** tdasilva has joined #openstack-swift14:46
openstackgerritAndreas Jaeger proposed a change to openstack/python-swiftclient: Add "." for help strings  https://review.openstack.org/9152414:52
*** haomaiwa_ has joined #openstack-swift14:54
*** zaitcev has joined #openstack-swift14:54
*** ChanServ sets mode: +v zaitcev14:54
*** kevinc_ has joined #openstack-swift14:55
*** haomai___ has quit IRC14:56
*** nshaikh has quit IRC15:01
*** mrsnivvel has joined #openstack-swift15:08
*** elambert has joined #openstack-swift15:10
*** pberis has joined #openstack-swift15:14
*** Midnightmyth has joined #openstack-swift15:15
*** kevinc_ has quit IRC15:21
*** matsuhas_ has quit IRC15:25
*** matsuhashi has joined #openstack-swift15:25
*** kevinc_ has joined #openstack-swift15:26
*** haomaiwa_ has quit IRC15:29
*** keving has joined #openstack-swift15:29
*** matsuhashi has quit IRC15:31
*** chandan_kumar has quit IRC15:34
ophukportante: sorry - had to go sit in the meeting15:35
ophukportante: give me one sec to look it over before I post15:36
portantek15:36
*** keving has quit IRC15:38
*** foexle has quit IRC15:39
*** mwstorer has joined #openstack-swift15:41
ophukportante: oh wow...lots of errors... seems like a lot of 404 errors - here is the file http://paste.ubuntu.com/7416690/15:42
ophukportante: seems like I'm not able to connect to it via localhost, 127.0.0.1.15:44
ophukmaybe it's a firewall issue. The connection is being refused15:45
ophukportante: do I need to run swift-init all start as root or can I run it as a normal user?15:46
peluse_ophuk:  or I think you may get that if you have http_proxy set  (no, you don't need to be root to run swift-init)15:48
peluse_ophuk:  also, FYI, when I've accidentally run tox as root I've had to go fix my tmp dir permissions (delete everything, chown back to what they should be) or I'd get the same errors you are seeing - old files w/wrong permissions messing up future runs15:49
ophukpeluse_: ok. I'll delete everything in /tmp and reset to default permissions, 1777?15:49
ophukpeluse_: I don't remember setting http_proxy is that the default?15:50
peluse_ophuk:  yes, those are the perms I use, also make sure owner is root.  The http_proxy depends on your system, just do env | grep http to see if its set to something15:51
ophukpeluse_: env | grep http returned nothing. I set it and set the owner and group to root15:52
*** foexle has joined #openstack-swift15:52
*** mmcardle has quit IRC15:53
ophukpeluse_: why I asked if I need to be root, or sudo actually, is because when I run swift-init all start as my normal user I get this warning - WARNING: Unable to modify file descriptor limit.  Running as non-root?15:54
portanteophuk: so in my SAIO, I do the following to run the functional tests (if you have followed the SAIO correctly): resetswift; remakerings; startmain; ./.functests -v15:59
ophukportante: ok - I'll try that15:59
ophukportante: so there is a problem with my resetswfit - it doesn't like my16:04
portantegetting those scripts right from the SAIO makes a big difference16:09
ophukportante: so the first problem I have with it is that it's trying to umount /mnt/sdb1 - the mount point they use in the tutorial. Mine is /data - I'm looking through the config files now to see if I can find if I missed a location and didn't change it16:14
portantek16:14
ophukportante: is sdb1 referenced in remakerings that I need to change? I don't see that part in the tutorial but i see sdb1 referenced in it. I changed those, they looked like the points we create in this step - mkdir -p /srv/1/node/sdb1 /srv/2/node/sdb2 /srv/3/node/sdb3 /srv/4/node/sdb4 but I don't see where it states to change it. Changing it still doesn't fix the issue16:19
portanteso the SAIO document describes a suggested configuration, if you deviate from that, then you need to update all the references to match your deviation.16:20
portanteI ran into that as well, where I missed a few things in the setup that did not match16:21
portanteI'd recommend that for an initial use of SAIO, do exactly what it says to make sure you get it working.16:21
portantethen later, if you want to tweak the layouts and setup, you can make those changes and get it working again16:21
notmynamehttps://github.com/swiftstack/vagrant-swift-all-in-one is a simpler way to build an SAIO (thanks clayg and alpha_ori!)16:22
portanteyeah, that too!16:22
ophukportante: yeah I changed everything it said but missed the remakerings since it didn't state it need to be changed. Ok, I can go back and change the mount points but I'll still need to change a bit since i have no real sdb device16:22
portanteokay16:23
ophukportante: though as of right now I feel like it should work. Other than the inital creation part I only see sdb being referenced in the SAIO documentation in the use partition for storage part, resetswift, and remakerings script. And I've just changed sdb1 to data in all of those parts16:26
portanteokay16:26
ophukportante: and I think I'm an idiot. Does anything automatically copy the remakerings/resetswift script to /usr/bin ?16:29
portantenot user bin, but if you follow the setup, it will set all that stuff up for you16:30
ophukportante: making sure. I'm pretty sure in my original setup where I was using root I moved it all to /usr/bin instead of /root/bin16:31
ophukand thus running remakerings and resetswift was using those since they came in my path first16:31
portantemight be better moving it to the user's bin directory, which is where I believe I moved mine, but have to check16:32
*** keving has joined #openstack-swift16:35
ophukportante: I had I just never removed the original ones so I had two scripts but since one directory was in the path first it used that one16:35
portantek16:35
*** keving has quit IRC16:42
*** jamie_h has quit IRC16:51
*** jamie_h_ has joined #openstack-swift16:51
ophukalright much better...273 errors/failures down to 2 errors:)16:54
ophukdoesn't seem like it can use "PUT"16:55
*** jamie_h_ has quit IRC16:55
*** gyee has joined #openstack-swift16:56
*** jamie_h has joined #openstack-swift16:56
*** sasi has joined #openstack-swift16:58
portantehuh, can you share the 2 failures17:03
ophukportante: yeah one sec. http://pastebin.com/PPv4k6tw17:04
*** zanc has quit IRC17:05
*** sasi has quit IRC17:09
*** zanc has joined #openstack-swift17:19
ophukportante: here is the full output if you want that - http://paste.ubuntu.com/7417263/17:20
*** acoles is now known as acoles_away17:21
portantek sec17:21
*** keving has joined #openstack-swift17:23
*** shri has joined #openstack-swift17:24
*** j_king_ is now known as j_king17:24
portanteophuk: so these disks are XFS, right?17:25
portanteand we should look at the log files, /var/log/swift, to see what the 503 error message is about17:26
ophukportante: yes17:27
ophukportante: what am I looking for exactly in this log...I'm also assuming it's the all.log right?17:28
portantedepends on the choice you made setting up the SAIO, but yes, sure.17:28
*** zul has quit IRC17:30
ophukportante: all in one log and hourly proxy logs17:31
portanteokay, great, then let's look there for "Traceback" and see if there are any internal exceptions being thrown17:31
ophukportante: yeah there are a few. I'm going to clear this log, restart rsyslog, and re run the functest so all we have is this one test in it to17:32
portantek17:33
*** kevinc_ has quit IRC17:45
*** jamie_h has quit IRC17:46
*** jamie_h has joined #openstack-swift17:46
*** kevinc_ has joined #openstack-swift17:47
ophukportante: most of them seem to be device out of space errors. one I'm not sure - I gave more details on that one at the very bottom. http://pastebin.com/XajRtxCZ17:49
ophukthe device out of space I don't understand. It should have plenty of space - though I don't see it mounted any more so I can't see how much is left17:49
ophukportante: are UUID bad to mount with instead of say /dev/sda5?17:50
portantesec17:52
ophuktake your time17:53
zaitcevophuk: depends what your system is, but essentially in modern systems the topology is not fixed, so /dev/sda moves around. I find it the easiests to mount by label.17:54
portanteophuk: if they are not mounted, has the root volume filled up?17:54
ophukzaitcev: I have it mounted by UUID, ubuntu defaults to this but I do it also to make sure /dev/ doesn't move around17:55
ophukportante: no I'm using around 5GB it says of 100GB17:55
ophukbut that had to be the problem then becuase it just passed17:55
ophukodd17:55
*** elambert has quit IRC17:56
portantehmmm17:58
ophukcan UUID's change?17:59
*** tdasilva has quit IRC17:59
*** bach has quit IRC18:00
Alex_GaynorFor the folks who were curious why the swiftclient tests stopped running correctly on py3k, the answer is this issue: https://bugs.launchpad.net/testrepository/+bug/131760718:01
*** pberis has quit IRC18:03
ophukportante: I think I figured it out. When you format a partition the UUID changes. So you can have the entry in your fstab by UUID and need it by label most likely. Rerunning the test now to see if it fails then I'll get back to you on it18:03
portantek18:04
portantethis is for the loopback device, you mean?18:04
ophukportante: no it's a partition. I have one 160GB hard drive installed on this machine divided into three partitions, 100GB for / and roughly 58GB for /data18:08
*** wer has quit IRC18:08
ophukI also think partitions lose their label when formatted - mine has been lost it seems:/18:09
*** zul has joined #openstack-swift18:14
*** foexle has quit IRC18:14
*** pberis has joined #openstack-swift18:16
*** foexle has joined #openstack-swift18:16
*** wer has joined #openstack-swift18:17
*** bach has joined #openstack-swift18:18
*** bach has quit IRC18:21
*** bach has joined #openstack-swift18:23
*** kevinc_ has quit IRC18:23
ophukso since partitions lose their UUID and label when using mkfs.xfs how are we supposed to mount it?18:24
zaitcevone more reason to use labels18:26
ophukzaitcev: labels get lost as well - I had one18:28
*** bach has quit IRC18:28
*** bach has joined #openstack-swift18:40
ophukzaitcev: actually I might be wrong on the label part. I originally had put a lab I thought but I was testing it more and the label seems to persist across mkfs18:55
*** kevinc_ has joined #openstack-swift18:56
zaitcevI don't think it normally does but it's an explicit step, so your script is where it actually resides, and thus persists.18:56
*** Midnightmyth has quit IRC18:58
*** openstackgerrit has quit IRC19:04
*** openstackgerrit has joined #openstack-swift19:04
*** tdasilva has joined #openstack-swift19:13
*** foexle has quit IRC19:15
*** foexle has joined #openstack-swift19:17
*** foexle has quit IRC19:22
*** Trixboxer has quit IRC19:27
*** annegentle has joined #openstack-swift19:33
*** annegentle has quit IRC19:35
*** annegentle has joined #openstack-swift19:36
*** piousbox__ has quit IRC19:36
*** annegentle has quit IRC19:36
*** annegentle has joined #openstack-swift19:36
*** annegentle has quit IRC19:37
*** annegentle has joined #openstack-swift19:39
*** elambert has joined #openstack-swift19:40
openstackgerritA change was merged to openstack/swift: Fix cross policy versioning DELETE  https://review.openstack.org/9150319:42
*** bach has quit IRC19:43
*** jamie_h has quit IRC19:43
*** wasmum has joined #openstack-swift19:45
wasmumnginx or apache with mod_wsgi in front of keystone?  What is everyone using and what is preferred?19:45
*** bach has joined #openstack-swift19:46
*** bach has quit IRC19:48
portanteare you asking about swift services or keystone services?19:55
*** tdasilva has quit IRC19:57
wasmumportante: I am actually asking about keystone, authenticating for a swift cluster20:00
notmynameacoles_away: may be able to share what he's doing. he's got keystone with swift20:01
peluse_acoles_away:  is that kinda like "anchors away"?20:06
*** tdasilva has joined #openstack-swift20:13
*** Midnightmyth has joined #openstack-swift20:18
*** bsdkurt has quit IRC20:25
*** bsdkurt has joined #openstack-swift20:28
*** tdasilva has quit IRC20:31
*** keving has quit IRC20:31
*** keving has joined #openstack-swift20:34
*** bach has joined #openstack-swift20:44
peluse_clayg:  FYI I have a small patch to address (paritally) the expiring obj scenario you mentioned, will try to get it up there today but will likely be tomorrow.  Its a start, but likely will need some tweaking after I get a better udnerstaning of the reconslicer20:52
*** bach has quit IRC20:53
*** judd7 has quit IRC21:15
*** wasmum has quit IRC21:22
*** foexle has joined #openstack-swift21:24
*** foexle has quit IRC21:44
*** bach has joined #openstack-swift21:44
*** mrsnivvel has quit IRC21:45
*** Midnightmyth has quit IRC21:45
*** NM1 has quit IRC21:49
*** elambert has quit IRC21:55
*** elambert has joined #openstack-swift22:00
claygpeluse_: understood - thanks for looking into that - feel free to push up some unfinished work and I can jump start the review - i'm curious about what you found22:02
*** zul has quit IRC22:05
*** Diddi has quit IRC22:47
mattoliverauMorning all22:53
*** elambert has quit IRC22:54
openstackgerritChuck Thier proposed a change to openstack/swift: Add targeted config loading to swift-init  https://review.openstack.org/9293322:57
claygcreiht: the commit message makes it sound like the -c option?22:58
creihtclayg: yeah but this is more explicit22:58
creihtbecause if I have a public.conf and replication.conf22:58
creihtwhich one is -c 122:58
creiht:)22:58
* clayg sings his alphabet22:59
creihtyeah I know22:59
creihtbut this makes it more explicit for ops22:59
creihtyou don't have to think in your head is public 1 or 022:59
creihtplus if you see something like swift-init object-server.replication restart23:00
creihtin a script, you know what it is23:00
claygyeah sounds pretty good - sweet!23:01
creihtcool23:01
creihtI know there is overlapping functionality with -c23:01
creihtbut figured this would be better/less error prone for ops23:02
creihtwe are working on switching over replication to its own server23:03
creihtso that we can better test/control ssync23:03
claygno I think I love it - you should have ripped out -c ;)23:03
creihthah23:03
creihtI was worried that someone might have scripts with -c23:03
claygplus it looks like you can say swift-init object.1 object.2 restart - and -c isn't cumulative23:04
creihtahh yeah23:04
claygcreiht: unlikely no one knows how that shit works23:04
creihtlol23:04
creihtI didn't know it was even there until I started looking into this :)23:04
clayghehhe23:04
creiht If there is enough concensus, I'm fine with removing -c23:05
creihtbut I'll leave it up there for a bit to see what others think23:06
creihtI also need to doc it somehow, but couldn't find a good place for it23:06
creihtat least there are tests :)23:06
claygcreiht: heh, well no it probably has to stick around a release or so - but if we're gunna do doc we should doc the new hawtness - cool hack23:12
creihtyeah I'll work on that tomorrow thanks23:14
creihtand maybe add a note about -c deprecation23:14
openstackgerritA change was merged to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/8815223:15
claygyeah it's really good trick if you're doing seperate replication configs... kinda the only thing we've had for awhile... so we may not be only the people using it.23:15
*** occupant has joined #openstack-swift23:15
*** keving has left #openstack-swift23:26

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