Tuesday, 2017-02-28

*** cppforlife_ has quit IRC00:00
*** spotz has quit IRC00:00
*** amit213 has quit IRC00:01
*** zacksh has quit IRC00:02
*** nikhil|afk has quit IRC00:02
*** nikhil|afk has joined #openstack-swift00:03
*** amit213 has joined #openstack-swift00:06
*** zacksh has joined #openstack-swift00:09
*** spotz has joined #openstack-swift00:09
claygtdasilva: timburke: kota_: any ideas?  https://bugs.launchpad.net/pyeclib/+bug/166844700:09
openstackLaunchpad bug 1668447 in PyECLib "python3 tests fail" [Undecided,New]00:09
*** sams-gleb has joined #openstack-swift00:13
*** dja has quit IRC00:15
*** darrenc has quit IRC00:16
*** jamielennox|away is now known as jamielennox00:16
*** darrenc has joined #openstack-swift00:17
*** sams-gleb has quit IRC00:17
*** dja has joined #openstack-swift00:18
*** rledisez has quit IRC00:18
*** rledisez has joined #openstack-swift00:18
timburkeclayg: your py27 run created a pyeclib_c.so in the working tree, yeah? try deleting it then running py34 (or w/e) again00:31
timburkethat's what seemed to do it for me... master still passes on my machine00:32
claygtimburke: brilliant!00:33
*** gatuus has quit IRC00:51
claygtimburke: so just a simple `tox -re py34` isn't enough because I guess the .so get's built not in the tox env?00:58
claygtimburke: is something funky going on with our paths?  .tox/py34/lib/python3.4/site-packages/pyeclib_c.cpython-34m.so01:01
claygtimburke: well you were right, deleting the .so made the tox -e py34 pass01:05
*** zhugaoxiao has quit IRC01:06
*** Administrator_ has quit IRC01:06
* tdasilva is back01:06
clayggotta be directory prefernces kinda thing?01:06
kota_godd morning01:14
kota_clayg, timburke: i also suppose kevin and tushar had py3 compatible work in those days01:15
claygkota_: timburke: tdasilva: this is so opaque - I have no idea if this is even close?  https://review.openstack.org/#/c/438756/01:16
kota_clayg, timburke: and nice to have py3 gate job to avoid regression, let me look at what's going on the test01:16
patchbot_patch 438756 - openstack-infra/project-config - Add experimental python34 job to pyeclib01:16
kota_clayg: what's "experimental"? is that for non-voting?01:17
claygkota_: I was just reading https://docs.openstack.org/infra/manual/creators.html#zuul-best-practices and following tdasilva's lead01:18
claygit's definately non-voting01:18
kota_ok, got it01:18
claygi see absolutely NO reason to add a job to voting until we can see if it works?01:18
claygbut I think maybe I have to land something before I can see if it works... i have no idea01:18
claygi just thought it was good first step to get my feet wet with project-config01:18
tdasilvaclayg: need to update one more file IIRC01:20
claygtdasilva: i was hoping using the pre-existing job made that not needed?01:21
tdasilvaclayg: yeah, i think you are right: - python-jobs should take care of it in projects.yaml ???01:22
tdasilvai agree it is very opaque01:22
tdasilvalots of trial and error01:22
openstackgerritThiago da Silva proposed openstack/swift master: use correct py3 rpm package in bindep  https://review.openstack.org/43875801:25
tdasilvaclayg: patch 436642 failed because of above ^^^01:25
patchbot_https://review.openstack.org/#/c/436642/ - swift - WIP: centos func test01:25
claygtdasilva: i don't really understand who uses bindep and to what ends?01:25
clayg2017-02-27 23:29:02.283980 | No package python3-devel available.01:26
tdasilvaright, it is called python34-devel01:26
claygso apparently something in the gate/node magic somewhere expects bindep to do something...01:26
tdasilvanow here is the fun part: in centos liberasurecode-devel is packaged with rdo packages01:26
tdasilvaso we need to install rdo repo :(01:26
clayg^ zaitcev sound good to me!01:27
claygtdasilva: so can you do the "experimental" on patch 438758 and see if there's any other issues?01:28
patchbot_https://review.openstack.org/#/c/438758/ - swift - use correct py3 rpm package in bindep01:28
tdasilvathe problem is that rdo repos are per release. eg: centos-release-openstack-newton01:28
tdasilvayeah, i think i'm going to update it first01:28
claygtdasilva: even for dependencies?01:28
mattoliveraukota_: morning01:29
tdasilvaclayg: i believe so01:29
kota_mattoliverau: o/01:29
kota_mattoliverau: is everything fine?01:30
* kota_ is thinking mattoliverau had a long trip from Atlanta01:30
claygtdasilva: so I'm not sure the py34 tox env will still run in the gate?01:33
clayg  # Restrict python34 testing to <= Mitaka.01:33
clayg  - name: ^gate-.*-python34(-db)?(-nv)?$01:33
clayg    branch: ^stable/(liberty|mitaka)01:33
clayg  # Restrict python35 testing to >= Newton.01:33
clayg  - name: ^gate-.*-python35(-db)?(-nv)?$01:33
clayg    branch: ^(?!stable/(liberty|mitaka)).*$01:33
tdasilvalol01:33
tdasilvagreat!01:33
claygpy34 was so last year01:33
tdasilvaprobably should remove the line then???01:34
tdasilvaand isn't that a problem for the whole TC Goals thing?01:35
tdasilvathis is so weird01:35
kota_that means, we need py35 gate and bindep should follow that?01:36
kota_i mean patch 43875801:36
patchbot_https://review.openstack.org/#/c/438758/ - swift - use correct py3 rpm package in bindep01:36
claygwho knows?01:36
kota_idk01:36
tdasilvai'm trying to figure out if anyone is running py3 tests on centos01:37
claygwhy does swift have a bindep on python3<anything>?01:37
claygtdasilva: but you're not *trying* to run py3 tests?  you're just trying to run on centos?01:37
tdasilvaclayg: because we want to test again py3 right? don't we have unit tests already in py3?01:37
tdasilvaclayg: correct! but i think running bindep is part of the gates setup script ???01:37
mattoliveraukota_: yeah it was long, but back at work now.. now just a little jet lagged the other way round :P01:37
mattoliverauyou?01:38
* mattoliverau stops for some lunch01:38
kota_clayg, tdasilva, mattoliverau: btw, could you guys review https://review.openstack.org/#/q/Ib90adcc2f059adaf203fba1c95b2154561ea7487,n,z?01:38
kota_if you have time to look at01:38
tdasilvakota_: starred, but probably won't be able to look at it today :(01:39
kota_that is needed to close...01:39
kota_timburke: thx01:39
claygtdasilva: yeah you're right - we have gate-swift-python3501:39
kota_tdasilva: ah, i ping timburke incorrectly, thanks for starring.01:41
tdasilvadoes anyone know what is the file we are supposed to update talking about py3 goals01:43
tdasilvawould like to have a look to see if I can learn if there's a project doing py3 on centos testing01:44
*** sams-gleb has joined #openstack-swift01:45
*** sams-gleb has quit IRC01:50
claygtdasilva: https://governance.openstack.org/tc/goals/pike/python35.html ?01:51
*** cppforlife_ has joined #openstack-swift02:00
*** disaster has joined #openstack-swift02:01
disasterHi! Is there a way in openstack swift to set an user as sendonly? With ACL or something02:02
claygdisaster: you should be able to drop the --read-acl from this example:  https://docs.openstack.org/developer/swift/overview_acl.html#example-shared-writable-container02:03
claygand get a write-only container02:03
claygI think most folks try to leverage PUT tempurls for that use-case, YMMV02:04
tdasilvaclayg: given that paste you shared earlier, should you have used py35 in patch 438756 ?02:05
patchbot_https://review.openstack.org/#/c/438756/ - openstack-infra/project-config - Add experimental python34 job to pyeclib02:05
claygI think I need to add a py35 env to pyeclib tox.ini but yes02:05
disasterclayg: and write wont allow delete?02:05
claygdisaster: PUT tempurl would be better then02:06
claygdisaster: PUT can always destory data - you can over-write?02:06
openstackgerritThiago da Silva proposed openstack/swift master: add rdo repo to install liberasurecode-devel  https://review.openstack.org/43875802:07
claygtdasilva: ^ brilliant02:08
tdasilvaclayg: really ugly IMO :/02:08
claygwell see if it works first02:08
tdasilvaclayg: sad if we have to keep updating this line every release: centos-release-openstack-newton02:09
disasterclayg: arf my use case is cronjob backup but in case of hack i would like the server don't store the full access to the object storage02:09
claygdisaster: container level tempurls are great for that use-case02:10
disasterclayg: ok but how my cronjob can have the tempurl?02:10
claygcreate a container server-xyz-backups and put a tempurl on it - then from the cronjob just `swift tempurl` with the right bits and upload with curl02:11
claygmaybe tricker if you also need segmented uploads02:11
claygdisaster: are you using keystone?02:11
disasterclayg: in fact it's on the ovh object storage02:12
disasterclayg: so i don't really know02:12
*** klrmn has quit IRC02:12
tdasilvaovh is using keystone02:13
claygdisaster: ok, well if it's public cloud you might ask their support what's supported - a non-admin account with a write-acl container is probably near the best solution02:14
disasterclayg: ok and the account use from the server will not be able to delete files?02:16
claygdisaster: you need to ask you're service provier what they support - a write-acl even without listing could still allow for delete/overwrite - but limited to the container02:17
disasterclayg: ok thank you02:19
tdasilvadisaster: just note what clayg said about over-writing objects02:19
openstackgerritClay Gerrard proposed openstack/pyeclib master: Add more isolation to tests  https://review.openstack.org/43877002:24
disastertdasilva: yes i will ask the support, my only other option is to take a server for backup on chroot ssl and rotate the chroot directory02:25
disastertdasilva: or maybe you have a third way?02:25
tdasilvadisaster: what i mean to say, is that clayg pointed out that even if you are able to find a way to get acls to only write data, and not delete the data, your server could still overwrite the same object with 0 bytes, effectively deleting it02:26
tdasilvadisaster: unless i'm missing something02:26
claygtdasilva: I think he mostly just doesn't want to put his keys-to-the-kingdom on a server just for backups02:27
claygthe use-case may be more restrictive than that - but I'd shoot for solving that risk model first and going from there02:27
*** bkopilov has quit IRC02:27
tdasilvaoic02:28
openstackgerritClay Gerrard proposed openstack/pyeclib master: Don't let nose play with our PYTHONPATH.  https://review.openstack.org/43877002:30
tdasilvanow i'm getting this: /tmp/04-cd800e142a044f52b054d7a1af3acebd.sh: line 5: mkfs.xfs: command not found02:31
tdasilvabut i thought i'd get mkfs.xfs with xfsprogs02:31
disastertdasilva: clayg: thank you for your help02:34
*** disaster has quit IRC02:34
tdasilvaclayg: where is your mkfs.xfs installed ? /usr/sbin ?03:02
*** rledisez has quit IRC03:06
*** rledisez has joined #openstack-swift03:08
*** adriant has joined #openstack-swift03:16
*** tqtran has quit IRC03:19
tdasilvaclayg: just got a link for https://trunk.rdoproject.org/centos7-master-head/report.html03:20
tdasilvastill trying to understand what that is....03:21
tdasilvajust FYI...03:21
openstackgerritThiago da Silva proposed openstack/swift master: fix bindep file to enable func test in centos  https://review.openstack.org/43875803:23
adriantJust digging through the swiftclient code and trying to confirm something... Does the swiftclient handle expired tokens in any capacity?03:26
adriantAs in, does it catch the error, and fetch a new token.03:26
adriantIt looks like it sort of does in the _retrying function, but only once03:27
adriantWhat I'm trying to handle here is a case where a duplicity backup with Swift is taking over 12 hrs, and the token expiry is 12 hours.03:30
adriantThe token is running out, and the backup falls over.03:30
tdasilvaclayg: yay!! http://logs.openstack.org/58/438758/3/experimental/gate-swift-tox-xfs-tmp-func-centos-7/cd2467a/console.html03:31
adriantMost of the other clients handle this fine by using keystoneauth which handles fetching new tokens for you, but Swift doesn't seem to...03:31
*** klrmn has joined #openstack-swift03:45
*** sams-gleb has joined #openstack-swift03:47
*** bkopilov has joined #openstack-swift03:48
*** cshastri has joined #openstack-swift03:50
*** sams-gleb has quit IRC03:51
mattoliverauadriant: swiftclient now supports using a keystone auth context, and I also thought it retried. But timburke or joeljwright would be the best to answer this. If they or noone else can't chime  in I can take a look at the code.. but am about to step out for an errand so might be gone for a bit.04:01
adriantmattoliverau, the weird part is that Swift seems to has responded with a 502, but on looking through the HAproxy logs I've matched that to a 401 from Keystone, so I'm not sure if the token expired and the error swiftclient got was silly...04:03
openstackgerritClay Gerrard proposed openstack/pyeclib master: Don't let nose play with our PYTHONPATH.  https://review.openstack.org/43877004:20
*** psachin has joined #openstack-swift04:23
zaitcevclayg: https://review.openstack.org/438793 - but I can almost guarantee you that this won't build, because it needs Source0 automatically found somehow.04:25
patchbot_patch 438793 - rpm-packaging - Add PyECLib and liberasurecode04:25
claygzaitcev: AWESOME!04:30
zaitcevI tried to cargo-cult what I could from pre-existing specs, mostly the {{ }} patterns.04:31
claygzaitcev: *totally* - AFAIK all packages are cargo-cult's - srly let the gods please give us blessings from the sky!04:32
*** klrmn has quit IRC04:32
claygwhy does gate-rpm-packaging-tox-lint-ubuntu-xenial sound weird to me?04:34
zaitcevYeah, I don't see how lint(1) would help04:34
zaitcevIn fact, it probably does not exist on Linux.04:35
claygliberasurecode.spec.j2.suse should not use '%setup'. Please use '%autosetup' instead.04:35
zaitcevok04:36
zaitcevWhat about the Source0 question04:36
*** jrichli has quit IRC04:36
*** jrichli has joined #openstack-swift04:36
zaitcevAlso, autosetup comes from openstack_macros, right?04:36
clayggate jobs say the darndest things04:36
zaitcevOh. I thought you said it04:37
claygzaitcev: there's got to be some magic somewhere that untars the upstream source tar balls in the right place to make something work04:37
zaitcev     master-rpm-packaging-build-centos7 #2995: FAILURE // Reported result: SUCCESS04:38
zaitcevThey do say darnest things!04:38
zaitcevI think Source0 has to be an http:// and then it all works. But which one?04:38
*** ChanServ sets mode: +v jrichli04:39
claygi say we call this a huge success for the day - and tomorrow we'll try to get dirk to give us some advice04:39
zaitcevI have a bunch of meetings starting 07:30 tomorrow04:41
claygwell i hope the first one is where a bunch of people come in to say how awesome zaitcev is!  I think that's what'll be my first meeting tomorrow.04:41
claygg'night pete!04:42
zaitcevLater04:42
kota_how awesome zaitcev is! good night!04:46
zaitcevoh no04:46
zaitcevYou are the only one who managed to put your patch in, in the aftermath of PTG.04:47
zaitcev:-)04:47
kota_:-)04:48
*** Jeffrey4l__ has quit IRC04:49
openstackgerritClay Gerrard proposed openstack/pyeclib master: Add py35 tox environment  https://review.openstack.org/43879904:51
*** Jeffrey4l__ has joined #openstack-swift04:52
claygnotmyname: i'm worried if i try to make https://wiki.openstack.org/wiki/Meetings/Swift setup for next meeting I'll ruin everything05:03
*** rickflare has joined #openstack-swift05:07
*** adriant has quit IRC05:30
claygi'm still having trouble with that cannot switch to different thread someimes... even after patch 42549505:39
patchbot_https://review.openstack.org/#/c/425495/ - swift - Give spawn a cycle (MERGED)05:39
*** sams-gleb has joined #openstack-swift05:49
*** zaitcev has quit IRC05:49
*** sams-gleb has quit IRC05:54
*** dmorita has quit IRC06:03
*** Jeffrey4l__ is now known as Jeffrey4l06:10
*** dja has quit IRC06:22
*** gk-1wm-su has joined #openstack-swift06:35
*** gk-1wm-su has left #openstack-swift06:35
*** sams-gleb has joined #openstack-swift07:02
*** tqtran has joined #openstack-swift07:03
*** tqtran has quit IRC07:07
*** rcernin has joined #openstack-swift07:11
*** ChubYann has quit IRC07:15
*** geaaru has joined #openstack-swift07:17
*** tesseract has joined #openstack-swift07:34
*** hseipp has joined #openstack-swift07:40
*** circ-user-6O5Su has joined #openstack-swift07:47
*** dja has joined #openstack-swift07:57
circ-user-6O5SuI have a query, I have done a setup of openstack cloud with swift as a backend for glance in  mitaka version..  From command line it is working fine, but in dashboard, when i click object-store→ container, it shows blank page.. Is there anything to be enabled in horizon for mitaka version??  My proxy-server.conf - http://paste.openstack.org/show/600718/ In swift log everything is normal except this, http://paste.openstack.org/show/6007108:00
circ-user-6O5Supls do guide08:00
*** dmorita has joined #openstack-swift08:03
*** dmorita has quit IRC08:07
*** bob_cheesey has joined #openstack-swift08:11
*** gk-1wm-su has joined #openstack-swift08:14
*** gk-1wm-su has left #openstack-swift08:14
*** pcaruana has joined #openstack-swift08:17
*** klrmn has joined #openstack-swift08:38
*** jordanP has joined #openstack-swift08:39
*** klrmn has quit IRC08:49
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Small homework for ec duplciation  https://review.openstack.org/43886208:58
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Small homework for ec duplciation  https://review.openstack.org/43886208:59
*** Jeffrey4l has quit IRC09:00
*** Jeffrey4l has joined #openstack-swift09:00
*** csmart has quit IRC09:09
*** cbartz has joined #openstack-swift09:12
*** circ-user-6O5Su has quit IRC09:32
*** surf has joined #openstack-swift09:37
*** surf has quit IRC09:56
*** edausq has joined #openstack-swift09:57
*** bob_cheesey has quit IRC10:08
*** bob_cheesey has joined #openstack-swift10:09
*** csmart has joined #openstack-swift10:36
*** dfflanders has quit IRC10:37
*** jith has joined #openstack-swift10:39
*** jith has left #openstack-swift10:39
*** jith has joined #openstack-swift10:40
*** mvk has quit IRC10:42
jithhi all, I have a query, I have done a setup of openstack cloud with swift as a backend for glance in  mitaka version..  From command line it is working fine, but in dashboard, when i click object-store→ container, it shows blank page.. Is there anything to be enabled in horizon for mitaka version??10:44
jithMy proxy-server.conf - http://paste.openstack.org/show/600718/In swift log everything is normal except this, http://paste.openstack.org/show/600719/10:44
*** dja has quit IRC10:45
*** mvk has joined #openstack-swift11:14
*** sams-gleb has quit IRC11:31
*** sams-gleb has joined #openstack-swift11:31
*** sams-gleb has quit IRC11:36
*** sams-gleb has joined #openstack-swift11:51
*** cppforlife_ has quit IRC12:02
*** bkopilov has quit IRC12:07
*** fungi has quit IRC12:11
*** fungi has joined #openstack-swift12:18
*** kei_yama has quit IRC12:30
*** csmart has quit IRC12:39
*** csmart has joined #openstack-swift12:40
jithhi all.. I have a query, I have done a setup of openstack cloud with swift as a backend for glance in  mitaka version..  From command line it is working fine, but in dashboard, when i click object-store→ container, it shows blank page.. Is there anything to be enabled in horizon for mitaka version??12:48
jithMy proxy-server.conf - http://paste.openstack.org/show/600718/In swift log everything is normal except this, http://paste.openstack.org/show/600719/12:48
jithpls do guide12:48
*** cshastri has quit IRC13:03
-openstackstatus- NOTICE: restarting gerrit to address performance problems13:08
*** ChanServ changes topic to "restarting gerrit to address performance problems"13:09
*** klamath has joined #openstack-swift13:26
*** klamath has quit IRC13:26
*** klamath has joined #openstack-swift13:26
*** _JZ_ has joined #openstack-swift13:28
*** amoralej is now known as amoralej|lunch13:32
-openstackstatus- NOTICE: ok gerrit is back to normal13:38
*** ChanServ changes topic to "ok gerrit is back to normal"13:38
tdasilvagood morning13:43
*** ChanServ changes topic to "Topic: Let's talk, we're nice. | PTG etherpad: https://etherpad.openstack.org/p/swift-ptg-pike | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews"13:44
-openstackstatus- NOTICE: gerrit is back to normal and I don't know how to use the openstackstaus bot13:44
asettleJesse is incredibly type A and very driven. Him and I both are in different ways. JP sits between us and I do feel sorry for him sometimes.13:45
asettleOH FFS13:45
asettleGuess who changed the channel and pressed enter13:45
asettleThis idiot13:45
openstackgerritGábor Antal proposed openstack/swift master: Use more specific asserts in test/unit/common  https://review.openstack.org/34278113:49
*** silor has joined #openstack-swift13:49
*** silor1 has joined #openstack-swift13:53
*** silor has quit IRC13:55
*** silor1 is now known as silor13:55
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Small homework for ec duplciation  https://review.openstack.org/43886213:57
*** openstackgerrit has quit IRC14:03
*** bkopilov has joined #openstack-swift14:03
*** cppforlife_ has joined #openstack-swift14:09
*** chlong has joined #openstack-swift14:30
*** zaitcev has joined #openstack-swift14:35
*** ChanServ sets mode: +v zaitcev14:35
*** amoralej|lunch is now known as amoralej14:38
*** foutatoro has joined #openstack-swift14:45
*** sams-gleb has quit IRC15:01
*** sams-gleb has joined #openstack-swift15:02
*** dmorita has joined #openstack-swift15:04
*** sams-gleb has quit IRC15:06
*** dmorita has quit IRC15:08
*** chlong has quit IRC15:11
*** sams-gleb has joined #openstack-swift15:16
*** hseipp has quit IRC15:39
*** psachin has quit IRC15:41
*** chlong has joined #openstack-swift15:43
*** ediardo has quit IRC15:44
*** ediardo has joined #openstack-swift15:46
*** tonanhngo has joined #openstack-swift15:49
notmynamegood morning16:00
*** bob_cheesey has quit IRC16:04
*** rcernin has quit IRC16:08
timburkegood morning16:08
*** foutatoro has quit IRC16:09
*** jcaron has quit IRC16:15
*** jcaron has joined #openstack-swift16:16
*** jcaron1 has joined #openstack-swift16:26
*** jcaron has quit IRC16:26
*** pcaruana has quit IRC16:34
*** chsc has joined #openstack-swift16:37
*** chsc has joined #openstack-swift16:37
*** Jeffrey4l has quit IRC16:41
*** csmart has quit IRC16:42
*** Jeffrey4l has joined #openstack-swift16:42
*** gatuus has joined #openstack-swift16:44
*** openstackgerrit has joined #openstack-swift16:46
openstackgerritClay Gerrard proposed openstack/pyeclib master: Add py35 tox environment  https://review.openstack.org/43879916:46
openstackgerritClay Gerrard proposed openstack/pyeclib master: Use py35 tox environment by default  https://review.openstack.org/43879916:47
*** cppforlife_ has quit IRC16:47
*** cbartz has quit IRC16:49
*** csmart has joined #openstack-swift16:51
notmynameI'm going through Boston summit presentations this morning. some of them stand out just because of "here's this cool stuff in swift!" but I've never seen any of it upstream16:52
tdasilvanotmyname: yeah, i noticed that too :/16:52
notmynamewhich isn't to say that everything has to go upstream, but on the other hand, stuff that's modifying swift should probably have some upstream collaboration16:52
notmynameso, I'm like "cool!" but also "who are you?"16:53
*** geaaru has quit IRC16:55
openstackgerritThiago da Silva proposed openstack/swift master: refactor some common code from crypto  https://review.openstack.org/43905816:58
*** tqtran has joined #openstack-swift16:59
*** tqtran has quit IRC16:59
*** mvk has quit IRC17:02
*** tesseract has quit IRC17:09
*** csmart has quit IRC17:11
*** jordanP has quit IRC17:19
claygtdasilva: so you think that we don't really *need* to merge something like this https://review.openstack.org/#/c/43879317:21
patchbot_patch 438793 - rpm-packaging - Add PyECLib and liberasurecode17:21
claygtdasilva: in order to get infra/upstream packages in the gate?17:22
claygtdasilva: because you can just use existing rdo packages on centos nodes?17:22
tdasilvaclayg: i actually am not sure. I need to figure that out...I was given a link yesterday that seems to list packages that are built for every commit, which maybe could be kind of cool??? idk17:25
tdasilvaOTOH, does it solve our problem of specifying a release tag?17:25
claygnotmyname: it reminds me of the "never had only 3 contributors" problem - rather we have years of experience keeping clasically-closed-source-big-corp from messing up the projects while learning how to upstream17:26
tdasilvaclayg: because even if with that we can build again top of master, we still really want to be able to build again a tagged release that has not been made available yet by downstream packagers17:26
claygtdasilva: yeah ideally we would have a cent7-downstream and cent7-upstream job - they would both say "I need liberasurecode-devel" one would get what you or I would get on our cent7 vm - the cent7-upstream would get whatever was latest the tagged release of liberasurecode - because those packages are built automatically and stuffed into the infra repository17:27
tdasilvaright17:27
claygtdasilva: ah right, and the rdo packages might have "newer than stock downstream" - but they won't have "constantly built from tags during the development of the next release"17:27
claygtdasilva: ok, so we should try to address Dirk's comments?  And try to better understand what's the next steps after we have liberasurecode in the rpm-pacaging17:28
tdasilvaclayg: looking at Dirk's comments17:29
tdasilvaclayg: a problem we might have is that liberasurecode does not get a tarball in http://tarballs.openstack.org/17:30
tdasilvanot sure if that's what Dirk is asking for on hist third comment there17:31
claygtdasilva: ah, maybe so - i kind of remember writing that down somewhere17:31
claygthat's good tho!?17:31
clayg... except the deb-liberasurecode job doesn't need it apparently?17:31
tdasilvaisn't that because the deb-liberasurecode actually copies the whole source code to their repo?17:32
notmynametimburke just pointed this ML post out to me. http://lists.openstack.org/pipermail/openstack-dev/2017-February/113029.html tl;dr horizon moving to a 1 +2 to land model (with a goal of landing small patches sooner)17:34
robcresswellnotmyname: My ears are burning17:34
*** mmotiani_ has joined #openstack-swift17:34
notmynamerobcresswell: it's really interesting. something that we've talked about before (and chosen not to make "official" guidelines about)17:35
robcresswellnotmyname: I dont know what Swifts situation is, but Horizon now has 2 active cores, and a couple very part time.17:35
notmynamerobcresswell: for us, the only rule is "use your best judgement" with a bias towards 2 cores.17:35
robcresswellSo we really dont haver a choice :)17:35
notmynameyeah, that's a really important point17:36
robcresswellhave a *17:36
tdasilvawe have a hard time landing patches with 10+ cores, can't imagine with 2...17:36
robcresswellYeah. The idea here is that we can bump small patches that people feel comfortable with; minor improvements, docs, etc, without holding them up on dual approval.17:38
robcresswellhigher risk of course, but thats the decision I'm going with for now :)17:38
notmynameagain, openstack never learned how to be successful as or with small projects. we're only learning that now17:38
notmynamerobcresswell: yeah, we've always had a standing "if you think it's low impact and an ok patch, go ahead and land it" rule17:39
notmynamerobcresswell: so I think it's a totally reasonable decision to make, especially given the limited cores you have.17:39
robcresswellnotmyname: Thats good to hear, thanks17:40
notmynamerobcresswell: I hope it results in shorter patch review time overall. however, I suspect the cost might be increased "stability" testing or integration work. but only in the sense that more eyes up front is likely to account for more edge cases before it lands instead of after17:42
*** gatuus has quit IRC17:42
notmynamerobcresswell: regardless of how many reviewers you have, we'll always land bugs, so the basic "try to make it better and solve user problems, fixing bugs as we know about them" is still exactly the same17:43
robcresswellnotmyname: It'll definitely increase the risk of faulty/incomplete patches landing.17:43
robcresswellMy hope is that maintaining some pace will encourage new contributors who may become core17:43
robcresswellthe other option is to make the merge rate painfully slow, which wont add to the cores long term17:43
notmynameI've floated the idea that we should just give everyone commit rights. (I was told that is a bad idea) ;-)17:44
zaitcevI routinely eschew +A even on 2x+2 if the patch is something tricky like the part++ patch.17:45
* robcresswell shudders at the thought17:45
robcresswellAbsolutely, hence the note in the email to ask for a second opinion for complex code. The important part is that cores feel they *can* approve code with a single +2, not that they *must*17:46
notmynamethat's the key, to me. core, or having a commit bit, is about trust. so if a core says something should or shouldn't land, they should be able to do that on their own. and I trust them to make the right call regardless of how many other reviews there are17:48
*** gatuus has joined #openstack-swift17:48
*** dmorita has joined #openstack-swift17:50
tdasilvaclayg: i'm trying to organize my thoughts on how to make progress on gate jobs tasks. What are you focusing on, what can I help you with or maybe find others to help?17:51
robcresswellnotmyname: Agreed17:51
*** csmart has joined #openstack-swift17:51
tdasilvaclayg: would it help to share a etherpad, trello, whatever to compile a list of task items, goals?17:51
*** dmorita has quit IRC17:52
*** dmorita has joined #openstack-swift17:52
*** mmotiani_ has quit IRC18:05
*** chlong has quit IRC18:06
*** klrmn has joined #openstack-swift18:11
tdasilvaanother major s3 outage :/18:26
zaitcevall regions or just the default Virginia center?18:39
*** thumpba has quit IRC18:40
notmynameus-east-118:42
*** mmotiani_ has joined #openstack-swift18:43
*** cppforlife_ has joined #openstack-swift18:45
notmyname"But wait. Isn't S3 "the cloud". Everyone promised the cloud would never go down, ever. It has infinite uptime and reliability. Well good thing I have my backups on [some service that happens to also use S3 as a backend]."18:46
claygtdasilva: i'm just sort of chipping at the eduges18:48
*** bkopilov has quit IRC18:49
claygtdasilva: if I'm entirely honest about the epic, it's really - know enough about openstack-infra/devstack/gate so that when someone says "but golang!? you can't!" I can say "we already do"18:50
notmynamethat's the ticket! ^18:50
claygall this libec stuff is mostly a means to an end - if it has independent value along the way it's kind of only a bonus18:50
*** ChubYann has joined #openstack-swift18:51
claygit also help me get infra to help with stuff that is already a problem so they don't see me as making new golang problems18:51
claygby the time I start to ask for changes to be merged to infra projects "because golang" I should already be able to make a reasoned argument as to why the changes is obviously the correct path forward because point to how we handle other non-python services/depencies18:53
claygtdasilva: so i'm ok with a trello board for "swift merges golang code" - and it having libec/pyeclib stories in it because that's a great way to get started18:55
*** dmorita has quit IRC18:59
*** dmorita has joined #openstack-swift19:01
tdasilvaclayg: ack19:03
*** bkopilov has joined #openstack-swift19:05
*** thumpba has joined #openstack-swift19:10
*** thumpba has quit IRC19:10
tdasilvaclayg: when you have a chance, can you take a look at patch 43875819:11
patchbot_https://review.openstack.org/#/c/438758/ - swift - fix bindep file to enable func test in centos19:11
timburkeoh yeah, what *is* the deal with that? can we get rid of python-devel, too? what about the deb -dev packages?19:12
*** patchbot_ is now known as patchbot19:12
*** amoralej is now known as amoralej|off19:13
claygtdasilva: I'm with timburke that doesn't look obviously correct at all19:16
claygtdasilva: "fix bindep/centos" is not enough context to judge the change19:16
claygtdasilva: what's broken?  why does that change help?19:17
tdasilvaclayg: sorry, should have provided better patch comments19:18
tdasilvait's currently broken because there's no such thing as python3-devel19:18
tdasilvarpm package19:18
tdasilvaideally we would substitue for the right thing19:18
timburke...and we can't because...?19:18
tdasilvabut in centos there's only py34, which i don't think we are interested in at the moment19:19
tdasilvaso for now....i'm just not adding a py3 job for centos nodes19:19
tdasilvabut would like to add other jobs19:19
tdasilvathen i'll look into adding py3 jobs in centos nodes19:19
openstackgerritJim Cheung proposed openstack/liberasurecode master: Add Phazr.IO libphazr backend to liberasurecode  https://review.openstack.org/42435319:19
tdasilvapy35 jobs that is19:19
tdasilvatimburke, clayg: does that make sense? if it does, i'll add as a comment to the patch in case we need to look back into it19:21
tdasilvai mean commit message19:21
openstackgerritMerged openstack/python-swiftclient master: Expose --prefix as an option for st_delete  https://review.openstack.org/43733219:22
claygtdasilva: that makes *more* sense19:24
tdasilvabut?19:25
*** chlong has joined #openstack-swift19:25
timburkeis py34 available for centos in the gate currently?19:25
tdasilvatimburke: yeah, the rpm package i believe is available, so I could add that in place if you all think it will be helpful19:26
claygtdasilva: so I guess the part that would complete the picture for me is a failing gate-swift-tox-xfs-tmp-py35-centos-7 job since I guess ubuntu-xenial's python3-dev installs a py35 version?19:26
tdasilvaand we can focus on py35 later??19:26
claygyeah for me python34-devel makes more sense than pulling it out19:27
claygeven if no jobs use it19:27
timburkei'm just struggling to see why the py34 -devel package doesn't already satisfy python3-devel19:27
tdasilvaworks for me19:27
* clayg goes to find a cent7 node19:28
tdasilvatimburke: i was just going by a paste clayg provided yesterday that py34 was for <= Mitaka19:28
tdasilvaso my understanding is that we are now targeting py3519:28
tdasilvabut that's ok, let's add py34 now, this should not be a big deal...19:28
timburkethat's certainly true, at least for ubuntu. no idea about what -infra's plans are wrt centos, though19:29
tdasilvatimburke: me neither :/19:30
claygtimburke: I think infra thinks ubuntu by default - I would have thought sometime around xenial they started thinking py35 instead of py34 because that's what their default downstream ships?19:31
claygalso py35 is better than py34 in a bunch of cool async def ways ;)19:31
timburkeclayg: yeah, that's my impression, too19:31
timburkebut py36 is *even better*19:31
timburke(i assume. it's 0.1 bigger!)19:31
clayg10% is a big deal19:32
notmynameat least I know I've made *some* impact on the swift community over the years. "bigger version == better" ;-)19:35
claygis swift-get-nodes -p known broken for non-legacy policies?19:38
claygssh 127.0.0.1 "ls -lah ${DEVICE:-/srv/node*}/sdb14/objects-/673"19:38
notmynamedoes it use the right ring and just mess up the output there?19:39
clayglooks like the right devices for that part on that ring19:40
claygnotmyname: output is correct if you use -P option instead of ring19:41
claygi don't think we have a bug for it19:41
notmynameI'm working on a PTG summary for the ML. anyone want something specific to be said?19:41
claygnotmyname: it was awesome19:44
claygnotmyname: put it something about the food19:44
notmynameclayg: clearly the most important part of the week ;-)19:44
redboAnd someone should make a costco run for snacks next time.19:45
*** Renich has joined #openstack-swift19:46
timburkehmmm.... now i wonder how swift-get-nodes behaves mid-part-power-increase....19:47
claygtimburke: which part?19:48
notmynameclayg: all of the parts! *ba-dum-dish*19:48
timburkewell, both parts, anyway19:48
timburkeat any rate, it might be worth noting that an increase is in progress...19:49
*** dja has joined #openstack-swift19:55
*** gatuus has quit IRC20:07
*** mmotiani_ has quit IRC20:10
*** mmotiani__ has joined #openstack-swift20:10
*** dja has quit IRC20:11
*** mmotiani_ has joined #openstack-swift20:15
*** mmotiani__ has quit IRC20:15
*** mmotiani_ has quit IRC20:23
*** silor has quit IRC20:36
*** mvk has joined #openstack-swift20:37
notmynamemy thoughts on the PTG http://lists.openstack.org/pipermail/openstack-dev/2017-February/113062.html20:39
notmyname(I didnt' mention food)20:39
*** dja has joined #openstack-swift20:39
claygI didn't mention food is basically like saying "you don't need to read this there's nothing important in it"20:41
*** tonanhngo has quit IRC20:42
*** dja has quit IRC20:44
tdasilvalol20:46
claygtdasilva: I've been making jokes all week about how everytime someone talks about "how was the PTG" food comes up - my attitude is basically "did we eat; not sure I remember that.."20:47
tdasilvai just remember bbq! that was good20:48
tdasilvabut yeah, sandwiches got old really quickly and no snacks :/20:49
*** dja has joined #openstack-swift20:54
openstackgerritThiago da Silva proposed openstack/swift master: fix bindep file to enable func test in centos  https://review.openstack.org/43875820:56
*** dja has quit IRC21:00
jrichlinotmyname: good write-up.  I am glad you mentioned that scheduling and awareness has issues to work-out.  I didn't see that in a different PTG summary I saw on Twitter.21:07
claygrledisez: onovy: do we have a bug for the thing that says "we shouldn't force a recalc when we do_listdir?"21:23
*** dfflanders has joined #openstack-swift21:24
*** chlong has quit IRC21:27
timburketdasilva: so it seems kinda strange that there wouldn't be a python3-devel meta-package that would grab 3.4 or 3.5 or whatever -- how does that work for the non-devel package? do they have to install python34? is that just baked into the base image?21:31
tdasilvatimburke: i think that's just what's available in centos epel21:33
tdasilvai'm not sure why they didn't provide a python3-devel meta-package21:33
tdasilvastrange, i agree21:33
tdasilvaat least that's my understanding...21:33
timburkeyep, seems to check out looking at https://dl.fedoraproject.org/pub/epel/7/x86_64/p/ ...21:34
*** Jeffrey4l has quit IRC21:35
*** dja has joined #openstack-swift21:36
*** chlong has joined #openstack-swift21:39
claygtdasilva: i added check experimental - should work21:40
tdasilvaclayg: thanks! also proposed this: https://review.openstack.org/#/c/439143/21:41
patchbotpatch 439143 - openstack-infra/project-config - add centos-7 jobs to libec, pyeclib, swift21:41
tdasilvanot sure i got it all right, but maybe -infra guys can provide some guidance21:41
*** Renich has quit IRC21:42
*** Jeffrey4l has joined #openstack-swift21:48
*** chlong has quit IRC21:58
timburketdasilva: where was the change for pyeclib? i think i missed it...22:01
*** tonanhngo has joined #openstack-swift22:01
timburkeclayg: it's no fair nerd-sniping me with a bug and then not reviewing the patch -- https://review.openstack.org/#/c/438720/22:08
patchbotpatch 438720 - swift - Stop using client headers for cross-middleware com...22:08
timburkebah, i mean https://review.openstack.org/#/c/437236/22:08
patchbotpatch 437236 - swift - Log correct status code for conditional requests22:08
mattoliveraumorning22:13
*** tonanhngo has quit IRC22:13
*** adriant has joined #openstack-swift22:21
timburkeoh oh! mattoliverau! you can go land patch 331369 now that you understand how os.environ['TZ'] is bass-ackwards!22:23
patchbothttps://review.openstack.org/#/c/331369/ - swift - Always set swift processes to use UTC22:23
notmynamemattoliverau: hello! I wanted to ask you a couple of questions about your PR to runway22:33
notmynamemattoliverau: but I just got back from the kids' school. give me a bit to get my mind back in work mode ;-)22:33
mattoliverautimburke: kk22:34
mattoliveraunotmyname: kk22:34
timburkethanks mattoliverau :-)22:42
mattoliverautimburke: nps :)22:43
mattoliverauI had tested it alot, which is what lead to my initial confustion, thanks for clearing it up at the PTG22:43
notmynamemattoliverau: is the TZ sign different because you're in the southern hemisphere?22:47
*** sams-gleb has quit IRC22:48
timburkesounds right22:48
notmynameopenstack summit going back to Vancouver https://www.openstack.org/blog/2017/02/the-openstack-summit-is-returning-to-vancouver-in-may-2018/22:54
mattoliverauyay, I liked vancouver!22:55
mattoliveraunotmyname: sounds a good a reason as any :P22:55
zaitcevBut... there's no developer-oriented content at the Summit anymore, right?23:19
klrmnthat doesn't mean notmyname gets a pass =)23:21
notmynameklrmn: I'll probably get a free pass to go ;-)23:22
notmynamezaitcev: I need to look in to that. I'll do that this week23:23
notmynamemattoliverau: how does this work? https://github.com/swiftstack/runway/pull/1/files#diff-9339dccc15a12a00ff8ca4ba686a9417R5023:24
notmynamemattoliverau: what's the source dir for that?23:24
notmynameI'd expect a chdir or something in there23:24
klrmnnotmyname: i kinda meant pass *from* going, not pass *to* go…but only realized the ambiguity after hitting send.23:24
notmynameklrmn: I know :-)23:25
openstackgerritTim Burke proposed openstack/swift master: Container sharding docs  https://review.openstack.org/43832223:25
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925023:26
*** kei_yama has joined #openstack-swift23:26
*** klamath has quit IRC23:31
mattoliveraunotmyname: roles/swift/files/23:31
mattoliveraunotmyname: anything relative comes from a roles files direcory. So it easier to move around.23:32
mattoliveraunotmyname: so https://github.com/swiftstack/runway/pull/1/files#diff-1c6427c722c534363f630ecdb933955823:32
mattoliveraunotmyname: that didn't link properly, so the 'ansible/make_rings.sh → ansible/roles/swift/files/remakerings'23:33
*** chsc has quit IRC23:39
kota_good morning23:44
timburkegood morning kota_!23:45
kota_good morning timburke!23:45
kota_timburke: did the fix for auth land?23:46
timburkenot yet. notmyname's been distracted, i guess? he's the one that needs to push the buttons so the swift3 fix can land...23:46
kota_i see23:47
timburkeyeah, i may have pulled the trigger a bit early on submitting those patches :-/23:48
notmynametimburke: what did I (not) do?23:50
notmynamemattoliverau: hmm...ok23:51
mattoliveraukota_: morning23:51
notmynamemattoliverau: ah! I see23:51
timburkemerge the tempauth fix (& backport) so we can close https://bugs.launchpad.net/swift3/+bug/156119923:51
openstackLaunchpad bug 1561199 in OpenStack Security Advisory "Client-accessible headers are used to send authentication information to other middlewares" [Undecided,Incomplete]23:51
timburkenotmyname: i'm tempted to go +2/+A https://review.openstack.org/#/c/438720/ but you're the one that needs convincing on the backport23:52
patchbotpatch 438720 - swift - Stop using client headers for cross-middleware com...23:52
notmynametimburke: IIRC the only reason to do a backport is to enable gate checking of stable branches (ie to backport the real patch)23:53
timburkekota_: you should take a look at ps2 on https://review.openstack.org/#/c/438719/ -- i think i covered most of your concerns?23:54
patchbotpatch 438719 - swift3 - Stop using client headers for cross-middleware com...23:54
timburkenotmyname: swift3 (master) gates off of ocata swift23:55
notmynameclayg: check out mordred's ML post about zuul v3. looks like actual job config can eventually be moved to our repo (I think that's awesome)23:55
timburke(used to be even older, so at least we've got that going for us)23:55
*** dja has quit IRC23:57
*** dja has joined #openstack-swift23:58
kota_timburke: yup, i just read the subscription from gerrit that notify me it was updadted.23:58

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