Tuesday, 2018-06-19

*** lifeless_ has joined #openstack-swift00:05
*** lifeless has quit IRC00:05
*** mikecmpbll has quit IRC00:13
*** mwheckmann has joined #openstack-swift00:56
*** two_tired has joined #openstack-swift01:02
*** gyee has quit IRC01:33
*** lifeless_ has quit IRC01:43
*** lifeless has joined #openstack-swift01:45
*** armaan_ has joined #openstack-swift01:46
*** armaan has quit IRC01:46
*** mwheckmann has quit IRC02:07
*** mvenesio has joined #openstack-swift02:21
*** armaan_ has quit IRC02:24
*** armaan has joined #openstack-swift02:25
*** psachin has joined #openstack-swift02:40
*** armaan has quit IRC02:54
*** armaan has joined #openstack-swift03:00
*** mvenesio has quit IRC03:11
*** itlinux has joined #openstack-swift03:15
*** germs has quit IRC04:07
*** itlinux has quit IRC04:09
*** two_tired has quit IRC04:32
kota_hello world04:39
mattoliveraukota_: o/04:50
kota_mattoliverau: o/05:01
*** cshastri_ has joined #openstack-swift05:23
*** links has joined #openstack-swift05:33
*** cshastri_ has quit IRC05:44
*** lifeless has quit IRC05:53
*** lifeless has joined #openstack-swift05:53
*** cshastri has joined #openstack-swift06:11
*** armaan has quit IRC06:17
*** armaan has joined #openstack-swift06:18
*** hseipp has joined #openstack-swift06:41
*** hseipp has quit IRC06:41
*** hseipp has joined #openstack-swift06:46
*** psachin has quit IRC06:54
*** neonpastor has quit IRC07:00
*** neonpastor has joined #openstack-swift07:01
*** tesseract has joined #openstack-swift07:02
*** rcernin has quit IRC07:05
*** cshastri has quit IRC07:12
*** ccamacho has joined #openstack-swift07:19
*** cshastri has joined #openstack-swift07:28
*** geaaru has joined #openstack-swift07:33
*** mikecmpbll has joined #openstack-swift07:48
*** pcaruana has joined #openstack-swift07:50
*** mikecmpb_ has joined #openstack-swift07:53
*** gkadam has joined #openstack-swift07:54
*** mikecmpbll has quit IRC07:54
*** cbartz has joined #openstack-swift08:03
*** armaan has quit IRC08:12
*** armaan has joined #openstack-swift08:13
*** gkadam has quit IRC08:13
*** gkadam has joined #openstack-swift08:13
*** lifeless has quit IRC08:28
*** mahatic has quit IRC08:35
*** mahatic_ has joined #openstack-swift08:35
*** armaan has quit IRC08:40
*** armaan has joined #openstack-swift08:41
*** gkadam has quit IRC08:54
*** hseipp has quit IRC09:04
*** kei_yama has quit IRC09:29
*** mikecmpb_ has quit IRC09:35
*** mikecmpbll has joined #openstack-swift09:36
*** kei_yama has joined #openstack-swift09:51
*** armaan has quit IRC10:38
*** armaan has joined #openstack-swift10:39
*** armaan has quit IRC10:39
*** armaan has joined #openstack-swift10:40
*** mikecmpbll has quit IRC11:01
*** mikecmpbll has joined #openstack-swift11:02
*** links has quit IRC11:06
*** lifeless has joined #openstack-swift11:19
*** links has joined #openstack-swift11:22
*** hseipp has joined #openstack-swift11:24
*** lifeless has quit IRC11:28
*** lifeless has joined #openstack-swift11:28
*** kei_yama has quit IRC11:32
*** armaan has quit IRC11:37
*** armaan has joined #openstack-swift11:38
*** links has quit IRC11:39
*** vpc_ has joined #openstack-swift11:42
vpc_hi11:42
vpc_how can i get this11:42
vpc_Swift account = test11:42
acolesvpc_: I'm not sure I understand your question - do you want to know how to set up the test accounts?11:53
*** vpc_ has quit IRC11:56
*** mwheckmann has joined #openstack-swift12:03
*** links has joined #openstack-swift12:05
*** ndk_ has quit IRC12:14
*** ndk has joined #openstack-swift12:15
*** mikecmpb_ has joined #openstack-swift12:23
*** d0ugal has quit IRC12:24
*** mikecmpbll has quit IRC12:24
*** jistr is now known as jistr|mtg12:28
*** mikecmpb_ has quit IRC12:30
*** mikecmpbll has joined #openstack-swift12:32
*** vpc has joined #openstack-swift12:41
vpcHi how can i enable func_test this is for openstack swift plus openwhisk. Im trying to curl with x-:storage-user and password12:41
*** armaan has quit IRC12:43
*** armaan has joined #openstack-swift12:43
*** d0ugal has joined #openstack-swift12:44
*** vpc has quit IRC12:49
*** mvenesio has joined #openstack-swift12:52
*** armaan has quit IRC12:59
*** armaan has joined #openstack-swift12:59
*** links has quit IRC13:22
*** jistr|mtg is now known as jistr13:42
*** ccamacho has quit IRC13:42
*** ccamacho has joined #openstack-swift14:00
*** cshastri has quit IRC14:08
*** germs has joined #openstack-swift14:08
*** germs has quit IRC14:08
*** germs has joined #openstack-swift14:08
*** germs has quit IRC14:15
*** armaan has quit IRC14:18
*** armaan has joined #openstack-swift14:18
*** armaan has quit IRC14:22
*** germs has joined #openstack-swift14:22
*** armaan has joined #openstack-swift14:22
*** mvk has quit IRC14:24
*** germs has quit IRC14:27
*** germs has joined #openstack-swift14:31
*** germs has quit IRC14:31
*** germs has joined #openstack-swift14:31
*** mrjk has quit IRC14:32
*** mrjk has joined #openstack-swift14:35
*** ccamacho has quit IRC14:53
openstackgerritAlistair Coles proposed openstack/swift master: PUT+POST: simplify object server POST handler, other fixes  https://review.openstack.org/57551214:55
acoleszaitcev: I got the replicated policy path working with the DoublePutter and func tests passing ^^14:58
zaitcevacoles: I'll have a look, thanks.14:59
acoleszaitcev: I probably added some new bugs, I've just been hacking on it14:59
zaitcevacoles: I was going to look at your comments on P+P #26 today15:00
acolesI couldn't make the DoublePutter the default (for functional tests) without breaking the unit tests, so left that out (oops, I didn't update my commit message)15:01
zaitcevhmm... The tests take from .conf, at least if they aren't in-process tests15:02
zaitcevI wonder if anyone runs full-up functests that are not in-process anymore. I used to do it regularly.15:03
timburkegood morning15:24
*** pcaruana has quit IRC15:29
acoleszaitcev: I still do on an SAIO because the time to first test result is shorter than a tox job15:31
acolesand I don't keep all the env vars in my head for in process tests!15:31
zaitcevPYTHONPATH=$(pwd) TMPDIR=/var/tmp SWIFT_TEST_IN_PROCESS=1 SWIFT_TEST_IN_PROCESS_CONF_LOADER=ec ./.functests15:33
zaitcevmight be a little unwieldy15:33
acoleshehe15:33
*** SkyRocknRoll has joined #openstack-swift15:44
openstackgerritAlistair Coles proposed openstack/swift master: Use PUT+POST protocol for in process tests  https://review.openstack.org/57656515:51
acoleszaitcev: that ^^ will get PUT+POST functionally tested on zuul15:52
zaitcevacoles: I thought that was in-process. But maybe I'm wrong.15:53
acoleszuul runs both in process and devstack func tests IIRC15:54
*** cbartz has quit IRC15:59
*** SkyRocknRoll has quit IRC16:15
*** armaan has quit IRC16:18
*** armaan has joined #openstack-swift16:19
*** hseipp has quit IRC16:26
*** armaan has quit IRC16:32
*** armaan has joined #openstack-swift16:32
*** mikecmpbll has quit IRC16:40
*** gyee has joined #openstack-swift16:46
*** bharath1234 has joined #openstack-swift16:50
notmynamegood morning17:00
*** pcaruana has joined #openstack-swift17:05
*** bharath12345 has joined #openstack-swift17:06
*** tesseract has quit IRC17:08
*** lifeless_ has joined #openstack-swift17:12
*** lifeless has quit IRC17:12
bharath1234hey guys, I am trying to set up a swift development VM using the instructions from  the openstack website17:13
bharath1234I am facing issues in the unit testing. The error is "Mock" object has no attribute '__getitem__'17:14
bharath1234this error initiates at test_wsgi.py and nets till /python2.7/dist-packages/eventlet/wsgi.py line 59. host,port = self.request.getsockname()[:2]. I think that the mock value is being indexed using [] and there is no __getitem__ method to take care of it. Please help if any of you have faced this issue :D17:16
acolesbharath1234: if you can paste more context using http://paste.openstack.org/17:18
notmynamebharath1234: were you using https://docs.openstack.org/swift/latest/development_saio.html ?17:18
bharath1234yes I was indeed using the instructions from the openstack website17:20
bharath1234i will paste more context in the website17:20
bharath1234I have pasted the error with a description and the entire error message at http://paste.openstack.org/17:26
acolesbharath1234: once you hit the paste button the url changes to include a unique number - can you copy that here?17:27
bharath1234i ll give you the entire url?17:28
bharath1234http://paste.openstack.org/show/723842/17:28
acolesyep17:28
bharath1234please do tell if more context is needed17:29
bharath1234i will be more than willing to describe everything i did from the beginning17:30
acolesbharath1234: what version of eventlet do you have installed? 'pip show eventlet'17:35
bharath1234the version is 0.18.417:36
bharath1234the latest stable version is 0.22.1. Should i go ahead with upgrading it and run the unittests again?17:39
acolesalso what version of swift?17:40
bharath1234i cloned the master release of swif17:41
bharath1234swift*17:41
acolesok, I can reproduce the same error with those versions :/17:43
acolesso yes, upgrade eventlet, but not to 0.23.0. I have pip install eventlet==0.20.117:44
acoles(0.23.0 is blacklisted)17:44
bharath1234yes i upgraded eventlet. Now i am running the unittests17:45
bharath1234I have upgraded eventlet to the same version :D17:45
bharath1234i was getting a lot of version errors during the unittests17:46
*** geaaru has quit IRC17:46
bharath1234was able to solve all of them except this.17:46
bharath1234Is this an issue in the swift unittesting? Should we update the requirements list with the right version?17:47
acolesbharath1234: need to dig deeper to understand the cause - most likely a test problem so maybe the test needs improving.17:48
acolesthanks for alerting us. if you are able to write a brief bug report on https://bugs.launchpad.net/swift with the same info you pasted that would be great. I have to leave now, otherwise I'll look a bit more tomorrow.17:49
acolesbharath1234: ^^17:50
bharath1234yup looking at it17:50
bharath1234I ll write the bug report describing the errors i got and if solved(unittests are running right now) put the solution17:51
acolesbharath1234: BTW there's some useful tips here https://docs.openstack.org/swift/latest/development_guidelines.html#testing-guidelines - if you are not already using tox and virtualenvs it can help avoid version conflicts17:51
acolesbharath1234: thanks17:51
acolesgoodnight17:51
bharath1234I ll put a point of the requirements list having a chance of not being updated.17:53
bharath1234goodnight :) Thanks for the help17:53
bharath1234updating the version of eventlet helped :)17:54
bharath1234the unittests have passed17:54
bharath1234also could i get some suggestions on some good books on openstack swift :) I am digging deep into the code and gritty details of swift. Any good learning tips will help greatly!17:58
notmynamebharath1234: https://docs.openstack.org/swift/latest/ is the best place to start. there's a couple of books at https://www.swiftstack.com/resources. they've got good info, but are a few years old at this point so they don't have info about latest developments. https://www.youtube.com/results?search_query=openstack+swift is another great place to go18:02
notmynamebharath1234: what's your goal? if I know more about what you're trying to do, I may be able to give you some more specific things18:03
bharath1234I am working research problem in my university. Understanding the problem in itself requires good understanding of swift and its underlaying details18:07
bharath1234So my goal right now is to familiarize myself with the working of swift i.e how objects are distributed into different object nodes etc(conceptual understanding) and also understanding of the code base18:09
bharath1234till i reach a level where i am able to understand the research problem. Basically I am a beginner to swift. My experience with openstack is setting up devstack and deploying an instance through command line and horizon. Now i am trying to work through the codebase of swift in particular.18:10
*** mikecmpbll has joined #openstack-swift18:10
notmynamecool18:10
claygswift is awesome18:10
notmynameI would not recommend using devstack18:10
claygdevstack is ... bash ... bash is ... also awesome18:11
bharath1234just a simple question. My previous issue which i posted here , i have just solved right now. Should i post it on bugs launchpad?18:11
notmynamehttps://docs.openstack.org/swift/latest/development_saio.html is much better (for understanding how the parts work together) and https://github.com/swiftstack/vagrant-swift-all-in-one18:12
bharath1234I used devstack as a means to understand openstack i.e what goes on in vm deployment. Now i created a seperate VM in my computer to understand swift!18:12
bharath1234Yes SAIO is exactly what i did!18:12
notmynamegreat!18:12
claygbharath1234: honestly, hanging around in irc and asking questions is sorta the best thing you can do - but, yes, ostensibly bugs go on launchpad ...18:13
notmynameswift's README file has a good overview and starting point links for understanding the code18:14
claygbut often times filing a bug on launchpad would be proceeded by someone on IRC saying something like "yikes, yeah... we should probably file a bug on that, it'd be a huge help if you could do that?" - otherwise, launchpad is less effective for feedback/questions18:14
bharath1234I ll check the README file, once i done with functional and probe tests! Hope there are no bugs there!18:15
bharath1234yup, the response time and participants of this irc is great :)18:15
bharath1234hmm.. duly noted about the launchpad. I shall post the bug with the fix i used to remove it. maybe it might help someone else :)18:16
claygbharath1234: fair enough!  search-ability for future users is one great reason to document stuff on launchpad!  and if there's an alternative way to work-around the failure that wasn't obviously discorable the bug report can also point at that!18:19
* clayg recalls all the times "future users" was acctually just my own future self 18:20
bharath1234clayg: Yup thats the idea!18:20
clayg😁18:21
bharath1234clayg: i dont want this to haunt me if i set up a swift dev VM again :D so basically this is gonna help me as much as it will help everyone else :D18:22
clayglol18:22
claygi like you bharath123418:22
bharath1234clayg: haha :D18:29
bharath1234quick question. I need to specify the exact version of swift i have used in the bug report. I have cloned swift from the master branch. How do i know the version of swift now?18:29
notmynamecurrent version is 2.18.018:29
notmynamepython -c 'import swift; print swift.__version__'18:30
bharath1234thanks :D18:30
timburkealternatively, you can look at the most recent version in the CHANGELOG. notmyname's always pretty good about keeping that up o date ;-)18:31
notmynameand https://wiki.openstack.org/wiki/Swift/version_map18:31
timburkeor if you're feeling extra fancy, include the SHA that you've got checked out18:31
notmynametimburke: https://i.imgur.com/I4vGe3W.gif18:32
timburke`git show -q` shows you the commit metadata, the SHA's the hex in the first line18:33
bharath1234ahh was about to ask that :)18:33
timburkenotmyname: i should rewatch firefly sometime soon... it's been a bit18:33
zaitcevI was using git for many years but only now I noticed that "git log" shows tags, if any are attached to commits.18:41
bharath1234timburke: I already submitted the bug! will put the SHA from next time :D18:47
bharath1234One more error, while running the functional tests i m getting a dynamic linking error18:48
timburkeno worries :-)18:48
bharath1234i have read that its harmless? but am not entirely sure... what do you guys think?18:48
bharath1234timburke: :D18:48
bharath1234liberasurecode[14216]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory18:48
bharath1234^^ to be specific18:49
notmynamethat's ok18:49
zaitcevdon't use Jerasure for a test VM18:49
zaitcevJust use built-in that liberasurecode provides18:49
notmynameyes, what zaitcev says18:49
zaitcever18:49
timburkezaitcev: the git formatters are really nice once you dig into them enough! i was messing with this command line just yesterday -- git for-each-ref --format '%(creatordate:short)  %(refname:strip=2)' --sort='-creatordate' --count 10 refs/tags18:49
notmynamebut earlier versions of libec would spew warnings for "missing" libraries it knows about. but that was fixed in later versions18:50
zaitcevthis was very long ago. 1.0.9 was the last with warnings, IIRC18:50
bharath1234well I dont have jerasure18:50
notmynameyeah, but ubuntu still has the old version I think18:50
zaitcevok18:50
notmynameat least 16.04 was never updated18:51
bharath1234the ec_type in my swift.conf is libersurecode_rs_vand18:51
* notmyname is just now working on an ansible script to install libec from source to work around that18:51
notmynamebharath1234: yeah, that's good18:51
bharath1234so I ll just ignore the dynamic linking error?18:51
timburkeyep. not actually a problem18:57
bharath1234timburke: Thanks!!! This IRC is making me less afraid of errors as I am moving on!18:59
*** mikecmpbll has quit IRC19:14
*** bharath1234 has quit IRC19:41
*** bharath12345 has quit IRC19:50
*** pcaruana has quit IRC20:29
*** mvenesio has quit IRC20:34
*** mvenesio_ has joined #openstack-swift20:34
*** guimaluf has quit IRC20:35
*** guimaluf has joined #openstack-swift20:48
*** armaan has quit IRC20:50
*** armaan has joined #openstack-swift20:51
*** mvenesio_ has quit IRC21:18
*** guimaluf has quit IRC21:22
*** lifeless has joined #openstack-swift21:59
*** lifeless_ has quit IRC21:59
*** mwheckmann has quit IRC22:11
*** rcernin has joined #openstack-swift22:12
*** mvenesio has joined #openstack-swift22:30
openstackgerritSamuel Merritt proposed openstack/swift master: Refactor replicators' statistics  https://review.openstack.org/56464622:47
*** kei_yama has joined #openstack-swift23:20
mattoliveraumorning23:28
timburkemattoliverau: o/23:29
openstackgerritTim Burke proposed openstack/swift master: Change PUT bucket conflict error  https://review.openstack.org/57582923:39
*** lifeless_ has joined #openstack-swift23:41
*** lifeless has quit IRC23:42
openstackgerritMerged openstack/swift master: Tighten up staticweb redirect test  https://review.openstack.org/57490123:50
openstackgerritTim Burke proposed openstack/swift master: Include '-' in multipart ETags  https://review.openstack.org/57586023:57
timburkenote that some decisions in ^^^ were influenced by https://review.openstack.org/#/c/337960/23:59
patchbotpatch 337960 - swift - Send correct SLO ETag for container updates23:59
timburketimur: you might be interested in either of those two23:59

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