Wednesday, 2017-08-23

*** baojg has joined #openstack-swift00:00
*** baojg has quit IRC00:06
*** rmcall has quit IRC00:07
*** baojg has joined #openstack-swift00:07
*** baojg has quit IRC00:12
*** baojg has joined #openstack-swift00:13
kota_good morning00:15
kota_mattoliverau, notmyname: currently I don't have any special topics for 0700 meeting00:16
mattoliveraukota_: morning00:16
*** baojg has quit IRC00:17
*** baojg has joined #openstack-swift00:18
*** two_tired has joined #openstack-swift00:19
*** mbirru has joined #openstack-swift00:25
*** shuyingya has joined #openstack-swift00:25
mbirruHi00:26
mbirruCould somebody help me to figureout the issue I am  seeing the "Account HEAD failed: http://A1-39978-controller:8080/v1/AUTH_380ec248a37a402baf9f529e5b936326 503 Service Unavailable" for my "swift stat"00:27
mbirruhere my swift-proxy service is running on 8080 port00:28
tdasilvamattoliverau: sounds awesome! do you remember if the ring building part is working well?00:28
mbirrumattoliverau: First I would like thank you for kind response00:28
mattoliverautdasilva: it works... but definitely could be better. it needs swift installed on the localhost. and so there is a bit of a chicken and egg prob.00:30
mbirrumy ring building was success. here is the output https://pastebin.com/WFFJNTmr00:31
mattoliveraumbirru: your welcome, tho I must admit, I can't remember, its been a crazy last few months :)00:31
*** baojg has quit IRC00:32
tdasilvamattoliverau: oh yeah, i remember that00:32
*** kiennt has joined #openstack-swift00:32
mattoliveraumbirru: what does your proxy and account logs say?00:32
tdasilvayeah, sometimes i almost wish we would have a swift utils rpm00:32
*** baojg has joined #openstack-swift00:32
*** baojg has quit IRC00:33
mattoliveraumbirru: do you have account_autocreate enabled in the proxy config?00:34
mbirrumattoliverau: for my proxy-server I couldnt find logs. could you pint me where logs are writing by default. I am searching in /var/log00:35
mattoliveraumbirru: looking at your rings, it seems one of your devices in the account ring is pointing to /dev/sda600:36
mbirrumattoliverau: yes account_autocreate is true in proxy.conf00:36
mbirrumattoliverau: yes you are right .its pointing to /dev/sda600:37
mattoliveraumbirru: depends on how you set it up.. if you haven't given rsyslog rules to point to something like /var/log/swift/.. then they could be in /var/log/messages or /var/log/syslog depending on your distro.00:38
mattoliveraumbirru: you can't point them directly to the devices (the /dev) they need to point to mount points.00:38
mattoliverautdasilva: what are you still doing up anyway?00:39
tdasilvamattoliverau: just put baby to sleep, so just stopped by to check things out here00:39
mattoliverautdasilva: I can see why somepeople use a dedicated node to build rings.. if only there was a ringbuilder that could deploy rings :P00:40
mattoliverautdasilva: ahh :)00:40
mbirrumattoliverau: I could see proxy-log in /var/log/syslog here are some error I see 0000:42
mbirru0000:42
mbirrumattoliverau: here are errors https://pastebin.com/Rta2ewks00:42
mattoliveraumbirru: yeah, so the proxy is finding insufficant storage (507) and so error limiting the nodes and retuning a 503.00:44
mattoliverauwhat are your devices in your account, container and object servers, are they all pointing at /dev? or have you mounted the all the devices somewhere, and pointing to the mount point locations? because the latter is what you need.00:45
mattoliveraumbirru: ^00:45
mbirrumattoliverau: I allocated 30 GB to /dev/sda6 and /dev/sda7. Could you please let me know how is recommended. just to test the basic storage is working fine. Here I am using only one harddisk where my linux is installed. But I created 3 partitions with each30 GB00:46
mattoliverauonly asking because of the /dev/sda6 in the account ring00:46
mattoliveraumbirru: that should be fine00:46
mattoliveraumbirru: so you need to format sda6 and sda7 with XFS, then mount them somewhere, say under /srv.. eg:00:47
mattoliveraumkdir /srv/{sda6,sda7}00:47
mattoliverauthen mount them there.00:48
mattoliverauthen finally in your swift account, container and object configs point the devices to /srv/00:48
mattoliverauthen your rings will point to the mountpoints rather then the devices, which it needs.00:48
mattoliverauObviously this is just to get it working, it would be better to setup fstab entries, so they automount.00:49
mattoliveraumbirru: ^00:49
mattoliveraumbirru: does that make sense?00:49
mbirrumattoliverau: yes I did XFS and mounted to /srv/node00:49
mbirruhttps://pastebin.com/kM8N5uHw00:50
mattoliveraumbirru: cool00:51
mbirrumattoliverau: I followed exactly as you said from the https://docs.openstack.org/mitaka/install-guide-ubuntu/swift-storage-install.html00:51
*** itlinux has joined #openstack-swift00:51
mattoliveraumbirru: then you need to make sure your devices paramater in your configs (account, container and object) are /srv/node00:52
mattoliverauand your rings would need to point to sdb and sdc00:52
mattoliverauie. point the rings to the mount points not the devices.00:52
mattoliveraumbirru: ^00:53
mbirrumattaoliverau: here is config https://pastebin.com/1qtbJWsr00:54
mbirrumattoliverau: Yes I did00:54
mattoliveraumbirru: great00:54
mattoliveraumbirru: we should now just need to fix the rings :)00:55
mattoliveraujust rebuild them and point to sdb and sdc00:55
mattoliverauinstead of sda6 and asd700:56
mbirrumattoliverau: got it understood. thanks a lot for you are kind help00:56
mbirrumattoliverau: let change and update you00:56
mattoliveraumbirru: anytime :) you know where to find us if you need anymore help!00:56
mattoliveraumbirru: kk00:56
mattoliveraumbirru: and thanks for trying out swift :)00:57
*** cshastri has joined #openstack-swift00:57
mbirrumattoliverau: thank you00:57
*** shuyingya has quit IRC01:01
*** itlinux has quit IRC01:04
*** tovin07_ has joined #openstack-swift01:25
*** shuyingya has joined #openstack-swift01:27
*** itlinux has joined #openstack-swift01:29
*** gyee has quit IRC01:29
*** itlinux has quit IRC01:35
*** itlinux has joined #openstack-swift01:43
*** bkopilov has quit IRC01:48
*** itlinux has quit IRC01:56
*** itlinux has joined #openstack-swift02:06
*** itlinux has quit IRC02:21
mbirrumattoliverau: After rebuilding the rings.I am able to successfully run the swift-proxy server able to store the object02:25
mbirrumattoliverau: Thanks a lot for help02:25
mattoliveraumbirru: \o/02:28
mattoliverauNps02:28
*** baojg has joined #openstack-swift02:35
*** baojg has quit IRC02:43
*** itlinux has joined #openstack-swift02:50
*** itlinux has quit IRC02:57
*** bkopilov has joined #openstack-swift03:04
*** itlinux has joined #openstack-swift03:12
*** kei_yama has quit IRC03:12
*** itlinux has quit IRC03:14
*** kei_yama has joined #openstack-swift03:17
*** itlinux has joined #openstack-swift03:17
*** kei_yama has quit IRC03:18
notmynamekota_: if you or eran have a question on storlets for me (ie for the pike release), please let me know in here, and I'll get back to you03:21
*** itlinux has quit IRC03:30
*** gkadam has joined #openstack-swift03:40
openstackgerritTim Burke proposed openstack/swift master: Socket errors don't warrant tracebacks when talking to memcached  https://review.openstack.org/49615003:43
*** links has joined #openstack-swift03:57
kota_notmyname: thanks04:01
kota_notmyname: sorry, i'll leave for a while, so if something needed with eranrom, I'll ask you later.04:02
openstackgerritMerged openstack/swift master: Drop reconstructor stats when worker has no devices  https://review.openstack.org/49580504:17
*** two_tired has quit IRC04:30
*** itlinux has joined #openstack-swift04:30
*** mvk_ has joined #openstack-swift04:31
*** itlinux has quit IRC04:34
*** mkrcmari__ has joined #openstack-swift04:34
*** mvk_ has quit IRC04:35
*** rmcall has joined #openstack-swift04:38
*** chetna has joined #openstack-swift04:39
*** mvk has joined #openstack-swift04:43
mahaticmattoliverau: skipping 0700 meeting makes sense, thanks for checking04:45
mahaticnotmyname: ^04:45
mattoliveraukk, we'll skip it04:45
*** mkrcmari__ has quit IRC04:46
mattoliverauacoles, rledisez and anyone else, the 0700 meeting has been canceled for today.04:46
*** chetna has quit IRC04:48
*** mvk has quit IRC04:58
*** mrhillsman has quit IRC05:02
*** Jeffrey4l has quit IRC05:02
*** afazekas has quit IRC05:02
*** d34dh0r53 has quit IRC05:02
*** dhellmann has quit IRC05:02
*** kencjohnston_ has quit IRC05:02
*** mrhillsman has joined #openstack-swift05:02
*** afazekas has joined #openstack-swift05:02
*** dhellmann has joined #openstack-swift05:03
*** Jeffrey4l has joined #openstack-swift05:03
*** jcook has quit IRC05:04
*** d34dh0r53 has joined #openstack-swift05:04
*** kencjohnston has joined #openstack-swift05:04
*** jcook has joined #openstack-swift05:07
*** itlinux has joined #openstack-swift05:07
*** silor has joined #openstack-swift05:11
*** mvk has joined #openstack-swift05:12
*** itlinux has quit IRC05:19
*** mat128 has joined #openstack-swift05:24
*** mvk has quit IRC05:26
*** mvk has joined #openstack-swift05:27
*** mat128 has quit IRC05:28
*** mvk_ has joined #openstack-swift05:34
*** mvk has quit IRC05:37
openstackgerritTim Burke proposed openstack/swift master: slo/dlo: Segment/ListingErrors don't need tracebacks  https://review.openstack.org/49649305:39
zaitcevLOL guys I knew it was PEP8 :-) https://review.openstack.org/#/c/496150/05:41
patchbotpatch 496150 - swift - Socket errors don't warrant tracebacks when talkin...05:41
zaitcevGets you every time doesn't it05:41
*** kiennt has quit IRC05:41
timburkeevery time :-(05:49
*** ChubYann has quit IRC05:51
*** hoonetorg has quit IRC05:54
*** hoonetorg has joined #openstack-swift06:07
*** kiennt has joined #openstack-swift06:09
*** rcernin has joined #openstack-swift06:16
*** skudlik has joined #openstack-swift06:17
*** skudlik has left #openstack-swift06:17
*** tovin07_ has quit IRC06:20
*** jlvillal has quit IRC06:21
*** jlvillal has joined #openstack-swift06:21
*** kiennt has quit IRC06:23
*** kiennt has joined #openstack-swift06:24
*** hseipp has joined #openstack-swift06:40
*** m_kazuhiro has joined #openstack-swift06:43
*** geaaru has joined #openstack-swift06:45
mathiasbgood morning06:52
openstackgerritTim Burke proposed openstack/swift master: container sync: reraise properly, don't log traceback for ClientExceptions  https://review.openstack.org/49651706:53
*** cschwede_ has joined #openstack-swift06:55
*** tovin07_ has joined #openstack-swift06:55
acolesmattoliverau: ack, thanks06:59
*** m_kazuhiro has quit IRC07:01
*** pcaruana has joined #openstack-swift07:11
*** karmine has joined #openstack-swift07:14
*** tesseract-RH has joined #openstack-swift07:17
mattoliveraumathiasb: o/07:19
mattoliverauacoles: morning07:19
acolesmattoliverau: o/07:19
mahaticacoles: mathiasb o/07:22
*** klrmn has quit IRC07:29
mattoliverautdasilva: I've pushed what I have into the master of my fork.. but might needed some more testing.. only really checked it on redhat/cenos, the debian variables are clearly wrong, but I want to get it to work on something first, and cause I'm using your vagrant redhat wins :)07:30
mattoliveraubut will PR it to you when I'm more happy with it. (just an FYI).07:31
openstackgerritTim Burke proposed openstack/swift master: expirer: unexpected responses don't warrant tracebacks  https://review.openstack.org/49653407:35
openstackgerritTim Burke proposed openstack/swift master: Simplify testing for logging at error vs exception  https://review.openstack.org/49653507:35
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Imported Translations from Zanata  https://review.openstack.org/49613707:39
timburkei'm not entirely sure i like the tactics of that last one, but getting there certainly shook out a bunch of cases where we seem to be logging tracebacks that aren't useful07:41
*** oshritf has joined #openstack-swift07:55
*** openstackgerrit has quit IRC08:03
*** hseipp has quit IRC08:05
*** cbartz has joined #openstack-swift08:09
*** klrmn has joined #openstack-swift08:12
*** klrmn has quit IRC08:31
*** rmcall has quit IRC08:34
*** oshritf has quit IRC08:34
*** dosaboy has joined #openstack-swift08:38
*** spotz has quit IRC08:46
*** oshritf has joined #openstack-swift08:46
*** spotz has joined #openstack-swift08:49
*** mrhillsman has quit IRC08:51
*** mrhillsman has joined #openstack-swift08:52
*** oshritf has quit IRC09:13
*** bkopilov has quit IRC09:16
*** tovin07_ has quit IRC09:49
*** oshritf has joined #openstack-swift09:53
*** mkrcmari__ has joined #openstack-swift09:54
*** mvk_ has quit IRC09:58
*** kiennt has quit IRC10:03
*** oshritf has quit IRC10:11
*** oshritf has joined #openstack-swift10:12
*** mbirru has quit IRC10:18
*** cshastri has quit IRC10:42
*** hoonetorg has quit IRC10:43
*** hoonetorg has joined #openstack-swift10:43
*** oshritf has quit IRC11:30
*** mat128 has joined #openstack-swift11:37
*** hseipp has joined #openstack-swift11:40
*** iprokg has joined #openstack-swift11:51
*** iprokg has quit IRC11:52
*** iprokg has joined #openstack-swift11:52
*** iprokg has joined #openstack-swift11:52
*** iprokg has quit IRC11:54
*** kmARC has quit IRC12:11
*** kencjohnston has quit IRC12:12
*** kmARC has joined #openstack-swift12:14
*** kencjohnston has joined #openstack-swift12:14
*** mat128 has quit IRC12:19
*** openstackgerrit has joined #openstack-swift12:22
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873612:22
*** gkadam has quit IRC12:43
*** shuyingya has quit IRC12:56
*** lucasxu has joined #openstack-swift13:10
*** abhitechie has joined #openstack-swift13:15
*** shuyingya has joined #openstack-swift13:19
*** baojg has joined #openstack-swift13:21
*** shuyingya has quit IRC13:23
*** bkopilov has joined #openstack-swift13:26
openstackgerritPeter Lisák proposed openstack/swift master: Added swift version to recon cli  https://review.openstack.org/41399113:28
*** baojg has quit IRC13:34
*** links has quit IRC13:38
*** shuyingya has joined #openstack-swift13:42
*** SkyRocknRoll has joined #openstack-swift13:43
*** baojg has joined #openstack-swift13:47
*** baojg has quit IRC13:47
*** baojg has joined #openstack-swift13:48
*** mat128 has joined #openstack-swift13:52
*** mat128 has quit IRC13:53
*** mat128 has joined #openstack-swift13:57
*** baojg has quit IRC14:03
jrichlimathiasb: congrats on the merge!  I was on vaca and just now saw that in scrollback this morning.14:04
*** gabor_antal has joined #openstack-swift14:04
mathiasbjrichli: thanks, and thanks for all your feedback and testing also!14:06
*** baojg has joined #openstack-swift14:09
*** baojg has quit IRC14:15
*** bkopilov has quit IRC14:15
*** abhitechie has quit IRC14:20
*** abhitechie has joined #openstack-swift14:21
*** abhitechie has quit IRC14:21
*** vint_bra has joined #openstack-swift14:25
*** SkyRocknRoll has quit IRC14:26
*** itlinux has joined #openstack-swift14:27
*** abhitechie has joined #openstack-swift14:30
*** abhitechie has quit IRC14:31
*** abhitechie has joined #openstack-swift14:31
*** abhitechie has quit IRC14:32
*** abhitechie has joined #openstack-swift14:33
*** itlinux has quit IRC14:34
*** abhitechie has quit IRC14:35
*** abhitechie has joined #openstack-swift14:35
*** two_tired has joined #openstack-swift14:38
*** SkyRocknRoll has joined #openstack-swift14:38
*** abhitechie has quit IRC14:40
*** abhitechie has joined #openstack-swift14:40
*** srbgupta has joined #openstack-swift14:41
*** gyee has joined #openstack-swift14:41
*** mkrcmari__ has quit IRC14:47
*** abhitechie has quit IRC14:48
*** abhitechie has joined #openstack-swift14:48
*** mvk has joined #openstack-swift14:48
openstackgerritMerged openstack/swift master: Socket errors don't warrant tracebacks when talking to memcached  https://review.openstack.org/49615014:55
*** shuyingya has quit IRC15:08
*** abhitechie has quit IRC15:11
*** abhitechie has joined #openstack-swift15:11
*** lucasxu has quit IRC15:13
*** abhitechie has quit IRC15:16
*** abhitechie has joined #openstack-swift15:16
*** klrmn has joined #openstack-swift15:19
*** abhitechie has quit IRC15:23
*** abhitechie has joined #openstack-swift15:23
*** abhitechie has quit IRC15:24
*** abhitechie has joined #openstack-swift15:25
*** catintheroof has joined #openstack-swift15:25
*** two_tired has quit IRC15:27
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/common  https://review.openstack.org/34278115:29
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/account tests  https://review.openstack.org/34276615:29
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/common/middleware  https://review.openstack.org/34277015:29
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/container  https://review.openstack.org/34280815:31
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/obj tests  https://review.openstack.org/34283015:31
openstackgerritGábor Antal proposed openstack/swift master: Update hacking and enable off-by-default checks  https://review.openstack.org/48662715:31
*** itlinux has joined #openstack-swift15:47
*** lucasxu has joined #openstack-swift15:49
*** karmine has quit IRC15:51
timburkegood morning15:51
*** abhitechie has quit IRC15:53
*** abhitechie has joined #openstack-swift15:53
*** klrmn has quit IRC16:09
notmynamegood morning16:11
notmynamejoeljwright: around? do we have anything to talk about with *ambles today?16:21
joeljwrightnotmyname: I am16:21
*** cbartz has quit IRC16:21
joeljwrightI don't think there's much to cover regarding *ambles16:22
notmynameok16:22
joeljwrightother than a nudge16:22
joeljwrightand a promise that I now have a tlo WIP16:22
notmynameyou were working on finding/showing some different formats, right? any progress on that?16:22
joeljwrightthat I will be sharing this week16:22
notmynameah, right. the full TLO thing16:22
joeljwrightTLO implemented as a manifest transformation16:23
notmynameok, in that case, let's cancel today's 2100 meeting16:23
joeljwrightsure, I'll have more ammo for next week's meeting :)16:23
notmynameacoles: mattoliverau: kota_: cschwede_: mahatic: zaitcev: clayg: timburke: tdasilva: jrichli: torgomatic: jungleboyj: no 2100 meeting today16:24
*** rcernin has quit IRC16:29
*** mat128 has quit IRC16:35
*** chsc has joined #openstack-swift16:38
*** chsc has joined #openstack-swift16:38
cschwede_notmyname: alright, thx for the info!16:40
notmynamecschwede_: do you know what's the status on https://bugs.launchpad.net/swift/+bug/1580678 (which is likely related to https://bugs.launchpad.net/swift/+bug/1648082 which might be closed by https://review.openstack.org/#/c/446762/)16:42
openstackLaunchpad bug 1580678 in OpenStack Object Storage (swift) "UnicodeDecodeError when rebalancing a ring" [Medium,In progress] - Assigned to Christian Schwede (cschwede)16:42
patchbotpatch 446762 - oslo.i18n - add notes about skipping log translation setup (MERGED)16:42
openstackLaunchpad bug 1648082 in OpenStack Object Storage (swift) "Yet UnicodeDecodeError: 'ascii' codec can't decode byte..." [Undecided,New]16:42
*** itlinux has quit IRC16:44
timburkenotmyname: i'm skeptical of any claim that a commit to oslo.i18n "closes" a bug that reports a traceback in swift ;-)16:45
notmyname:-)16:45
timburkewe still need to go through an purge any gettext calls for log messages. *then* i could consider those bugs closed16:46
timburkealthough, i'm not sure we *should* purge translations for ring rebalances -- operator CLI tool *might* actually be worth having translations? i suppose you still have the discoverability issues, coupled with the fact that it's hard to translate jargon, especially when *we make up things* like "replicanths"16:48
cschwede_notmyname: no, but i can have a look again at it. and i agree with timburke to purge any gettext logging calls16:49
notmynamecschwede_: just was asking you since your name is on it ;-)16:49
jungleboyjnotmyname:  Thanks for letting me know.  That helps my schedule for the day.  :-)16:49
notmynametimburke: cschwede_: yeah, I agree about "closed when log translations dropped"16:50
notmynamemy gut says to not translate errors or logs because of the problems mentioned. but also my gut said that in English and is not really qualified to say if it should be in non-English16:52
*** itlinux has joined #openstack-swift16:55
timburkemaybe there's some additional context that ought to be considered? like, if we (1) expect this to be something that only an operator (being the people that actually control what locale a server uses) would see, either at a CLI *or* in logs, and (2) are providing fairly specific, actionable information (like, say, https://github.com/openstack/swift/blob/2.15.1/swift/obj/replicator.py#L112-L115) then maybe it *should* be translated?16:58
timburkei'm really not sure that "don't translate logs" is the right call, particularly since our CLI stuff sometimes uses logging to emit messages to the user, like in https://github.com/openstack/swift/blob/master/swift/cli/relinker.py17:02
timburkemaybe i was wrong to push for that there? but it seemed silly to reinvent log levels for --debug17:03
*** klrmn has joined #openstack-swift17:06
*** pcaruana has quit IRC17:08
*** hseipp has quit IRC17:12
*** tesseract-RH has quit IRC17:12
*** mvk_ has joined #openstack-swift17:30
*** mat128 has joined #openstack-swift17:31
*** itlinux has quit IRC17:32
*** mkrcmari__ has joined #openstack-swift17:33
*** mvk has quit IRC17:33
*** mat128 has quit IRC17:34
*** rcernin has joined #openstack-swift17:34
*** mvk_ has quit IRC17:35
*** rmcall has joined #openstack-swift17:49
*** itlinux has joined #openstack-swift17:50
*** SkyRocknRoll has quit IRC18:06
*** catintheroof has quit IRC18:07
*** mkrcmari__ has quit IRC18:28
notmynameteam photo (like at the last PTG) scheduled for 2:50 pm on the wednesday of the ptg18:30
*** cschwede_ has quit IRC18:40
*** ChubYann has joined #openstack-swift18:43
tdasilvanotmyname: cool, also thanks for the meetings heads up18:44
*** rcernin has quit IRC18:47
*** rmcall has quit IRC19:07
*** itlinux has quit IRC19:10
*** mat128 has joined #openstack-swift19:20
acolesnotmyname: ack no meeting19:33
tdasilvahi everyone! gnocchi is a time-series database (like influxdb) that is used by the openstack telemetry team (e.g., ceilometer) to store metrics. One of the cools things about it is that it is designed to be very scalable so it contains drivers to store its data directly into storage systems like swift and ceph19:39
tdasilvalong story short: akrzos from red hat openstack performance team has been doing some cool work testing it with swift19:40
tdasilvaand would like to talk about it during the PTG19:40
tdasilvaso I encouraged him to add as a topic to the wiki19:40
notmynametdasilva: nice19:42
*** itlinux has joined #openstack-swift19:43
*** itlinux has quit IRC19:47
*** itlinux has joined #openstack-swift20:01
timburkehuh. do we not log ssync requests like we do other requests on the object server? i saw Unexpected response: ":ERROR: 500 'ERROR: With :UPDATES: 1 failures to 0 successes'" somewhere, went grepping for ' 500 ' on the other end and didn't turn up anything20:02
timburkeeventually got "ssync subrequest failed with 409: PUT ..." but i had to go searching by the path20:02
timburke...which, given the load i was driving (lots of overwrites/deletes of the same object) isn't surprising... but i wonder if we should maybe consider a 409 as successful in this context? the other end told me they have something newer; my job as relay is done20:05
acolestimburke: IIRC ssync receiver tolerates some subrequest failures before giving up20:05
acolestimburke: this may be relevant https://review.openstack.org/#/c/181407/20:07
patchbotpatch 181407 - swift - EC: Avoid conflicts when ssync'ing fragments20:07
acolesbut it's so long ago I'd need to reload context20:07
acolesfinal sentence of commit msg says "The patch also results in newer fragments on the receiver always resulting in the sender not attempting to PUT data."20:07
timburkeyeah, and that's fine... i guess my original complaint is that, when one end says they received a 500, i want to be able to search for ' 500 ' (with the spaces on either side to avoid partial matches on trans ids/content lengths) in my logs...20:08
*** rmcall has joined #openstack-swift20:12
acolesOIC20:13
*** itlinux has quit IRC20:14
*** itlinux has joined #openstack-swift20:17
*** silor has quit IRC20:29
notmynamekong: I just saw your questions about horizon in the meeting. if you can't get what you need from horizon, would other object storage clients work?20:32
kongnotmyname: hey20:33
kongnotmyname: what do you mean by 'other clients'20:33
notmynamekong: there's a lot more ways to talk to a swift cluster and see what's in it that just using horizon. I only mean using something else20:34
notmynamekong: however, if horizon is your single view for customers into the cloud, then that might not be possible20:35
kongnotmyname: unfortunately, horizon is the only one dashboard we are using20:35
notmynameok, I understand20:35
*** rcernin has joined #openstack-swift20:35
robcresswellfwiw, we're happy to accept improvements, it's just that "the horizon team" nowadays is something like 3 part-timers20:35
notmynamerobcresswell: no offense intended :-)20:36
robcresswellWe're not being deliberately obtuse about adding functionality :)20:36
robcresswellnotmyname: None taken, I just wanted to clarify my stance on it20:36
notmynamegot it :-)20:36
notmynamekong: it sounds like you've got some pretty active users on your swift cluster, too. that's really great to hear20:37
notmynamekong: have you kept up with the long-term work we've been doing in swift to support very large containers? (the "container sharding" work)20:38
*** lucasxu has quit IRC20:38
notmynamekong: will you be at the PTG next month?20:38
*** lucasxu has joined #openstack-swift20:38
kongnotmyname: yeah, and many customers were considering transit to swift after we made the announcement last year20:39
kongnotmyname: no :-(20:39
notmynamecool (using swift) and I'm sorry to hear it (you not being at the ptg)20:39
mattoliveraunotmyname: ack20:39
notmynamekong: what was the announcement you made last year?20:40
mattoliverautdasilva: cool20:40
kongnotmyname: we provide Geo-replicated Object Storage Service20:40
notmynamenice!20:40
notmynamehave you used the geo-replicated EC policies yet?20:40
*** itlinux has quit IRC20:41
kongnotmyname: not yet, but i think it's a good addon if customers are asking for that20:41
tdasilvamattoliverau: o/20:43
notmynamereminder: no 2100 swift team meeting today20:46
*** lucasxu has quit IRC20:48
*** m_kazuhiro has joined #openstack-swift20:57
notmynamepeluse just did a code review?! (on a 2 year old patch)20:58
kota_oh20:58
kota_no 2100 meeting?20:58
notmynamekota_: no 2100 meeting today20:58
notmynamekota_: enjoy a slow breakfast :-)20:59
kota_notmyname: thanks, being back to my bed and enjoy my birthday ;-)20:59
notmynamekota_: happy birthday!20:59
kota_:P21:00
openstackgerritTim Burke proposed openstack/swift master: container sync: reraise properly, don't log traceback for ClientExceptions  https://review.openstack.org/49651721:09
openstackgerritTim Burke proposed openstack/swift master: expirer: unexpected responses don't warrant tracebacks  https://review.openstack.org/49653421:09
openstackgerritTim Burke proposed openstack/swift master: Simplify testing for logging at error vs exception  https://review.openstack.org/49653521:09
timburkenotmyname: yeah, i saw that too :-) i think it's my fault for leaving a comment on it21:11
notmynameheh21:11
*** eckesicle has joined #openstack-swift21:12
mattoliveraukota_: happy birthday!!21:13
eckesiclehello. I have some data hosted with a cloud provider in openstack swift, that I would like to securely wipe. is there any way to do this in swift?21:13
*** m_kazuhiro has quit IRC21:13
notmynameeckesicle: no, there is not21:13
eckesicleif i overwrite an object, it creates a new object on a different disk node?21:14
notmynameassuming the cluster is in a steady state with no failures, it will write to the same disks, but it will be new files21:14
notmynamethe existing on disk data would be unlinked, but there is no overwrite of existing data21:14
eckesicleand if I add encryption with a random key, it will create new files too?21:15
notmynameyou mean if you PUT the same object but this time encrypted?21:15
eckesicleyes21:15
notmynameyeah, same story (swift just sees you send a blob of bytes. doesn't matter if you've encrypted them or not, swift treats them the same way)21:16
eckesiclethat's a shame21:16
notmyname(for completeness, since you mentioned it, the cluster may also write the new object into different places than the existing object. just depends on what's going on in the cluster at the time)21:17
notmynameeckesicle: it sounds like you implied that you are not the cluster operator21:17
eckesicleim not21:20
eckesicleive been asked by a client to securely wipe some data for them21:20
notmynameeckesicle: in my experience, overwrite requirements normally come from certain compliance or regulatory requirements. (otherwise, unlinking the data should be sufficient)21:20
notmynameah21:20
eckesicleit is for compliance21:20
eckesiclei guess we'll have to contact the operator21:21
notmynameyeah, the best you can do is either send an overwrite or a delete21:21
notmynameit will also be very difficult for the operator21:21
notmynamedepending on what the requirements are21:21
notmynameeckesicle: you've got a couple of paths forward21:22
jrichlisecure deletion is something that must hit the hardware level, and would have to involve some hardware-specific element21:22
*** mat128 has quit IRC21:23
notmynameone is to send a PUT for the same object name to overwrite it. the existing data will be unlinked. or send a delete and the existing data will be unlinked. the data will not be overwritten on the drive21:23
eckesicle@notmyname with a bit of luck we are on our own cluster21:23
notmynamethis is pretty much the best you'll be able to do (when considering time/cost/etc)21:24
eckesicleand they can just wipe the disks/send them to us21:24
notmynamewell, sortof21:24
notmynamethe question then is, "which disks"21:24
notmynameand that's the second thing you could do21:24
notmynameask the cluster operator to scan every drive for the bad data and overwrite it if found21:24
eckesiclewell if we're on our own cluster, then just all the disks, after we migrate the data we want to keep to a new cluster21:25
*** itlinux has joined #openstack-swift21:25
*** mbirru has joined #openstack-swift21:25
notmynameimagine this scenario: @T0, PUT bad.data. @T1, one of the primary drives fails. the cluster replicates the data to a different location. @t@ the operator repairs the failed drive and the cluster moves a replica back to there and delete (ie unlinks, not overwrites) the replica on the handoff21:26
notmynamein this case, you've got your replicas in the cluster in the right place, but there was a time when you had another copy of the data in the cluster that was deleted but not overwritten21:27
notmynameso the only way to be sure that the string of bytes that you need scrubbed are well and truly scrubbed from the cluster is to check every disk21:27
torgomaticyou might also consider a wood chipper with its output aimed into an acid bath21:28
jrichliyes, it goes farther than that.  again, it also depends on hardware - is there a way to guarantee on your hardware that your particular "overwrite" really used the same memory21:29
notmynameeckesicle: the at-rest encryption functionality that we have in swift is designed to allow drive to leave the cluster without leaking object data (but that's not exactly the same thing you're looking for)21:29
notmynamelol, we're all piling on :-)21:30
jrichlihonesti]21:30
eckesicleyeah21:30
jrichlihonestly, without us having code that was hardware dependent cases, i dont think real secure deletion is possible21:30
eckesicleexactly, which is why ideally id like to have the disks in my hand21:30
eckesicleand run them through a microwave21:30
torgomatichttps://www.youtube.com/watch?v=aCbfMkh940Q21:31
notmynameeckesicle: so, I'm not trying to make light of your situation. but from a technical perspective, there's not really a way to securely overwrite data in a swift cluster21:31
eckesiclei was afraid of that21:31
eckesicleso ill break in to the data center21:31
notmynamelol21:31
timburkeclient-side crypto give you, the user, a lot more control. issue a delete (so you stop getting billed for it), securely wipe the key locally (which has the added benefit of being much smaller). but that requires that the plaintext *never* makes it to the cluster21:31
notmynametimburke: yes! +10021:32
eckesicleyeah, but unfortunately there are a few really old files that made it in plaintext21:32
eckesiclethose are the ones im trying to get rid of21:32
timburkeyeah, i kinda figured. sorry. that's going to be problematic21:33
eckesiclethat's ok. i can always blame my predecessor21:39
notmynametorgomatic: thanks for the comments on patch 36537121:47
patchbothttps://review.openstack.org/#/c/365371/ - swift - Add Preamble and Postamble to SLO and SegmentedIte...21:47
torgomaticnotmyname: 👍21:47
*** srbgupta has quit IRC22:01
*** geaaru has quit IRC22:06
*** abhitechie has quit IRC22:19
*** abhitechie has joined #openstack-swift22:19
*** itlinux has quit IRC22:29
*** abhitechie has quit IRC22:53
*** vint_bra has quit IRC23:03
mattoliveraumoring (officially as I'm at my desk) :)23:05
mattoliverau*morning even23:05
notmynamemattoliverau: hello23:12
notmynamemattoliverau: hope the commute to work wasn't too rough on your this morning23:12
kota_mattoliverau: thx!23:17
mattoliveraunotmyname: it was tough, its slightly colder downstairs in the office. And not to mention having to deal with a gate on the stairs to protect the toddler. That add a few seconds :P23:18
*** kei_yama has joined #openstack-swift23:25
*** chsc has quit IRC23:35
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873623:36
*** vint_bra has joined #openstack-swift23:41
*** vint_bra has quit IRC23:46

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