Tuesday, 2018-02-27

« Monday, 2018-02-26 Index Wednesday, 2018-02-28 »
*** mvk has quit IRC00:08
*** mvk has joined #openstack-swift00:11
*** gerardgine has joined #openstack-swift00:20
*** vint_bra has joined #openstack-swift00:27
*** NM has joined #openstack-swift00:41
*** ukaynar has quit IRC00:48
*** ukaynar has joined #openstack-swift00:48
*** tovin07_ has joined #openstack-swift00:50
*** ukaynar has quit IRC00:53
*** threestrands has joined #openstack-swift01:01
*** threestrands has quit IRC01:01
*** threestrands has joined #openstack-swift01:01
*** threestrands has quit IRC01:02
*** threestrands has joined #openstack-swift01:02
*** threestrands has quit IRC01:02
*** threestrands has joined #openstack-swift01:02
*** NM has quit IRC01:10
*** Anticime1 is now known as Anticimex01:14
*** vint_bra has quit IRC01:18
*** vint_bra has joined #openstack-swift01:18
*** vint_bra has quit IRC01:19
*** itlinux has joined #openstack-swift01:24
*** threestrands has quit IRC01:28
*** cshastri_ has joined #openstack-swift01:30
*** rcernin has quit IRC01:46
*** rcernin has joined #openstack-swift01:47
openstackgerritTim Burke proposed openstack/swift feature/deep: Use direct_container_op more  https://review.openstack.org/54811401:48
openstackgerritTim Burke proposed openstack/swift feature/deep: Add a put_objects helper  https://review.openstack.org/54811501:48
openstackgerritTim Burke proposed openstack/swift feature/deep: Add some threading  https://review.openstack.org/54811601:48
*** tovin07 has quit IRC02:35
*** tovin07_ has quit IRC02:35
*** tovin07_ has joined #openstack-swift02:36
*** tovin07 has joined #openstack-swift02:36
*** gerardgine has quit IRC02:45
*** ggine has joined #openstack-swift02:47
*** mvk has quit IRC03:04
*** bkopilov has quit IRC03:06
*** psachin has joined #openstack-swift03:21
*** links has joined #openstack-swift03:25
*** kei_yama has quit IRC03:35
*** ggine has quit IRC03:35
*** gerardgine has joined #openstack-swift03:35
*** gerardgine has joined #openstack-swift03:36
*** andybotting has joined #openstack-swift03:39
*** gerardgine has quit IRC03:41
andybottinghey guys, I'm seeing swiftclient 'hang' with python3. It appears to do the right thing (i.e. list works, delete works) but it never returns to the prompt. Just sits there forever. I'm using Python 3.6 on Arch Linux - from both the distro package and from virtualenv.03:50
andybottingPython 2 works fine. Debug output looks mostly the same.03:51
andybottingLet me know if there's some info I can provide03:51
*** kei_yama has joined #openstack-swift04:00
andybottinglooks like it's just the distro package. I'll look into it more04:01
*** gerardgine has joined #openstack-swift04:17
*** zaitcev has joined #openstack-swift04:26
*** ChanServ sets mode: +v zaitcev04:26
*** gerardgine has quit IRC04:34
*** gerardgine has joined #openstack-swift04:35
*** armaan has quit IRC04:41
*** armaan has joined #openstack-swift04:42
*** gerardgine has quit IRC04:42
*** bkopilov has joined #openstack-swift04:47
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Split expirer methods and parametrize task account  https://review.openstack.org/54387405:55
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Split expirer methods and parametrize task account  https://review.openstack.org/54387406:08
*** geaaru_ has joined #openstack-swift06:12
*** geaaru has quit IRC06:14
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Imported Translations from Zanata  https://review.openstack.org/54552306:55
*** gerardgine has joined #openstack-swift06:58
*** gerardgine has quit IRC07:01
*** geaaru_ has quit IRC07:14
*** gerardgine has joined #openstack-swift07:18
*** gerardgine has quit IRC07:22
*** pcaruana has joined #openstack-swift07:30
*** zaitcev has quit IRC07:36
*** hseipp has joined #openstack-swift07:47
*** armaan has quit IRC07:59
*** armaan has joined #openstack-swift08:00
*** neonpastor has quit IRC08:00
*** neonpastor has joined #openstack-swift08:01
*** tesseract has joined #openstack-swift08:14
*** gkadam has joined #openstack-swift08:16
*** m_kazuhiro has joined #openstack-swift08:17
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Parameterize expirer unit tests  https://review.openstack.org/54392308:17
*** rcernin has quit IRC08:23
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Split expirer methods and parametrize task account  https://review.openstack.org/54387408:30
*** cbartz has joined #openstack-swift08:34
*** cbartz1 has joined #openstack-swift08:35
*** cbartz has quit IRC08:38
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Parameterize expirer unit tests  https://review.openstack.org/54392308:38
*** geaaru has joined #openstack-swift08:45
kota_good morning guys09:07
acoleskota_: good morning09:12
acolesanyone at PTG yet?09:12
kota_acoles: good morning. I just saw mattoliverau and m_kazuhiro but it doesn't seem to have a room yet09:13
*** zhurong has joined #openstack-swift09:14
kota_i'm on a sheet in front of registration09:14
acolesI'm going to walk there soon - probably arrive about 10am09:15
kota_acoles: sounds nice09:17
claygback in 66109:17
*** notmyname has quit IRC09:20
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Ignore found/created shards when shrinking  https://review.openstack.org/54807709:21
*** notmyname has joined #openstack-swift09:22
*** ChanServ sets mode: +v notmyname09:22
*** notmyname has quit IRC09:22
*** notmyname has joined #openstack-swift09:22
*** ChanServ sets mode: +v notmyname09:22
mattoliveraumorning09:23
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/s3api: Merge remote-tracking branch 'remotes/origin/master' into merge-master  https://review.openstack.org/54819309:24
notmynamewe're in 661 again today09:26
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/s3api: Merge remote-tracking branch 'remotes/origin/master' into feature/s3api  https://review.openstack.org/54819309:26
acolesnotmyname: the community cluster job didn't run on https://review.openstack.org/#/c/548077 yesterday :'(09:29
patchbotpatch 548077 - swift (feature/deep) - Ignore found/created shards when shrinking09:29
notmynameacoles: checking09:31
kota_clayg, notmyname: good notification for the room. I'll be thre soon.09:32
*** d0ugal has joined #openstack-swift09:33
notmynameacoles: jenkins server may be down. martin is checking09:33
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Add object-expirer new mode to execute tasks from general task queue  https://review.openstack.org/51738909:36
acoleson my way09:37
*** m_kazuhiro has quit IRC09:37
notmynameacoles: it's back up. should be able to recheck old stuff and check new stuff now09:37
*** zaitcev has joined #openstack-swift09:41
*** ChanServ sets mode: +v zaitcev09:41
*** m_kazuhiro has joined #openstack-swift09:44
*** d0ugal has quit IRC10:00
*** geaaru has quit IRC10:03
*** tovin07_ has quit IRC10:07
acolesnotmyname: thanks10:15
*** geaaru has joined #openstack-swift10:15
kota_gerrit seems unstable10:20
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Kill rsync coros when lockup detector tries to kill the process  https://review.openstack.org/54801810:21
kota_^ perhaps, better one to prevent zombie rsync process but I'm still not sure that is correct thing10:22
-openstackstatus- NOTICE: gerrit is being restarted due to extreme slowness10:23
kota_if that is10:24
*** d0ugal has joined #openstack-swift10:28
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Kill rsync coros when lockup detector tries to kill the process  https://review.openstack.org/54801810:35
kota_small fix in unit test10:35
kota_i checked the behavior of the patch 548018 in my saio with narrow bandwidth (e.g. 10KB/s) and lockup_timeout with 1.0 sec. No mare rsync process (and also zombiee process) increasing.10:40
patchbothttps://review.openstack.org/#/c/548018/ - swift - Kill rsync coros when lockup detector tries to kil...10:40
*** d0ugal has quit IRC10:44
kota_thanks clayg checking it!10:51
openstackgerritKota Tsuyuzaki proposed openstack/swift master: DNM: Try out to pull execution logs of functests  https://review.openstack.org/54822611:08
*** links has quit IRC11:15
*** mlanner has joined #openstack-swift11:25
*** bkeller`_ has quit IRC11:25
*** bkeller` has joined #openstack-swift11:26
*** links has joined #openstack-swift11:28
*** mlanner has quit IRC11:33
*** mlanner has joined #openstack-swift11:34
*** armaan has quit IRC11:36
*** armaan has joined #openstack-swift11:36
*** armaan has quit IRC11:41
*** armaan has joined #openstack-swift11:42
*** armaan has quit IRC11:46
*** bkopilov has quit IRC11:49
*** zhurong has quit IRC11:54
*** mlanner has quit IRC12:03
notmynamelunch is available. there's a zuulv3 talk right after lunch in the same room, and there's a room this afternoon talking about release cycles12:14
notmynamewe'll be in 661 all afternoon, too12:14
*** mlanner has joined #openstack-swift12:14
*** cshastri_ has quit IRC12:16
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: WIP: Add "Manual" Tiering Feature  https://review.openstack.org/54695812:20
*** m_kazuhiro has quit IRC12:21
*** kei_yama has quit IRC12:38
*** zaitcev has quit IRC12:38
*** cbartz1 has quit IRC12:48
openstackgerritMerged openstack/swift feature/deep: Ignore found/created shards when shrinking  https://review.openstack.org/54807712:57
openstackgerritMerged openstack/swift feature/s3api: Merge remote-tracking branch 'remotes/origin/master' into feature/s3api  https://review.openstack.org/54819312:57
*** armaan has joined #openstack-swift13:10
*** pdardeau has joined #openstack-swift13:14
*** ianychoi has quit IRC13:18
*** mvk has joined #openstack-swift13:28
*** cshastri_ has joined #openstack-swift13:32
*** zhurong has joined #openstack-swift13:35
*** _alastor__ has joined #openstack-swift13:35
*** _alastor__ is now known as _alastor_13:38
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Add note about enabling sharding  https://review.openstack.org/54827613:41
*** zaitcev has joined #openstack-swift13:41
*** ChanServ sets mode: +v zaitcev13:41
*** zhurong has quit IRC13:43
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Add note about enabling sharding  https://review.openstack.org/54827613:49
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Add note about enabling sharding  https://review.openstack.org/54827613:50
*** bkopilov has joined #openstack-swift13:54
openstackgerritTim Burke proposed openstack/swift feature/deep: Add override_devices/override_partitions options  https://review.openstack.org/54828113:56
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Let shard-info work with conf.d  https://review.openstack.org/54828213:57
kota_got it. now the func gate is using in-process instead of dsvm http://logs.openstack.org/26/548226/1/check/swift-tox-func/18ee7bb/job-output.txt.gz#_2018-02-27_11_11_13_714257 even it's just `tox -efunc`13:58
*** zhurong has joined #openstack-swift14:08
kota_(if we don't have test conf tho ^)14:10
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Only shrink into an ACTIVE acceptor  https://review.openstack.org/54829614:12
*** zhurong has quit IRC14:15
notmynamelet me know if the "happening now" section for swift needs to change to something other than "open discussion"14:20
openstackgerritTim Burke proposed openstack/swift feature/deep: Add override_devices/override_partitions options  https://review.openstack.org/54828114:23
*** armaan has quit IRC14:33
*** d0ugal has joined #openstack-swift14:35
*** charz has quit IRC14:36
*** charz has joined #openstack-swift14:39
*** psachin has quit IRC14:42
*** m_kazuhiro has joined #openstack-swift14:43
*** zhurong has joined #openstack-swift14:44
thurloathow's the conf?14:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Cleanup ContainerBroker.get_own_shard_range  https://review.openstack.org/54747814:52
*** itlinux has quit IRC14:55
*** zaitcev has quit IRC15:01
*** corvus is now known as corvusicle15:02
notmynamethurloat: great. it's always really good to see everyone in person (however, I stayed up too late last night and I'm pretty tired now)15:03
thurloateasy to get carried away at confs :)15:06
*** zaitcev has joined #openstack-swift15:07
*** ChanServ sets mode: +v zaitcev15:07
notmynameacoles: mattoliverau: kota_: how's room 661 going?15:19
kota_notmyname: I'm at release-cycle room15:19
notmynameoh hi15:20
notmynamekota_: how do you think this release-cycle conversation is going?15:22
*** SkyRocknRoll has joined #openstack-swift15:23
kota_notmyname: good question.15:23
notmynameI thought so ;-)15:24
notmynamewhat do you think?15:24
kota_notmyname: in the moment, exactly there are some impact to change the release-cycle but...15:25
kota_in developer perspective, the current cycle is being tighten for developer15:26
kota_exactly i understand the opinions of the operators and packagers.15:26
kota_i'm feeling the room has spent much time for ops/packagers/sales perspective for now15:27
kota_the topics for devs seems at the bottom of the pad tho15:28
notmynamedo you think the conversation is going in a way that will hurt developers?15:28
kota_not sure to go the conclusion. I think it's brainstorming and some of the opinion may be good feedbacks to dev.15:30
notmynametdasilva: what do you think about this room's conversation?15:30
*** corvusicle is now known as corvus15:31
kota_notmyname: in the perspective of Japanese culture, the frequency of the releases won't be impacted because many of customers doesn't try upgrading so frequently15:33
tdasilvaget the feeling that there are good reasons to go longer and good reason to go shorter, but i'm not sure if there's any leaning at the moment...like kota_ said hard to take any conclusions atm...15:33
tdasilvagut feeling is that things will remain the same????15:33
kota_but if there is something impacted, the important thing is WHAT'S CHANGED and IT IS ABLE TO UPGRADE IF POSSIBLE, i suppose.15:34
notmyname"all right everyone, we've talked about it for years now, and we've decided to keep everything the same. good talk"15:34
notmynamekota_: yeah. I agree15:34
*** cshastri_ has quit IRC15:35
notmynamecurrently, my opinion is that, like kota_ says, there's reasons to adjust release cycles either way, and so we should choose whatever is best for us as the contributor community15:36
notmynameI did chuckle when the question, "would deploying openstack in containers help?" was asked. it's all about the kuuuubes! /cc clayg15:37
tdasilvanotmyname: in the end i think this would affect very little about how swift community does releases...15:38
claygnotmyname: deploying in containers would *totally* help - not only that it would solve all the problems - scaling - rolling upgrades - world peace - kubes solves it all15:38
notmynamepractically, swift releases every two months (ish) and has an LTS every six months (where "long" is defined as 18 months)15:38
claygfor free!15:38
kota_notmyname: at least, I'm looking forward to proxy_fs container image to deploy NFS endpoint with an existing Swift cluster like docker-registory ;)15:38
notmyname*mind blown*15:39
tdasilvaclayg, notmyname: good thread: https://twitter.com/kelseyhightower/status/96341350830081229515:42
kota_just an idea I like to have if it's possible15:42
*** itlinux has joined #openstack-swift15:42
kota_tdasilva: nice15:42
notmynamekota_: definitely possible. that's something that's (sortof) being worked on right now.15:44
kota_notmyname: good info!15:45
acolesnotmyname: did anyone answer you? some of us have been discussing replication of sharding containers in rm 66115:46
notmynameacoles: that's the first answer I got15:47
*** Guest36 has joined #openstack-swift15:49
*** Guest36 is now known as Darkpixl15:51
acolesnotmyname: that's cos we've been looking at a flipchart ;-)15:53
acolesalthough I'm not sure anything was written on the flipchart15:54
openstackgerritClay Gerrard proposed openstack/swift feature/deep: better replication debugging  https://review.openstack.org/54833015:59
*** d0ugal has quit IRC16:00
*** cbartz has joined #openstack-swift16:01
*** links has quit IRC16:04
*** htruta has quit IRC16:06
openstackgerritMerged openstack/swift feature/deep: Add note about enabling sharding  https://review.openstack.org/54827616:06
*** pcaruana has quit IRC16:07
*** SkyRocknRoll has quit IRC16:08
notmynamehmm.... it's not so much that "you have no business contributing maintenance patches because you dont' know the codebase". that's not always an accurate statement. it's that there's a thing called "swift" and it's not appropriate for a 3rd party shouldn't be managing it without also participating in the rest of the swift community16:13
notmynametdasilva: kota_: ^ clarity on what I just said in the room16:13
tdasilvanotmyname: my take is that it's not about how appropriate but about what reality actually is...16:15
tdasilvaif you told me today that I need to fix a security issue in cinder, i'd go after a cinder dev, not try to fix it myself...16:15
tdasilvaso I think the idea that we will pass on the work to another team (that is possiblity not already in the community) is a bit of wishful thinking, in reality i'd guess that work would just turn back to us in one way or another16:17
notmynameyeah, that's what I was trying to get at originally. but the counter is that there exists some internal team at a vendor that has committed to understanding an maintaining a project, eg swift. if that team exists, I believe (strongly) that what they produce shouldn't be called "Swift" without them participating with the rest of us16:18
notmynamewe can't pass off maintenance of older versions to a team that isn't participating with the rest of the community. worst case, they make a right royal mess of it and "swift" now looks bad16:19
*** Darkpixl has quit IRC16:20
kota_On our Swift community, I don't think community LTS is much matter for now, true?16:24
notmynameI don't understand16:25
kota_just keeping open stable branch to be backported some important issues.16:25
tdasilvakota_: just for example, I (red hat) will be supporting Newton for a very long time still16:25
tdasilvabut I'm not sure I (red hat) should be putting that burden on the upstream community16:26
kota_ah... I might mis-read of context of "supporting"16:26
kota_maintaining vs supporting16:26
openstackgerritTim Burke proposed openstack/swift feature/deep: Tighten up assertions on the sharded shard  https://review.openstack.org/54833516:27
*** Supun has joined #openstack-swift16:28
notmynametdasilva: (1) maybe upstream should do the work, because distros are the way people use our software; (2) you as tdasilva *do* participate upstream already16:29
thurloatand I've been maintaining and supporting a 1.13 + upstream backports versio nfor a dog's age16:29
notmynamebut if there were a team at red hat that were supporting newton and *not* participating upstream, IMO that should be "redhat-swift" instead of "swift"16:30
thurloattrying to shed that baggage as we go, but its not always as simple as keeping master stable and following along in a large org16:30
kota_sounds true.16:30
kota_as well as "swiftstack" instead of "swift"?16:31
*** saint_ has quit IRC16:31
notmynamekota_: yeah. if swiftstack isn't participating upstream16:31
thurloatwhat if swiftstack is maintaining their own patches and features while still participating, can tehy still call it swift?16:31
thurloatcan/should16:32
notmynamethurloat: I think we're only talking about maintenance on older releases. IMO your question is different16:32
tdasilvathurloat: I think to notmyname's point is that we would not want an "official upstream release of 1.13.500 that is maintained by people who are not swift cores16:33
notmynameright16:34
thurloatunderstood, thanks tdasilva16:34
tdasilvaif it's swiftstack's version of swift 1.13.500, "I don't care"16:34
*** geaaru has quit IRC16:34
notmynametdasilva: lol. yep. you were right. nothing changing :-)16:34
kota_lol16:35
thurloatdevil's advocate: now what if there were a large userbase stuck in 1.13 land who want the set of patches that whatever non-community member is maintaining -- and swift is so far beyond that that those patches don't even apply upstream16:35
thurloatthe communityt isn't interested in maintaining a 1.x release anymore16:35
notmynamethurloat: to an extent, that's the reality today (at least the fact that there are some people using versions old enough to not be easily maintained by applying current patches). hard to know of "large userbase" or not16:37
*** Guest36 has joined #openstack-swift16:37
notmynameso my gut reaction is that the community shouldn't run away from their users16:37
notmynameie if there are a lot of users using old stuff, the community has a degree of responsibility to support that16:38
kota_oh, yeah, I might be wrong. Even it's upstream code base, too old release is hard to maintain.16:38
kota_espicially, after some code refactoring work.16:38
tdasilvai think reality sets in a a community...a community is a group of people that share the same goals/interestest/whatever...if my users, your users and notmyname users are all stuck on 1.13.+ i think naturally we will get together and work together16:38
notmyname"support" may simply be answer questions and providing guidance. that's what I think we do today, and it's on the "easy" side of the spectrum16:38
tdasilvaif it's just my users, i think at some point the community is going to tell me to take a hike16:38
thurloatcould end up with a python 2/3 situation as a community if its not careful in that regard16:39
notmynamethat's a really good analogy :-)16:39
notmynamebut I think the goal should be to do our best to avoid that!16:40
notmynameone thing I think we've done well so far is to support upgrades to new versions without having to go through every intermediate release16:41
thurloatagreed with that, the upgrade process is pretty brainless16:41
thurloat,s/brainless/seamless/16:42
notmynamethurloat: so in your case, I think it's "our" responsibility (our in quotes only because of the weirdness of assuming for the moment that you somehow aren't part of "us"--but of course you totally are) is to help you when you have questions and issues with your older version and to also encourage you to upgrade!16:42
kota_notmyname: +116:43
thurloati think that the project being as big as it is in popularity (and growing), should it discourage people forking to support 1.13 users? i.e. redhat-swift.16:43
notmynameIMO we should discourage forking in nearly every case16:44
notmynameperfect timing! the conversation in the room is ending, and my laptop is running out of battery!16:45
*** zhurong has quit IRC16:45
kota_lol16:45
* notmyname closes up for now...16:45
thurloati'm distracting everyone from the conference from the comfort of my office16:45
*** gkadam has quit IRC16:47
*** cbartz has quit IRC16:48
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Workaround glitchy container stats in probe test after shrinking  https://review.openstack.org/54835116:50
claygtorgomatic: I still need container-replicators to have -p options please16:55
rledisezhi guys, alecuyer and I will arrive tomorrow around noon. our flight to Paris is delayed, we'll miss the connection for Dublin tonight. see you tomorrow16:56
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Cleanup ContainerBroker.get_own_shard_range  https://review.openstack.org/54747816:56
acolesrledisez: hope you make it16:58
claygrledisez: woot!  see you tomorrow!16:58
*** m_kazuhiro has quit IRC17:02
*** zaitcev has quit IRC17:07
*** mvk has quit IRC17:14
*** gyee has joined #openstack-swift17:16
openstackgerritMerged openstack/swift feature/deep: Let shard-info work with conf.d  https://review.openstack.org/54828217:18
*** Supun has quit IRC17:21
*** Supun has joined #openstack-swift17:22
*** hseipp has quit IRC17:24
*** ejat has quit IRC17:31
*** ejat has joined #openstack-swift17:31
*** ejat has quit IRC17:31
*** ejat has joined #openstack-swift17:31
*** links has joined #openstack-swift17:35
*** Supun has quit IRC17:40
*** Supun has joined #openstack-swift17:41
*** Supun has quit IRC17:58
*** Supun has joined #openstack-swift17:58
*** pdardeau has quit IRC18:01
openstackgerritMerged openstack/swift feature/deep: Only shrink into an ACTIVE acceptor  https://review.openstack.org/54829618:05
*** gerardgine has joined #openstack-swift18:13
*** gyee has quit IRC18:31
*** tesseract has quit IRC18:31
*** m_kazuhiro has joined #openstack-swift18:36
*** Guest36 has quit IRC18:38
*** gerardgine has quit IRC18:40
*** gerardgine has joined #openstack-swift18:44
*** gerardgine has quit IRC18:45
*** gerardgine has joined #openstack-swift18:45
*** Guest36 has joined #openstack-swift19:09
*** gerardgine has quit IRC19:10
*** m_kazuhiro has quit IRC19:10
*** gerardgine has joined #openstack-swift19:15
*** armaan has joined #openstack-swift19:16
*** Supun has quit IRC19:16
*** Supun has joined #openstack-swift19:17
*** Guest36 has quit IRC19:18
*** Supun has quit IRC19:19
*** Supun has joined #openstack-swift19:19
*** Supun has quit IRC19:19
*** gerardgine has quit IRC19:23
*** gerardgine has joined #openstack-swift19:27
kota_oh the snow has stopped19:27
kota_rledisez: hope safe journey19:29
*** Guest36 has joined #openstack-swift19:49
*** Guest36 has quit IRC19:59
*** links has quit IRC20:30
DHEis there a CLI tool to make a composite ring, or am I going to have to make my own using the python api?20:30
*** Guest36 has joined #openstack-swift20:52
*** gerardgine has quit IRC20:58
*** gerardgine has joined #openstack-swift20:59
*** Guest36 has quit IRC21:02
*** duobei has joined #openstack-swift22:00
*** Guest36 has joined #openstack-swift22:09
*** Guest36 has quit IRC22:19
*** gerardgine has quit IRC22:30
*** gerardgine has joined #openstack-swift22:35
*** mvk has joined #openstack-swift22:36
*** pdardeau has joined #openstack-swift22:39
*** itlinux has quit IRC22:40
*** gerardgine has quit IRC22:43
*** gerardgine has joined #openstack-swift22:44
*** Guest36 has joined #openstack-swift22:50
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Split expirer methods and parametrize task account  https://review.openstack.org/54387422:50
*** rcernin has joined #openstack-swift22:59
*** Guest36 has quit IRC22:59
*** kei_yama has joined #openstack-swift23:05
*** duobei has quit IRC23:22
*** Guest36 has joined #openstack-swift23:30
*** duobei has joined #openstack-swift23:37
*** duobei has quit IRC23:38
*** Guest36 has quit IRC23:40
« Monday, 2018-02-26 Index Wednesday, 2018-02-28 »

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