*** m_kazuhiro has joined #swift3 | 00:50 | |
*** m_kazuhiro has quit IRC | 04:03 | |
*** m_kazuhiro has joined #swift3 | 04:08 | |
openstackgerrit | Tim Burke proposed openstack/swift3: Update pep8 config to (mostly) match upstream swift https://review.openstack.org/336879 | 05:08 |
---|---|---|
openstackgerrit | Tim Burke proposed openstack/swift3: Update pep8 config to (mostly) match upstream swift https://review.openstack.org/336879 | 05:24 |
*** acoles_ is now known as acoles | 09:09 | |
*** m_kazuhiro has quit IRC | 09:59 | |
*** chsc has joined #swift3 | 14:47 | |
*** chsc has quit IRC | 14:47 | |
*** chsc has joined #swift3 | 14:47 | |
*** acoles is now known as acoles_ | 17:14 | |
*** acoles_ is now known as acoles | 20:58 | |
*** acoles is now known as acoles_ | 21:37 | |
kota_ | hello | 23:02 |
*** chsc has quit IRC | 23:07 | |
kota_ | timburke: ping | 23:12 |
timburke | hi kota_! | 23:15 |
kota_ | hello timburke! | 23:15 |
kota_ | coul you have a time to talk? | 23:16 |
timburke | absolutely | 23:16 |
kota_ | ok, let's get started | 23:16 |
kota_ | Last night, I updated a few things on https://wiki.openstack.org/wiki/Meetings/swift3 | 23:17 |
timburke | i just read it | 23:18 |
kota_ | for the first item, I merged some follow up for sigv4 recently. | 23:18 |
kota_ | and saw some patches updated from you. | 23:18 |
kota_ | but probably I didn't look at for all yet. that's my current status for now. | 23:19 |
timburke | thanks! i think there's still one more sigv4 follow-up i'd like to see before a release -- https://review.openstack.org/#/c/330888/ | 23:19 |
patchbot | timburke: patch 330888 - swift3 - Stop using email.utils.mktime_tz | 23:19 |
kota_ | but I think, the followup for sigv4 specific items all done, right? | 23:19 |
kota_ | oh, one more. | 23:20 |
kota_ | ok, gotcha. sigv4 patch includes some changes around timestmp handling | 23:20 |
kota_ | that seems related to. | 23:20 |
timburke | but i'm getting ahead of myself a little. i merged in some test cleanup (assertEquals -> assertEqual) and submitted a patch to keep it that way -- https://review.openstack.org/#/c/336879/ | 23:21 |
patchbot | timburke: patch 336879 - swift3 - Update pep8 config to (mostly) match upstream swift | 23:21 |
kota_ | oh, yeah. the change since my last commented is just updating hacking requirement? | 23:22 |
kota_ | looking at... | 23:22 |
timburke | yep | 23:22 |
kota_ | timburke: one question | 23:23 |
timburke | but i think that's been most of what i've been working on. there are some more patches i need to circle around on; in particular i still want to get us using headers_raw if it's available, and i need to look at how AWS responds to various requests with no body | 23:23 |
kota_ | the hacking requirement looks different from current swift master's one, why is it? | 23:24 |
kota_ | swift says hacking>=0.10.0,<0.11 | 23:24 |
timburke | global-requirements updated. i figured it was better to follow them (although i suppose we don't seem to have a requirements gate job...) | 23:24 |
kota_ | yep, headers_raw one seems good to save us. | 23:24 |
timburke | https://github.com/openstack/requirements/blob/master/global-requirements.txt#L369 | 23:25 |
kota_ | ah, ok. that one is that swift has been shutdown to merge for so long long time. | 23:26 |
timburke | yeah. we keep picking up the occasional up-rev, but i don't know when the last time would've been that swift accepted a bot-initiated update to requirements | 23:27 |
kota_ | https://review.openstack.org/88736 | 23:29 |
kota_ | it looks like since 2014 | 23:29 |
timburke | so "before my time" ;-) | 23:29 |
notmyname | mostly we're trying to set the all-time record for most patch sets to a single review | 23:29 |
kota_ | hehe | 23:30 |
kota_ | it takes more than 450 patch set. | 23:30 |
notmyname | but if we keep going, nobody will be able to catch up! | 23:31 |
timburke | notmyname: hey, we've gotta stress -infra somehow! | 23:31 |
timburke | thanks kota_! | 23:32 |
kota_ | anyway, the patch 336879 looks reasonable enough, so i pushed my +2 +A right now :) | 23:32 |
patchbot | kota_: https://review.openstack.org/#/c/336879/ - swift3 - Update pep8 config to (mostly) match upstream swift | 23:32 |
timburke | i saw :) | 23:33 |
kota_ | and ok, we will make a release after timestamp one get merged. | 23:33 |
kota_ | those are most of today's meeting, i think. | 23:34 |
kota_ | can i move to the next one, or any updates for looking at? | 23:34 |
timburke | seems good to me. i'll take a look at the patch you submitted recently, too | 23:35 |
kota_ | thanks :) | 23:36 |
kota_ | speaking of the next item, for barcelona i mean. | 23:36 |
timburke | ah, yes! sorry i hadn't gotten back to you about that yet | 23:37 |
kota_ | Did you see my E-mail for barcelna topic? | 23:37 |
kota_ | no worries. | 23:37 |
kota_ | but we are now getting to close to the deadline :P | 23:37 |
timburke | i think there are definitely some worthwhile topics we could bring up, and i'd be happy to help with it | 23:37 |
timburke | indeed | 23:37 |
kota_ | i think, bill_az has great look for topic what we should bring to there. | 23:38 |
timburke | i might also get some opinions from doug soltesz here at swiftstack; he's done a good bit of integrating ISVs with swift through swift3 | 23:39 |
kota_ | so rough scketch of the presentation scenario is swift3 (ans swift, s3) overview -> API compatibility -> story ? | 23:39 |
kota_ | story means usecase. | 23:39 |
kota_ | oh, yeah. sounds great. | 23:40 |
timburke | yeah, i definitely want to highlight some customer stories | 23:40 |
timburke | and how the work that we've done for swift3 has led to broader improvements in swift (like concurrent bulk deletes) | 23:41 |
kota_ | absolutely, that's what I mostly prefer on swift3 :) | 23:41 |
kota_ | does doug also want to talk there? | 23:43 |
timburke | i get the impression doug always wants to give presentations :-) | 23:43 |
kota_ | ok | 23:43 |
openstackgerrit | Merged openstack/swift3: Update pep8 config to (mostly) match upstream swift https://review.openstack.org/336879 | 23:43 |
kota_ | I'm not sure for now for the submit limitation. | 23:44 |
kota_ | thank you patch bot | 23:44 |
kota_ | yesterday I sounds someone said the speaker limtited to 3 | 23:44 |
kota_ | but I'm wondering I attended panel session at vancouver summit as 1 of 6 or 7 people??? | 23:45 |
timburke | looks like presentations can have up to 3 speakers, and panels 4 speakers + 1 moderator | 23:45 |
timburke | ...where we probably took some liberties with the "moderator" title | 23:46 |
kota_ | exactly | 23:47 |
timburke | with the three speaker limit in mind, we probably shouldn't include doug (he'll find some talks to do i'm sure :) though i'll probably still get some feedback from him | 23:47 |
kota_ | ok, thanks. | 23:48 |
kota_ | so speaking of schedule, I'm willing to draft of abstraction in this week and we could submit in the next week during hackathon? | 23:49 |
timburke | sounds good! | 23:50 |
kota_ | if you could send me something which you wnat to include specifically as a content, it will be great to help me to write it ;-) | 23:51 |
kota_ | that's all for today from me | 23:53 |
timburke | thanks kota_! me too | 23:53 |
kota_ | timburke: thanks for joining :) | 23:54 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!