Tuesday, 2016-10-04

*** diogogmt has joined #openstack-swift00:20
*** mathiasb has quit IRC00:24
*** zaitcev has joined #openstack-swift00:24
*** ChanServ sets mode: +v zaitcev00:24
kota_good morning00:28
kota_notmyname: talking on liberasurecode warning, https://bugs.launchpad.net/swift/+bug/1628906/comments/10, you can ignore the warning00:30
openstackLaunchpad bug 1628906 in OpenStack Object Storage (swift) "swift-object-reconstructor memory leak" [High,Confirmed]00:30
kota_notmyname: it appears when backend ".so" library not found. And IIRC, it will run only once when initialize the pyeclib module to check the backends availability.00:32
kota_notmyname: so that warning means, you can't use the backend anyway, however, if you don't want to use it, nothing you have to do on the message.00:33
kota_notmyname: looking back at the bug comment, rledisez doesn't install isal (Intel ErasureCode engine, you know) and shss (NTT's backend) in his environment. I think you see a warning log just for shss, doesn't it?00:35
*** mathiasb has joined #openstack-swift00:36
kota_notmyname: Speaking of EC work, please let me check the conflict status.00:38
mattoliveraukota_: o/00:39
*** oak has quit IRC00:39
kota_notmyname: in my feeling, i want to land mine first because it's already too old but in the community perspective, the acoles's one seems to have more benefit00:40
kota_mattoliverau: o/00:40
*** adu has quit IRC00:41
kota_notmyname: on another perspective, iirc, mine vs acoles's doesn't seem to conflict a lot because his work should change on diskfile layer basically and my work is on proxy and index mapping so...00:43
kota_notmyname: anyway, I'll take a look for his one and will update my opinion.00:44
kota_mattoliverau: btw, does gerrit gate have been broken yet?00:44
mattoliveraukota_: well I've seen some stuff merge... so I hope that means it's working again00:45
*** tqtran has quit IRC00:46
kota_mattolvierau: good to hear, thanks!00:46
*** adu has joined #openstack-swift00:49
notmynamekota_: thanks. yeah, I get that it's just a warning. but it gets printed on every call of `swift-recon`01:04
kota_notmyname: hmm... yeah, I'm just writing the response meesage for the comment01:05
kota_notmyname: could you tell me the *liberasurecode* version?01:05
kota_i think timur was working on the suppressing that https://github.com/openstack/liberasurecode/commit/c7a94df0724af30b26e3856f9c14344fc9b73a0901:06
*** natarej_ has joined #openstack-swift01:07
kota_yeah, swift recon client import the POLICIES and storage_policy module import VALID_EC_TYPES which will trigger the log.01:08
kota_if you're using older liberasurecode.01:08
notmynamekota_: https://gist.github.com/notmyname/8a75111177a66675d92085dbaa62614a01:08
kota_notmyname: let me see01:08
kota_notmyname: probably what you need to do is upgrading liberasurecode :0)01:09
kota_notmyname: https://github.com/openstack/pyeclib/blob/master/pyeclib/ec_iface.py#L42-L4601:09
notmynameok, maybe because I grabbed the distro version (xenial)01:09
notmynamekk01:09
notmynameok, I need to go eat dinner01:10
notmynamebut let me know on the patches01:10
kota_notmyname: enjoy01:10
*** natarej has quit IRC01:10
*** klrmn has quit IRC01:16
*** cdelatte has quit IRC01:18
kota_notmyname: comment added at your gist. if you need more on something, please ping me.01:24
*** dmorita has quit IRC01:27
*** dmorita has joined #openstack-swift01:28
*** dmorita has quit IRC01:32
*** adu has quit IRC01:33
*** adu has joined #openstack-swift01:37
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: WIP: Conditional Fast-POST  https://review.openstack.org/38136301:57
*** chsc has quit IRC02:11
jrichliI haven't gotten any email that allows me to cast my vote for TC.  That is how this works, right?  you get an email?02:11
*** dmorita has joined #openstack-swift02:13
timburkejrichli: i hadn't either. contact the election folks with one of your commit SHAs per http://lists.openstack.org/pipermail/openstack-dev/2016-October/105002.html -- tonyb got me sorted out inside of 10 mins (thanks again tonyb!)02:18
tonybtimburke: np02:19
jrichlithanks, will do.  Hi tonyb :-)02:19
tonybjrichli: o/02:21
jrichlitonyb: do you need the official email, or can I send you the sha here?02:33
tonybjrichli: Please send it to all the officals addresses are here: http://governance.openstack.org/election/#election-officials02:34
jrichliok, thx02:34
tonybjrichli: that way all the officals are on the same page02:34
jrichligotcha02:34
*** klrmn has joined #openstack-swift02:39
*** tqtran has joined #openstack-swift02:43
*** _JZ_ has joined #openstack-swift02:44
*** adu has quit IRC02:45
*** tqtran has quit IRC02:48
*** trananhkma has joined #openstack-swift02:55
*** dmorita has quit IRC02:58
*** dmorita has joined #openstack-swift02:59
notmynamegood evening03:01
*** tqtran has joined #openstack-swift03:02
*** dmorita has quit IRC03:03
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925003:04
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873603:04
*** dmorita has joined #openstack-swift03:05
notmynameoh, yikes. is there a bug for https://review.openstack.org/#/c/381363/03:05
patchbotpatch 381363 - swift - WIP: Conditional Fast-POST03:05
zaitcevoh noes03:05
zaitcevOTL orz ...03:06
*** tqtran has quit IRC03:06
openstackgerritTuan Luong-Anh proposed openstack/swift: Fix a typo in documentation  https://review.openstack.org/38137703:07
openstackgerritPete Zaitcev proposed openstack/swift: Add a configurable URL base to staticweb  https://review.openstack.org/37280903:09
*** links has joined #openstack-swift03:10
*** _JZ_ has quit IRC03:13
*** chsc has joined #openstack-swift03:25
*** dmorita has quit IRC03:27
openstackgerritMerged openstack/swift: Fix typo: remove redundant 'that'  https://review.openstack.org/38093803:27
*** chsc has quit IRC03:30
*** dmorita has joined #openstack-swift03:31
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873603:33
mattoliveraunotmyname: o/03:38
notmynameyo03:38
openstackgerritJohn Dickinson proposed openstack/swift: adding reno sphinx tree  https://review.openstack.org/38138203:49
*** natarej__ has joined #openstack-swift04:06
*** mingyu has joined #openstack-swift04:08
*** natarej_ has quit IRC04:09
*** mingyu has quit IRC04:14
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: [Don't merge] Use __init__() of Daemon class in sub classes  https://review.openstack.org/36561404:38
mahatic_jrichli: timburke :thanks for the info. I was waiting for TC email too04:43
*** klrmn has quit IRC04:44
openstackgerritKota Tsuyuzaki proposed openstack/swift: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916504:51
*** zaitcev has quit IRC05:03
*** dmorita has quit IRC05:07
*** nadeem has joined #openstack-swift05:09
*** dmorita has joined #openstack-swift05:23
*** dmorita has quit IRC05:24
*** dmorita has joined #openstack-swift05:25
*** dmorita has quit IRC05:30
*** takashi has joined #openstack-swift05:47
*** mingyu has joined #openstack-swift06:02
*** tqtran has joined #openstack-swift06:05
*** tqtran has quit IRC06:10
*** Jeffrey4l__ has quit IRC06:14
*** Jeffrey4l__ has joined #openstack-swift06:14
*** Jeffrey4l__ has quit IRC06:14
*** Jeffrey4l_ has joined #openstack-swift06:15
*** Jeffrey4l_ is now known as Jeffrey4l06:15
*** winggundamth has quit IRC06:17
*** nadeem has quit IRC06:28
*** nadeem has joined #openstack-swift06:29
*** tqtran has joined #openstack-swift06:31
*** tqtran has quit IRC06:35
*** tqtran has joined #openstack-swift06:38
*** rcernin has joined #openstack-swift06:43
*** takashi has quit IRC06:44
*** ppai has joined #openstack-swift06:46
*** admin6_ has joined #openstack-swift06:50
*** tesseract- has joined #openstack-swift06:52
*** hseipp has joined #openstack-swift06:54
openstackgerritHanxi Liu proposed openstack/swift: Add links to more detailed overview in overview_architecture  https://review.openstack.org/38144606:56
openstackgerritHanxi Liu proposed openstack/swift: Add links to more detailed overview in overview_architecture  https://review.openstack.org/38144606:58
openstackgerritHanxi Liu proposed openstack/swift: Add links to more detailed overview in overview_architecture  https://review.openstack.org/38144607:01
*** rledisez has joined #openstack-swift07:19
openstackgerritKota Tsuyuzaki proposed openstack/swift: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916507:24
*** geaaru has joined #openstack-swift07:31
*** takashi has joined #openstack-swift07:55
*** jistr has joined #openstack-swift07:57
*** admin6_ has quit IRC07:59
*** amoralej|off is now known as amoralej08:03
openstackgerritHanxi Liu proposed openstack/swift: Add links to more detailed overview in overview_architecture  https://review.openstack.org/38144608:03
*** lhx_ has joined #openstack-swift08:03
*** takashi has quit IRC08:05
*** jordanP has joined #openstack-swift08:06
*** tqtran has quit IRC08:09
*** takashi has joined #openstack-swift08:11
*** takashi_ has joined #openstack-swift08:31
*** takashi has quit IRC08:32
*** takashi_ is now known as takashi08:37
*** lhx_ has quit IRC08:44
*** acoles_ is now known as acoles08:45
acolesgood morning09:01
kota_acoles: morning :-)09:02
acolesso should we have received TC voting mail? anyone know the email subject so i can search for it09:04
acoleshi kota_09:04
kota_acoles: Poll: OpenStack Technical Committe (TC) Election - October 201609:06
kota_acoles: the subject which you are looking for.09:06
acoleskota_: thanks09:08
acoleslooks like I didn't receive that09:08
kota_acoles: that's too bad :/09:09
*** nadeem has quit IRC09:11
kota_notmyname: since the result of quick look at the durable eliminate patch and my global ec work, the order is not significant for the technical reason because the conflict area is just test/unit/proxy/test_server.py09:14
kota_notmyname: the order for landing.09:15
kota_notmyname: it seems to still conflict with mine but it looks easy to rebase rather than ever.09:15
* kota_ has working on rebasing, rebasing and rebasing anytime on the change at test/unit/porxy/test_server.py09:16
kota_since the experience, I'm realizing, i want to cleanup the proxy/test_server.py code because it's so long lines in *a* file.09:17
kota_but it's also not ugent, anyway, though.09:17
kota_notmyname: since i can rebase easily, i think, it's ok for vice-versa09:19
* kota_ is leaving his office09:22
kota_see you swifters.09:22
mahatic_acoles: good morning09:25
mahatic_acoles:  If you're expecting the poll email it to your gmail, you should ask them to resend it. They suspect there's a problem between CIVS and gmail09:26
acolesmahatic_: thanks, it should be coming to me at hpe though. I requested another.09:48
mahatic_acoles: ah okay09:49
*** jistr is now known as jistr|mtg09:59
*** zigo has quit IRC10:01
*** zigo has joined #openstack-swift10:04
*** zigo is now known as Guest8478010:05
cnfwhy would swift be constantly using about 800 IOPS while havig no traffic?10:07
cnfand every 7 minutes it drops to 0 for a little while10:08
ahalemaybe auditor or replicator processes ?10:14
*** Guest84780 has quit IRC10:14
*** zigo_ has joined #openstack-swift10:16
cnfit's a single node wih replication set to 110:16
*** SkyRocknRoll has joined #openstack-swift10:20
cnfnotmyname any idea?10:25
*** abhitechie has joined #openstack-swift10:29
*** SkyRocknRoll has quit IRC10:54
*** rcernin has quit IRC10:57
*** rcernin has joined #openstack-swift10:58
*** jistr|mtg is now known as jistr11:00
*** amoralej is now known as amoralej|lunch11:13
*** silor has joined #openstack-swift11:21
*** zigo_ is now known as zigo11:23
*** dmorita has joined #openstack-swift11:25
*** silor has quit IRC11:28
*** silor has joined #openstack-swift11:28
*** dmorita has quit IRC11:29
*** admin6 has quit IRC11:30
*** admin6 has joined #openstack-swift11:31
*** silor1 has joined #openstack-swift11:31
*** silor has quit IRC11:32
*** silor1 is now known as silor11:32
*** ppai has quit IRC11:35
*** mingyu has quit IRC11:40
*** lhx_ has joined #openstack-swift11:49
*** ppai has joined #openstack-swift11:51
*** jlwhite has quit IRC12:14
*** jlwhite has joined #openstack-swift12:15
*** furlongm has quit IRC12:15
*** furlongm has joined #openstack-swift12:16
*** mingyu has joined #openstack-swift12:18
cnfhmm, this is so strange12:20
cnfconstant 800IOPS or about 100MB/s reads12:21
*** takashi has quit IRC12:26
cnfit seems to be /usr/bin/swift-object-auditor /etc/swift/object-server.conf12:30
*** ppai has quit IRC12:32
*** cdelatte has joined #openstack-swift12:33
*** _JZ_ has joined #openstack-swift12:35
*** amoralej|lunch is now known as amoralej12:37
*** cbartz has joined #openstack-swift12:41
*** klamath has joined #openstack-swift13:03
*** klamath has quit IRC13:05
*** klamath has joined #openstack-swift13:05
*** klamath has quit IRC13:07
*** klamath has joined #openstack-swift13:10
*** kei_yama has quit IRC13:16
*** mingyu has quit IRC13:20
*** oak has joined #openstack-swift13:21
jrichliacoles: I didn't get the mail either.  I followed the instructions in http://lists.openstack.org/pipermail/openstack-dev/2016-October/105002.html13:31
jrichlithey sent a mail to the same address that worked this time13:32
*** daemontool has joined #openstack-swift13:33
acolesjrichli: yep I did same13:33
acolesmathiasb: hi, I'm looking at your patch 364878 and trying to understand how to use openstackclient to interact with barbican, as shown in the commit message, but I can't see support for a 'secret' subcommand in the CLI. How does that work?13:33
patchbothttps://review.openstack.org/#/c/364878/ - swift - WIP: Storing encryption root secret in Barbican13:33
acolesjrichli: have you any success with this ^^ ?13:34
jrichliacoles: sadly, I haven't attempted the barbican install  myself yet.13:34
acolesjrichli: ok, nm. I have barbican running, just need to get my secret setup. resorting to curl now.13:36
acolesAnyone else still missing the 'f' shortcut in gerrit? It's been a while now but I'm still longing for it to come back :'(13:42
tdasilvayes!13:42
tdasilvaacoles: if you run for the TC promising to bring back the 'f' shortcut you will get my vote ;)13:44
acolestdasilva: LOL. The one sure ticket for victory... "Make the f key great again"13:45
tdasilvalol13:45
jrichli:-)13:46
*** links has quit IRC13:49
*** diogogmt has quit IRC13:59
*** tmoreira has quit IRC14:01
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being restarted to address performance degradation and should return momentarily14:01
*** abhitechie has quit IRC14:03
*** daemontool_ has joined #openstack-swift14:06
*** daemontool has quit IRC14:10
*** natarej__ has quit IRC14:21
*** natarej__ has joined #openstack-swift14:22
*** vint_bra has joined #openstack-swift14:24
*** zaitcev has joined #openstack-swift14:40
*** ChanServ sets mode: +v zaitcev14:40
*** mingyu has joined #openstack-swift14:50
*** admin6_ has joined #openstack-swift14:50
*** sgundur has joined #openstack-swift14:53
stevemaracoles: key management support via barbican is available as a plug-in to openstackclient. you need to install openstackclient, then install barbicanclient and the 'secret' command will show up. cc jrichli14:55
*** tmoreira has joined #openstack-swift14:56
acolesstevemar: OIC. thanks!14:56
jrichlistevemar: thanks14:57
mathiasbacoles: maybe it's a version issue? i am running openstack client 2.3.014:58
mathiasbif you have the barbican client you can use that as well, "barbican secret store"14:58
*** sgundur has quit IRC15:01
acolesmathiasb: what stevemar said seems to work, I just didn't have barbicanclient installed, now I do and I get the secret subcommands15:02
mathiasbacoles: great, somehow I missed that comment, thanks stevemar!15:03
acolesmathiasb: btw i have openstack 3.2.015:04
*** oak has quit IRC15:04
acolesso now I need to set up barbican endpoints in keystone15:04
*** klrmn has joined #openstack-swift15:06
stevemarnp swifterinos :)15:08
*** rcernin has quit IRC15:10
*** daemontool_ has quit IRC15:19
*** diogogmt has joined #openstack-swift15:21
notmynamegood morning15:23
*** dmorita has joined #openstack-swift15:26
*** daemontool has joined #openstack-swift15:27
*** dmorita has quit IRC15:31
*** chsc has joined #openstack-swift15:41
cnfohai notmyname15:43
cnfmy workday is pretty much done15:43
cnfwell, the office one, anyway15:43
*** chsc has quit IRC15:51
openstackgerritHanxi Liu proposed openstack/swift: Remove the file named MANIFEST.in  https://review.openstack.org/38194715:56
notmynamereminder that the cross-project sessions etherpad is at https://etherpad.openstack.org/p/ocata-cross-project-sessions. take a look now that there's a tentative schedule proposed15:57
notmynamealso, please continue to fill out https://etherpad.openstack.org/p/ocata_swift_summit_topics for the swift sessions15:57
*** arch-nemesis has joined #openstack-swift16:00
*** diogogmt_ has joined #openstack-swift16:07
*** diogogmt has quit IRC16:08
*** diogogmt_ is now known as diogogmt16:08
*** silor has quit IRC16:09
*** tongli has joined #openstack-swift16:11
*** rledisez has quit IRC16:17
*** links has joined #openstack-swift16:17
*** links has quit IRC16:18
*** sgundur has joined #openstack-swift16:21
*** cdelatte has quit IRC16:23
*** admin6_ has quit IRC16:26
*** openstackgerrit has quit IRC16:26
*** openstackgerrit has joined #openstack-swift16:27
*** openstackgerrit has quit IRC16:28
*** tesseract- has quit IRC16:29
*** openstackgerrit has joined #openstack-swift16:29
*** openstackgerrit has quit IRC16:30
*** chsc has joined #openstack-swift16:30
*** dmorita has joined #openstack-swift16:30
*** openstackgerrit has joined #openstack-swift16:30
*** daemontool has quit IRC16:35
*** cbartz has left #openstack-swift16:39
*** hseipp has quit IRC16:41
*** mingyu has quit IRC16:41
*** nikivi has joined #openstack-swift16:46
openstackgerritJohn Dickinson proposed openstack/swift: adding reno sphinx tree  https://review.openstack.org/38138216:51
acolesnotmyname: once we move to reno will we cease to have CHANGELOG file?17:00
*** chsc has quit IRC17:00
notmynameacoles: I don't want to17:02
* timburke wonders if it'd be worth adding an [extras] section to osc's setup.cfg...17:03
timburkegood morning17:03
notmynameacoles: with 2.10.0, I wrote the CHANGELOG entry and then translated it to yaml to put in the reno file17:03
*** jordanP has quit IRC17:04
*** nadeem has joined #openstack-swift17:04
*** nikivi has quit IRC17:05
acolesnotmyname: and do you intend to continue that way? I ask because today I was trying to read the release notes for another project and ended up having to google my way to where they are published by openstack i.e. they weren't in the repo in a form I could read :/17:05
*** mingyu has joined #openstack-swift17:05
notmynameI really don't like the idea of either (1) to read release notes, go download a dependency and run a script to get something printed to a screen or (2) go look at a webpage someplace else that may or may not be currently available17:06
notmynameso yeah, I really like the idea of human-written notes in plain text that live with the code in the repo17:06
notmynamefor now, I expect to continue to maintain the CHANGELOG file, but I'll admit I'm fighting against gravity here, so it partly depends on how tired I get17:07
*** mingyu has quit IRC17:07
*** mingyu has joined #openstack-swift17:08
timburkenotmyname: look at it this way: you fight against gravity and *win* every morning!17:08
cnfhey notmyname, is it normal for a mostly-kinda default install of swift to generate 800 iops constantly (about 100MB/s)17:09
cnfit was the auditor, but it was just doing it for hours on end, with 2 files in the storage ^^;17:10
notmynamethat does seem high17:10
cnfyah17:10
*** mingyu has quit IRC17:10
notmynamecnf: swift will continually look at the drives in the cluster to check that the data is good and in the right place. this is done by the auditor and the replicator17:10
cnfright17:11
notmyname(there are several of each)17:11
cnfI figured that bit out17:11
notmynameand they can be tuned to not be as active17:11
cnfi also disabled them on my single node install :P17:11
cnfbut 800iops seems incredibly expensive, even on enterprise HW17:11
cnfnotmyname:  disabeling them on a single node instance should not matter much, right?17:12
notmynameyeah, it matters, if you've got multiple drives and are using more than one replica17:13
cnfno, 1 replica17:13
cnfnotmyname:  i know it's not a typical setup :P17:15
cnfanyway, if you keep it on, 800iops on a default install does seem mighty high17:15
cnfis it supposed to just keep using that, constantly?17:15
notmynamewith one replica, you can't recover from any failures, so there's no reason to run auditors. replication would only need to be run if you change the cluster capacity (to move a bit of data around)17:15
cnfright17:16
cnfi'm counting on the ZFS it is stored on to keep the data sane17:16
cnfI didn't find how to not start the auditor though17:16
notmynameremove/rename the auditor sections in {account,container,object}-server.conf17:17
cnfah, ok17:17
claygnotmyname: you could contribute a plugin to make reno support plaintext output so you could generate them from the yaml17:17
notmynameand/or `swift-init account-auditor stop`17:17
*** sgundur has quit IRC17:18
cnfnotmyname:  so if I set up swift properly, 800iops constantly on every swift node is just part of normal upkeep?17:18
notmynameclayg: it currently takes the yaml and outputs plain test. or you mean a plugin to take plain text as input? that might be better17:18
cnfalso, when read/writes happen, does that get throttled back at all?17:18
notmynamecnf: well, no single spinning drive can even do half of 800iops, so your number is dependent on how many drives you have in the server. it's normal to have some background activity as a baseline. the amount depends on several things, including your ring part power, how much data is in the cluster, and any failures currently in the cluster17:20
*** lhx_ has quit IRC17:20
cnfwell, I did a create 8 1 117:21
*** sgundur has joined #openstack-swift17:21
*** mingyu has joined #openstack-swift17:21
cnfand yeah, "some" I was expecting, but I am trying to figure out why my system was getting hammered with 800iops17:22
notmynamepart power of 8 is nice and small. glad you didn't go for something like 18 ;-)17:22
claygi thought it generated rst or something?  if it already spits out plaintext change logs why can you just check them in when you run it?  i'm confused.17:23
claygSee - you have solved nothing - we're all going to reno experts in like 2 hours17:23
cnfnotmyname:  i was reading about it, and some page i read said smaller than 8 had an averse effect, and larger made things heaver on small installs17:24
cnfso i just went wirh 8 :P17:24
cnfhmm, I realize swift on a single node is kinda overkill17:25
cnfbut I can't find any other halfdecent object store to run17:25
notmynameclayg: `reno report` generates plain text. but the sphinx doc tree is necessary for the CI job to generate the URL structure at http://docs.openstack.org/releasenotes/swift/* so that it can be linked from https://releases.openstack.org/newton/index.html17:27
*** lhx_ has joined #openstack-swift17:28
*** sgundur has quit IRC17:36
*** sgundur has joined #openstack-swift17:36
*** geaaru has quit IRC17:42
*** nadeem has quit IRC17:42
*** nadeem has joined #openstack-swift17:42
*** lhx_ has quit IRC17:48
*** bjolo_ has joined #openstack-swift17:53
*** hseipp has joined #openstack-swift17:54
*** tqtran has joined #openstack-swift17:55
*** chsc has joined #openstack-swift17:58
*** chsc has joined #openstack-swift17:58
*** rcernin has joined #openstack-swift17:58
*** mingyu has quit IRC18:08
*** hseipp has quit IRC18:13
*** acoles is now known as acoles_18:20
*** amoralej is now known as amoralej|off18:29
*** Suyi has joined #openstack-swift18:35
ahaleahh, thats why i didnt get a TC vote email, I don't qualify to vote :(18:39
notmynamewhat are the criteria? I thought it was "be a foundation member"18:42
ahale" Foundation individual members that are also committers for one of the official project teams repositories over the Liberty-Mitaka timeframe"18:42
notmynameah18:42
*** silor has joined #openstack-swift18:43
*** nikivi has joined #openstack-swift18:45
nadeemI have voted....lets hope more people vote for the change :)18:46
ahalemake openstack great again ?18:46
nadeemI would rather destroy the wall rather than creating new ones (as far as new ideas are concerned)18:47
ahalea vote against golang is a vote against walls18:48
*** silor has quit IRC18:48
*** sgundur has quit IRC19:05
*** sgundur has joined #openstack-swift19:08
openstackgerritShashirekha Gundur proposed openstack/swift: Invalidate cached tokens api  https://review.openstack.org/37031919:15
*** cdelatte has joined #openstack-swift19:34
openstackgerritThiago da Silva proposed openstack/swift: Fix swiftdir option and usage of storage policy aliases  https://review.openstack.org/34469319:34
*** nikivi has quit IRC19:36
cnfnotmyname:  do you know if I can run  swift and keystone behind the same reverse proxy on the same port?19:45
notmynamenot on the same port19:46
cnfhmm, damn19:46
cnfthey use the same paths?19:46
notmynamethey're likely using unique paths, but they don't share a common URL router, so only one process gets the request to read off the socket. if you send a keystone request to the swift proecess, swift will return an error. and vice versa.19:48
notmynameyou could write your own, but they'd still need to be listening on different sockets on the backend19:48
cnfwell, yeah, but they are behind a reverse proxy for ssl termination anyway19:48
*** bjolo_ has quit IRC19:49
*** bjolo_ has joined #openstack-swift19:49
*** sgundur has quit IRC19:50
*** sgundur has joined #openstack-swift19:51
cnfnotmyname:  sorry for trying to do things with swift it's not meant for :P19:51
notmynamenicest user ever. "oops I'm actually trying to use your software. is that ok?" YES! totally ok :-)19:51
cnf^^;19:52
cnfI need to read up more on how auth / keystone works, and how it interacts with swift19:53
clarkbI know horizon and keystone run on the same port with apache using different url prefixes for them19:54
clarkbso at least for keystone it is happy to do that19:54
*** sgundur has quit IRC19:55
cnfhmm19:55
clarkber with devstack specifically19:55
cnfclarkb: do you know any docs for that?19:55
*** sgundur has joined #openstack-swift19:55
clarkbI am not aware of any specific docs no, but you could see how devstack sets that up. (both are running as wsgi too which may affect stuff)19:56
cnfok19:56
cnfhmm, they all seem to use /v1 and /v2 etc though19:58
notmynameyeah, the "write your own" could also be spelled "use apache,etc and configure the paths yourself"19:58
cnfhttp://developer.openstack.org/api-ref/identity/v3/ that is keystone, right?19:59
*** sgundur has quit IRC20:00
*** _JZ_ has quit IRC20:00
clarkbyes20:00
cnfhmm20:01
cnffor now, sending /v3 to keystone would work, I guess20:01
*** bjolo_ has quit IRC20:01
cnfbut if swift upgrades api version to 3, i'd be boned :P20:01
clarkbI think devstack uses eg /identity/v3 and /dashboard20:01
cnfhmm20:02
cnfinteresting20:02
cnfso you can configure the base path somewhere?20:02
*** sanchitmalhotra has quit IRC20:02
clarkbya I think there are different config options to set the root url20:02
clarkband if not you can probably hack it with mod rewrite20:03
cnfhmm, admin_endpoint and public_endpoint, it seems20:03
cnfnice20:03
*** mingyu has joined #openstack-swift20:04
cnfok, i'll play with it some, tomorrow20:07
cnfand then try figure out how the user id / token thing works20:07
*** sgundur has joined #openstack-swift20:07
pdardeaucnf: you might find swift-on-file interesting https://github.com/openstack/swiftonfile20:10
cnfpdardeau:  hmm, thanks20:12
cnfpdardeau:  i'm assuming you lose the accounting / etc functionality if you use it?20:12
cnf(which I don't use anyway)20:12
pdardeaucnf: i have no idea. i haven't used it myself.20:13
cnfright20:13
cnfi will have a look at this, once I figure out how to run swift and swift3 properly20:13
cnfthanks a lot20:14
cnf"It is also recommended that these Filesystems provide data durability as Swift-On-File should not use Swift's replication mechanisms."20:14
cnfmakes sense20:14
pdardeaucnf: tdasilva can probably answer questions about it20:15
cnfok20:16
tdasilvahello20:16
cnfohai :P20:16
cnfdo you use swiftonfile tdasilva ?20:19
tdasilvacnf: I don't have any deployment clusters, just a dev.20:20
cnfright20:20
tdasilvas/deployment/deployed20:20
tdasilvacnf: what's your question?20:20
cnfnothing atm, pdardeau just linked it 10 minutes ago20:21
cnfi'm doing some unconventional things with swift, atm20:21
notmynametdasilva: cnf is running swift on zfs in a small cluster20:21
pdardeautdasilva: cnf expressed interest in running swift on top of zfs with replica=120:21
pdardeautdasilva: reminded me of swift-on-file20:21
cnfyeah20:22
cnfi mostly care about the swift (and S3) api, and not so much about the multi node features20:22
cnfwell, for this current project at home, at $dayjob is a different thing20:22
tdasilvacnf: cool! are you trying to do something like a home nas support the swift api?20:23
cnftdasilva:  yep20:23
cnfand swift is the most workable answer I found to getting an object store API going20:24
tdasilvacnf: neat...the cool play with swiftonfile for that use case, is that a lot of 'home' use cases might still use like a file access20:25
tdasilvaso you could write the data over file, and then with swift access be able to acess that data over web20:25
cnfindeed!20:25
cnfmy main goal is to share storage to family etc for backups and the like20:25
tdasilvacnf: nice, i've thought about doing something like that, a small swift cluster at home, and then having something like rackspace/ovh's public cloud for remote backup20:27
cnfright, really looks interesting20:28
cnfbut first on my list is figuring out the auth20:28
cnftdasilva:  backblaze b2 is really cheap as wel20:28
tdasilvacnf: for home, why don't you start with something simple like swauth?20:28
cnfyeah, been looking at swauth20:28
cnfbut "home" is also a test env for me20:28
cnfif I do get keystone working, I can point openstack test installs to it20:28
cnfit's a "nice to have" and not a must work, though20:29
tqtranacoles_: ping, still around?20:29
cnfthe "NAS" is an 8 core intel avaton with 32G ECC and 16T of usable storage btw20:30
cnfand I have an intel NUC as a play ESXi node as well20:30
tdasilvaheh20:30
cnfso I have some room to play :P20:30
tdasilvacnf: if you want to give SoF a quick spin, https://github.com/thiagodasilva/ansible-saio sets everything up for you20:31
tdasilvacnf: i'd like to get keystone setup on that project one day too...20:31
cnf:P20:32
cnfI got keystone working in docker atm20:32
cnfand swift mostly20:32
*** dfflanders has joined #openstack-swift20:32
tdasilvacnf: cool, have you pushed any images to docker hub?20:33
cnfnot yet, atm they are very very highly customised to my situation20:33
cnfso they need quite some cleanup20:34
cnfI can always send the files I have though20:34
*** Jeffrey4l_ has joined #openstack-swift20:34
cnfit's a multi domain setup with ldap20:34
cnfstill not entirely certain how to integrate ldap cleanly into keystone20:35
*** Jeffrey4l has quit IRC20:35
cnftdasilva:  I do plan on pushing some stuff once I get it cleaned up a bit, though20:36
tdasilvacnf: cool, i'll keep an eye out, last time i looked on docker hub there wasn't anything there20:36
cnfyeah, indeed20:36
tdasilvacnf: i keep hearing about the kolla project, but haven't had a chance to play with it tho20:37
cnfkolla project?20:37
cnfoh, https://github.com/openstack/kolla ?20:37
cnfhmm20:37
mattoliverauMorning20:38
cnfhmm, no automated builds, darn20:39
cnfhey mattoliverau20:39
cnfhmm, I also need to figure out how to get openstack stats into influxdb, and logs into graylog20:41
cnfbut later, need to get it working, first :P20:41
tdasilvacnf: yeah sorry, that's the project20:44
cnfhad not seen that before20:44
cnfi'll poke around their stuff20:44
*** sgundur has quit IRC20:46
*** sgundur has joined #openstack-swift20:46
cnfit's a good project, I think20:48
*** sgundur has quit IRC20:50
*** sgundur has joined #openstack-swift20:52
*** gyee has joined #openstack-swift20:55
*** diogogmt_ has joined #openstack-swift20:59
*** diogogmt has quit IRC21:01
*** diogogmt_ is now known as diogogmt21:01
*** sgundur has quit IRC21:11
*** sgundur has joined #openstack-swift21:11
*** sgundur has quit IRC21:20
*** sgundur has joined #openstack-swift21:23
*** dfflanders has quit IRC21:25
*** dfflanders has joined #openstack-swift21:28
*** cdelatte has quit IRC21:28
*** diogogmt has quit IRC21:44
*** sgundur has quit IRC21:44
*** mingyu has quit IRC21:44
*** mingyu has joined #openstack-swift21:47
*** nadeem has quit IRC22:01
*** mingyu has quit IRC22:03
tqtranhello all, have a question. when we are doing things such as verifying account information in keystoneauth, are we making external calls to keystone? if so, could you point me to where the code is?22:14
*** mingyu has joined #openstack-swift22:16
*** vint_bra has quit IRC22:16
*** mingyu has quit IRC22:17
mattoliverautqtran: that happens in the authtoken and keystone middleware. The first is keystones middleware and does the talkin to keystone and dumps the information into the enviromnent, then the keystone middleware does it's thing22:18
mattoliverauthat might be a bit confusing when reading back.. keystone's provided middleware is authtoken, and it talks to keystone and dumps account and group impormation into the wsgi environment, the keystoneauth middleware is ours and reads the env and makes decisions.22:22
mattoliverautqtran: ^22:22
timur_I don't know if anyone else is interested in this, but I'd like to attempt to ressurect https://review.openstack.org/#/c/196755/8. This looks like a pretty valuable thing to do with Swift. I do wonder if the database crawling approach (like suggested for metadata search) would subsume it (I can see arguments both ways), but it keeps popping up as something that Swift operators want to do22:29
patchbotpatch 196755 - swift - Add notification middleware22:29
*** timur_ is now known as timur22:30
tqtranmattoliverau: keystone provided middleware is authtoken, is that part of swift's code?22:30
tqtranright, i figured that the information was populated prior to keystoneauth since everything is already stored in environment. i was trying to figure out where/how that happens.22:31
mattoliverautqtran: its not in the swiftc code base, it comes from keystonemiddleware, a part of keystone. You can: pip install keystonemiddleware (and it probably packaged by your distro) or checkout the code locally or in github.22:33
tqtrani see, thanks for the pointer. so i guess if swift wanted to make a call directly into keystone, is that something that swift would have to implement or is it possible to somehow reuse that the keystonemiddleware to do its bidding?22:35
jrichlitimur: bkeller` has been working on a notifications patch.  It isn't ready to upload yet.  It would be good to share ideas.22:35
tqtrani guess what im trying to say is, if swift needed to do something like - a name to id lookup - what would be the best approach?22:36
timurjrichli: oh, good to know. I guess maybe we can all talk about it at the summit22:37
jrichlitimur: good plan!  we will probably have a WIP patch uploaded by then, or an ideas page on it at the least.22:38
timburketqtran: am i right to think this has to do with https://review.openstack.org/#/c/356715/ ? is the idea to let clients specify a name in the acl, then lookup the current id to actually store it?22:42
patchbotpatch 356715 - swift - Supporting Account ACL in keystoneauth22:42
*** klamath has quit IRC22:43
tqtrantimburke: yes, basing it off of what was discussed a few years ago22:45
tqtranhttps://wiki.openstack.org/wiki/Swift/ContainerACLWithKeystoneV322:45
*** rcernin has quit IRC22:50
timburketqtran: but when reading it back, clients will still be presented with ids, yeah? i'm kinda inclined to say that clients should need to specify ids, always. especially if it's a new api -- keystone users have never been able to set account acls before, right? or at least, not with any useful effect22:54
*** diogogmt has joined #openstack-swift23:06
tqtrantimburke: my current patch actually only support id. my intention is for my next patch to also allow the account owner to specify user name/domain. we then map this name/domain to an id which we store in the acl.23:07
tqtranthis way, if name changes, it doesnt matter at all.23:08
tqtranbut it does additional burden since we have to hit keystone for verification23:08
*** diogogmt has quit IRC23:09
*** jamielennox is now known as jamielennox|away23:12
*** jamielennox|away is now known as jamielennox23:13
timburke...and if they specify, say, 30 name/domain pairs, we make 30 subrequests?23:16
tqtrani guess so. its a convenience feature, maybe we can have it as an option in the conf file to disable/enable it, disabled by default. realistically, do we normally have 30 people in the acl?23:22
notmynameoh my I think I'm finally finished with defcore updates23:23
tqtranor.. maybe it can happen in the background in a separate thread? iono =/23:23
*** kei_yama has joined #openstack-swift23:27
*** arch-nemesis has quit IRC23:28
*** chsc has quit IRC23:36
*** Suyi has quit IRC23:36

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