Tuesday, 2015-12-15

*** zhill has joined #openstack-swift00:00
mattoliverauwell true, we could just use that :)00:00
notmynameah. meeting time00:01
*** haomaiwang has quit IRC00:01
mattoliveraunotmyname: tag team ;)00:02
*** lcurtis has quit IRC00:02
*** haomaiwang has joined #openstack-swift00:03
openstackgerritBen Martin proposed openstack/swift: Print min_part_hours lockout time remaining  https://review.openstack.org/25757700:03
blmartinAnd with that, good night00:05
*** blmartin has quit IRC00:06
*** Zyric has quit IRC00:18
*** pgbridge has quit IRC00:30
kota_good morning00:45
*** zhill has quit IRC00:50
notmynamemattoliverau: back00:51
notmynamemattoliverau: did you find anything?00:52
notmynamelooks like I did get an error on that test run00:53
mattoliveraustill failed for me on the SAIO that was failing, and it's memory is 1/2 swapped out, rebooting and doing it again incase it was in a bad state to begin with.00:57
mattoliverauI wonder if something has upgraded and not cleaning itself up as well as it used to.00:57
mattoliverauI did notice in my getting it to work the other week that the .kill() to the proxy server in in_process wasn't killing it properly, so I have a hack to close the socket.. but maybe the proxy still taking up memory.00:57
mattoliverauactaully maybe it's not swapped out... I'm getting confused with all my open tabs :P00:57
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
kota_looks like gates has an issue?01:02
*** openstack has joined #openstack-swift01:08
*** haomaiwang has quit IRC01:10
*** dmorita has quit IRC01:12
*** gyee has quit IRC01:17
then3rdnotmyname: I saw your message from a couple days ago about upgrading. I forgot this was currently icehous.01:20
notmynamethen3rd: have you done an upgrade on the cluster since you took it over?01:20
then3rdI have not. From what I've read it *should* be mostly straight forward, no?01:21
notmynameyeah, it is01:22
notmynamehttps://swiftstack.com/blog/2013/12/20/upgrade-openstack-swift-no-downtime/01:22
then3rdYep, looked at that earlier.01:22
notmynamethen3rd: you're upgrading from a pretty old version (relatively speaking), so you'll need to take some extra care with checking for config updates01:23
then3rdYou beat me to my next question. XD01:23
notmynamethen3rd: but there's no reason to do every upgrade01:23
notmynamethen3rd: and there's not any "upgrade here first, then go to the next version"01:24
then3rdSo, it is feasible to go directly to liberty?01:24
notmynamethen3rd: yes. but the further you upgrade, the more care you should take (in general)01:24
notmynamethen3rd: eg with 2.4.0 there were some dependency and config changes called out https://github.com/openstack/swift/blob/master/CHANGELOG01:24
notmynamethen3rd: and there have been various things moved to middleware (eg dlo and versioning) since the version you're running01:25
notmynamethen3rd: and there's some great stuff too that you'll probably want to use, like the "Allow 1+ object-servers-per-disk deployment" (also in 2.4.0)01:26
notmynamethen3rd: but the first goal is to upgrade without adding anything new. get that working, only then make it work better01:26
*** dmorita has joined #openstack-swift01:27
notmynamethen3rd: if you didn't want to go in one big upgrade, then I'd recommend going to 2.0 first, then 2.5.001:27
then3rdExactly. I'd like to get it upgraded without it getting fubar'd01:27
notmynamethen3rd: of course :-)01:27
notmynamethen3rd: I'd suggest doing in in a lab or VM first01:28
then3rdIf I had that luxury.. another one of my goals.01:28
notmynameheh01:28
notmynamethen3rd: are you on 1.11 or 1.13?01:29
then3rdyeah.. someone else built this, quit, and left zero notes.01:29
then3rd1.13.101:29
notmynameok. so 2.0 is easy and will "just work"01:29
then3rdFrom everyting I have seen, this is a pretty standard install. I believe he followed the openstack.org install guide, so configs will probably be copy-edit-paste. Ultimately, I'd like to deploye/manage this with Ansible.01:31
notmynamethen3rd: then you should talk to mattoliverau or tdasilva about that. i think they both have ansible playbooks for swift01:31
notmynamethen3rd: ok, I reviewed the changelog. nothing jumps out that would cause your existing configs to break with newer code01:32
notmynamethen3rd: so upgrading to the new version should be relatively painless01:32
notmynamethen3rd: and after than you can update the config file for new settings01:33
then3rdThat's good news.01:33
notmynamethen3rd: of course, standard disclaimer, some guy on the internet telling you it will work is no guarantee that it will. be sure to check it yourself ;-)01:33
notmynamethen3rd: looks like the notes for 2.0 and 2.4.0 are probably the most important ones01:34
notmynamefor upgrades01:34
then3rdRandom guy on the internet is still more reputable than anything else I can come up with. ;-)01:34
*** lyrrad has quit IRC01:34
notmynamethen3rd: and please ask about anythign you need more clarity on. measure twice, cut once, and all that01:34
then3rdCertainly. I really apreaciate the help.01:35
notmynameok, time for me to bike home01:36
then3rdBe safe, ttyl!01:37
*** rminmin has joined #openstack-swift01:37
*** garthb_ has quit IRC01:39
*** haomaiwang has joined #openstack-swift01:40
mattoliverauthen3rd: we (rackspace private cloud) deploy using ansible, so feel free to ask me questions too ;)01:40
openstackgerritMerged openstack/swift: Merge branch 'master' into feature/crypto  https://review.openstack.org/25741601:42
then3rdmattoliverau: thanks! I think my trouble has been finding playbooks that are complete and easy to use, yet not overly complex. I'm still probably less than 100 hours hands-on with asnible, so it takes a while to review what exactly the roles are doing.01:43
*** Zyric_ is now known as Zyric01:46
then3rdSwiftacular looked promising but seems to revolve around vagrant. the official openstack-ansible project seems like its best supported but looks like a chore to get working.01:46
then3rdI think it was openstack-ansible I got working though. Only successfull with the all-in-one lxc build.01:48
*** rminmin has quit IRC01:48
*** badari has quit IRC01:52
mattoliverauthen3rd: openstack-ansible is what we RPC use. I have my own simpler ansible setup I use for building test clusters, but it's definitely not feature full, infact it's only what I've getten around to writting as I need to test things :)01:52
mattoliverauthen3rd: but if you want to follow the openstack-ansibe root, I can introduce you to the people who work on it day to day :)01:54
*** badari has joined #openstack-swift01:54
then3rdI've thought about doing something similar. I don't think we need to be able to turn every knob right now.. it could be easier to add in thigs as-needed.01:54
mattoliverauthen3rd: where are you based?01:54
then3rdUtah, USA.01:54
then3rdSince I'm in a time crunch, I won't be able to work on stuff like automation until February. I'll make it a goal to automate the dev environment. Should lead to automating production.01:56
mattoliverauthen3rd: good idea :)01:56
mattoliverauthen3rd: if you want to go down the OSA (openstack ansible path) then in Feb I can introduce you to the people in the know ;)01:57
then3rdThat is, if I don't find somewhere that actually pays their admins enough first. :D01:58
mattoliveraubut we're always avalabile here to help in anyway we can01:58
mattoliveraulo01:58
then3rdCertainly!01:58
mattoliverauthen3rd: *cough* rackspace *cough* :P01:58
then3rdI do have at least one friend in rackspace devops, San Antonio... I should see if he has the hookup. hehe02:00
*** haomaiwang has quit IRC02:01
*** eikke has quit IRC02:02
mattoliverauthen3rd: cool, and if you want to continue doing openstack devops (OSA even) I can always pass something on or make initial intros ;)02:02
*** kei_yama has quit IRC02:02
*** kei_yama has joined #openstack-swift02:03
mattoliverauanyway I've had lunch so am heading home to debug exciting testr issues. bbs.02:03
then3rdI'm all for exploring my options.. this place struggles to really be truly innovative.02:04
then3rdAnd so far, I'm loving everything that openstack can do. Anyway, catch you later02:05
*** rvasilets__ has quit IRC02:05
*** asettle has quit IRC02:11
*** dewsday has joined #openstack-swift02:11
*** dewsday is now known as asettle02:11
*** klrmn has quit IRC02:14
*** asettle has quit IRC02:14
*** asettle has joined #openstack-swift02:15
*** noark9 has joined #openstack-swift02:20
*** mtreinish has quit IRC02:20
*** mtreinish has joined #openstack-swift02:20
*** changbl has quit IRC02:21
*** alexandra has joined #openstack-swift02:26
*** haomaiwang has joined #openstack-swift02:29
*** asettle has quit IRC02:30
*** alexandra is now known as asettle02:30
homattoliverau: quick question about doc/source/development_auth.rst. in the doc there is a word "Cross Origin RequestS". does it mean "Corss Origin Requests" or does it have special meaning?02:32
notmynameho: it's for CORS, but it's supposed to be Cross-Origin Resource Sharing02:34
honotmyname: my question is why last charactor is large S02:35
notmynameho: right. it's a mistake02:35
*** changbl has joined #openstack-swift02:35
honotmyname: i see. i would like to know there is a special meaning. thanks!02:35
notmynameho: someone was trying to fit it to CORS02:35
honotmyname: oh, i see. is it better to fix it or keep it?.02:37
notmynamefix it. it's wrong the way it is now02:37
honotmyname: OK. i will submit it soon.02:39
then3rdnotmyname: Dumb question.. I finally managed to locate the ubuntu-cloud repos for the different releases (http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/juno/main). Are there packages for other "minor" releases too? i.e: 2.0 mentioner earlier? (https://launchpad.net/swift/juno/2.0.0)02:39
notmynamethen3rd: no. it seems that most ditros have only chosen to package (most of) the openstack major releases02:39
notmynamemost deployers end up building their own packages to have some more control over it02:40
notmynamethen3rd: what OS are you on/02:40
then3rdubuntu 14.0402:41
openstackgerritHisashi Osanai proposed openstack/swift: Fix a typo in development_auth.rst  https://review.openstack.org/25765402:41
notmynameho: could you make it say "Cross-Origin Resource Sharing (CORS)"?02:43
honotmyname: OK i will change it.02:43
notmynamethen3rd: hmm.. the place I was going to point you to hasn't been updated a while02:44
notmynamethen3rd: do they have a 2.2.0?02:45
notmynamethen3rd: here's some info that might be handy https://wiki.openstack.org/wiki/Swift/version_map02:45
*** ianbrown has quit IRC02:46
*** ianbrown has joined #openstack-swift02:47
notmynamethen3rd: so if you wanted to take 2 upgrade steps, you might try 2.2.0 and 2.5.002:47
then3rdYep. Only thing I'm concerned about may be keystone v3. I won't break my v2 auth, right?02:47
notmynamenope02:47
then3rdCool. In the event I do break something, is there any sort of backup (simply make a copy of /etc/swift ?) I should be making first? If it doesn't work, should I expect any downgrade complications?02:49
then3rdnotmyname: I know these are pretty generic questions, but they've been hard to find answers to.02:50
notmynamethen3rd: from looking at the changelog earlier, and from memory, there aren't any on-disk format changes in the range you're looking at. so I don't anticipate any downgrade complications02:50
notmynamehowever, if you add new storage policies, you won't be able to get at those anymore if you downgrade02:50
notmynamehmm02:51
openstackgerritHisashi Osanai proposed openstack/swift: Fix a typo in development_auth.rst  https://review.openstack.org/25765402:51
notmynamethere's a not in the 2.4.0 release about versioning and downgrading there02:51
notmynameho: thanks02:52
notmynamethen3rd: that's the kind of thing you'll have to watch out for on downgrades02:52
notmynamethen3rd: we're generally very careful at keeping an upgrade path and letting you do that without any issue02:53
then3rdI see. The client would like to run whatevever is latest anyway, so downgrading is just a backout plan if I discover I'm completely incompetent.02:53
then3rd:P02:54
*** sanchitmalhotra has joined #openstack-swift02:56
then3rdI think I'll chew on this a little more tonight, put together a change control procedure and try this tomorrow. Again, thanks for the pointers.02:57
*** haomaiwang has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
janonymousmorning03:03
mattoliveraujanonymous: morning03:05
hojanonymous: morning!03:05
janonymousPlease find links for review if somebody can lend some time:  https://review.openstack.org/#/c/208222/  , https://review.openstack.org/#/c/254276/03:09
janonymous:)03:13
openstackgerritMerged openstack/python-swiftclient: Delete python bytecode before every test run  https://review.openstack.org/25221003:25
then3rdnotmyname: another question I'm not having much luck with. My object-server nodes don't seem to have any swift logs. It seems that log_requests defaults to true, but I don't have anything swifty in /var/log. There are no extra logging options set in any of my configs.03:26
then3rdoh hey. it goest to syslog aka /dev/log. mystery solved.03:28
then3rds/goest/goes/03:28
*** klrmn has joined #openstack-swift03:30
*** pgbridge has joined #openstack-swift03:33
*** haomaiwang has quit IRC03:40
*** kei_yama_ has joined #openstack-swift03:44
*** kei_yama has quit IRC03:44
*** venkat has joined #openstack-swift03:45
*** ppai has joined #openstack-swift03:50
*** yatin has joined #openstack-swift03:50
*** david-lyle has quit IRC03:50
*** david-lyle has joined #openstack-swift03:58
*** david-lyle has quit IRC04:01
*** david-lyle has joined #openstack-swift04:02
*** km has quit IRC04:02
*** km has joined #openstack-swift04:03
*** links has joined #openstack-swift04:07
*** proteusguy_ has quit IRC04:18
*** haomaiwang has joined #openstack-swift04:23
*** openstackstatus has quit IRC04:24
*** openstack has joined #openstack-swift04:26
*** ChanServ sets mode: +v openstackstatus04:26
*** SkyRocknRoll has joined #openstack-swift04:29
*** proteusguy_ has joined #openstack-swift04:35
*** haomaiwang has quit IRC04:36
*** haomaiwang has joined #openstack-swift04:38
*** haomaiwang has quit IRC04:39
*** 17WABA6GG has joined #openstack-swift04:39
*** 17WABA6GG has quit IRC04:40
*** 21WAAHVK2 has joined #openstack-swift04:40
*** 21WAAHVK2 has quit IRC04:41
*** 14WAAGEZK has joined #openstack-swift04:41
*** 14WAAGEZK has quit IRC04:42
*** haomaiwa_ has joined #openstack-swift04:42
*** haomaiwa_ has quit IRC04:43
*** haomaiwang has joined #openstack-swift04:43
*** haomaiwang has quit IRC04:44
*** haomaiwang has joined #openstack-swift04:44
*** haomaiwang has quit IRC04:45
*** 21WAAHVNZ has joined #openstack-swift04:45
*** 21WAAHVNZ has quit IRC04:46
*** 14WAAGE11 has joined #openstack-swift04:46
*** 14WAAGE11 has quit IRC04:47
*** 21WAAHVO2 has joined #openstack-swift04:47
*** 21WAAHVO2 has quit IRC04:48
*** 21WAAHVPK has joined #openstack-swift04:48
*** 21WAAHVPK has quit IRC04:49
*** 14WAAGE3N has joined #openstack-swift04:49
*** 14WAAGE3N has quit IRC04:50
*** haomaiwa_ has joined #openstack-swift04:50
*** haomaiwa_ has quit IRC04:51
*** 18WABIL7Z has joined #openstack-swift04:51
*** 18WABIL7Z has quit IRC04:52
*** haomaiwang has joined #openstack-swift04:52
*** haomaiwang has quit IRC04:53
*** haomaiwa_ has joined #openstack-swift04:53
*** haomaiwa_ has quit IRC04:54
*** km has quit IRC05:31
*** km has joined #openstack-swift05:32
*** takashi has joined #openstack-swift05:55
*** pgbridge has quit IRC05:58
*** noark9 has quit IRC06:07
*** badari has quit IRC06:14
*** mac_ified has quit IRC06:19
*** Jeffrey4l has joined #openstack-swift06:19
*** dmorita has quit IRC06:19
janonymousI am still getting trouble with tox -e py27 test.unit.container.test_reconciler:TestReconcilerUtils.test_parse_raw_obj , when i run the whole UT , i.e. tox -e py27 everythin is ok.06:29
*** ppai has quit IRC06:42
*** ppai has joined #openstack-swift06:56
*** takashi_ has joined #openstack-swift07:17
*** takashi has quit IRC07:19
*** takashi_ has quit IRC07:19
*** takashi has joined #openstack-swift07:20
*** takashi_ has joined #openstack-swift07:20
*** zaitcev has quit IRC07:27
openstackgerritShu Muto proposed openstack/python-swiftclient: Drop py33 support  https://review.openstack.org/25770707:38
openstackgerritChristian Schwede proposed openstack/swift: Fix full_listing in internal_client  https://review.openstack.org/25750207:38
*** ntt has joined #openstack-swift07:46
*** trifon has joined #openstack-swift07:48
*** akle has quit IRC07:54
*** wbhuber has quit IRC08:03
*** arnox has joined #openstack-swift08:06
*** rledisez has joined #openstack-swift08:08
*** klrmn has quit IRC08:15
*** hseipp has joined #openstack-swift08:28
*** admin0 has joined #openstack-swift08:29
*** rvasilets__ has joined #openstack-swift08:30
*** acoles_ is now known as acoles08:52
*** ho has quit IRC08:54
*** jistr has joined #openstack-swift08:56
acolesblmartin: did you get an answer re viewkeys problem in unit tests - i saw same yesterday but conveniced myself i had too old six version. you need six>=1.9.0, maybe use tox -r.09:00
acoleskota_: thanks for reviewing the diskfile patch, i will respond to your comments asap09:08
*** admin0 has quit IRC09:09
openstackgerritMerged openstack/swift: Deprecated tox -downloadcache option removed  https://review.openstack.org/25659709:10
openstackgerritMerged openstack/python-swiftclient: Deprecated tox -downloadcache option removed  https://review.openstack.org/25671509:13
*** admin0 has joined #openstack-swift09:20
*** acoles is now known as acoles_09:31
*** janonymous has quit IRC09:33
*** takashi_ has quit IRC09:34
*** takashi has quit IRC09:34
*** openstackgerrit has quit IRC09:47
*** openstackgerrit has joined #openstack-swift09:48
*** dewsday has joined #openstack-swift09:58
*** jmccarthy has joined #openstack-swift09:59
*** aix has joined #openstack-swift10:01
*** venkat has quit IRC10:12
*** aix has quit IRC10:26
*** aix has joined #openstack-swift10:28
*** openstackgerrit has quit IRC10:32
*** openstackgerrit has joined #openstack-swift10:33
kota_acoles: great to hrear, I'm looking forward to it :-)10:47
*** admin0 has quit IRC11:11
*** admin0 has joined #openstack-swift11:12
*** ppai has quit IRC11:14
*** haomaiwang has joined #openstack-swift11:19
*** haomaiwang has quit IRC11:20
*** ig0r_ has quit IRC11:20
*** haomaiwang has joined #openstack-swift11:20
*** haomaiwang has quit IRC11:21
*** haomaiwang has joined #openstack-swift11:22
*** haomaiwang has quit IRC11:23
*** haomaiwang has joined #openstack-swift11:23
*** haomaiwang has quit IRC11:24
*** 14WAAGM1V has joined #openstack-swift11:24
*** 14WAAGM1V has quit IRC11:25
*** haomaiwa_ has joined #openstack-swift11:25
*** haomaiwa_ has quit IRC11:26
*** ppai has joined #openstack-swift11:26
*** haomaiwang has joined #openstack-swift11:26
*** haomaiwang has quit IRC11:27
*** haomaiwang has joined #openstack-swift11:27
*** haomaiwang has quit IRC11:28
*** haomaiwang has joined #openstack-swift11:28
*** haomaiwang has quit IRC11:29
*** 14WAAGM54 has joined #openstack-swift11:29
*** 14WAAGM54 has quit IRC11:30
*** sanchitmalhotra has quit IRC11:31
*** haomaiwang has joined #openstack-swift11:32
*** haomaiwang has quit IRC11:33
*** 21WAAH3GU has joined #openstack-swift11:33
*** 21WAAH3GU has quit IRC11:34
*** haomaiwang has joined #openstack-swift11:34
*** haomaiwang has quit IRC11:35
*** haomaiwang has joined #openstack-swift11:35
*** haomaiwang has quit IRC11:36
*** haomaiwang has joined #openstack-swift11:36
*** haomaiwang has quit IRC11:37
*** haomaiwang has joined #openstack-swift11:37
*** haomaiwang has quit IRC11:38
*** haomaiwang has joined #openstack-swift11:38
*** haomaiwang has quit IRC11:39
*** haomaiwang has joined #openstack-swift11:39
*** haomaiwang has quit IRC11:40
*** haomaiwang has joined #openstack-swift11:40
*** haomaiwang has quit IRC11:41
*** haomaiwang has joined #openstack-swift11:41
*** haomaiwang has quit IRC11:42
*** 14WAAGNG5 has joined #openstack-swift11:42
*** 14WAAGNG5 has quit IRC11:43
*** haomaiwang has joined #openstack-swift11:46
*** haomaiwang has quit IRC11:47
*** haomaiwang has joined #openstack-swift11:47
*** haomaiwang has quit IRC11:48
*** 17WABBDO5 has joined #openstack-swift11:48
*** 17WABBDO5 has quit IRC11:49
*** haomaiwang has joined #openstack-swift11:49
*** haomaiwang has quit IRC11:50
*** haomaiwang has joined #openstack-swift11:50
*** haomaiwang has quit IRC11:51
*** haomaiwang has joined #openstack-swift11:51
*** haomaiwang has quit IRC11:52
*** haomaiwang has joined #openstack-swift11:52
*** haomaiwang has quit IRC11:53
*** 18WABIUKW has joined #openstack-swift11:54
*** 18WABIUKW has quit IRC11:55
*** haomaiwa_ has joined #openstack-swift11:55
*** mattoliverau has quit IRC11:55
*** haomaiwa_ has quit IRC11:56
*** yatin has quit IRC11:56
*** haomaiwa_ has joined #openstack-swift11:56
*** matt6434 has joined #openstack-swift11:56
*** haomaiwa_ has quit IRC11:57
*** haomaiwa_ has joined #openstack-swift11:57
*** haomaiwa_ has quit IRC11:58
*** haomaiwa_ has joined #openstack-swift11:58
*** Jeffrey4l has quit IRC11:58
*** haomaiwa_ has quit IRC11:59
*** 14WAAGNTQ has joined #openstack-swift12:00
*** 14WAAGNTQ has quit IRC12:01
*** 14WAAGNU9 has joined #openstack-swift12:01
*** 14WAAGNU9 has quit IRC12:02
*** haomaiwang has joined #openstack-swift12:02
*** haomaiwang has quit IRC12:03
*** haomaiwang has joined #openstack-swift12:03
*** haomaiwang has quit IRC12:04
*** acoles_ is now known as acoles12:04
acoleskota_: are you still here?12:04
*** rvasilets__ has quit IRC12:05
*** haomaiwang has joined #openstack-swift12:06
*** haomaiwang has quit IRC12:07
*** 18WABIUWU has joined #openstack-swift12:07
*** 18WABIUWU has quit IRC12:08
*** 18WABIUXV has joined #openstack-swift12:08
*** 18WABIUXV has quit IRC12:09
*** haomaiwang has joined #openstack-swift12:10
*** haomaiwang has quit IRC12:11
*** haomaiwang has joined #openstack-swift12:11
*** haomaiwang has quit IRC12:12
*** haomaiwang has joined #openstack-swift12:12
*** CaioBrentano has joined #openstack-swift12:12
*** haomaiwang has quit IRC12:13
*** haomaiwang has joined #openstack-swift12:15
*** haomaiwang has quit IRC12:16
*** haomaiwang has joined #openstack-swift12:17
*** haomaiwang has quit IRC12:18
*** dewsday has quit IRC12:18
*** haomaiwang has joined #openstack-swift12:18
*** haomaiwang has quit IRC12:19
*** ppai has quit IRC12:19
*** haomaiwang has joined #openstack-swift12:19
*** haomaiwang has quit IRC12:20
*** haomaiwang has joined #openstack-swift12:20
*** haomaiwang has quit IRC12:21
*** haomaiwang has joined #openstack-swift12:21
*** haomaiwang has quit IRC12:22
*** 17WABBED5 has joined #openstack-swift12:22
*** 17WABBED5 has quit IRC12:23
*** haomaiwang has joined #openstack-swift12:23
*** haomaiwang has quit IRC12:24
*** haomaiwang has joined #openstack-swift12:24
*** haomaiwang has quit IRC12:25
*** haomaiwang has joined #openstack-swift12:25
*** haomaiwang has quit IRC12:26
*** 17WABBEGT has joined #openstack-swift12:26
*** 17WABBEGT has quit IRC12:27
*** haomaiwa_ has joined #openstack-swift12:27
*** haomaiwa_ has quit IRC12:28
*** 14WAAGOIE has joined #openstack-swift12:28
*** 14WAAGOIE has quit IRC12:29
*** haomaiwang has joined #openstack-swift12:29
*** km has quit IRC12:29
*** haomaiwang has quit IRC12:30
*** haomaiwa_ has joined #openstack-swift12:32
*** haomaiwa_ has quit IRC12:33
*** ppai has joined #openstack-swift12:33
*** 18WABIVH4 has joined #openstack-swift12:34
*** 18WABIVH4 has quit IRC12:34
*** admin0 has quit IRC12:34
*** km has joined #openstack-swift12:34
*** haomaiwa_ has joined #openstack-swift12:35
*** haomaiwa_ has quit IRC12:36
*** haomaiwang has joined #openstack-swift12:37
*** haomaiwang has quit IRC12:38
*** haomaiwa_ has joined #openstack-swift12:38
*** haomaiwa_ has quit IRC12:39
*** haomaiwang has joined #openstack-swift12:40
*** haomaiwang has quit IRC12:41
*** 21WAAH43O has joined #openstack-swift12:41
*** 21WAAH43O has quit IRC12:42
*** haomaiwa_ has joined #openstack-swift12:42
*** haomaiwa_ has quit IRC12:43
*** haomaiwa_ has joined #openstack-swift12:43
*** haomaiwa_ has quit IRC12:44
*** haomaiwang has joined #openstack-swift12:44
*** haomaiwang has quit IRC12:45
*** SkyRocknRoll has quit IRC12:46
*** haomaiwa_ has joined #openstack-swift12:46
*** haomaiwa_ has quit IRC12:47
*** haomaiwang has joined #openstack-swift12:47
*** haomaiwang has quit IRC12:48
*** haomaiwang has joined #openstack-swift12:48
*** haomaiwang has quit IRC12:49
*** ppai has quit IRC12:49
*** admin0 has joined #openstack-swift12:52
*** km has quit IRC12:53
*** sayali_ has quit IRC12:56
*** sayali has joined #openstack-swift12:58
*** kei_yama_ has quit IRC13:01
openstackgerritMerged openstack/swift: Fix a typo in development_auth.rst  https://review.openstack.org/25765413:02
*** ppai has joined #openstack-swift13:03
*** links has quit IRC13:09
*** sayali has quit IRC13:18
*** sayali has joined #openstack-swift13:20
*** petertr7_away has quit IRC13:23
*** petertr7_away has joined #openstack-swift13:24
*** petertr7_away is now known as petertr713:24
*** lpabon has joined #openstack-swift13:25
*** sayali has quit IRC13:26
*** ppai has quit IRC13:27
*** sayali has joined #openstack-swift13:28
*** sayali has quit IRC13:30
*** breitz has quit IRC13:31
*** breitz has joined #openstack-swift13:32
*** sayali has joined #openstack-swift13:32
kota_Back13:33
*** sayali has quit IRC13:33
*** whydidyoustealmy has joined #openstack-swift13:35
*** sayali has joined #openstack-swift13:35
*** shakamunyi has joined #openstack-swift13:35
*** whydidyoustealmy is now known as superflyy13:36
*** petertr7 has quit IRC13:38
*** sayali has quit IRC13:40
*** sayali has joined #openstack-swift13:42
*** petertr7_away has joined #openstack-swift13:43
*** petertr7_away is now known as petertr713:43
*** janonymous has joined #openstack-swift13:48
*** links has joined #openstack-swift13:51
*** aix has quit IRC13:52
kota_acoles: what's up?13:57
acoleskota_: hi! i had a question about one of your comments , but I figured it out now :) about durable_timestamp. Actually your comment caused me to realise there was some tests missing.13:58
acoleskota_: thanks!13:58
*** sayali has quit IRC13:59
kota_Great!13:59
*** rcernin has joined #openstack-swift14:02
kota_Sorry, i had a party today for late response14:04
*** aix has joined #openstack-swift14:05
acoleskota_: enjoy the party :D14:10
*** sayali has joined #openstack-swift14:11
kota_acoles: thanks!14:14
*** sayali has quit IRC14:24
*** sayali has joined #openstack-swift14:27
*** sayali has quit IRC14:32
*** badari has joined #openstack-swift14:33
*** sayali has joined #openstack-swift14:36
*** Jeffrey4l has joined #openstack-swift14:41
*** dslevin_ has quit IRC14:42
*** dslevin has quit IRC14:42
*** hseipp has quit IRC14:44
*** sayali has quit IRC14:50
*** janonymous has quit IRC14:51
*** links has quit IRC14:58
*** links has joined #openstack-swift14:59
*** blmartin has joined #openstack-swift15:03
*** dslevin has joined #openstack-swift15:06
*** rvasilets__ has joined #openstack-swift15:08
*** aix has quit IRC15:09
*** aix has joined #openstack-swift15:09
*** noark9 has joined #openstack-swift15:18
*** joeljwright has joined #openstack-swift15:22
*** ChanServ sets mode: +v joeljwright15:22
*** janonymous has joined #openstack-swift15:24
*** tsg has joined #openstack-swift15:30
*** changbl has quit IRC15:35
openstackgerritAlistair Coles proposed openstack/swift: Don't ssync data when only a durable is missing  https://review.openstack.org/23268415:36
openstackgerritAlistair Coles proposed openstack/swift: Make ECDiskFile report all fragments found on disk  https://review.openstack.org/23112115:36
*** wbhuber has joined #openstack-swift15:44
*** Guest56642 has joined #openstack-swift15:47
*** Guest56642 has left #openstack-swift15:47
*** wbhuber_ has joined #openstack-swift15:47
*** wbhuber has quit IRC15:48
*** wbhuber_ is now known as wbhuber15:48
*** admin0 has quit IRC15:53
*** rcernin has quit IRC15:58
*** Jeffrey4l has quit IRC16:00
*** dslevin has quit IRC16:06
*** diazjf has joined #openstack-swift16:07
*** eranrom has joined #openstack-swift16:07
openstackgerritAlistair Coles proposed openstack/swift: Minor cleanup of repeated identical test assertions  https://review.openstack.org/25798416:12
blmartincschwede: Thanks for reviewing the patch, It looks like the error you were seeing is the following: rebalance is attempted, as min_part_hours has passed the ring is rebalanced but no partitions need to be reassigned. last_part_moves_epoch is updated and then after that we check if min_part_seconds_left is > 0 which it always will be as we just updated the moves_epoch. This is easily fixed by moving the check before attempting the rebalance (just l16:14
*** pgbridge has joined #openstack-swift16:22
blmartinacoles: Thanks for the answer about viewkeys. I ran that and it may have solved it (when I activate the venv I can import six and call viewkeys) I'll let you know later if tox plays nicely with it16:23
acolesblmartin: good luck!16:24
*** garthb has joined #openstack-swift16:26
*** arnox has quit IRC16:33
*** eranrom has quit IRC16:39
*** arnox has joined #openstack-swift16:40
*** arnox has quit IRC16:40
*** rledisez1 has joined #openstack-swift16:52
*** rledisez1 has quit IRC16:53
*** zhill has joined #openstack-swift16:53
*** janonymous_ has joined #openstack-swift16:57
*** lcurtis has joined #openstack-swift16:59
notmynamegood morning16:59
vinshcschwede: Hello, I want to talk about https://review.openstack.org/#/c/230914/ with you when you are around.17:00
vinshcschwede: I like your idea behind the patch and I would like to rebase it for you if you don't mind.17:01
vinshIts in conflict with some larger changes I made the last few weeks and I could bring it up to speed quickly.17:01
*** rledisez has quit IRC17:02
*** david-lyle has quit IRC17:02
*** gyee has joined #openstack-swift17:03
*** yatin has joined #openstack-swift17:08
*** lyrrad has joined #openstack-swift17:08
*** yatin has quit IRC17:09
pdardeaugood morning!17:11
diazjfnotmyname, I will be having a hangout session with the Barbican team tomorrow to discuss what is needed for Castellan in Swift. Would be cool if you could attend 8-)17:12
notmynamewhen?17:12
*** david-lyle has joined #openstack-swift17:12
diazjfnotmyname, its most likely gonna be 2PM Central, but I can move it to 3 if you need.17:13
notmynameI can do that17:13
diazjfnotmyname awesome. I'll post the hangout link tomorrow.17:14
openstackgerritStuart McLaren proposed openstack/python-swiftclient: Retry download of object body  https://review.openstack.org/15920817:16
openstackgerritStuart McLaren proposed openstack/python-swiftclient: Test 'string' behaviour of get_object  https://review.openstack.org/25801817:16
openstackgerritBen Martin proposed openstack/swift: Print min_part_hours lockout time remaining  https://review.openstack.org/25757717:16
openstackgerritShashirekha Gundur proposed openstack/swift: Update SAIO setup for Ubuntu 14.04  https://review.openstack.org/20779017:22
*** nadeem has joined #openstack-swift17:27
*** garthb_ has joined #openstack-swift17:27
*** dmorita has joined #openstack-swift17:27
*** dmorita has quit IRC17:28
*** nadeem has quit IRC17:29
*** garthb has quit IRC17:29
*** nadeem has joined #openstack-swift17:29
*** dmorita has joined #openstack-swift17:29
*** petertr7 is now known as petertr7_away17:30
*** noark9 has quit IRC17:31
*** acoles is now known as acoles_17:38
hurricanerixyo17:41
hurricanerixerr, morning =)17:41
*** blmartin has quit IRC17:47
*** blmartin has joined #openstack-swift17:48
*** links has quit IRC17:50
*** klrmn has joined #openstack-swift17:55
notmynamehurricanerix: so what are we going to do about the testr patch?17:59
*** garthb_ has quit IRC18:00
*** garthb_ has joined #openstack-swift18:00
notmynamehurricanerix: with the in-process tests, I'm seeing the same as mattoliverau. tons of memory usage18:01
hurricanerixnotmyname i will take a look at it again today.18:01
notmynamehurricanerix: in general, it seems to work ok for me when doing `restswift && startmain && tox -efunc`18:01
notmynamebut the in-process tests don't work18:02
*** joeljwright has quit IRC18:03
notmynamegmmaha: were you looking at the testr stuff?18:08
*** diazjf has quit IRC18:17
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873618:18
*** tsg has quit IRC18:20
*** blmartin has quit IRC18:20
*** jistr has quit IRC18:22
openstackgerritTim Burke proposed openstack/python-swiftclient: Move python-keystoneclient to "extras"  https://review.openstack.org/25434618:35
* jrichli and others who work with her will be at holiday festivities the rest of today18:44
gmmahanotmyname: sorry wasnt at desk. yes, i was looking at it18:47
gmmahaif i run the patch 10 (testr) with --isolated i am able to get them all to pass with no memory burn18:47
patchbotgmmaha: https://review.openstack.org/#/c/10/18:47
gmmahabut it takes an hour to run on my machine :(18:47
gmmahaor we have to option of snubbing the logger and we should be fine18:48
gmmahaand tell folks that if you want logs, you can run per test or if you want the big one we need some above 4G18:49
notmynamewow18:49
gmmahaspoke to mtreinish about it and there isnt a nice way of snubbing out to the subunit stream out of ostestr into a file even as its needed for ostestr to assess the test results18:49
notmynameseems rather terrible to go from a 2 minute test run to a 60 minute test run18:50
gmmahayeah18:50
gmmahathere is one another thing, not sure if thats ok18:50
gmmahathe debug_logger, i can make it write to a tmp file18:50
gmmahaand then throw it out if all tests are good and leave it there if its not!18:50
gmmahathat might reduce the trash on the stdout which floods the subunit stream18:51
notmynameright. that seems reasonable I think18:51
notmynamebut the test run time is a really big deal18:51
notmynameany ideas why it takes so much longer to run?18:52
gmmahaif i remove the --isolated, we should be back18:52
gmmahathe --isolated will setup and teardown for each test, reducing the load on testr and keeping the mem usage down.18:52
gmmahabut the overhead of a setup and teardown is the time increase to an hour18:52
notmynameah18:53
notmynameisn't there a 40 minute timer in the gate? after that it gets killed?18:53
gmmahaohhh i didnt know about that :D18:54
gmmahabut i have a feeling that the gate machines are all running something over 4G which is why it passes for jenkins fine18:54
gmmahawhile our tests all fail18:54
notmynamegmmaha: I'd really like to see the result of the debug_logger change you're proposing18:55
notmynameis that somethign that will be in the test wrapper or in swift itself?18:55
gmmahanotmyname: right now i am thinking about swift..18:55
notmynamewell, both are "in swift" wrt the repo. I mean somethign int he logging in swift18:55
gmmahathe call to make the FakeLogger which write now writes to stdour with print(...)18:55
gmmahaits actually test/unit/__init__.py18:55
gmmahaaah i see your point. How do we make sure we can check the test result before blowing away the file :(18:59
notmyname...right...that was my point...totally what I meant...of course18:59
notmyname;-)18:59
gmmahahaha18:59
*** aix has quit IRC18:59
gmmahacan i just write a same named file in the swift repo itself19:00
gmmaha?19:00
gmmahaand asdd it to .gitignore?19:00
* gmmaha feels yucky saying that19:00
notmynameyeah, that doesn't sound nice19:00
notmynamegmmaha: but you may have found something interesting. if the log output can be modified in the test harness, that could be something cleaner to implement19:00
*** eranrom has joined #openstack-swift19:01
gmmahayeah19:01
gmmahado you think we can take my debug log snubbing patch now and file a follow on bug for a cleanup?19:01
gmmahanot sure how pressed on time we are on this19:01
*** tsg has joined #openstack-swift19:02
notmynamegmmaha: you're looking in unit/__init__.py? but we're looking at functional tests19:02
gmmahathe functional test __init__.py calls the debug_logger from test/unit/__init__.py to create the fake logger19:03
gmmahathat basically just does a print statement19:03
* gmmaha goes to double check that claim19:03
notmynameof course it does ;-)19:03
notmynameyup19:04
notmynameline 61819:04
gmmahayeah19:04
notmynamewhat about an envvar that redirects debug_logger? or a different setup of the in-process stuff that doesn't use debug_logger?19:05
notmynamehmm..why do we need debug logger for in-process stuff anyway?19:06
gmmahathats what i tried with this patch 25545719:06
patchbotgmmaha: https://review.openstack.org/#/c/255457/ - Option to supress logs for in_process test19:06
gmmahabasically env variable andno logs.. no env variable and i unleash the kracken19:07
notmynameah, right19:09
notmynameand i like that, but I'm wondering if there's another option besides stdout or nothing19:10
gmmahaaaah19:10
notmynamelike maybe doing a "real" logger to syslog? why not?19:10
gmmahayeah my patch is more of the band-aid than a real fix19:10
notmynamebut I like where you're going with it19:10
gmmahai thought the reason we didnt do real log was since its all in_process, leave no trace19:10
notmynamebut askign that question makes me wonder why we need a stdout logger at all.19:10
gmmaha:D19:10
pdardeaunotmyname: on the topic on long-running tests, it appears to take quite a while to create 60000 devices in ring?19:11
notmynamepdardeau: it's more of a function of the part power you're using, but yeah. math is hard. go buy better CPUs ;-)19:11
tdasilvanotmyname, gmmaha: so, in the case of tox, where did the in-process logging go?19:11
notmynamepdardeau: wow. that sounded a whole lot more snarky that I meant it to sound. ;-)19:12
gmmahatdasilva: its iwth tox, it goes to stdout19:12
gmmahawith the new switch to ostestr/testr19:12
tdasilvawas it being suppressed by tox?19:12
gmmahawith nosetests( i am not expert) it seems to keep it within itself happily19:12
ahalei was thinking that too pdardeau : it would be nice if ring-builder took ranges so you could easily add a bunch19:12
gmmahatdasilva: no sir. tox isnt doing any supressions..19:12
tdasilvagmmaha: I mean, we didn't have the problem of the logging being dumped on stdout, right?19:12
gmmahai am running all the tests with ttox19:12
pdardeaunotmyname: no worries!19:12
ahaleor an input file or something19:12
gmmahatdasilva: we have been dumping to stdout all this while.. dont think that code changes.. guessing its how nosetests vs testr/ostestr handle the stdout data19:13
tdasilvasorry, i mean nosetests19:13
notmynametdasilva: gmmaha: or is the reality that they were dumped to stdout and nose suppressed that therefore they were just unused?19:13
notmynametdasilva: gmmaha: if that's the case, then turning them off is effectively the same thing,r ight?19:13
tdasilvanotmyname: that's what i was trying to get ot19:13
tdasilvasounds like it19:14
gmmaha:D19:14
pdardeauahale: i might try doing that. i'll be running these a lot, and at current rate it'll take forever19:14
ahalebut then theres quite a few things wrong with ring-builder19:14
gmmahanotmyname: tdasilva: with an option to bring it out or without an option?19:14
tdasilvaaltought, if there's an option to do proper logging, then i'd prefer that19:14
notmynamepdardeau: what is it that's slow? adding devices or rebalancing?19:14
ahaleyah, one of my test rings took a day to build :(19:14
notmynameahale: get a better CPU! ;-)19:15
pdardeaupdardeau: adding devices19:15
notmynamepdardeau: ah, ok19:15
ahalenotmyname: use more cpu cores and i might !19:15
notmynamepdardeau: I was thinking the rebalance operation19:15
notmynameahale: rewrite it in go!19:15
ahalei might just !19:15
tdasilvahonestly, if what we have today is effectively no logging, then I wouldn't mind for now changing it to use 'None' instead of the DebugLogger19:15
notmynametdasilva: yes!19:15
notmynameahale: no not really. don't do that ;-)19:15
ahaletheres a few other things wrong with ring builder actually, main one is it will happily make rings it knows it will traceback when rebalancing19:16
tdasilvaemphasis on 'for now'. ideally we would have proper logging...eventually ;)19:16
* ahale needs to make bug report19:16
notmynametdasilva: which we still have if you aren't doing in-process19:16
gmmahanotmyname: tdasilva: so completely pull out the logging and then add a bug to follow-on19:16
notmynameahale: pdardeau: I seem to remember something about batch adds to the ring19:16
tdasilvagmmaha: sounds reasonable19:16
gmmahai am ok with that, though one part of me wants to have the flag in case there is someone more crazy than me19:17
notmynamegmmaha: yeah19:17
notmynamegmmaha: actually, just rolling your patch into the testr patch is probably a good idea19:17
tdasilvaso, off by default, on with flag?19:17
pdardeaunotmyname: so something better than builder.add_dev in loop?19:17
gmmahatdasilva: yeah thats what i was thinking19:18
ahalealso the holes remove makes in rings are annoying, they effecively reduce the max number of devices you can have :(19:18
gmmahanotmyname: okie. let me merge the patches then19:18
notmynamepdardeau: yeah, trying to find it19:18
gmmahasending anew one up in a bit19:18
tdasilvagmmaha: cool19:18
notmynameahale: have you used the latest version that jsut landed? any better there?19:18
ahaleso i have a ring with 30k devices in it that i cant rebalance cos theres >64k devs19:18
notmynameahale: right. that's what pdardeau is fixing right? :-)19:18
ahalenah havent tried that - the slowness of adding stuff to ring builder is so bad :)19:18
ahalei dunno, maybe?19:19
pdardeaunotmyname: yes, that's what i'm currently working on19:19
ahaleoh cool :)19:19
tdasilvagmmaha: just for reference, with the current patch, running against SAIO took 5 min. for me, running in-process took 20 minutes19:20
tdasilvanotmyname: ^19:20
ahalepdardeau: which bits are you thinking about fixing ? just out of interest - as theres been a few different things i've thought about19:22
notmynametdasilva: yeah, that's not good19:22
pdardeauahale: first up is to support more than 65535 devices (currently working on this)19:23
notmynamepdardeau: I'm nto sure what I was rememebering about adding a bunch of things to the ring at once. what about adding a device is taking a long time?19:23
notmynamepdardeau: I still hope you're looking at a dynamic number of bits there instead of a larger static number :-)19:23
pdardeauahale: and then allow increase of part power19:24
ahaleoh cool, I need that too :)19:24
pdardeaunotmyname: yeah, i'm just trying to get a test going up to the current limit right now19:24
notmyname:-)19:24
notmynamepdardeau: just get ahale to send you his ring ;-)19:24
ahalenotmyname: its slow because it only adds one at a time and loads up all the structures each time, while things like set weight operate on searches all at once, i guess19:25
pdardeauahale: yeah, it's a memory management exercise for a single core ;-)19:25
notmynameyeah " max(d['id'] for d in self.devs if d)" could be a little slow ;-)19:25
notmynamehmm..there are 2 loops over self.devs to add a device19:26
pdardeaunotmyname: it's all the list growing that happens 1 at a time19:27
notmynamegmmaha: cool. looking forward to it :-)19:31
notmynamepdardeau: yeah. :-(19:31
ahalepdardeau: if you need a big ring, i have a test one with 65476 devices. though its made with oldish ring code and has a lot of null in it19:31
*** openstackgerrit has quit IRC19:32
*** openstackgerrit has joined #openstack-swift19:33
pdardeauahale: i just made one with 60000 devices, laptop is still glowing19:33
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use testr  https://review.openstack.org/21420619:33
gmmahanotmyname: hurricanerix: tdasilva: ^^19:33
gmmahacan you give the patch and go and see how you feel about it19:33
ahalelol19:33
hurricanerixgmmaha sure19:34
gmmahathanks a lot19:34
* gmmaha just realized he is an idiot. :)19:36
notmynamepeluse: now that there is a new patch set, can you drop your -2 from patch 214206? no more danger of it landing from your +A misclick19:37
patchbotnotmyname: https://review.openstack.org/#/c/214206/ - Modify functional tests to use testr19:37
gmmahanotmyname: just messed it up a bit.. fixing and send a new one up in a few19:37
notmynameok19:37
notmynamegmmaha: I'm about to eat lunch, and then there's a company all-hands, so I probably won't look at it for a couple of hours19:38
gmmahanotmyname: no worries. and no rush. now that we have a solution19:38
gmmaha:)19:38
notmynamewe hope :-)19:38
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use testr  https://review.openstack.org/21420619:38
gmmaha:D19:39
gmmahapushed it up.. the envvar name changed between .testr.conf and the init.py file19:39
notmynamegmmaha: ok. can you leave a comment explaining the changes from patch set 12?19:39
gmmahanotmyname: sure can19:40
notmynamethanks19:40
notmynamedfg: thanks for the SLO ratelimit review19:41
tdasilvagmmaha: cool, in-process down to 3 min.19:42
notmynameyay19:42
gmmahatdasilva: awesome :D19:43
*** changbl has joined #openstack-swift19:44
gmmahanotmyname: added my comments.. please let me know if you think thats good.. but one last thing is that we havent addressed acoles_ comment19:46
gmmahahow do we run a single test? :(19:46
jlvillalgmmaha, If using os-testr I thought it was: tox -efunctional -- -r "SOME_REGEX"19:49
pdardeaunotmyname: ahale: looks like _set_parts_wanted is the guilty party19:50
gmmahajlvillal: yeah but the --regex is defaulted in the script.. trying to see if i can put it a logic to look for -n/--no-discover to remove the regex19:50
jlvillalgmmaha, huh? Why is it in script?19:50
* jlvillal hasn't read the patch...19:50
gmmahajlvillal: casue by default we only want the funcational tests to run.. without that, it will try and run all the tests19:51
jlvillalgmmaha, Aren't the functional tests in their own directory?19:51
gmmahaunder test/* yes19:51
jlvillalgmmaha, Not test/func/* ?19:51
jlvillaland test/unit/*19:52
jlvillal:)19:52
dfgnotmyname: np19:52
gmmahayes thats how they are laid out19:52
jlvillalThen should set the directory to run the tests19:52
jlvillalLet me find how ironic does it19:52
mtreinishgmmaha, jlvillal: so that's why tempest started setting custom discovery paths with an env var19:53
gmmahathanks.. that might help19:53
mtreinishthat pattern has been cargo culted to a lot of different projects19:53
jlvillalgmmaha, https://github.com/openstack/ironic/blob/master/.testr.conf#L2  At the end of the line TESTS_DIR19:53
mtreinishgmmaha: look at the.testr.conf in tempest or novaclient for an example19:53
mtreinishor that link from jlvillal :)19:53
jlvillalgmmaha, https://github.com/openstack/ironic/blob/master/tox.ini#L1519:54
gmmahamtreinish: thanks. checking the link, it still that the discover. I am trying to see if i can make it mutually exclusive with --no-discover19:54
*** gyee has quit IRC19:54
mtreinishgmmaha: the no discover flag doesn't use testr19:55
mtreinishthats a shortcut to run a specific test19:55
mtreinishit's the same as invoking subunit.run manually19:55
gmmahamtreinish: aah gotcha.. sorry was confusing the tests.. thanks. will fix the patch19:55
jlvillalgmmaha, We also run 'ostestr' from tox.ini19:56
jlvillalgmmaha,  https://github.com/openstack/ironic/blob/master/tox.ini#L1719:56
openstackgerritOndřej Nový proposed openstack/swift: Show only directories not files in recon device list  https://review.openstack.org/25813120:10
*** tsg has quit IRC20:26
*** zaitcev has joined #openstack-swift20:26
*** ChanServ sets mode: +v zaitcev20:26
pdardeaunotmyname: ahale: just took a quick stab at implementing a batch mechanism in builder.py20:36
pdardeauspeeds things up dramatically20:36
ahalecool :)20:37
*** changbl has quit IRC20:37
pdardeauahale: can now create 65535 devices in under 1 second20:39
ahaleoh wow ! thats amazingly faster20:39
pdardeauthe good thing is it's a very simple change20:39
zaitcevwhat's the partition power20:41
pdardeau1020:42
*** changbl has joined #openstack-swift20:44
*** dslevin has joined #openstack-swift20:47
*** matt6434 is now known as mattoliverau20:48
*** ChanServ sets mode: +v mattoliverau20:48
mattoliverauMorning20:48
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use testr  https://review.openstack.org/21420620:50
gmmahagood morning mattoliverau20:50
*** changbl has quit IRC20:53
*** tsg has joined #openstack-swift20:56
*** gyee has joined #openstack-swift21:01
*** nadeem has quit IRC21:13
*** nadeem has joined #openstack-swift21:13
gmmahamattoliverau: morning. Any chance you could check the latest patch and see if that works for you?21:15
gmmahaalso i removed the regex search. that will help with a single line test21:15
*** dmorita has quit IRC21:16
mattoliveraugmmaha: just about to look at it :) nice work on finding fixes :)21:16
gmmahamattoliverau: thanks.. :) more of a band-aid..21:16
gmmahatdasilva: mattoliverau: notmyname: the bug that i create to make logging less painful, should that be a wishlist entry or a bug?21:17
tdasilvagmmaha: i'm ok with wishlist21:18
gmmahatdasilva: thanks.21:18
gmmahawas leaning towards that as well.21:19
onovyhey, swift is cool http://postimg.org/image/nn16ge657/ 1200 req/sec just now :)21:21
*** admin0 has joined #openstack-swift21:22
vinshAnyone that might know..... :) :  I have a customer, they uploaded a large (6gig) object to swift.  This worked fine.. the client broke it into segments.  This customer then set a referer/key on that container containing that object.21:24
vinshthat container is private21:24
vinshThey can not GET this object if the container_segments container is set to private21:25
vinshif they set container_segments to public. it all works21:25
vinshI wonder, does the segments container require a similar/specific acl?21:25
gmmahatdasilva: i created it.. but apparently i dont have the rights to set it to wishlilst (importance) :/21:25
gmmahahttps://bugs.launchpad.net/swift/+bug/152653821:25
openstackLaunchpad bug 1526538 in OpenStack Object Storage (swift) "Enhancements to debug logger" [Undecided,New]21:25
tdasilvagmmaha: done21:28
gmmahatdasilva: thanks.21:28
tdasilvagmmaha: no no, thank you! ;)21:29
gmmaha;)21:29
mattoliverauvinsh: yeah, if you give access to the container holding an *LO then you also need to give them access to the container holding the segments, otherwise the sub requests to get the segments will fail.21:29
mattoliverauvinsh: also if your using a DLO then container listing is important so they may need the rlisting set as well21:30
vinshAh.. good idea.  I'll test now.21:32
vinshwith the acl set on the segments container.. a wget yields "Username/Password Authentication Failed."21:33
vinshwithout the acl it just responds with a 40121:33
vinshI guess those are both 401 :)21:33
*** dmorita has joined #openstack-swift21:34
tdasilvagmmaha: in master, i'm able to run a specific test like this: tox -e func -- test.functional.tests:TestContainer.testDelete , but with the testr patch it fails, is there a new way to run specific tests?21:39
vinshmattoliverau: I set .r:<key>.example.com,.rlistings  on both the container and the segements container. That what you were suggesting?21:40
*** ntt has quit IRC21:41
vinshah.. setting the segments container to .r:*,.rlistings works though21:42
vinshsetting the same domain/key as the main container doesn't though21:42
vinshhrm21:42
mtreinishtdasilva: try 'tox -efunc -- --no-discover test.functional.tests:TestContainer.testDelete'21:43
gmmahatdasilva: can you try tox -e func -- -r test.functional.tests.TestContainer.testDelete$21:43
mattoliveraugmmaha: Nice work, it works for me, nice work finding the logs being the cause of the memory usage.21:43
mattoliveraugmmaha: left a comment regarding default settings in .testr.conf.21:43
openstackgerritOndřej Nový proposed openstack/swift: Keystone middleware deprecated option is_admin removed  https://review.openstack.org/25815821:43
onovyit's cleanup time :)21:44
gmmahamattoliverau: checking the patch now.. seems there is another comment as well. :D21:44
*** ntt has joined #openstack-swift21:45
mtreinishmattoliverau: for running a single test --no-discover/-n will be a bit better because it skips the discovery phase, it just directly calls subunit.run on the path you give it21:47
gmmahamattoliverau: got loads of help from you guys and others :)21:47
gmmahamattoliverau: for the default in the testr.conf, would you prefer it be test/functional since we know that it works today21:49
gmmahaand then cahnge it to unit on a lter date?21:49
gmmahalater*21:49
mattoliverauyup, and since that's what the change does21:49
mattoliverauit's and easy change/patch for later.21:49
*** ntt has quit IRC21:49
gmmahamtreinish: the -n was causing an expcetion when we ran it that way21:49
mtreinishgmmaha: did you file a bug?21:51
gmmahamtreinish: not yet.21:51
mtreinishdo you have a pastebin of the exception, because that's how it's supposed to work. You give it a python object path with tests and it runs it21:51
gmmahamtreinish: i can get you one in a few secs21:52
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use ostestr/testr  https://review.openstack.org/21420621:52
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use ostestr/testr  https://review.openstack.org/21420621:53
gmmahamtreinish: http://paste.openstack.org/show/482017/21:53
tdasilvagmmaha, mtreinish: so the closest I could get is this: tox -efunc -- --no-discover test.functional.tests.TestContainer21:53
notmynameonovy: nice!21:53
gmmahatdasilva: didnt -- -r test.funcation.tests.TestContainer$ work for you?21:53
* gmmaha goes to test it out21:53
jlvillalmattoliverau, I wasn't sure how someone would use the default test/unit path. Since unit tests haven't been setup to use testr21:54
tdasilvagmmaha: one sec, let me try that again21:54
mtreinishgmmaha: the difference is -r does a regex match against discovery. So testr runs the discover command from your .testr.conf builds a list of tests and regex matches the arg against that list and then runs all the tests in that list21:55
mtreinishwhile -n litterally runs subunit.run $path21:55
mtreinishso the regex is a bit more forgiving to user error21:55
tdasilvagmmaha: yeah, that also works, I thought the $ was a typo, but I guess it is also important21:55
*** petertr7_away is now known as petertr721:56
gmmahamtreinish: does -n let me run the exact test itself. i think tdasilva confirmed and i am able to run the class test as well21:56
gmmahatox -efunc -v -- -n test.functional.tests.TestContainer works but tox -efunc -v -- -n test.functional.tests.TestContainer.testDelete fails21:56
tdasilvagmmaha: naahh...nevermind, the $ is not needed21:57
mtreinishgmmaha: there is a typo in you command, looking at the code it should be -n test.functional.test_container.TestContainer21:57
gmmahatdasilva: aaah :)21:57
*** david-lyle has quit IRC21:58
mtreinishgmmaha: it takes a module, a class, or a method (or a test suite if you're manually constructing one anywhere)21:58
tdasilvagmmaha: oops, i guess it's late for me and I'm not paying attention....the $ does make a difference. with it, only one test runs testDelete, without $ 3 tests that begin with testDelete runs, so it's really a regex21:59
*** david-lyle has joined #openstack-swift22:00
gmmahatdasilva: ok.. thanks for confirming22:01
jlvillalmtreinish, There is a 'test.py' file that has TestContainer22:01
gmmahamtreinish: there is a test_container file and also a tests.py which has a class TestContainer22:01
gmmahabut you confirmed that it has to be a class/method/module to be called with -n22:01
jlvillalBut isn't a method a class method?22:02
gmmahanotmyname: tdasilva: have a feeling all this has to go into one of our docs :)22:02
tdasilvagmmaha: now, i'm going to test with pdb22:02
jlvillaltdasilva, pdb++ ;)22:02
gmmahatdasilva: awesome.. thanks a lot.. did not think about that at all.. :D22:02
*** tsg has quit IRC22:02
jlvillaltdasilva, I mean pudb ...22:03
mtreinishgmmaha: it's calling subunit.run without doing any discovery. (hence the name) You have to pass it a python module path to an object that it can run22:03
mtreinishjust like the unittest cli interface22:03
tdasilvajlvillal: haven't used pudb yet :(22:04
jlvillaltdasilva, https://pypi.python.org/pypi/pudb22:04
mattoliveraujlvillal: pudb +122:04
jlvillalmtreinish, So why can it run: test.functional.tests.TestContainer but not test.functional.tests.TestContainer.testDelete22:05
jlvillalIs it because ...testDelete is not an object?22:05
mattoliveraujlvillal: .test.conf is run by testr by deafult, so by running: ostestr --serial it will use the default path used in the .test.conf. And we have haven't or will not make any effort to make sure the unit test pass in testr, at least not yet.22:05
jlvillalmattoliverau, Okay. /me wonders who would do that....22:06
jlvillal:)22:06
mattoliverauanyone looking at the testr config and go cool, unit tests must work22:06
mattoliverauso anyone who like to explore.. ie. most engineers :P22:07
jlvillalmattoliverau, Okay. I'm not sure how likely that is. But already has gotten changed in .testr.conf.22:08
*** ianbrown has quit IRC22:08
jlvillalmattoliverau, So I think all is good :)22:08
gmmahajlvillal: i think there is a WIP patch to do that. patch 25705322:09
patchbotgmmaha: https://review.openstack.org/#/c/257053/ - [WIP] testr to run unittests22:09
*** ianbrown has joined #openstack-swift22:09
mattoliveraujlvillal: it doesn't matter how likely it is, the change was to get functaional tests to use testr, so it needs to be complete. But yeah, it's been changed so it doesn't matter anymore :)22:09
mattoliverauwell it needs to be complete for me to put my +2 on it anyway :P22:10
jlvillal:)22:10
tdasilvajlvillal: so is pudb is just a better version of pdb or is the only way that will work with testr?22:12
tdasilvapdb is not working for me :/22:12
*** asettle is now known as asettle-afk22:13
mattoliverautdasilva: it's a ncurses interface so easier to use and looks better.22:15
mattoliverauand you can still use: import pudb .. pudb.set_trace()22:15
*** rcernin has joined #openstack-swift22:16
tdasilvamattoliverau: mm..currently, neither one is working...let me paste errors somewhere...22:17
mattoliveraugmmaha: made one last comment regarding .testr.conf.. sorry my bad, I notice the path was incorrect. .testr.conf is in the swift dir, so from there the functional tests live under test/functional not swift/test/functional22:20
jlvillaltdasilva, Just a better pdb I believe.22:21
jlvillaltdasilva, To use pdb have to pass in a certain flag.  mtreinish Knows it off the top of his head :)22:22
* jlvillal has to google22:22
mtreinishjlvillal: --pdb or --no-discover22:22
mtreinishthey do the same thing under the covers (they didn't use to which is why there are 2 flags)22:22
mattoliveraumtreinish: good to know ;)22:23
jlvillalmtreinish, Thanks. tdasilva ^^^22:23
*** trifon has quit IRC22:23
jlvillaltdasilva, tox -efunctional -- --pdb22:23
tdasilvamtreinish, jlvillal: thanks, trying that now22:23
jlvillalor something like that22:23
mtreinishjlvillal: you need to give it an object path too22:24
mtreinishit doesn't know what to run otherwise22:24
mtreinishjust like --no-discover22:24
gmmahamattoliverau: i can fix that for the patch. let me check pdb as well and upload the final patch22:25
mtreinishiirc, the issue is testr starts the actual runners in subprocesses which interferes with pdb catching breakpoints or whatever it's doing (I don't really use pdb so it's all secondhand)22:25
*** barker has joined #openstack-swift22:25
tdasilvaso, pdb sort of worked for me, but I couldn't provide the test name, only the class name (same error as before), so I had to run it like this: tox -e func -- --pdb test.functional.tests.TestContainer22:27
*** asettle-afk is now known as asettle22:27
tdasilvaotherwise I get the error: TypeError: unbound method testDelete() must be called with TestContainer instance as first argument (got nothing instead)22:27
*** admin0 has quit IRC22:28
gmmahatdasilva: ok. same happening here22:29
openstackgerritGanesh Maharaj Mahalingam proposed openstack/swift: Modify functional tests to use ostestr/testr  https://review.openstack.org/21420622:31
mattoliverauI just used the old 'python -m testtools.run discover --load-list my-list' like mentioned in https://wiki.openstack.org/wiki/Testr to degug testr tests. And you can replace pdb with pudb if you so desire. But if it works from ostestr that's even better.22:36
gmmahamattoliverau: i think what tdasilva did worked for me but not with pudb. the display was restricted with 1/4 of the scren on the left leaving it not so easily usable22:37
gmmahai remember reading something about that in one of the wiki pages22:38
mattoliverauahh, though I guess patches are welcome :P22:38
openstackgerritPaul Dardeau proposed openstack/swift: Add batch mode feature to RingBuilder  https://review.openstack.org/25817222:40
vinshmattoliverau: I'm stumped.  Just want to verify what I am doing makes sense.  I applied the same acl of ".r:<key>.example.com,.rlistings" that was on the main container.. to the matching segments container.  However we are still hitting a 401 trying to get that object in that container.  ONLY when we set the segments container to ".r:*,.rlistings" can we get the object... the problem then is that the segments container is p22:40
vinshublic.22:40
*** barker has quit IRC22:53
*** barker has joined #openstack-swift22:53
*** garthb__ has joined #openstack-swift22:54
*** garthb_ has quit IRC22:55
*** hurricanerix has quit IRC22:56
*** hurricanerix has joined #openstack-swift22:56
pdardeaumy latest patch is hosed, please ignore22:59
then3rdnotmyname: This isn't normal, is it? It looks like all my storage nodes are doing it: http://pastebin.com/raw.php?i=qvDx3uwu22:59
*** dustins is now known as dustins|out22:59
*** petertr7 is now known as petertr7_away22:59
*** david-lyle has quit IRC23:01
*** garthb__ has quit IRC23:01
*** david-lyle has joined #openstack-swift23:01
then3rdheh, looks like one of the nodes has bad permissions on the object storage directory and hasn't been syncing. Fun.23:03
*** barker has quit IRC23:07
*** barker has joined #openstack-swift23:08
*** km has joined #openstack-swift23:10
notmynamethen3rd: I was in a meeting. glad you found the issue23:14
notmynamethen3rd: a good heuristic when seeing errors in swift after a deployment is first check permissions, then check drive health23:15
*** eranrom has quit IRC23:16
*** eranrom has joined #openstack-swift23:17
*** rcernin has quit IRC23:20
*** barker_ has joined #openstack-swift23:20
notmynamethen3rd: it's probably a good idea to raise the max connections in rsync. looks like you're erroring with just 2 connections. probably want to raise that somewhat to 10 or 2023:21
notmynamethen3rd: depends a little on your cluster size and the activity in it23:21
then3rdNo worries! Yeah, I corrected perms and restarted storage/background processes. Took a couple minutes to sync, but erros went away on all nodes. It's magic.23:21
*** barker has quit IRC23:22
gmmahatdasilva: thanks for the comment on the patch :)23:23
*** barker_ has quit IRC23:24
then3rdnotmyname: Right now it's only 5 storage nodes with four 3TB raids. We have four more nodes with 4tb arrays in another reigon ready to go. I have no idea how large it'll end up... 2 connections did seem a little limiting.23:25
pdardeaunotmyname: ahale: my earlier posts regarding the slowness of adding devices was wrong!23:25
pdardeaumy environment was jacked up - i was picking up OLD code23:26
pdardeauthe slowness was fixed by clayg patches on Dec 723:26
notmynamecool23:26
pdardeaui'm an idiot!23:26
pdardeaubut it was slow once upon a time23:26
notmynameI believe it!23:27
*** kei_yama has joined #openstack-swift23:30
notmynamepdardeau: do you still want the batch mode patch?23:31
pdardeaunotmyname: no, it's not needed23:31
notmynameack. would you mind abandoning it, then?23:32
*** nadeem has quit IRC23:33
*** david-lyle_ has joined #openstack-swift23:33
pdardeaunotmyname: sure will. gotta figure out how to do that in gerrit :)23:33
*** nadeem has joined #openstack-swift23:33
notmynamethere's a button23:33
pdardeaugot it, thx23:34
*** david-lyle has quit IRC23:36
notmynamegmmaha: tdasilva: I step out to a meeting and I see comments in here, comments in gerrit, and two new patch sets23:41
*** nexusz99 has joined #openstack-swift23:43
*** nexusz99 has quit IRC23:43
gmmahanotmyname: :) the latest patch seems to be good and tdasilva has a nice comment on how to run single tests and pdb with it23:44
notmynamegood23:44
notmynameI'll take a look (and I'd love to have mattoliverau's comment too)23:45
gmmahanotmyname: awesome. thanks23:45
mattoliverauJust moving from hacking place number 1, brb23:45
gmmahajust one thing is pudb doesnt work. Not sure if its an issue with how testr is. i do remeber reading something about it. I will check on that later23:45
*** ho has joined #openstack-swift23:50
*** chlong has quit IRC23:59

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