Friday, 2014-04-04

notmynamepiousbox: I'd love to. and if you're in the SF area, I'd be happy to get coffee and talk face to face00:02
piousboxnotmyname: I'm in San Jose00:02
piousboxnotmyname: where are you? ;)00:02
zaitcevSF of course. All the cool kids moved there. San Jose is not cool anymore.00:03
notmynameheh00:03
notmynameI gotta run. I'll be back later this evening. (riding home on my bike like the cool kids in SF do)00:03
zaitcevwhat, no Google bus for you?00:04
piousboxCool cool. Bicycles are very important :)00:17
piousboxnotmyname: I'm downtown SF this weekend. We should exchange emails 'n stuff.00:17
piousboxnotmyname:  piousbox at gmail is me.00:17
piousboxzaitcev: I like SJ00:18
piousboxzaitcev: I actually moved out of SF a few years ago.00:18
*** mmcardle has joined #openstack-swift00:27
*** mmcardle has quit IRC00:31
*** zaitcev has quit IRC00:39
*** shri has left #openstack-swift00:39
notmynamepiousbox: ah. I'll be out of town this weekend on a mini vacation with my family. maybe later00:46
notmynameah! topic update time!00:46
*** ChanServ changes topic to "Current Swift Release: 1.13.1 | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews | Channel Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"00:47
*** chuck_ has quit IRC00:55
*** Edward-Zhang has joined #openstack-swift01:26
*** mmcardle has joined #openstack-swift01:29
*** mmcardle has quit IRC01:33
*** nosnos has joined #openstack-swift01:33
*** piousbox has quit IRC01:34
*** bill_az has quit IRC01:35
*** Edward-Zhang has quit IRC01:35
*** simpleAJ has joined #openstack-swift01:41
*** simpleAJ2 has joined #openstack-swift01:43
simpleAJ2Hi01:43
simpleAJ2does anybody know if I would be able to install swift on single debian vm or may be two debian vm to start with using this guide01:44
simpleAJ2http://docs.openstack.org/developer/swift/howto_installmultinode.html01:44
simpleAJ2I just want to get my hands dirty and play with it01:44
creihtsimpleAJ2: if you wanted to just install on one node to try out, I recommend http://docs.openstack.org/developer/swift/development_saio.html01:45
notmynamesimpleAJ2: https://github.com/swiftstack/vagrant-swift-all-in-one is a good way to get started quickly too01:46
simpleAJ2it need to be strictly one node..I can bring two three nodes for sure..but  just want to install as easily as possible ;)01:46
notmynamecreiht: you'd probably like that too, actually01:46
simpleAJ2oh good ..will start with that then01:46
creihtnotmyname: yeah I've been meaning to check it out01:46
notmynamesimpleAJ2: ya, both of those are one VM with simulated 4 servers in it01:46
simpleAJ2ok..great..otherwise..with very simple setup...would I be needing atleast 5 nodes..01:47
simpleAJ2with replication factor say just 1..01:47
creihtsimpleAJ2: really depends on your use case, and how much redundancy, and performance you need01:47
simpleAJ2replication would 1..this just prototyping phase01:48
creihtthen you could easily set that up on one machine01:48
simpleAJ2but that should give me some idea how to go about it01:48
simpleAJ2ok sounds good01:48
simpleAJ2and one more question that I am meaning to ask is that..(sorry if I haven't gone through documentation that well enough)..01:49
simpleAJ2question is01:49
simpleAJ2in proxy server..will I be able to intercept the client request  and decide which storage node to be used like out of 10..these 5 are good for you client01:50
creihtsimpleAJ2: can you expand what your use case is?01:50
simpleAJ2sure..01:50
creihtdo you want like fast(ssd) and slow(sata) storage, or something like that?01:50
simpleAJ2no..actually that would be something like those nodes would be closer to client..have less congested bandwidth and may be less loaded servers01:51
creihtwell I think you could use the region support to do that01:51
creihtbut I'm not as familiar with those bits01:52
creihtnotmyname could probably help you more in that area01:52
simpleAJ2ok very well then. thank you for your help..will digg into region servers to see if that can help me01:52
*** mwstorer has quit IRC01:54
simpleAJ2notmyname: in case you have any pointers let me know..It seems that I would need to override some module that makes this decision..because things like network congestion or experiment data affinity would like to be available from external sources..and I would need to somehow find a way to tell that to proxy server01:56
simpleAJ2s/would like/would likely01:57
*** changbl has joined #openstack-swift02:22
*** zhiyan_ is now known as zhiyan02:24
*** mmcardle has joined #openstack-swift02:29
notmynamesimpleAJ: I'm not sure I follow your use case yet02:32
simpleAJoh02:32
*** simpleAJ2 has quit IRC02:33
simpleAJbasically when client would like to write an object02:33
simpleAJif I got it correctly proxy server determines which of the storage nodes it would like to write to.02:33
simpleAJmay be that decision made based on regions and zones.02:34
*** mmcardle has quit IRC02:35
simpleAJif that is correct, then I would like to see if we can have pluggable decision making module..like that will tell proxy server ..  these are the nodes that you would want to write to for certain reasons02:36
glangewhere an object "lives" in swift is too fundamental to how it works to put the object in some sort of arbitary location, I think02:37
simpleAJok02:37
glangeswift calculates a number based on the object name/path and then looks up in the ring which servers the object lives on02:37
glangeand that is used by replication, when the object is read, etc02:38
simpleAJthat is during read right?02:38
simpleAJi want to control where to write too.02:38
glangeit used during writes, reads, heads, posts, replication, etc02:38
glangeby everything02:38
simpleAJinteresting didn't know that02:38
portantesimpleAJ, what is coming is storage polices, which will let you construct different rings for differing kinds of offerings02:39
simpleAJok sounds reasonable02:40
portanteso you might have a ring of SSDs, another ring of 7200rpm, 10rpm, etc., and then you associated a policy with a container02:40
portanteso you might have gold, silver, bronze, for SSD, 10krpm and 7krpm, and you associate the "gold" with container A, charging customers more for that then the bronze level02:41
portanteor something like that scheme02:41
portantestorage policies will enable stuff like Erasure Codes, or other storage backends that come available02:41
simpleAJok02:42
simpleAJjust a thought that..these things look like static properties..02:42
simpleAJbasically what I am looking at is dynamic nature of the environment. where network is not that stable02:42
glangesimpleAJ: I think what you want is not in swift now and might never be in swift02:42
simpleAJhmm :)02:43
glangebut it's good to want things :)02:43
simpleAJyeah02:43
simpleAJI think these pointers are good to get started with swift..thanks a lot people02:44
notmynamesimpleAJ: for an overview of some concepts, check out the videos and blog posts and especially the architecture page at https://swiftstack.com/openstack-swift/02:47
simpleAJawesome that looks helpful02:47
notmynamesimpleAJ: what you're asking for is sort of like what's being built for storage policies (but I think that's a little too complicated for what you're looking for), and sorta like the existing "affinity" feature02:48
simpleAJyeah right.02:48
simpleAJbasically i am grad student..and exploring what are effects of really unstable network on storage systems..02:49
simpleAJand I found swift kinda of familiar with my concepts..so I am trying to explore that :)02:49
glangehttp://tinyurl.com/o5ue64902:49
glangethat is what the ring looks like02:49
glangethe object ring02:49
notmynamesimpleAJ: realize that the purpose of swift is to abstract away storage volumes so you have a single namespace, scalable storage system, where you, as the consumer (client), don't have to worry about pools of storage, filesystem limits, or hardware failures02:49
simpleAJ:D02:49
simpleAJright agree02:50
notmynamedurable storage, built for scale, and high availability and massive aggregate concurrency. basically, if you have user-generated content served on the web, you need swift02:51
simpleAJok02:53
*** matsuhas_ has joined #openstack-swift02:53
*** matsuhashi has quit IRC02:53
*** matsuhas_ has quit IRC02:54
*** matsuhashi has joined #openstack-swift02:56
*** matsuhashi has quit IRC03:02
*** matsuhashi has joined #openstack-swift03:04
*** scoorp has joined #openstack-swift03:11
*** simpleAJ has left #openstack-swift03:13
notmynamesimpleAJ: found it. if you're interested specifically in network issues, here's a couple of old videos of talks I've given on swift failure handing. https://www.youtube.com/watch?v=Z7z_1gBsoAc and http://mirror.linux.org.au/linux.conf.au/2013/mp4/Playing_with_OpenStack_Swift.mp403:13
*** nosnos has quit IRC03:17
*** cheri has joined #openstack-swift03:26
*** zackf has joined #openstack-swift03:31
*** mmcardle has joined #openstack-swift03:31
*** mmcardle has quit IRC03:35
openstackgerritA change was merged to openstack/swift: Fixed error in container sync exc handling  https://review.openstack.org/8519703:53
*** matsuhashi has quit IRC04:01
*** scoorp has quit IRC04:02
*** cheri has quit IRC04:03
*** cheri has joined #openstack-swift04:04
*** matsuhashi has joined #openstack-swift04:05
*** zackf has quit IRC04:14
*** chandan_kumar has joined #openstack-swift04:16
*** europack has joined #openstack-swift04:17
*** cheri has quit IRC04:19
*** nosnos has joined #openstack-swift04:20
openstackgerritJenkins proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8120704:28
*** h6w has joined #openstack-swift04:28
h6wHallo ppl.04:29
h6wI had to change the IPs of a couple of storage nodes.04:29
h6wSo I called set_info on the IP and replication IP.   All good according to swift-ring-builder.04:29
h6wHowever, if I do swift-recon, it seems to use the old IP addresses.04:29
h6wWhere is that stored?04:30
*** mmcardle has joined #openstack-swift04:33
*** cheri has joined #openstack-swift04:33
*** mmcardle has quit IRC04:38
*** madhuri has joined #openstack-swift04:40
*** chandan_kumar has quit IRC05:06
*** ben00b has joined #openstack-swift05:06
*** ben00b has quit IRC05:08
*** chandan_kumar has joined #openstack-swift05:08
*** nshaikh has joined #openstack-swift05:24
*** zhiyan is now known as zhiyan_05:25
*** mmcardle has joined #openstack-swift05:34
*** mmcardle has quit IRC05:38
*** Guest__ has joined #openstack-swift05:58
*** Guest__ is now known as bach06:04
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394206:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8518606:12
*** bach has quit IRC06:13
*** Guest__ has joined #openstack-swift06:18
*** madhuri has quit IRC06:23
*** mmcardle has joined #openstack-swift06:29
*** madhuri has joined #openstack-swift06:31
*** mmcardle has quit IRC06:31
*** mmcardle has joined #openstack-swift06:31
*** mmcardle has quit IRC06:35
*** Guest__ has quit IRC06:38
*** bvandenh has joined #openstack-swift06:38
Anjuclayg : ping06:40
*** madhuri has quit IRC06:41
*** cheri has quit IRC06:41
*** ppai has joined #openstack-swift06:52
*** ashish_ has joined #openstack-swift06:56
*** europack has quit IRC06:57
*** chandankumar_ has joined #openstack-swift06:59
ashish_Hey EveryOne I got the foolowing error when running the "ssbench-worker -h" command in the ssbench benchmarking tool. paste.openstack.org/show/75059/07:06
ashish_Please help.07:06
*** matsuhashi has quit IRC07:07
*** saju_m has joined #openstack-swift07:12
*** mmcardle has joined #openstack-swift07:13
*** Longgeek_ has joined #openstack-swift07:21
hugokuoashish_: you need newer greenlet version07:23
*** chandankumar_ has quit IRC07:23
hugokuoashish_:  pip freeze | grep green ; sudo pip install --upgrade greenlet07:27
hugokuohope it help07:27
*** cheri has joined #openstack-swift07:32
*** nacim has joined #openstack-swift07:40
*** zhiyan_ is now known as zhiyan07:56
*** ashish_ has quit IRC07:58
*** Longgeek_ has quit IRC07:59
*** als has joined #openstack-swift07:59
alshi I have a problem debugging proxy-server08:00
alsi am doing remote deubgging with pydev08:00
alsi can see the log in the debugger saying that 'the conection is attached'08:00
alsbut when the client makes a request08:00
alsto the proxy server08:01
alsthe proxy cant respond08:01
alsi put my code in08:01
als swift / swift / common / wsgi.py08:02
alsi put there pydev.settrace  ...08:02
alsand that connects back to the debugger08:02
alsmy question is, how do you set up proxy-server debugging?08:03
*** matsuhashi has joined #openstack-swift08:04
*** Midnightmyth has joined #openstack-swift08:06
*** tanee-away is now known as tanee08:12
*** Longgeek_ has joined #openstack-swift08:14
*** als has left #openstack-swift08:14
openstackgerritA change was merged to openstack/swift: Read the configuration once for all func tests  https://review.openstack.org/8433208:28
*** Longgeek_ has quit IRC08:31
*** cheri has quit IRC08:35
*** matsuhashi has quit IRC08:35
*** fbo_away is now known as fbo08:40
*** tanee is now known as tanee-away08:41
*** nacim has quit IRC08:42
*** cheri has joined #openstack-swift08:51
*** matsuhashi has joined #openstack-swift08:53
*** nacim has joined #openstack-swift08:54
openstackgerritYuan Zhou proposed a change to openstack/swift: Fixes versioning function tests with non-zero default policy  https://review.openstack.org/8251508:54
openstackgerritVictor Stinner proposed a change to openstack/python-swiftclient: Python 3: fix tests on HTTP headers  https://review.openstack.org/8471108:57
*** saurabh_ has quit IRC09:08
*** jamie_h has joined #openstack-swift09:18
*** mkollaro has joined #openstack-swift09:21
*** nacim has quit IRC09:42
*** matsuhashi has quit IRC09:47
*** matsuhashi has joined #openstack-swift09:47
*** Longgeek_ has joined #openstack-swift09:50
*** nacim has joined #openstack-swift09:56
*** saju_m has quit IRC09:56
*** cheri has quit IRC09:58
*** Longgeek_ has quit IRC09:59
*** Longgeek_ has joined #openstack-swift10:00
*** ppai has quit IRC10:07
*** Longgeek_ has quit IRC10:08
*** saju_m has joined #openstack-swift10:09
*** saju_m has quit IRC10:14
*** matsuhashi has quit IRC10:23
*** nacim has quit IRC10:28
*** nacim has joined #openstack-swift10:29
*** saju_m has joined #openstack-swift10:30
*** matsuhashi has joined #openstack-swift10:30
*** mkollaro has quit IRC10:31
*** nosnos has quit IRC10:33
*** Trixboxer has joined #openstack-swift10:34
*** saju_m has quit IRC10:35
*** saju_m has joined #openstack-swift10:35
*** matsuhashi has quit IRC10:38
*** chandankumar_ has joined #openstack-swift10:39
*** nosnos has joined #openstack-swift10:39
*** saju_m has quit IRC10:40
*** saju_m has joined #openstack-swift10:40
*** matsuhas_ has joined #openstack-swift10:41
*** cheri has joined #openstack-swift10:43
*** matsuhas_ has quit IRC10:52
*** matsuhashi has joined #openstack-swift10:52
*** tanee-away is now known as tanee10:54
*** chandankumar_ has quit IRC10:55
*** matsuhashi has quit IRC10:57
*** chandankumar_ has joined #openstack-swift11:12
*** cheri has quit IRC11:27
*** nosnos has quit IRC11:30
openstackgerritPeter Portante proposed a change to openstack/swift: Move module level setup under setup_package method  https://review.openstack.org/8433911:31
openstackgerritPeter Portante proposed a change to openstack/swift: In-process swift server for functional tests  https://review.openstack.org/6610811:31
*** saju_m has quit IRC11:38
openstackgerritJenkins proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8120711:57
*** mmcardle has quit IRC11:58
*** mkollaro has joined #openstack-swift12:04
*** saju_m has joined #openstack-swift12:10
*** saju_m has quit IRC12:14
*** saju_m has joined #openstack-swift12:15
*** mmcardle1 has joined #openstack-swift12:18
*** JuanManuelOlle has joined #openstack-swift12:18
*** tdasilva has left #openstack-swift12:24
*** tanee is now known as tanee-away12:30
*** JuanManuelOlle1 has joined #openstack-swift12:32
*** mmcardle1 has quit IRC12:35
*** JuanManuelOlle has quit IRC12:35
*** mmcardle has joined #openstack-swift12:43
*** mmcardle1 has joined #openstack-swift12:44
*** mmcardle has quit IRC12:45
*** chandankumar_ has quit IRC12:47
*** Fin1te has joined #openstack-swift12:49
*** saju_m has quit IRC12:57
*** Fin1te has quit IRC12:57
openstackgerritFlorent Flament proposed a change to openstack/python-swiftclient: Update help message to specify unit of --segment-size option.  https://review.openstack.org/8533513:07
openstackgerritFlorent Flament proposed a change to openstack/python-swiftclient: Update help message to specify unit of --segment-size option.  https://review.openstack.org/8533513:11
*** JuanManuelOlle1 has quit IRC13:18
*** PradeepChandani has quit IRC13:18
*** krtaylor has joined #openstack-swift13:24
*** lpabon has joined #openstack-swift13:36
*** piyush1 has joined #openstack-swift13:40
*** piyush2 has joined #openstack-swift13:44
*** tdasilva has joined #openstack-swift13:45
*** piyush1 has quit IRC13:46
openstackgerritMadhuri Kumari proposed a change to openstack/swift: Bypass committing pending records from .pending file  https://review.openstack.org/8535113:48
*** madhuri has joined #openstack-swift13:51
madhuriCan anyone please help reviewing this https://review.openstack.org/#/c/84819/ ?13:51
openstackgerritDonagh McCabe proposed a change to openstack/swift: Reclaim containers even if account db is reclaimed  https://review.openstack.org/8469613:53
cschwedemadhuri: hmm, maybe I miss something here - but https://review.openstack.org/#/c/84819/ is adding some methods that aren’t used?14:02
*** foexle has joined #openstack-swift14:12
*** Longgeek_ has joined #openstack-swift14:17
*** zackf has joined #openstack-swift14:30
*** mwstorer has joined #openstack-swift14:30
*** saju_m has joined #openstack-swift14:31
*** a_hacker2 has joined #openstack-swift14:33
*** saju_m has quit IRC14:34
a_hacker2creiht:  I think I mave have found it. http://paste.openstack.org/show/lyAaCCUArlEUvvypWba8/14:34
*** saju_m has joined #openstack-swift14:35
a_hacker2creiht:  the md5's of the ring files are the same on all boxes14:39
*** ashish_ has joined #openstack-swift14:42
*** mkerrin has quit IRC14:42
ashish_hugokuo thanks14:42
creihta_hacker2: well either one of your services is using the wrong ring, or you have another cluster or something misconfigured so you have cross-talk causing weird issues14:56
creihtsomething weird is going on14:56
a_hacker2yes - i'm pretty confused14:57
creihtI've heard that you guys have had issues before where internal ips get re-used or something like that so that there is cross-talk between different swift clusters14:57
creihtor something like that14:58
creihtdon't remember the exact specifics14:58
a_hacker2yeah, this is a new environment in a seperate datacenter :(14:58
creihtbut either way, either one of the services are getting the wrong ring somehow, or something external is interfering15:00
a_hacker2i can't find/think of anything external.  i also made a new ring with only 1 machine and just 3 disks.15:00
a_hacker2i think it's the account service/replicator that is somehow getting the wrong ring data15:01
*** joeljwright has joined #openstack-swift15:01
creihtthe other possibility is that some of the servers have the wrong hash prefix/suffix on some of the servers15:01
a_hacker2checking that15:02
creihta_hacker2: also when you isolated everything to one box, did you remove that box from the original cluster?  (to make sure the original cluster isn't trying to make requests to that box)15:08
creihtIn other news, I'm really disliking Requests right now :/15:10
openstackgerritFlorent Flament proposed a change to openstack/python-swiftclient: Update help message to specify unit of --segment-size option.  https://review.openstack.org/8533515:11
*** IRTermite has quit IRC15:13
*** IRTermite has joined #openstack-swift15:14
*** IRTermite has quit IRC15:23
*** lpabon has quit IRC15:26
*** nshaikh has quit IRC15:32
*** tanee-away is now known as tanee15:34
*** saju_m has quit IRC15:35
*** Finite has joined #openstack-swift15:35
a_hacker2creiht:  looks like that was it. swift.conf is different on the machines15:38
a_hacker2TYVM!15:38
creihtthere you go15:39
creihtnp15:39
*** JuanManuelOlle has joined #openstack-swift15:40
*** swiftishard has joined #openstack-swift15:40
*** Finite has left #openstack-swift15:43
*** Finite has joined #openstack-swift15:43
a_hacker2Finite!15:44
*** dmartls1 has joined #openstack-swift15:44
Finitea_hacker2 115:45
Finite!!!15:45
openstackFinite: Error: "!!" is not a valid command.15:45
gholtcreiht: Once again, swift.conf on the attack.15:54
a_hacker2creiht: sorry for wasting your time.  I'm writing a config test for this condition right now.15:55
gholta_hacker2: That has happened to many, so don't feel bad at all.15:55
gholtcreiht's got some ideas to try to make it more obvious when that is the issue.15:56
*** RockKuo_TW has quit IRC16:01
*** russellb is now known as rustlebee16:06
*** Finite_ has joined #openstack-swift16:08
*** JuanManuelOlle has quit IRC16:14
*** JuanManuelOlle has joined #openstack-swift16:17
dmartls1Running swift-proxy-1.12 with apache/wsgi, uploading unsegmented objects works fine, however when trying to segment the object is complains about the segment size being too large and reports the size of the entire object (before segmenting), is there some special config I'm missing to support DLO and wsgi?16:24
creihta_hacker2: yeah it is an easy problem to have16:25
*** csd_ has joined #openstack-swift16:29
*** bill_az has joined #openstack-swift16:33
joeljwrightHi everyone, as I mentioned a few weeks ago, I've been working on refactoring the python-swiftclient into an importable library, and updating the swift binary (now shell.py) to use that library. The updated code is available here: https://github.com/sohonetlabs/python-swiftclient/tree/swift-service and I'm hoping this could be integrated into the python-swiftclient project.16:33
joeljwrightObviously the patch is huge, so there will be work to so yet16:33
joeljwrightwanted to get feedback on the patch and advice on submitting the update16:34
joeljwrightThe code in that branch is based on the latest code in openstack/python-swiftclient master16:36
*** Longgeek_ has quit IRC16:36
creihtjoeljwright: can you give a short example of how it is different?16:38
zackmdavisjoeljwright, um, I thought python-swiftclient already was an importable library; "from swiftclient import client"16:38
creihtfor example you could already use swiftclient as a library16:39
creihtyeah what zackmdavis said16:39
joeljwrightwell, there was also a lot of logic in the swift binary16:39
creihta *lot* of projects already use it that way16:39
joeljwrightI haven't touched the code in client.py at all16:39
joeljwrightall I've done is create a new SwiftService class that incorporates all the logic from the swift binary16:40
*** mwstorer has quit IRC16:41
creihtahh16:41
joeljwrightand updated the multithreading code to allow multiple operatons16:41
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix issue with account broker and pre-SPI databases  https://review.openstack.org/8384016:42
*** chandankumar_ has joined #openstack-swift16:42
*** mwstorer has joined #openstack-swift16:42
joeljwrightso any code that uses client.py is fine, but there would be an extra layer to allow new projects to have access to multi-threaded upload/download from a simple import16:42
joeljwrightsorry, that should have been upload/download etc.16:43
joeljwrightthe porting of the swift binary to the library was a proof of concept16:44
creihthrm16:46
joeljwrightI'm hoping it will also help with testing the functionality from shell.py16:46
*** Guest__ has joined #openstack-swift16:48
creihtso I'm paging through the original shell.py code and *most* of the code is about parsing command line options, and mapping that to client.py calls16:48
creihtsorry if I'm missing something (which is entirely likely since my allergies are killing me today)16:48
creihtcan you help me understand what added functionality one would getting using service.py over client.py?16:49
joeljwrightwell, for example, in shell.py st_upload is ~300 lines of logic not included in client.py16:50
joeljwrightusing service.py you only have to specify container and an object list to get that logic and a multithreaded upload16:51
creihtahh I see16:51
creihtok thanks16:51
creihtsorry I'm a bit slow today :/16:51
joeljwright:)16:51
joeljwrightnp16:51
joeljwrightI ended up creating this because I was making calls out to the swift binary from within scripts16:52
creihtso why not refactor most of that code into client.py rather than having another wrapping class?16:52
joeljwrightbut I wanted better control over threading16:52
creihtunderstood16:52
joeljwrightultimately it started as a separate project, but I thought it might be useful here16:52
joeljwrightand I didn't want to mess with client.py because so many people are using it as is16:53
creihtyeah I can see the use of pulling the extra logic out of shell.py16:53
*** Guest__ has quit IRC16:54
joeljwrightI'm not expecting this to be an easy process16:54
joeljwrightjust wanted to start the discussion now that I have something reasonable to read and based off an up to date shell.py16:55
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix issue with account broker and pre-SPI databases  https://review.openstack.org/8384016:56
joeljwrightthe patch itself is huge, and now doubt introduces new bugs, but it has been very useful to me16:56
creihtjoeljwright: I'll have to take a look when my brain is a bit less cloudy16:57
creiht:)16:57
joeljwrightnp16:57
creihtbut the only question left in my mind right now, is if it is better to refactor those things into client.py, or introduce a wrapping as you did in service.py16:57
joeljwrightcreiht: so that leads me onto another question: what's the process for continuing this discussion?16:58
creihtwell I think the general idea is a reasonable one16:58
creihtthe next step is proposing a patch through gerrit16:58
creihthttps://wiki.openstack.org/wiki/Gerrit_Workflow16:59
*** csd_ has quit IRC16:59
creihtThat describes the overall process16:59
joeljwrightok, thanks very much16:59
creihtonce a patch is proposed, I imagine you will get a lot more feedback16:59
joeljwrightI'll read though that - I already have the required accounts I think, it's just a case of working out how to use them16:59
creihthehe17:00
creihtyeah the process is a bit daunting at first17:00
creihtif you run into issues, feel free to ask in here and we can help17:00
joeljwrightThanks17:01
*** tanee is now known as tanee-away17:01
*** csd_ has joined #openstack-swift17:01
*** mmcardle1 has quit IRC17:05
*** chandankumar_ has quit IRC17:09
*** shri has joined #openstack-swift17:11
*** nacim has quit IRC17:13
*** mmcardle has joined #openstack-swift17:21
*** mmcardle has quit IRC17:26
claygjoeljwright: I looked at that change when you mentioned it before and I'm sure it only has gotten better - I'm quite ready to review on gerrit17:32
claygjoeljwright: as you said it's a big patch, so it may take some time to get it all merged in - sooner we get started the better!17:33
*** mmcardle has joined #openstack-swift17:38
*** mmcardle has quit IRC17:42
*** zhiyan is now known as zhiyan_17:42
*** ashish_ has quit IRC17:43
joeljwrightclayg: thanks for the enthusiasm, I've started working through the gerrit process, but this is the first time I've done it so it might take me a while17:46
*** mmcardle has joined #openstack-swift17:52
peluseclayg: time to discuss the17:52
pelusefix spi container thing?17:52
*** joeljwright has left #openstack-swift17:53
*** mmcardle has quit IRC17:57
*** openstackgerrit has quit IRC18:01
*** openstackgerrit has joined #openstack-swift18:02
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix issue with account broker and pre-SPI databases  https://review.openstack.org/8384018:03
creihtso it looks like the way we are using requests in python-swiftclient, it is generating a new connection for each request18:06
creihtI think we need to figure out how to use the session stuf in the client18:06
*** Gue______ has joined #openstack-swift18:07
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8394218:07
creihtor maybe not....18:07
creihtheh18:07
creihtok yes we are18:09
creihthehe18:09
creihtI think the HTTPConnection class needs to use a requests session instad of calling requests.request directly to keep the connection open18:11
Alex_Gaynorcreiht: I think there's a WIP review for doing that18:14
creihtAlex_Gaynor: oh really? link?18:14
Alex_Gaynorcreiht: https://review.openstack.org/#/c/74444/18:14
creihtAlex_Gaynor: hah yeah18:15
creihtthat's more or less what I was thinking of doing, but I think they put the session in the wrong place18:16
*** a_hacker2 has quit IRC18:16
creihtor maybe that is18:18
creihtstupid allergies18:18
creihtAlex_Gaynor: thanks18:18
creihtthat does seem to improve things a bit18:21
claygpeluse: yeah just got out of a meeting - do you think we should open up another card to fix migrations and just take out the update for now?18:22
peluseone sec18:23
claygpeluse: it turns out that spi on the un-migrated rows just get's left as null - not sure if we could do something in the alter to make it fill in 0's18:23
peluseclayg:  so the update was working for me - meaning if I have an old DB that didn't have the col and I then run with the patch, the update affects all rows that had nothing in them and puts a 0 in them18:25
peluseclayg:  the only strange thing was that I also added a test (likes your I think but I didn't look) and with the test code the assert we have as a SWL thing didn't hit (catching the attempt to update).  It only hit for me when I tested it "for real"18:26
claygpeluse: a) I'm pretty sure there was no test case covering that b) that doesn't seem to work for me, and I believe that makes sense seeing as how the containers table explicitly forbids any update's18:27
peluseSWL=SQL... new keyboard and I can't seem to use it18:27
clayglol18:27
claygpeluse: in my test I had to insert the row by hand before the migration since put_container would always trigger the migration when inserting the row - i.e. it takes some manual sql to make a pre-spi-schema database that has some rows in it18:28
peluseclayg:  why did you make this comment "we can't just alter the table and stuff in default values with an update," - it does work or do you mean we shouldn't be doing that for some reason18:28
peluseclayg:  ya, that's what I did too.18:29
claygthe test I wrote shows it doesn't work, and that makes sense to me since the containers table forbids updates18:29
peluseclayg:  :)  Yes, I was going to ask why it forbids it, clearly I thought it was OK to 'ignore that' for our case since we do have a valid reason to do an UPDATE (I tought/think)18:30
* peluse is going to buy a new keyboard at lunchtime18:31
claygoh... but do you disable it before the migration?18:31
peluseclayg:  not sure what you mean, wanna hop on the phone for a few?18:32
claygpeluse: skype - yeah one sec18:34
pelusebelieve it or not I don't use skype18:34
claygpeluse: heh18:34
pelusewe have Msft Lync at work :(18:35
peluse480-554-3688 if you can call from skype18:36
*** Gue______ has quit IRC18:36
peluseif not I think the answer to your question is yes , in _migrate_add_storage_policy_index I simply ignore the error that the 'verbotten code' is preventing when we do the UPDATE18:36
pelusehmm, maybe I can use lync to call sykpe after all... checking18:37
claygwow18:38
*** Gue______ has joined #openstack-swift18:40
*** byeager has joined #openstack-swift18:41
*** jamie_h has quit IRC18:45
anticwpeluse: @work they luvs the lync too :) i used to uninstall on the windows lappy but they keep reinstalling it when i turn my back18:47
*** csd_ has quit IRC18:48
*** mmcardle has joined #openstack-swift18:53
*** mkollaro has quit IRC18:53
*** csd_ has joined #openstack-swift18:54
*** mmcardle has quit IRC18:57
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545319:16
*** Gue______ has quit IRC19:22
*** joeljwright has joined #openstack-swift19:26
*** joeljwright has left #openstack-swift19:27
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545319:29
openstackgerritPeter Portante proposed a change to openstack/swift: Attempt to ensure connect always timesout  https://review.openstack.org/8545719:30
*** IRTermite has joined #openstack-swift19:39
*** fbo is now known as fbo_away19:41
openstackgerritJoel Wright proposed a change to openstack/python-swiftclient: Add importable SwiftService incorporating shell.py logic  https://review.openstack.org/8545319:42
*** Gue______ has joined #openstack-swift19:48
peluseanticw:  yeah, I can't get away from Windows at work.  Forced to run it on my Mac if you can believe it (actually does quite well)19:48
*** mmcardle has joined #openstack-swift19:54
*** piyush2 has quit IRC19:57
*** mmcardle has quit IRC19:59
*** Trixboxer has quit IRC20:03
*** jamie_h has joined #openstack-swift20:07
*** piyush has joined #openstack-swift20:08
*** piyush1 has joined #openstack-swift20:13
*** piyush has quit IRC20:14
*** Gue______ has quit IRC20:17
*** csd_ has quit IRC20:26
portantezaitcev: you around?20:28
portanteglange: you around?20:32
portanteFinally got https://review.openstack.org/84339 through the check jobs, can you approve?20:32
*** csd_ has joined #openstack-swift20:32
*** Guest___ has joined #openstack-swift20:34
*** Guest___ has quit IRC20:38
*** mmcardle has joined #openstack-swift20:55
*** serveascode has joined #openstack-swift20:59
*** mmcardle has quit IRC20:59
*** serveascode has quit IRC21:00
*** JuanManuelOlle has quit IRC21:11
*** tdasilva has left #openstack-swift21:16
peluseclayg:  you there?21:18
claygpeluse: sure sure21:19
*** piyush1 has left #openstack-swift21:20
peluseso your test code behaves for me as it does for you...21:21
pelusethe reason why my initial attempt to add test code like yours didn't work is (I think) because I was using in mem DB = that's why I went and tested it manually21:21
pelusestrange21:21
claygstupid memdb's - can't trust 'em21:21
peluseI will re-test manually to make sure I wasn't seeing things that I wanted to :)21:21
clayglol21:22
pelusewill let ya know21:22
*** zaitcev has joined #openstack-swift21:25
*** ChanServ sets mode: +v zaitcev21:25
*** csd_ has quit IRC21:25
*** byeager has quit IRC21:26
peluseclayg:  I'm not seeing things.  The UDPATE really does work when testing "for real".  Here are my exact staps (maybe you can spot something fishy)21:29
*** fbo_away is now known as fbo21:30
peluse1) checkout master (2) resetswift (4) start swift (5) put cont called 'mycont' (6) usw sqlbroser to confirm DB has no SPI and container is in DB container table (7) checkout fix bracch, with update included (8) restart but not reset swift (9) put container called 'mycont2' (10) look at DB and confirm both containers are in table and both have a vluae of 0 for SPI21:31
peluse(not that I put enough times to force merge)21:31
pelusedmanit, nott=note21:32
claygpeluse: hehehehe21:32
peluseugh21:32
claygpeluse: so that does look pretty sound, maybe you can push your backend changes over the gerrit review and I can pull down and try and duplicate your results?21:32
claygsqlite --version -> 3.7.9 2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e21:32
clayg^ fwiw21:32
peluseqq:  how do I check my sqlite version?  :)21:33
*** byeager has joined #openstack-swift21:33
clayglike does maybe your fix branch remove the "disallow update" triggery thing?  cause i don't know exactly how that gets applied for realzys21:34
*** Finite has quit IRC21:34
*** Finite_ has quit IRC21:34
pelusenope, its there21:34
*** byeager_ has joined #openstack-swift21:34
claygpeluse: i just said "sqlite --version" and it spit out a value - dunno if that's sufficient, but it does seem like a change in behavior between my functional test and yours21:34
clayg... so it could be differences in the implementation - or something else - i'm reaching21:35
*** serverascode has joined #openstack-swift21:35
pelusebut my test fails like yours does though21:35
pelusemeaning, with patch I can see that the row w/the old container does not get updated... however when I rmeove the 'prevent update' deal I still don't see the row updated when the test code checks it.  Will verify that again real quick21:36
clayghrmm.... but seems different functionally so idk - I'd like to try and duplicate your results functionally, but I already verified it womm functionally the way it does in the test (with my backend changes, so i want to retry with yours)21:36
pelusesame exact sqlite BTW21:36
claygpeluse: k, well if you wanna push it up on gerrit (or somewhere else I can nab your working tree) I'll try it out functionally on my setup21:37
peluseOK, will do.  Will double check a few things first21:37
*** byeager has quit IRC21:38
*** mmcardle has joined #openstack-swift21:57
*** csd_ has joined #openstack-swift22:00
*** mmcardle has quit IRC22:01
peluseclayg:  I think I see why manual testing works....22:08
peluseits not the UPDATE thats getting the spi updated, its in _commit_puts_load22:09
claygpeluse: oh i missed your bit on same sql version, so that rules out that i 'spose22:10
claygyeah if the .pending file is processed against the new code it would definately get the right value in spi22:10
peluseyup22:10
claygbah, i need to rebase torgomatic keep-per-object-spi on the latest changes in feature/ec22:11
peluseso at least that solves the 'difference between test and func' behavior and solidifies that we can't blow off the integrity error22:11
peluseso is it possible for the scenario created by the current test code to happen for real?  I mean, all DB merges come through the pending file right?22:12
peluse(so all will get spi of 0 if they don't have the col)22:13
claygpeluse: yeah i mean a db that's been around awhile is going to have those rows in the database not in the .pending file22:17
claygpeluse: maybe I don't quite follow what you're asking, or i'm still missing something about your functional test22:18
peluseclayg: damned existing installed base22:18
peluseclayg:  you actually just asnwered my question22:18
claygpeluse: bummer22:19
peluseclayg:  so I think I have a handle on this if you'd like me to take a stab at getting it right.  Have to head to football practice (son, not me) so will be over the weekend sometime22:19
claygpeluse: i'm not so sure there's such a rush - we need to get it squared of course - but ultimately it all needs to work and I need to stay on the reconciler - so have fun!22:20
peluserock n roll.  as usual, thanks for the insights....22:21
*** byeager_ has quit IRC22:21
*** byeager has joined #openstack-swift22:22
*** byeager_ has joined #openstack-swift22:23
*** byeager has quit IRC22:23
*** csd_ is now known as csd22:26
*** byeager_ has quit IRC22:27
*** byeager has joined #openstack-swift22:27
*** byeager has quit IRC22:31
*** techguru has joined #openstack-swift22:42
*** fbo is now known as fbo_away22:43
*** Midnightmyth has quit IRC22:45
*** jamie_h has quit IRC22:47
*** Fin1te has joined #openstack-swift22:55
*** mwstorer has quit IRC22:55
*** mmcardle has joined #openstack-swift22:58
*** mmcardle has quit IRC23:02
*** dmartls1 has quit IRC23:10
*** zackf has quit IRC23:18
*** techguru has quit IRC23:20
*** mmcardle has joined #openstack-swift23:51
*** mmcardle1 has joined #openstack-swift23:53
*** mmcardle has quit IRC23:53
*** Fin1te has quit IRC23:55
*** foexle has quit IRC23:57
*** mmcardle1 has quit IRC23:57

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