Tuesday, 2015-06-16

*** zhill has quit IRC00:01
openstackgerritDarrell Bishop proposed openstack/swift: Allow 1+ object-servers-per-disk deployment  https://review.openstack.org/18418900:02
mattoliverauho: morning00:03
*** haomaiwa_ has joined #openstack-swift00:04
*** haomaiw__ has quit IRC00:04
homattoliverau: morning!00:07
hocharlesw: it's better to ask keystonemiddleware guys for supporting auth_region_name. in your case maybe it's a time to use federated authentication :-)00:19
*** zhill has joined #openstack-swift00:19
hoacoles: thanks for the info about swift_gap_scratchpad and torgomatic's patch :)00:21
*** breitz has quit IRC00:23
*** haomaiwa_ has quit IRC00:23
*** zhill has quit IRC00:24
*** david-lyle has quit IRC00:24
*** charlesw has joined #openstack-swift00:27
*** rcoleman has quit IRC00:30
janonymous_#openstack-dev00:30
*** dmorita has joined #openstack-swift00:31
*** CR7 has joined #openstack-swift00:42
*** haomaiwang has joined #openstack-swift01:03
hotorgomatic, all: do we have users which require this "if you want two different reseller prefixes, but the same auth system for both, you might have two instances of the auth middleware in the pipeline"?01:10
hos/which/who/01:11
hotorgomatic, all: above like come from https://etherpad.openstack.org/p/swift_gap_scratchpad01:11
*** CR7 has quit IRC01:23
mattoliverauho: yup, that's how it currently works, except for the service token stuff, which allows you _now_ to have a service prefix.01:23
*** CR7 has joined #openstack-swift01:33
*** gyee_ has quit IRC01:40
homattoliverau: thanks! but i'm not sure how to use it. for example, there are authtoken and authtokenX from same middleware in pipeline, each authtoken access to differnt keystone. is it possible?01:47
mattoliverauho: yup, you need a seperate paste config with a seperate reseller_prefix.01:51
mattoliverauho: oh you mean authtoken part01:53
*** janonymous_ has quit IRC01:57
*** kota_ has joined #openstack-swift02:04
*** ChanServ sets mode: +v kota_02:04
kota_morning (a bit later)02:04
mattoliveraukota_: morning02:04
*** charlesw has quit IRC02:06
openstackgerritTim Burke proposed openstack/python-swiftclient: Add bulkdelete command  https://review.openstack.org/19088702:07
*** david-lyle has joined #openstack-swift02:08
mattoliverauho: I think you have multiple authtoken's in your pipeline, but you need to make sure the keystone each point to have a required PublicURL that matches the keystoneauths reseller_prefix.. tho I have never tested this, this is just what I assume :)02:11
*** bkopilov has quit IRC02:28
*** amoturi has quit IRC02:31
homattoliverau: thanks! we can get info from config but the authorization methond will be overrided so I think it doesn't work as we expected. I might mis-understood torgomatic's comment I will wait his response. thanks again! :-)02:35
*** CR7 has quit IRC02:50
*** zhill has joined #openstack-swift03:03
*** zhill has quit IRC03:08
*** ianbrown has quit IRC03:08
*** ianbrown has joined #openstack-swift03:09
*** silor has joined #openstack-swift03:14
*** ppai has joined #openstack-swift03:42
* notmyname installs swift onto some real hardware...03:48
*** bkopilov has joined #openstack-swift03:49
*** kbee has joined #openstack-swift04:11
hoacoles: FYI, latest keystonemiddleware solved the torgomatic's concern (keystonemiddleware doesn't work with paste ini when there is a customized authplugin) of patch 152283.  https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L82804:11
patchbotho: https://review.openstack.org/#/c/152283/04:11
*** zhill has joined #openstack-swift04:15
*** jrichli has joined #openstack-swift04:21
*** jrichli has quit IRC04:36
*** steve_mc has joined #openstack-swift04:54
*** zhill has quit IRC05:01
*** SkyRocknRoll has joined #openstack-swift05:16
*** kbee has quit IRC05:20
*** CR7 has joined #openstack-swift05:46
*** ronenkat has joined #openstack-swift06:02
*** zhill has joined #openstack-swift06:08
*** krykowski has joined #openstack-swift06:08
openstackgerritPradeep Kumar Singh proposed openstack/python-swiftclient: SwiftClient object upload beginning with / or "./"  https://review.openstack.org/18526906:10
*** kbee has joined #openstack-swift06:43
*** ianbrown has quit IRC06:53
*** zhill has quit IRC06:55
*** mmcardle has joined #openstack-swift06:58
*** greghaynes has quit IRC07:08
*** greghaynes has joined #openstack-swift07:11
*** chlong has quit IRC07:18
openstackgerritPradeep Kumar Singh proposed openstack/python-swiftclient: SwiftClient object upload beginning with / or "./"  https://review.openstack.org/18526907:22
openstackgerritHisashi Osanai proposed openstack/swift-specs: WIP: Oslo config support in Swift  https://review.openstack.org/19209407:29
openstackgerritHisashi Osanai proposed openstack/swift-specs: WIP: Oslo config support in Swift  https://review.openstack.org/19209407:30
*** jordanP has joined #openstack-swift07:32
*** haomaiwang has quit IRC07:39
*** haomaiwang has joined #openstack-swift07:40
*** acoles_away is now known as acoles07:44
acolesjoeljwright: congrats!07:46
joeljwrightacoles: thanks :)07:48
*** CR7 has quit IRC07:51
*** ronenkat has quit IRC07:52
*** haypo has joined #openstack-swift07:58
*** geaaru has joined #openstack-swift07:58
haypohi. clayg wrote me on https://review.openstack.org/#/c/186071 that he prefers writing "StringIO()" than "six.StringIO()", so use "from six import StringIO" instead of "six"07:59
haypoin most openstack projects, the strict import rules are checked by mandatoray tests. obviously (according to swift code), it's not the case in swift08:00
haypoi'm fine with "from six import StringIO"08:00
haypodoes anyone want to slowly move to OpenStack coding style, or are you all ok with "from six import StringIO"? http://docs.openstack.org/developer/hacking/08:01
acoleshaypo: thats interesting - which rule does  "from six import StringIO" violate?08:03
haypoacoles: "Do not import objects, only modules (*)" http://docs.openstack.org/developer/hacking/#imports08:04
acoleshaypo: oic, thx08:04
haypowhen i started to develop on OpenStack, i was upset by this rule08:04
haypothen i stopped to care, i just learnt to respect it :)08:04
*** ronenkat has joined #openstack-swift08:05
haypoi don't like spending too much time to discuss coding style already decided long time ago :)08:05
haypoacoles: it's possible to configure flake8 to allow importing some objects08:06
haypoacoles: (which is also done in many projects)08:06
haypoi guess that it's easier to mock modules in unit tests, than mocking objects08:07
acolesi wasn't aware of that rule ;) imho sometimes the module prefix just makes code harder to read when used with a commonly occurring class08:08
haypoacoles: the annoying consequence is that lines are longer, so it's harder to respect the other rule: 80 columns08:09
haypobut at the end, it's not so hard to respect all these rules, you just have to be aware of them ;)08:09
acoleshaypo: yes! not so bad when the module is 'six.' but you can end up line wrapping before your code has actually done anything useful ;)08:11
haypoacoles: sometimes splitting a long line into simpler instructions make the code more readable08:11
acoleshaypo: true08:12
haypoacoles: i have no strong opinion, i will just follow the crowd :)08:12
openstackgerritHisashi Osanai proposed openstack/swift-specs: WIP: Oslo config support in Swift  https://review.openstack.org/19209408:13
acoleshaypo: so back to your original question, if you follow clayg's suggestion i would not -1, and i think there are other places in swift where we have class imports08:13
acolese.g. exceptions imports08:14
*** ianbrown has joined #openstack-swift08:22
hoacoles, torgomatic: I dumped my idea for "hybrid" oslo config support. please take a look. I will leave now because we have a foot ball game for russia world cup elimination :-)08:37
*** ho has quit IRC08:37
acolesho: ok thx. enjoy the football. go japan!08:38
*** proteusguy has joined #openstack-swift08:38
*** ronenkat has quit IRC08:55
*** chlong has joined #openstack-swift08:59
*** aix has joined #openstack-swift09:00
*** bill_az has quit IRC09:05
*** chlong has quit IRC09:07
*** chlong has joined #openstack-swift09:20
*** geaaru has quit IRC09:23
*** geaaru has joined #openstack-swift09:27
*** krykowski has quit IRC09:27
*** haomaiwang has quit IRC09:31
*** silor has quit IRC09:39
*** CR7 has joined #openstack-swift09:58
*** aix has quit IRC10:01
*** ronenkat has joined #openstack-swift10:09
*** aix has joined #openstack-swift10:12
*** proteusguy has quit IRC10:24
openstackgerritMerged openstack/swift: Replace it.next() with next(it) for py3 compat  https://review.openstack.org/19188110:27
*** haomaiwa_ has joined #openstack-swift10:28
*** kei_yama has quit IRC10:34
*** silor has joined #openstack-swift10:39
*** kbee has quit IRC10:49
eikkewhen object names are passed through inside swift code (as str's), should those be interpreted as bytes or str's (in python3-speak)?10:56
redboit'd make sense to represent them internally with str, but I'm a little afraid that byte-str-byte roundtripping won't always end up back at the same place.11:11
*** ronenkat has quit IRC11:19
redbowell.. I guess we already make sure that object names can round-trip encode to themselves in check_utf8.11:24
eikkeand swift expects object names with non-ascii unicode chars in them to be utf8-encoded in their URL?11:26
redboyeah, object names have to be valid utf-811:27
redboit has to satisfy name == name.decode('utf-8').encode('utf-8'), no nul characters, and no unicode surrogates11:31
eikkethen, in for example DiskFileManager, is the 'obj' argument of get_diskfile a bytestring (using whatever encoding), or something that should be encoded into bytes later on?11:36
*** CR7 has quit IRC11:45
*** kota_ has quit IRC11:46
*** ronenkat has joined #openstack-swift11:48
*** ronenkat has quit IRC12:03
*** CR7 has joined #openstack-swift12:05
*** ronenkat has joined #openstack-swift12:16
*** km has quit IRC12:21
openstackgerritVictor Stinner proposed openstack/swift: Replace xrange() with six.moves.xrange()  https://review.openstack.org/18546012:22
*** MooingLemur has quit IRC12:22
*** janonymous_ has joined #openstack-swift12:29
*** bkopilov has quit IRC12:33
*** theanalyst has left #openstack-swift12:38
openstackgerritVictor Stinner proposed openstack/swift: Get StringIO and cStringIO from six.moves  https://review.openstack.org/18545712:39
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO for WSGI input  https://review.openstack.org/18607112:39
*** CR7 has quit IRC12:43
*** NM has joined #openstack-swift12:45
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO in ssync  https://review.openstack.org/18607312:47
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO for file  https://review.openstack.org/18607212:47
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO in ssync  https://review.openstack.org/18607312:54
openstackgerritVictor Stinner proposed openstack/swift: Replace StringIO with BytesIO for file  https://review.openstack.org/18607212:54
tdasilvagood morning12:54
*** proteusguy has joined #openstack-swift12:58
*** ianbrown has quit IRC12:59
*** MooingLemur has joined #openstack-swift13:00
*** ronenkat has quit IRC13:02
*** proteusguy has quit IRC13:02
*** petertr7_away is now known as petertr713:08
*** proteusguy has joined #openstack-swift13:13
openstackgerritRomain LE DISEZ proposed openstack/swift: Allows the replicator to rsync to a device-based module  https://review.openstack.org/19218613:15
*** erlon has joined #openstack-swift13:17
*** proteusguy has quit IRC13:19
*** proteusguy has joined #openstack-swift13:20
*** mahatic has joined #openstack-swift13:22
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873613:24
*** geaaru has quit IRC13:25
*** proteusguy has quit IRC13:26
*** SkyRocknRoll has quit IRC13:26
*** proteusguy has joined #openstack-swift13:29
*** erlon has left #openstack-swift13:30
*** fanyaohong has joined #openstack-swift13:33
*** proteusguy has quit IRC13:33
openstackgerritOndrej Novy proposed openstack/swift: Rsync port in ring file.  https://review.openstack.org/19219813:34
*** amoturi has joined #openstack-swift13:34
pelusemattoliverau, please have a look at my reply to your comments on https://review.openstack.org/#/c/191521/ when you can.  We can't run a real cluster with any real EC recon work without this one13:36
mattoliveraupeluse: thanks for the explanation. Removed my -1, will reexamine (if it hasn't merged) in the morning when I'm awake :)13:46
*** petertr7 is now known as petertr7_away13:49
pelusemattoliverau, cool, thanks man!13:49
*** acampbell has joined #openstack-swift13:50
*** kbee has joined #openstack-swift13:52
*** petertr7_away is now known as petertr713:58
*** blmartin has joined #openstack-swift14:00
*** ronenkat has joined #openstack-swift14:00
*** janonymous_ has quit IRC14:04
*** si1v3r has quit IRC14:05
*** bkopilov has joined #openstack-swift14:09
*** ppai has quit IRC14:10
*** kbee has quit IRC14:11
*** barker has joined #openstack-swift14:12
*** proteusguy has joined #openstack-swift14:14
*** proteusguy has quit IRC14:15
*** wbhuber has joined #openstack-swift14:17
*** bkopilov has quit IRC14:19
*** bkopilov has joined #openstack-swift14:31
*** barker has quit IRC14:31
*** jrichli has joined #openstack-swift14:32
*** ajiang has left #openstack-swift14:33
*** proteusguy has joined #openstack-swift14:38
*** vinsh has joined #openstack-swift14:42
*** minwoob has joined #openstack-swift14:45
*** blmartin_ has joined #openstack-swift14:48
*** blmartin has quit IRC14:48
*** jith_ has joined #openstack-swift14:53
*** si1v3r has joined #openstack-swift14:54
jith_hi all, i have installed swift (SAIO) in one VM.. i have to connect this with another devstack machine.. how to connect the standalone swift with another devstack machine.. should i create swift endpoint using swift vm's ip??14:54
*** ronenkat has quit IRC14:54
*** wbhuber has quit IRC14:56
*** barker has joined #openstack-swift14:56
*** barker has quit IRC14:56
*** wbhuber has joined #openstack-swift14:58
*** barker has joined #openstack-swift15:00
*** barker has quit IRC15:02
*** wbhuber has quit IRC15:04
*** esker has joined #openstack-swift15:07
*** lpabon has joined #openstack-swift15:08
*** wbhuber has joined #openstack-swift15:12
*** barker has joined #openstack-swift15:20
*** wbhuber has quit IRC15:27
*** wbhuber has joined #openstack-swift15:27
*** fanyaohong has quit IRC15:35
notmynamegood morning15:36
notmynamejrichli: acoles: I'm going to a meetup tonight about https://hashicorp.com/blog/vault.html. anything I should pay close attention to wrt encryption/keymanager in swift?15:37
notmynamepeluse: did you see the questions yesterday about pyeclib packaging from zigo?15:37
zigopeluse: Are you able to make a new release for pyeclib? 1.0.7m still has an egg-info with 1.0.5 in it, which makes it not useable for swift 2.3.0.15:38
zigoIt's currently a blocker for me...15:38
*** kbee has joined #openstack-swift15:39
jrichlinotmyname: Thanks for asking.  I will have a reply with some thoughts soon15:40
notmynamebah! I'm mad at myself for dropping the ball on the patch chain for six/py3. I wanted the ec fix to land first so we could cut a release with it before adding the new dependency15:41
notmynameoh well, my fault. it can be worked around15:41
*** barker has quit IRC15:45
*** janonymous_ has joined #openstack-swift15:48
*** barker has joined #openstack-swift15:48
*** barker has quit IRC15:49
*** vinsh has quit IRC15:52
*** ppai has joined #openstack-swift15:53
*** fthiagogv has joined #openstack-swift15:58
*** haypo has quit IRC16:06
*** barker has joined #openstack-swift16:06
*** petertr7 is now known as petertr7_away16:11
*** esker has quit IRC16:16
*** mfalatic has quit IRC16:21
*** zhill has joined #openstack-swift16:22
openstackgerritOndrej Novy proposed openstack/swift: Rsync port in ring file.  https://review.openstack.org/19219816:24
swifterdarrellzigo: not sure if it helps you, but we worked around the incorrect version string at the 1.0.7m tag by patching the source during packaging16:24
*** lpabon has quit IRC16:25
zigoswifterdarrell: I'd prefer not to, the version 1.0.7 which is used in the gate has more commits than version 1.0.7m, which seems wrong to me, and dangerous (packaging something which we don't gate with may lead to issues).16:25
*** mahatic has quit IRC16:25
swifterdarrellzigo: *nod* waiting for upstream is always an option :)16:26
swifterdarrellzigo: peluse: now that the gate servers have liberasurecode + jerasure, we can get a PyECLib 1.0.8 that's suitable for PyPi AND for packagers (and thus no 1.0.8m).16:28
swifterdarrellzigo: peluse: (haha, that was supposed to be a question or to include "hopefully")16:29
*** amoturi has quit IRC16:34
*** NM has quit IRC16:40
*** NM has joined #openstack-swift16:44
*** mfalatic has joined #openstack-swift16:47
jrichlinotmyname: some things that would be good to see in Vault would be support for multiple KMIP servers and multiple HSMs (multi-tenant for both)16:48
jrichliwould like if clients can have direct access, but that access can be restricted to their tenant16:48
jrichlibacked by mySQL, ... plans to work with Castellan interface16:49
notmynamegood info16:50
* notmyname finds some place to write that down16:50
notmynameI highly doubt they are going to work with castellan. or if there is some way to work together, it's probably on us in the openstack community to do that16:52
jrichlimakes sense16:52
*** petertr7_away is now known as petertr717:03
*** haomaiwa_ has quit IRC17:04
*** mmcardle has quit IRC17:04
*** ronenkat has joined #openstack-swift17:05
acolesnotmyname: be interesting if they have any performance figures for querys/sec to retrieve secrets17:06
*** proteusguy has quit IRC17:08
*** ppai has quit IRC17:10
*** haomaiwa_ has joined #openstack-swift17:13
*** jordanP has quit IRC17:15
*** vinsh has joined #openstack-swift17:19
peluseswifterdarrell, yeah for sure!  I'll ping tsg and see if its ready17:19
*** zhill has quit IRC17:22
pelusenotmyname, I was offline most of yesterdat so missed the pyeclib questions - just shot a note to tsg and keving though.  Will provide update later today (or one of them may jump on)17:22
*** nadeem has joined #openstack-swift17:22
*** proteusguy has joined #openstack-swift17:24
*** gyee has quit IRC17:24
*** acoles is now known as acoles_away17:25
*** proteusguy has quit IRC17:25
*** gyee has joined #openstack-swift17:26
*** proteusguy has joined #openstack-swift17:29
notmynameI'm not sure what to do with ho's oslo config patches. in general, I'm fairly worried about that kind of change because of the amount of code change or the amount of maintenance burden going forward17:32
*** aix has quit IRC17:37
tdasilvaswifterdarrell, notmyname: are you able to choose a SP when running ssbench, or do you just set the default policy to what you want to test?17:37
notmynametdasilva: I've got a pull request that allows for that17:38
notmynametdasilva: https://github.com/swiftstack/ssbench/pull/10717:38
tdasilvanotmyname: cool! will check it out17:38
tdasilvanotmyname: cschwede might have mentioned to you in vancouver that we were planning to do some EC testing17:39
notmynametdasilva: ah? good to know17:39
tdasilvawe are finishing getting a small cluster ready17:39
notmynametdasilva: most of my testing here is wrapping up. I have some raw numbers (like I shared in vancouver) but I need to turn them in to something interesting to look at17:40
tdasilvanotmyname: cool, I downloaded that tar you had posted before the summit, so i'm trying to test with those scenarios17:40
notmynametdasilva: great17:40
notmynametdasilva: note that you need 3 patches to the last release before doing EC testing17:41
notmyname2 are already on master. the third is https://review.openstack.org/#/c/191521/17:41
notmynameand that one needs to land asap so we can make another swift release17:41
tdasilvacool, will take a look17:42
*** barker has quit IRC17:47
*** minwoob has quit IRC17:58
*** proteusguy has quit IRC17:59
*** marzif_ has joined #openstack-swift18:00
*** zhill has joined #openstack-swift18:00
*** marzif has quit IRC18:01
*** barker has joined #openstack-swift18:01
*** proteusguy has joined #openstack-swift18:05
*** jasondotstar has joined #openstack-swift18:07
*** mahatic has joined #openstack-swift18:09
*** ajiang has joined #openstack-swift18:13
*** amoturi has joined #openstack-swift18:14
*** barker has quit IRC18:16
*** barker has joined #openstack-swift18:18
*** ronenkat_ has joined #openstack-swift18:32
*** janonymous_ has quit IRC18:33
*** ronenkat has quit IRC18:34
*** ronenkat has joined #openstack-swift18:35
*** marzif has joined #openstack-swift18:36
*** ronenkat_ has quit IRC18:38
*** silor1 has joined #openstack-swift18:49
*** silor has quit IRC18:51
*** tab__ has joined #openstack-swift18:59
*** mfalatic has quit IRC19:00
*** barker has quit IRC19:03
*** barker has joined #openstack-swift19:04
*** barker has quit IRC19:08
*** mahatic has quit IRC19:13
*** mahatic has joined #openstack-swift19:16
*** mahatic has quit IRC19:25
*** harlowja has quit IRC19:25
*** kbee has quit IRC19:41
*** thurloat_isgone is now known as thurloat19:48
*** silor1 has quit IRC19:48
hurricanerix_notmyname: You said you wanted a update on hummingbird tomorrow, right?  Is there any specific stuff you are wanting, or just general info on what we are finding with it?20:02
*** petertr7 is now known as petertr7_away20:08
*** ronenkat has quit IRC20:08
*** acampbell has quit IRC20:12
sweeper"we have found that go is awesome and any fault in developing a swift server in go is entirely ours" >.>20:13
notmynamehurricanerix_: general info about what's going on, what you're finding, and, ultimately, any plans you have for some comparative test results20:13
hurricanerix_notmyname: ok thanks20:15
swifterdarrellnotmyname: clayg: acoles_away: cschwede: tdasilva: can someone give some review-juice to https://review.openstack.org/#/c/191970/ ?20:20
notmynamepeluse: kota_: mattoliverau: redbo: glange: dfg_: zaitcev: ^20:21
swifterdarrellnotmyname: dammit, i can never remember the full set20:22
zaitcevthat's approach "uno", right?20:22
swifterdarrellzaitcev: ya20:23
openstackgerritMerged openstack/swift: go: limit replication per disk  https://review.openstack.org/19034020:23
*** petertr7_away is now known as petertr720:31
*** vinsh has quit IRC20:37
*** fthiagogv has quit IRC20:42
*** esker has joined #openstack-swift20:51
*** mfalatic has joined #openstack-swift20:53
*** tab__ has quit IRC20:56
*** blmartin_ has quit IRC20:59
*** petertr7 is now known as petertr7_away21:06
*** harlowja has joined #openstack-swift21:13
*** marzif has quit IRC21:13
*** amoturi has quit IRC21:17
*** joeljwright has quit IRC21:24
*** esker has quit IRC21:29
*** joeljwright has joined #openstack-swift21:31
*** ChanServ sets mode: +v joeljwright21:31
*** wbhuber has quit IRC21:40
*** ianbrown has joined #openstack-swift21:44
*** asettle has joined #openstack-swift21:58
*** harlowja has quit IRC22:00
*** harlowja has joined #openstack-swift22:02
*** jrichli has quit IRC22:10
*** joeljwright has quit IRC22:23
*** NM has quit IRC22:26
*** asettle is now known as asettle-afk22:35
*** openstackgerrit has quit IRC22:38
*** openstackgerrit has joined #openstack-swift22:38
mattoliverauMorning22:40
torgomatichi22:43
*** km has joined #openstack-swift23:05
*** chlong has quit IRC23:15
*** kei_yama has joined #openstack-swift23:20
*** zhill has quit IRC23:25
*** pgbridge has joined #openstack-swift23:36
*** zhill has joined #openstack-swift23:37
*** asettle-afk is now known as asettle23:38
*** zhill has quit IRC23:42
*** pgbridge has quit IRC23:49
*** pgbridge has joined #openstack-swift23:49
*** Kennan2 is now known as Kennan23:51
*** jrichli has joined #openstack-swift23:51
* notmyname waits for ho to log on...23:52
*** ho has joined #openstack-swift23:55
hogood morning guys!23:56
notmynameit's ho!23:56
notmynameho: I've been waiting for you to log on :-)23:56
notmynameho: got your coffee/tea? I want to talk to you about oslo config23:56
honotmyname: hello, i have it already :-)23:57
notmynameok23:57
notmynameso adding oslo config to swift worries me. beyond the other reasons listed in the etherpad, it means that we'd now have 2 config systems that we'd have to support forever and it adds a lot of complexity for deployers23:58
notmynameso why is oslo config required for the change you are wanting to make23:58
notmyname(to be clear, I'm not opposed to the policy.json stuff. I like that)23:58
*** petertr7_away is now known as petertr723:59
honotmyname: when I use oslo policy for policy.json support, oslo policy reqires oslo config. it's one reason.23:59

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