Thursday, 2014-10-02

*** zaitcev has quit IRC00:07
*** gyee has quit IRC00:08
*** kyles_ne_ has quit IRC00:15
*** kyles_ne has joined #openstack-swift00:15
*** kyles_ne has quit IRC00:20
*** rmcall has quit IRC00:38
*** shri has quit IRC00:50
*** judd7 has quit IRC01:04
*** addnull has joined #openstack-swift01:24
*** dmsimard_away is now known as dmsimard01:27
*** dmsimard is now known as dmsimard_away01:28
*** mahatic_ has quit IRC01:29
*** jamiehannaford has joined #openstack-swift01:42
*** tsg has quit IRC01:57
*** mitz_ has quit IRC02:11
*** nosnos has joined #openstack-swift02:14
*** echevemaster has quit IRC02:17
*** mitz_ has joined #openstack-swift02:18
*** hhuang has joined #openstack-swift02:27
*** mrsnivvel has quit IRC02:33
openstackgerritA change was merged to openstack/swift: fix a comment  https://review.openstack.org/12544602:39
*** jamiehannaford has quit IRC02:43
*** X019 has quit IRC02:51
*** mahatic has joined #openstack-swift02:51
*** X019 has joined #openstack-swift02:54
*** Alex_Gaynor has left #openstack-swift03:02
*** openstackgerrit has quit IRC03:08
*** openstackgerrit has joined #openstack-swift03:11
*** mrsnivvel has joined #openstack-swift03:13
*** openstackgerrit has quit IRC03:18
*** openstackgerrit has joined #openstack-swift03:19
*** oomichi has joined #openstack-swift03:25
*** mlauter has joined #openstack-swift03:28
*** nosnos has quit IRC03:29
*** nosnos has joined #openstack-swift03:30
*** DisneyRicky has quit IRC03:31
*** nosnos has quit IRC03:34
*** mlauter has quit IRC03:35
openstackgerritMichael Barton proposed a change to openstack/swift: sendfile for GETs  https://review.openstack.org/12554804:03
redbooh I forgot to run flake804:07
*** vdreamarkitex has quit IRC04:07
openstackgerritMichael Barton proposed a change to openstack/swift: sendfile for GETs  https://review.openstack.org/12554804:09
*** nosnos has joined #openstack-swift04:19
*** haomaiwang has joined #openstack-swift04:50
*** DisneyRicky has joined #openstack-swift04:59
*** haomaiwang has quit IRC05:02
*** haomaiwang has joined #openstack-swift05:02
*** SkyRocknRoll__ has joined #openstack-swift05:12
*** haomaiw__ has joined #openstack-swift05:15
*** haomaiw__ has quit IRC05:16
*** haomaiwang has quit IRC05:16
*** haomaiwang has joined #openstack-swift05:17
openstackgerritMatthew Oliver proposed a change to openstack/swift: Basic container sharding middleware  https://review.openstack.org/12555305:27
*** haomaiwang has quit IRC05:35
*** haomaiwa_ has joined #openstack-swift05:35
*** hhuang has quit IRC05:46
*** ttrumm has joined #openstack-swift06:05
*** ttrumm_ has joined #openstack-swift06:08
*** oomichi__ has joined #openstack-swift06:08
openstackgerritKota Tsuyuzaki proposed a change to openstack/swift: Efficient Replication for Distributed Regions  https://review.openstack.org/9982406:10
*** ttrumm has quit IRC06:10
*** oomichi has quit IRC06:10
*** oomichi__ has quit IRC06:27
*** X019 has quit IRC06:44
*** X019 has joined #openstack-swift06:44
openstackgerritMatthew Oliver proposed a change to openstack/swift: Basic container sharding middleware  https://review.openstack.org/12555306:50
openstackgerritMichael Barton proposed a change to openstack/swift: sendfile for GETs  https://review.openstack.org/12554806:55
*** SkyRocknRoll__ has quit IRC07:23
*** hhuang has joined #openstack-swift07:27
*** geaaru has joined #openstack-swift07:29
mattoliverauWell I'm calling it a night, nigth all... if anyone is around.. channel is eerily quiet with everyone at the hackathon07:40
*** jistr has joined #openstack-swift07:42
*** mitz_ has quit IRC07:53
*** mitz_ has joined #openstack-swift07:55
*** jamiehannaford has joined #openstack-swift07:59
*** hhuang has quit IRC08:25
*** nellysmitt has joined #openstack-swift08:51
*** kopparam has joined #openstack-swift08:55
*** ttrumm_ has quit IRC09:05
*** ttrumm_ has joined #openstack-swift09:07
*** ttrumm has joined #openstack-swift09:11
*** ttrumm_ has quit IRC09:11
*** ttrumm_ has joined #openstack-swift09:12
*** ttrumm has quit IRC09:15
*** hhuang has joined #openstack-swift09:22
*** ttrumm_ has quit IRC09:24
*** ttrumm has joined #openstack-swift09:24
*** mkollaro has joined #openstack-swift09:31
*** shaifali_ has joined #openstack-swift09:38
*** shaifali_ has quit IRC09:38
*** shaifali_ has joined #openstack-swift09:39
*** shaifali_ has quit IRC09:39
*** shaifali_ has joined #openstack-swift09:40
*** aix has joined #openstack-swift09:51
*** oomichi has joined #openstack-swift10:03
*** nellysmitt has quit IRC10:04
*** vdreamarkitex has joined #openstack-swift10:05
*** hhuang has quit IRC10:23
*** Dafna has quit IRC10:31
*** Dafna has joined #openstack-swift10:37
*** X019 has quit IRC10:46
*** nellysmitt has joined #openstack-swift10:46
*** nosnos has quit IRC10:50
*** nosnos has joined #openstack-swift10:51
*** nosnos has quit IRC10:55
*** mahatic has quit IRC10:56
*** X019 has joined #openstack-swift10:58
*** dmsimard_away is now known as dmsimard11:07
*** mahatic has joined #openstack-swift11:21
*** hhuang has joined #openstack-swift11:28
*** judd7 has joined #openstack-swift11:49
*** NM1 has joined #openstack-swift12:08
*** NM1 has quit IRC12:09
*** addnull has quit IRC12:28
*** shaifali_ has quit IRC12:29
*** X019 has quit IRC12:31
*** X019 has joined #openstack-swift12:31
*** hhuang has quit IRC12:32
*** oomichi has quit IRC12:32
*** fifieldt has joined #openstack-swift12:37
*** elambert has joined #openstack-swift12:39
*** NM1 has joined #openstack-swift12:41
*** elambert has quit IRC12:47
*** miqui has joined #openstack-swift12:50
dmsimardgood morning everyone12:59
dmsimardI'm trying to troubleshoot an issue with object-auditor looping infinitely in a bit of a crazy way. Can't see why. Logs (even in debug) aren't showing any errors or stack traces.13:00
dmsimardI traced the process and perhaps it might talk to you guys because it doesn't ring me a bell: http://paste.openstack.org/show/nAHuIsGoOruZ8yP5g161/13:00
*** NM1 has quit IRC13:00
dmsimardI've done the usual like checking syslogs, dmesg, checking drives health and permissions - nothing obvious showing up.13:00
*** NM1 has joined #openstack-swift13:01
dmsimardIt's only doing this in one of six storage nodes of a cluster split in three zones that is not yet in production. It's really pretty much empty (10GB total used reported by swift-recon)13:02
*** mwstorer has joined #openstack-swift13:06
*** ppai has joined #openstack-swift13:07
ahalethe trace kinda looks like it is just doing really fast passes of the mostly empty disk.. does that box have significantly less of the total compared to the rest ?13:09
*** elambert has joined #openstack-swift13:10
*** lcurtis has joined #openstack-swift13:12
dmsimardahale: Nope, they're all identical as far as I know. Both for hardware and software13:16
dmsimardahale: It's looping endlessly, I would understand a "fast pass", like, every now and then13:16
ahaleah no i meant less of that total 10GB disk usage13:16
dmsimardahale: At a glance, I see probably 1GB on that node.13:17
dmsimardNo more than 1.513:17
notmynamegood morning13:21
*** zaitcev has joined #openstack-swift13:25
*** ChanServ sets mode: +v zaitcev13:25
*** CaioBrentano has joined #openstack-swift13:26
*** tdasilva has joined #openstack-swift13:28
zaitcevdmsimard: what exact version are you running? e.g. python -c "import swift; print swift.__version__"13:28
dmsimardzaitcev: 1.13.1, packaged by Ubuntu's cloud archive13:28
zaitcevgo go gadget git checkout 1.13.113:29
*** CaioBrentano has quit IRC13:31
zaitcevoh, brother... http://www.zaitcev.us/things/dmsimard-auditor.diff13:31
zaitcevNever mind that parallel stuff, but you want that  self._sleep()13:32
dmsimardzaitcev: That's the diff from the master branch  ?13:33
zaitcevdmsimard: yes13:33
dmsimardzaitcev: git blame's giving me this commit for the patch that introduced the sleep: https://github.com/openstack/swift/commit/d317888a7eae276ae9dddf26a9030d01f6ba00fe13:35
*** CaioBrentano has joined #openstack-swift13:37
zaitcevno, it's actually bcdafa3831111f334caadd30505f051c81abcb1f13:37
dmsimardzaitcev: Oh, and that commit message exactly matches the issue I have :)13:38
dmsimardDo you know what version of Swift is matched with Juno ? Is it 2.0 or 2.1.0 ?13:39
zaitcevI'm pretty certain it's 2.1.013:39
notmynamethe juno release will include swift 2.2.013:40
notmynamewe've already released 2.1.013:40
zaitcevwell yeah... but he needs something to install today13:40
notmyname:-)13:41
zaitcevdmsimard: please continue from here and verify that your problem is actually fixed... I need something urgent to do here, so ttyl13:42
dmsimard2.2.0 !? :)13:42
zaitcevdmsimard: please continue from here and verify that your problem is actually fixed... I need something urgent to do here, so ttyl13:42
zaitcever13:42
dmsimarddmsimard: Sure.13:43
dmsimarder :p13:43
dmsimardzaitcev: sure13:43
*** nellysmitt has quit IRC13:49
*** CaioBrentano has quit IRC13:51
*** wasmum has joined #openstack-swift13:52
*** NM2 has joined #openstack-swift13:54
*** NM1 has quit IRC13:54
*** CaioBrentano has joined #openstack-swift13:54
*** DisneyRicky has quit IRC13:57
*** tsg has joined #openstack-swift13:58
*** vr1 has joined #openstack-swift14:02
vr1hello14:02
*** ttrumm has quit IRC14:06
openstackgerritDaniel Wakefield proposed a change to openstack/python-swiftclient: Replaces Stacktraces with useful error messages.  https://review.openstack.org/12540714:07
*** nellysmitt has joined #openstack-swift14:14
*** zaitcev has quit IRC14:16
*** DisneyRicky has joined #openstack-swift14:19
*** danw_ has joined #openstack-swift14:24
*** tsg has quit IRC14:24
*** kopparam has quit IRC14:26
*** nellysmitt has quit IRC14:28
*** nellysmitt has joined #openstack-swift14:29
*** danw_ has quit IRC14:30
*** nellysmitt has quit IRC14:33
*** vr1 has quit IRC14:34
*** vr1 has joined #openstack-swift14:35
*** nexusz99 has joined #openstack-swift14:35
*** nellysmitt has joined #openstack-swift14:38
NM2Does anyone recently migrate from version 1.x to version 2.x ? I'd like to know if there is anything else to worry beside storage policies…14:42
*** AnjuT has joined #openstack-swift14:49
lcurtisall, is it possible to actually run vm's in swift?14:51
lcurtisor used only to store images?14:51
jokke_lcurtis: swift is for storing "any" objects. Nova would be the compute part14:52
lcurtisthank you jakke14:52
lcurtisso in other words, i could store a kvm img in swift and run from the compute node?14:53
jokke_lcurtis: you want to store your image in Glance (which may use Swift as a back end) and you run it on Nova ;)14:54
lcurtislol14:54
lcurtisokay...still more reading to do14:54
lcurtisthank you14:54
jokke_lcurtis: good place to start from is http://www.openstack.org/software/14:55
lcurtisbut technically i could use either swift or cinder as back end for images?14:55
lcurtisi have been reading there...perhaps just not understanding fully14:56
*** nexusz99 has quit IRC14:57
NM2lcurtis: You never understand cloud computing on the first reading. I took 6 months to 'really' understand the ring :)14:58
jokke_lcurtis: Glance supports multiple storage drivers, more info from http://docs.openstack.org/developer/glance/configuring.html#configuring-the-filesystem-storage-backend14:58
*** NM2 is now known as NM14:59
lcurtiswould one really need cinder if vm's can be stored in swift?15:00
notmynamelcurtis: you don't run VMs from swift. but swift can store the images.15:00
*** nellysmitt has quit IRC15:00
notmynamelcurtis: cinder is for persistent block devices attached to your Vms15:00
lcurtisokay...so images are ephemeral in swift?15:01
notmynameno15:01
notmynameswift is durable storage15:01
lcurtishmm15:01
notmynamelcurtis: here's a good overview of swift https://swiftstack.com/openstack-swift/15:01
notmynamelcurtis: so swift is a place to put data. it can be deployed alongside nova and other openstack components or it can be deployed independently15:02
notmynamelcurtis: one kind of data people put in swift is VM images. and the way to do that using the rest of openstack is to use glance15:03
lcurtisso glance stores the image and runs the image using api calls to swift?15:03
lcurtisive read quite a few docs and listened to many youtubes on the commute home15:04
notmynamelcurtis: glance tracks where the image is stored. a user sends an API call to glance to store (or load) and image, and glance sends API calls to swift. the VMs don't run from swift, but glance pulls the data to the VM host machine and then runs it there15:05
lcurtisokay...if i wanted to do something like live migration, could i use either cinder or swift15:07
lcurtisAh...think I get it15:14
lcurtishttp://www.gossamer-threads.com/lists/openstack/dev/2195615:14
lcurtisso images would be static in swift15:14
notmynamelcurtis: correct15:15
*** tsg has joined #openstack-swift15:15
lcurtisand then i could use cinder to achieve live migration15:15
lcurtiscoming from vmware sab vsphere bkgd15:16
lcurtissan15:16
*** nexusz99 has joined #openstack-swift15:16
*** tgohad has joined #openstack-swift15:17
*** tsg has quit IRC15:20
*** annegent_ has joined #openstack-swift15:23
*** vr1 has quit IRC15:24
lcurtisnotmyname..thanks for your help15:30
lcurtismakes sense now15:30
notmynamegreat!15:31
*** vr1 has joined #openstack-swift15:31
*** vdreamarkitex has quit IRC15:32
*** nexusz99 has quit IRC15:38
swift_fan1Hello -- I do not wish to include the "gatekeeper" and "dlo" middlewares into my Swift proxy-server.conf pipeline, but the proxy server error log keeps saying that the "Pipeline was modified" by adding the filters/middleware in.15:48
swift_fan1Is this a Swift bug?15:48
swift_fan1notmyname : Or is this intentional by Swift, and if so, then what's the reason ?15:49
swifterdarrellswift_fan1: they're both required15:49
swift_fan1swifterdarrell : Why/how so?15:49
*** rmcall has joined #openstack-swift15:49
swifterdarrellswift_fan1: gatekeeper ensures system metadata doesn't get out to clients and DLO (dynamic large object) functionality used to be embedded in Swift but was fully extracted into middleware15:50
swifterdarrellswift_fan1: if you don't want to see the messages about them being added, you may explicitly enter them in your pipeline15:50
swift_fan1swifterdarrell : Thanks. But why is it that they must be included in ?15:52
swift_fan1swifterdarrell : I can sort of see the reason for gatekeeper, but it seems that dlo can be done without.....15:52
swifterdarrellswift_fan1: because without gatekeeper your Swift will be broken, and without DLO you won't have the same Swift everyone who's ever had swift has had15:52
swifterdarrellswift_fan1: they're simply required15:52
swifterdarrellswift_fan1: DLO is a functionality of Swift and always has been15:53
swift_fan1swifterdarrell : Is there a list of required Swift middleware vs. non-required Swift middleware ?15:54
swifterdarrellswift_fan1: probably in the code wherever gatekeeper and dlo get added15:54
swift_fan1swifterdarrell : Or is all the middleware that is initially available with a standard Swift installation, all required to be in the pipeline ?15:55
swifterdarrellswift_fan1: and/or maybe in the docs somewhere? I don't remember15:55
swifterdarrellswift_fan1: they're definitely not all required15:55
swift_fan1swifterdarrell : For instance, like tempURL or formpost ?15:55
swift_fan1swifterdarrell : They are in the middleware list that initially just comes with a standard Swift installation, but would they have a good chance of being *non-required* middleware ?15:56
openstackgerritSimon Lorenz proposed a change to openstack/swift: Added flag to create unique tmp dir per strg node  https://review.openstack.org/12408815:58
*** ZBhatti has joined #openstack-swift15:59
*** kyles_ne has joined #openstack-swift16:00
swifterdarrellswift_fan1: gatekeeper and dlo are probably the only "required" middlewares and they are added automatically in order to not break existing deployments16:00
swifterdarrellswift_fan1: you could consider an auth middleware "required" if you want any permissions enforcement16:01
swifterdarrellswift_fan1: you'd be crazy not to use proxy-logging (twice), but it's not "required"16:01
swifterdarrellswift_fan1: ditto for catch_errors16:02
swift_fan1swifterdarrell : Why would you care about an existing deployment, if all you're trying to do is set up your own, individual Swift cluster for your own use ?16:02
swifterdarrellswift_fan1: *blink* *bliink*16:03
swifterdarrellswift_fan1: are you asking why the developers of Swift care about deployments of Swift?16:03
swift_fan1swifterdarrell : I mean in scenarios where there isn't an existing deployment of Swift, and you're just trying to set one up (so there isn't an existing deployment in the first place).16:05
swifterdarrellswift_fan1: fresh deployments should probably be explicit vs. implicit and explicitly add the gatekeeper and dlo middleware16:05
swift_fan1swifterdarrell : But what if you want your Swift system to not care about dlo functionality ?16:06
swift_fan1or even gatekeeper16:06
swifterdarrellswift_fan1: you don't really get to do that16:06
swifterdarrellswift_fan1: this is like the bottom of the program where it does GOTO 1016:06
glangeswift_fan1: you can change the code to do what you want to do :)16:06
swifterdarrellswift_fan1: I feel like we already talked about how those are required16:06
swift_fan1glange swifterdarrell : So, if one wants to disable the dlo functionality for their Swift cluster, the only ways to do so are to (1) change the code itself (2,3,...) anything else that is recommended ?16:09
glangeswift_fan1: you maybe could write a middleware that prevents DLOs and use that -- that might be another option16:11
swift_fan1glange swifterdarrell : Because what if you're setting this up for some other people that you know, and you don't want them to utilize a particular functionality (such as dlo), then how do you make sure they they can't ?16:11
swift_fan1glange swifterdarrell : Other than just telling them not to use it.16:12
swift_fan1glange swifterdarrell : There are some reasons for this, but let's not focus on them right now. Thanks16:13
glangeanother option is to run an old version of swift that doesn't have dlo in it :)16:15
swifterdarrellheh16:15
*** CaioBrentano has quit IRC16:26
ahaleif you dont want people to use it set rate limit to a year per segment and kick in after the first segment.. or something16:27
*** ttrumm has joined #openstack-swift16:28
*** gyee has joined #openstack-swift16:30
*** vr1 has quit IRC16:32
*** ZBhatti has quit IRC16:41
*** swift_fan1 has quit IRC16:45
*** jistr has quit IRC16:45
*** AnjuT has quit IRC16:49
*** mkollaro has quit IRC17:05
*** shri has joined #openstack-swift17:11
*** tgohad has quit IRC17:19
*** CaioBrentano has joined #openstack-swift17:23
*** rmcall_ has joined #openstack-swift17:23
*** rmcall has quit IRC17:24
*** rmcall_ is now known as rmcall17:24
*** rmcall_ has joined #openstack-swift17:31
*** elambert has quit IRC17:31
*** rmcall has quit IRC17:31
*** mkollaro has joined #openstack-swift17:32
openstackgerritRichard Hawkins proposed a change to openstack/swift: Fix metadata overall limits bug  https://review.openstack.org/12536017:34
*** ZBhatti has joined #openstack-swift17:34
*** rmcall has joined #openstack-swift17:34
*** rmcall_ has quit IRC17:35
*** mwstorer has quit IRC17:37
*** ttrumm has quit IRC17:38
*** aix has quit IRC17:44
*** kopparam has joined #openstack-swift17:48
*** mkollaro has quit IRC17:49
*** geaaru has quit IRC17:50
*** elambert has joined #openstack-swift17:50
*** elambert has quit IRC17:50
*** kopparam has quit IRC17:52
*** swift_fan has joined #openstack-swift17:54
*** bill_az has joined #openstack-swift17:56
*** annegent_ has quit IRC18:00
*** htrmeira has joined #openstack-swift18:01
*** annegent_ has joined #openstack-swift18:08
swift_fanahale : A year per segment ?18:11
swift_fanahale : Is that a feasible solution ?18:12
swift_fanahale : Do you literally mean just only 1 segment, per year ?18:12
ahalei guess, its more silly really.. a day would do probably, cant remember if its swift that limits reqs to 24 hours or my lbs18:13
swift_fanglange swifterdarrell (as well).18:13
swift_fanahale : So, what does setting the rate limit to only 1 segment per day or year, have any relation to restricting others from using dlo ?18:14
ahaleits just not really something you'd wanna really hard disable since you want to permit tools to work that might assume its there as it was a core part pf proxy-server in the past18:14
swift_fanThanks18:14
ahalenah its in the dlo conf only .. check out the samples18:14
ahaleit would still accept requests for them, just make it totally impossible to use meaningfully.. discourage rather than disallow18:15
*** kopparam has joined #openstack-swift18:18
*** nellysmitt has joined #openstack-swift18:23
NMIs it possible that swif changed the ring files by itself?  In case of a drive failed or something like that.18:24
*** kopparam has quit IRC18:24
swift_fanahale : That's actually pretty clever!18:26
*** jamiehannaford has quit IRC18:36
glangeswift_fan: you can also make your swift cluster have unlimited capacity if you use a write only middleware :)18:50
*** tsg has joined #openstack-swift18:58
*** theanalyst has quit IRC19:00
*** kyles_ne has quit IRC19:00
*** kyles_ne has joined #openstack-swift19:01
*** kyles_ne has quit IRC19:05
*** theanalyst has joined #openstack-swift19:14
openstackgerritJay Bryant proposed a change to openstack/swift: Handle os.listdir failures in object-updater  https://review.openstack.org/12574619:18
*** mahatic has quit IRC19:26
notmynameNM: no. swift doesn't change the ring automatically19:36
*** ChanServ changes topic to "Swift 2.1.0 https://launchpad.net/swift/+milestone/2.1.0 | Swift Review Dashboard: http://bit.ly/1iVBigF | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews | Ideas: https://wiki.openstack.org/wiki/Swift/ideas | Kilo summit topics: https://etherpad.openstack.org/p/kilo-swift-summit-topics"19:45
notmynamenote the https://etherpad.openstack.org/p/kilo-swift-summit-topics in the topic now. this is the place to add summit session topics19:46
*** annegent_ has quit IRC19:51
*** kopparam has joined #openstack-swift19:52
*** bgmccollum has joined #openstack-swift19:52
swift_fanglange : What do you mean ?19:55
swift_fan??19:55
swift_fanglange : unlimited capacity ?19:56
notmynameswift_fan: he's not being serious. or actually, he is, but it's a totally unusable thing19:56
notmynameswift_fan: see http://www.supersimplestorageservice.com (hint: it's a joke)19:56
swift_fannotmyname : I know it was facetious, but I was wondering what this "unusable thing" is, regardless .......19:56
notmynamewrite only storage?19:57
notmyname /dev/null as a server?19:57
notmyname*service19:57
swift_fannotmyname : ?19:57
glangeswift_fan: if you write data and never read it, why do I even have to store it?19:58
glangeI can accept a lot of data if I don't have to store it19:59
NMnotmyname: Thanks. I think my ring got corrupted but I found some backups on the /etc/swift/backups dir. I'm thinking about to use then to restore the ring… Any thoughts?20:00
*** aerwin has joined #openstack-swift20:01
notmynameNM: yup. that's what the backups are for :-)20:02
*** aerwin has left #openstack-swift20:03
*** aerwin has joined #openstack-swift20:03
NMnotmyname: :)20:05
notmynameNM: so the trick would be to know what's changed in your infra since that backup was made20:05
notmynameNM: ie you don't want to deploy a ring that is going to cause a huge data movement problem in your prod cluster20:06
*** occupant has quit IRC20:06
*** occupant has joined #openstack-swift20:09
*** kopparam has quit IRC20:09
*** occupant has quit IRC20:09
*** ZBhatti has quit IRC20:09
openstackgerritAlistair Coles proposed a change to openstack/python-swiftclient: Fix cross account upload using --os-storage-url  https://review.openstack.org/12575920:09
*** kopparam has joined #openstack-swift20:10
*** occupant has joined #openstack-swift20:10
*** exploreshaifali has joined #openstack-swift20:13
*** kopparam has quit IRC20:14
exploreshaifaliI am trying to install swift in vmware, using vagrant, but getting "vagrant cannot detect virtualbox" error http://pastebin.com/5iGnvJse20:16
notmynameexploreshaifali: does vagrant support vmware these days?20:16
notmynameI know it originally was virtualbox only, but maybe they added vmware fusion support20:16
exploreshaifaliso I should try only with virtualbox20:17
notmynameI know that works20:17
exploreshaifaliokay20:17
exploreshaifali;20:17
exploreshaifali:)20:17
NMnotmyname: I was checking my ring and found this output object.builder, build version 020:17
NM262144 partitions, 3.000000 replicas, 0 regions, 0 zones, 0 devices, 0.00 balance20:17
NMI cant understand how it has 0 region/zone/devices but still works...20:18
NMBtw, this is a production cluster.20:18
*** annegent_ has joined #openstack-swift20:18
*** annegent_ has quit IRC20:19
*** annegent_ has joined #openstack-swift20:20
notmynameNM: don't push that ring. it doesn't have anything added20:21
*** kyles_ne has joined #openstack-swift20:21
openstackgerritRichard Hawkins proposed a change to openstack/swift: Fix metadata overall limits bug  https://review.openstack.org/12536020:22
NMnotmyname: that is the what is disturbing me:  the swift is running with this empty ring.20:23
notmynameNM: a backup is created on create() and on rebalance(). so what you are looking at is the one from the create() call. basically, just setting the replica count and part power20:23
notmynamesurely you have a different .ring.gz deployed20:23
*** nellysmitt has quit IRC20:23
notmynameNM: here's the help message that might (but I hope not!) be useful to you:20:25
notmynameswift-ring-builder <ring_file> write_builder [min_part_hours]20:25
notmyname    Recreate a builder from a ring file (lossy) if you lost your builder20:25
notmyname    backups.  (Protip: don't lose your builder backups).20:25
notmyname    [min_part_hours] is one of those numbers lost to the builder,20:25
notmyname    you can change it with set_min_part_hours.20:25
notmynameNM: if you really have lost your backups and corrupted your ring but you still have a .ring.gz around, you can use that command to (mostly) recreate your builder file20:26
notmynameNM: also, if you're at that point and this is necessary, then you also have to buy clayg a beer for writing it ;-)20:26
NMOn 2015 summit I can pay on for him and you for your help :)20:27
NMI think that explains why I can't see the devices on my ring but it still works...20:28
notmynameNM: so if you are at the point where you only have some .ring.gz files but you don't have any builder files, then you need to fix that ASAP and then audit your ring builder backup process20:29
NMThe backups files seens to be fine. I ran swift-ring-builder and the output was as expected20:31
notmynameNM: and you have old backup files? eg you should have builder files in the backups dir after the rebalance20:31
notmynamefrom before when it got whatever corruption you mentioned20:31
NMYes I have both.20:32
notmynameah, good20:32
notmynameso you're ok then20:32
*** mlauter has joined #openstack-swift20:32
NMI hope so. I'll restore then and watch my monitor.20:32
notmynamewell, wait. don't push deploy yet20:33
notmynameso the builder files don't have to be deployed anywhere20:33
notmynamethey're just there to build the ring.gz files20:33
NMThat was something that I always wanted to know :)20:33
notmynamebut since you're pulling a builder file from backup, then check it out to ensure that everything looks right. like I said, you don't want to push out some ring that's radically different and cause a bunch of data movement (at best) or unavailability (at worse)20:34
*** htrmeira has quit IRC20:35
NMIf I just run swift-ring-builder on my ring file, and the output is what I expected, should I deploy? I haven't modify my server/disks.20:35
notmynameNM: well, I don't want to be the guy who tells you to deploy or not ;-)20:37
NMHahahahaha! In your place I'd say the same thing.20:38
notmynameNM: but yeah, the first level of checking would be so see if the ring-builder output is what you expect. the right zones in the right places, etc20:38
NMWell, it's done. Lets see :D20:38
notmyname"NM, why is our site offline?" "well, some guy on the internet said it probably wouldn't break"20:38
*** zul has quit IRC20:44
*** aerwin has quit IRC20:47
*** rmcall has quit IRC20:55
*** HenryG has quit IRC20:55
*** annegent_ has quit IRC20:56
*** tsg has quit IRC21:09
openstackgerritSamuel Merritt proposed a change to openstack/swift: Fix ring-builder crash.  https://review.openstack.org/12579321:26
openstackgerritRichard Hawkins proposed a change to openstack/swift: Fix metadata overall limits bug  https://review.openstack.org/12536021:30
NMnotmyname: Actually I could name you. Your name is pretty common here :)21:31
notmynameheh. also, uh oh.21:31
*** mikehn has quit IRC21:39
*** corvus has quit IRC21:40
*** mikehn has joined #openstack-swift21:40
*** corvus has joined #openstack-swift21:41
*** tsg has joined #openstack-swift21:52
*** tsg has quit IRC21:57
*** mlauter has quit IRC21:58
openstackgerritJohn Dickinson proposed a change to openstack/swift: Ensure sys.exit called in fork_child after exception  https://review.openstack.org/12519721:59
notmynameI only fixed the spelling error. and approved it22:00
openstackgerritRichard Hawkins proposed a change to openstack/swift: Fix metadata overall limits bug  https://review.openstack.org/12536022:03
NMWell, I think I can leave now. Everything seens fine….22:04
*** tsg has joined #openstack-swift22:05
notmynameNM: nice22:12
NMTomorrow I'll fix the other storage nodes. I think it's a good idea to commit our ring files at git.22:13
notmynameNM: yeah, I know another swift deployer that uses VCS for storing configs (and rings are really just config files. sortof.)22:14
mattoliverauMorning all22:14
notmynamehi mattoliverau22:14
NMThank you guys! See you tomorrow! And congrats for the hackathon!22:15
mattoliverauYay some chatter in channel, its been very quiet with a hackathon going on!22:16
*** CaioBrentano has quit IRC22:16
mattoliverauHow's the hackathon going? Solved all the things yet?22:17
*** NM has quit IRC22:18
*** lcurtis has quit IRC22:19
notmynamemattoliverau: just about. looking at the last patch now22:29
notmynameit's been a very production week22:29
notmyname*productive22:30
*** sandywalsh has quit IRC22:33
mattoliverauAwesome, wish I could've been there, hopefully next time.22:33
*** sandywalsh has joined #openstack-swift22:36
notmynamehurricanerix: https://bugs.launchpad.net/swift/+bug/136535022:36
*** annegent_ has joined #openstack-swift22:37
openstackgerritRichard Hawkins proposed a change to openstack/swift: Fix metadata overall limits bug  https://review.openstack.org/12536022:38
*** annegent_ has quit IRC22:41
*** zul has joined #openstack-swift22:45
*** ZBhatti has joined #openstack-swift22:48
*** sandywalsh has quit IRC22:53
*** sandywalsh has joined #openstack-swift22:53
*** tdasilva has quit IRC22:53
*** ppai has quit IRC22:55
*** dmsimard is now known as dmsimard_away22:56
*** ZBhatti has quit IRC23:05
*** sandywalsh has quit IRC23:05
*** nosnos has joined #openstack-swift23:06
*** mlauter has joined #openstack-swift23:10
*** HenryG has joined #openstack-swift23:10
*** mlauter has quit IRC23:17
*** annegent_ has joined #openstack-swift23:19
*** annegent_ has quit IRC23:25
*** annegent_ has joined #openstack-swift23:28
*** annegent_ has quit IRC23:31
*** echevemaster has joined #openstack-swift23:34

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