Friday, 2019-05-17

*** zaitcev__ has joined #openstack-swift00:09
*** ChanServ sets mode: +v zaitcev__00:09
*** Guest28904 has quit IRC00:34
*** NM has joined #openstack-swift00:50
*** gkadam has joined #openstack-swift01:16
*** baojg has joined #openstack-swift01:22
*** diablo_rojo has quit IRC01:23
*** gkadam has quit IRC01:40
*** ianychoi has joined #openstack-swift02:00
openstackgerritMerged openstack/swift master: Set Content-Type with s3api metadata updates.  https://review.opendev.org/65894502:55
*** NM has quit IRC03:01
*** gkadam has joined #openstack-swift03:23
*** gkadam has quit IRC03:23
*** psachin has joined #openstack-swift03:41
*** blmt has quit IRC03:42
*** ianychoi has quit IRC03:49
*** ianychoi has joined #openstack-swift03:49
*** ianychoi has quit IRC03:51
*** ianychoi has joined #openstack-swift03:52
*** zaitcev__ has quit IRC04:39
*** zaitcev__ has joined #openstack-swift04:51
*** ChanServ sets mode: +v zaitcev__04:51
*** pcaruana has joined #openstack-swift05:20
*** baojg has quit IRC06:01
*** baojg has joined #openstack-swift06:36
*** hseipp has joined #openstack-swift06:47
*** tesseract has joined #openstack-swift07:08
*** rdejoux has joined #openstack-swift07:10
*** rcernin has quit IRC07:19
*** ccamacho has joined #openstack-swift07:27
openstackgerritAlexandre Lécuyer proposed openstack/swift master: Specify pickle protocol in REPLICATE()  https://review.opendev.org/65961407:41
*** zaitcev__ has quit IRC08:20
*** kota_ has quit IRC08:26
*** kota_ has joined #openstack-swift08:26
*** ChanServ sets mode: +v kota_08:26
*** ccamacho has quit IRC08:27
*** zaitcev__ has joined #openstack-swift08:31
*** ChanServ sets mode: +v zaitcev__08:31
*** tkajinam has quit IRC08:44
*** baojg has quit IRC08:45
*** baojg has joined #openstack-swift08:50
*** ccamacho has joined #openstack-swift08:59
*** baojg has quit IRC09:06
*** baojg has joined #openstack-swift09:07
*** zaitcev_ has joined #openstack-swift09:07
*** ChanServ sets mode: +v zaitcev_09:07
*** zaitcev__ has quit IRC09:11
*** e0ne has joined #openstack-swift09:17
*** baojg has quit IRC09:32
*** zaitcev__ has joined #openstack-swift09:42
*** ChanServ sets mode: +v zaitcev__09:42
*** zaitcev_ has quit IRC09:46
*** rcernin has joined #openstack-swift09:50
*** baojg has joined #openstack-swift11:02
*** henriqueof has joined #openstack-swift11:06
*** rcernin has quit IRC11:36
*** zaitcev__ has quit IRC11:56
*** hseipp has quit IRC12:00
*** zaitcev__ has joined #openstack-swift12:08
*** ChanServ sets mode: +v zaitcev__12:08
*** ccamacho has quit IRC12:15
*** cwright has quit IRC12:42
*** cwright has joined #openstack-swift12:43
*** ccamacho has joined #openstack-swift13:25
*** zaitcev__ is now known as zaitcev13:41
*** NM has joined #openstack-swift14:03
*** baojg has quit IRC14:16
*** baojg has joined #openstack-swift14:16
*** baojg has quit IRC14:16
*** baojg has joined #openstack-swift14:17
*** baojg has quit IRC14:17
*** baojg has joined #openstack-swift14:18
*** baojg has quit IRC14:19
*** baojg has joined #openstack-swift14:19
*** baojg has quit IRC14:19
*** baojg has joined #openstack-swift14:21
*** baojg has quit IRC14:21
*** baojg has joined #openstack-swift14:22
*** baojg has quit IRC14:23
*** baojg has joined #openstack-swift14:23
*** baojg has quit IRC14:23
*** baojg has joined #openstack-swift14:24
*** baojg has quit IRC14:24
*** baojg has joined #openstack-swift14:25
*** baojg has quit IRC14:25
*** baojg has joined #openstack-swift14:25
*** baojg has quit IRC14:26
*** baojg has joined #openstack-swift14:26
*** baojg has quit IRC14:27
*** baojg has joined #openstack-swift14:27
*** baojg has quit IRC14:27
*** baojg has joined #openstack-swift14:28
*** baojg has quit IRC14:28
*** baojg has joined #openstack-swift14:28
*** baojg has quit IRC14:29
*** baojg has joined #openstack-swift14:29
*** baojg has quit IRC14:30
*** baojg has joined #openstack-swift14:31
*** baojg has quit IRC14:31
*** baojg has joined #openstack-swift14:32
*** baojg has quit IRC14:32
*** baojg has joined #openstack-swift14:32
*** baojg has quit IRC14:33
*** baojg has joined #openstack-swift14:33
*** baojg has quit IRC14:34
*** baojg has joined #openstack-swift14:34
*** baojg has quit IRC14:34
*** baojg has joined #openstack-swift14:35
*** baojg has quit IRC14:35
*** baojg has joined #openstack-swift14:36
*** baojg has quit IRC14:36
*** baojg has joined #openstack-swift14:36
*** baojg has quit IRC14:37
*** baojg has joined #openstack-swift14:37
*** baojg has quit IRC14:38
*** baojg has joined #openstack-swift14:38
*** baojg has quit IRC14:38
*** baojg has joined #openstack-swift14:39
*** baojg has quit IRC14:39
*** baojg has joined #openstack-swift14:40
*** baojg has quit IRC14:41
*** baojg has joined #openstack-swift14:41
*** baojg has quit IRC14:42
*** baojg has joined #openstack-swift14:42
*** baojg has quit IRC14:42
*** baojg has joined #openstack-swift14:43
*** baojg has quit IRC14:43
*** gyee has joined #openstack-swift15:34
openstackgerritAlexandre Lécuyer proposed openstack/swift feature/losf: Add small unit tests for vfile and related modules  https://review.opendev.org/65951515:58
notmynamegood morning16:14
notmyname🎵Happy birthday to Swift!🎵16:14
alecuyerhello! happy birthday swift :-)16:15
*** tesseract has quit IRC16:17
*** psachin has quit IRC16:17
*** tesseract has joined #openstack-swift16:18
timburke🎉16:21
*** tesseract has quit IRC16:58
*** tesseract has joined #openstack-swift16:59
*** tesseract has quit IRC17:17
*** e0ne has quit IRC17:17
openstackgerritMerged openstack/swift master: Make build/upload/promote image jobs non-voting  https://review.opendev.org/65939117:27
openstackgerritTim Burke proposed openstack/swift master: Be explicit that a code path is just for py2  https://review.opendev.org/65985117:30
tdasilvatimburke: what was the decision about libec release?17:43
timburketdasilva, we should definitely do that. haven't gotten to it yet though :-)17:50
*** Alphazero_ has joined #openstack-swift17:51
tdasilvatimburke: was going to offer to help, i can start push buttons and prepare release notes...17:51
Alphazero_Hi all - I'm having real trouble installing Swift with JuJu - I keep getting the following error with Swift Proxy but I'm not sure what the problem is: http://paste.openstack.org/show/751530/17:51
timburketdasilva, that'd be great! thanks17:51
Alphazero_This is what my Swift proxy and Swift-Storage config file looks like: http://paste.openstack.org/show/751531/17:51
Alphazero_Any help or pointers would be appreciated thanks!17:52
timburkeAlphazero_, like notmyname I'm not real familiar with JuJu... am i right in thinking that the storage nodes are waiting on the proxy to come up? but then it looks like the proxy is refusing because it doesn't know about any storage nodes... hmm...17:54
Alphazero_thats correct - I was initially under the impression I was launching too few swift containers / too few swift zones - but with 15 of them up (3 per zone) - I can't see that being the issue17:56
timburkei wonder what `zone-assignment: auto` means/does...17:56
Alphazero_I think here: https://jaas.ai/swift-proxy/precise/46 - it automatically allocated new swift units to zones, in accordance with "balancing"17:58
Alphazero_I originally had it set to manual and was manually allotting units to zones - but that's resulted in the same issue17:58
Alphazero_this is the last last step of my openstack deployment (3 week long project) so keen to get it resolved :)17:59
timburkehuh. well, i definitely like to see more people deploying swift! let's see what we can do...18:00
Alphazero_I was originally following this guide - https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/install-openstack.html - but swift has been been giving me problems there too18:00
timburkeso what are the juju commands you've run to get to this point?18:00
Alphazero_this is effectively the order of commands: http://paste.openstack.org/show/751532/18:05
timburkeseems to make sense given the docs... i wonder if we can get some insight into what juju thinks the ring assignments ought to look like18:11
Alphazero_I'm new to that part I'm afraid - I actually started out trying to build it with just one swift node - but I haven't been able to get swift-proxy and swift-storage to talk to each other successfully no matter how many or how few units or zones are deployed18:13
Alphazero_nothing fails but this message is where it sits "Not enough storage zones for minimum replicas" and then everything becomes idle18:15
Alphazero_and there's not a whole lot to change in the config file :)18:16
timburkei wonder if it'd work with a minimal sort of a cluster: just one replica and one unit each for proxy and storage18:16
timburkeit really feels like a live-lock though: the proxy unit is blocked waiting for storage, but the storage doesn't want to come up until there's a proxy :-/18:18
timburkeinteresting... there are separate checks for # of nodes and # of zones: https://github.com/openstack/charm-swift-proxy/blob/cc280d9/lib/swift_utils.py#L1209-L121518:23
timburkeso it knows about the nodes... but is getting confused about the zones...18:23
timburkelooks like there are two failure paths in has_minimum_zones: https://github.com/openstack/charm-swift-proxy/blob/bec2714/swift_manager/manager.py#L183-L19918:25
timburkeso, is there any logging about "Not enough zones (X) defined to satisfy minimum replicas (need >= Y)"? do we know whether we'd see INFO level logs?18:26
timburkeif *not*... i guess it means the ring file doesn't exist yet?18:27
timburkeor maybe it's looking for a ring builder file...18:28
openstackgerritMerged openstack/swift master: Wait longer for log lines in unit test  https://review.opendev.org/65279118:30
timburkewow... i wonder when these got lifted: https://github.com/openstack/charm-swift-proxy/blob/bec2714/swift_manager/manager.py#L206-L23018:30
timburkeand at what point (if ever) they'd be able to move to the "new" builder format...18:31
Alphazero_http://paste.openstack.org/show/751536/ - these are the and debug logs related to Swift-proxy shown by "Juju Debug-log"18:33
timburkeor... no... i was thinking of the ring file that has a new format... i've just been meaning to get around to doing a new format for the builder, too :P18:34
timburkehuh. so ctxt['allowed_hosts'] knows about the storage nodes... but when we open up the ring builder, it doesn't have any devs at all...18:36
Alphazero_Could this be it - is there supposed to be relation between the Swift-storage zones - and units added?18:37
Alphazero_unit-swift-storage-zone2-5: 19:35:13 INFO unit.swift-storage-zone2/5.juju-log proxy relations's interface, swift-storage, is related but has no units in the relation.18:37
*** itlinux has joined #openstack-swift18:38
timburkethat'd make some sense. i woulda thought your `sudo juju add-unit --to lxd:3 swift-storage-zone2` would have added a unit for the zone, but ¯\_(ツ)_/¯18:41
Alphazero_haha same here18:41
Alphazero_but I can't seem to individually create those relations18:43
Alphazero_plus as you rightly say the command seems to do (atleast from how it appears in juju status) what its supposed to do18:44
timburkedo you see any logs about "Added new device to ring ..."?18:48
Alphazero_I originally had it setup as manual - I might take it down and and rerun the whole thing with auto set in the proxy file...18:48
Alphazero_I'll take a loot18:48
Alphazero_*look18:48
*** mvkr has joined #openstack-swift18:49
timburkeor "Storage relation changed -processing"18:49
timburkeor anything about devices "already processed" or "already in the ring" or "already mounted", or "Format device ... failed"18:56
Alphazero_aha!18:56
timburkei love those moments!18:57
Alphazero_http://paste.openstack.org/show/751540/18:59
Alphazero_I think I've messed up somewhere in defining the block device18:59
Alphazero_it funny because after going through config changed state - it basically kept waiting the proxy - but I guess all was not well!19:00
Alphazero_In my swift beginners mind I thought the block device was just the partition of the physical device?19:01
Alphazero_what MAAS shows is the following: https://pasteboard.co/If9Kuaz.png19:03
Alphazero_if you know what I should be setting the block device as that would be helpful :) - given that swift-storage units are running in containers I don't fully understand how they would interact with a physical disk - but I guess that was a heroic solution on my end!19:06
zaitcevSwift consumes a filesystem, not a block device. So, containers can bind-mount from the host.19:08
timburkewell, the /dev/sda-part1 definitely looks fishy -- i would've expected something more like /dev/sda1, which would imply you'd want just 'block-device: sda1'19:08
timburkebut i'm also more than a little fuzzy on how containers are supposed to be interacting with physical disks ;-)19:09
timburkezaitcev, poking at the charms source, it looks like they take care of formatting as xfs19:09
zaitcevThey can bind-mount /dev too. Usually it's done so host's /dev/log is visible. But if so, they can also access /dev/sda. It can be hazardous if you manage to start two of them though.19:10
timburkeyeah, i was just thinking that19:12
Alphazero_the juju docs for the swift proxy charm have this as the "block device": "/etc/swift/storage.img|2G"19:17
Alphazero_but is that something that gets created in the container (on its filesystem)?19:17
timburkei think so -- i'm guessing that's why they say "Good for development and testing." re: that format on https://jaas.ai/swift-storage19:18
timburkepresumably, for prod you'd want a real disk19:19
Alphazero_hmm so that hasn't worked it gives a very clear error with that ie "/etc/swift/storage.img|2G" set as the block device19:47
Alphazero_https://pastebin.com/bkNai72m19:48
Alphazero_http://paste.openstack.org/show/751545/ - basically all the swift-storage containers have error'd out19:49
Alphazero_I'm tempted to go for "guess" now that I've seen that as an option! :P19:49
Alphazero_within the debug log - this I think is the key line: unit-swift-storage-zone2-7: 20:49:52 DEBUG unit.swift-storage-zone2/7.config-changed subprocess.CalledProcessError: Command '['losetup', '--find', '/etc/swift/storagedev1.img']' returned non-zero exit status 1. unit-swift-storage-zone2-7: 20:49:52 ERROR juju.worker.uniter.operation hook "config-changed" failed: exit status 119:51
*** pcaruana has quit IRC20:02
*** itlinux has quit IRC20:06
*** zaitcev_ has joined #openstack-swift20:11
*** ChanServ sets mode: +v zaitcev_20:11
*** zaitcev has quit IRC20:15
notmynamehttp://d.not.mn/swift_cake_9th_bday.jpg  <--- cake for the birthday!20:16
*** zaitcev_ is now known as zaitcev20:36
*** rdejoux has quit IRC20:37
*** Alphazero_ has quit IRC20:45
zaitcevtimburke: so, how about we accept patch 657505 (alt-bulk)?20:53
patchbothttps://review.opendev.org/#/c/657505/ - swift - py3: bulk -- alternate approach - 4 patch sets20:53
timburkeWFM!20:53
zaitcevokay20:53
zaitcevI'm working on SLO and I'm tired of being careful not to push a wrong version of bulk by mistake.20:54
timburkeyeah, that's fair20:55
*** tdasilva has quit IRC20:55
*** NM has quit IRC21:07
*** henriqueof has quit IRC21:55
*** itlinux has joined #openstack-swift21:57
*** zaitcev_ has joined #openstack-swift22:19
*** ChanServ sets mode: +v zaitcev_22:19
*** zaitcev has quit IRC22:22
*** zaitcev_ has quit IRC22:29
*** zaitcev_ has joined #openstack-swift22:41
*** ChanServ sets mode: +v zaitcev_22:41
openstackgerritMerged openstack/swift master: py3: bulk -- alternate approach  https://review.opendev.org/65750522:49
*** itlinux_ has joined #openstack-swift22:51
*** itlinux has quit IRC22:52
*** zaitcev_ has quit IRC22:53
*** zaitcev_ has joined #openstack-swift23:05
*** ChanServ sets mode: +v zaitcev_23:05
openstackgerritPete Zaitcev proposed openstack/swift master: py3: slo  https://review.opendev.org/65050723:12
*** zaitcev_ has quit IRC23:19
*** mvkr has quit IRC23:21
*** gyee has quit IRC23:25

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