*** ChanServ has quit IRC | 15:34 | |
*** patchbot has quit IRC | 15:34 | |
*** notmyname has quit IRC | 15:34 | |
*** kota_ has quit IRC | 15:34 | |
*** mattoliverau has quit IRC | 15:35 | |
*** hrou has quit IRC | 15:35 | |
*** cschwede has quit IRC | 15:35 | |
*** alpha_ori has quit IRC | 15:35 | |
*** clayg has quit IRC | 15:35 | |
*** tdasilva has quit IRC | 15:35 | |
*** gmmaha has quit IRC | 15:35 | |
*** timburke has quit IRC | 15:35 | |
*** clayg has joined #swift3 | 15:37 | |
*** patchbot has joined #swift3 | 15:39 | |
*** notmyname has joined #swift3 | 15:39 | |
*** kota_ has joined #swift3 | 15:39 | |
*** timburke has joined #swift3 | 15:40 | |
*** hrou has joined #swift3 | 15:41 | |
*** gmmaha has joined #swift3 | 15:41 | |
*** tdasilva has joined #swift3 | 15:42 | |
*** hrou has quit IRC | 15:52 | |
*** gmmaha has quit IRC | 15:52 | |
*** mattoliverau has joined #swift3 | 15:59 | |
*** cschwede has joined #swift3 | 15:59 | |
*** alpha_ori has joined #swift3 | 15:59 | |
*** mattoliverau has quit IRC | 16:09 | |
*** cschwede has quit IRC | 16:09 | |
*** alpha_ori has quit IRC | 16:09 | |
*** gmmaha has joined #swift3 | 16:34 | |
*** hrou has joined #swift3 | 16:34 | |
*** mattoliverau has joined #swift3 | 16:34 | |
*** cschwede has joined #swift3 | 16:34 | |
*** alpha_ori has joined #swift3 | 16:34 | |
*** mattoliverau has quit IRC | 16:45 | |
*** cschwede has quit IRC | 16:45 | |
*** alpha_ori has quit IRC | 16:45 | |
*** hrou has quit IRC | 16:45 | |
*** gmmaha has quit IRC | 16:45 | |
*** alpha_ori has joined #swift3 | 16:46 | |
*** cschwede has joined #swift3 | 16:46 | |
*** mattoliverau has joined #swift3 | 16:46 | |
*** hrou has joined #swift3 | 16:46 | |
*** gmmaha has joined #swift3 | 16:46 | |
*** ChanServ has joined #swift3 | 17:04 | |
*** wolfe.freenode.net sets mode: +o ChanServ | 17:04 | |
*** siva_krishnan has joined #swift3 | 21:36 | |
*** lyrrad has joined #swift3 | 22:51 | |
timburke | meeting time? | 22:59 |
---|---|---|
kota_ | yup | 22:59 |
kota_ | who is here, today? | 22:59 |
lyrrad | I’m here. | 23:00 |
kota_ | lyrrad: hello :) | 23:01 |
kota_ | i expect someone from OIC want to attend...but doesn't look here | 23:01 |
kota_ | anyways, let's getting to start from available items | 23:02 |
lyrrad | Hmm.. the meeting time may be confusing on the wiki, it says 16:00 PDT, which is technically correct, but we switched back to Standard time last month. I’ll fix it. | 23:03 |
kota_ | oic | 23:03 |
kota_ | it's complicated in the timezone it has daylight saving... | 23:04 |
kota_ | i'll care the time expression on wiki since next meeting, thx | 23:05 |
kota_ | so | 23:05 |
kota_ | move on agendas | 23:05 |
kota_ | or, waiting someone might join? | 23:06 |
timburke | i leave it up to you | 23:07 |
kota_ | ok, let's start right now today because we can share the log if someone wants. | 23:09 |
kota_ | and i don't have so much time today for this, sorry. | 23:10 |
kota_ | so first one | 23:10 |
kota_ | security patch | 23:10 |
kota_ | I confirmed the patch worked well and it seems to be ready to land intu upstream. | 23:11 |
kota_ | into | 23:11 |
kota_ | and i made sure with notmyname about the process | 23:11 |
kota_ | from the process, i am planning to push it to gerrit with co-authed-by lyrrad and add +2 +A immediately. | 23:12 |
kota_ | i'll do that in this week | 23:12 |
timburke | sounds good. i know we'd talked about cutting a new release following that patch; is that still planned? | 23:13 |
kota_ | a point I mind a bit is whether or not we need "security impact" tag in committ message. | 23:13 |
kota_ | yup, I'm willing to propose a new release. | 23:14 |
lyrrad | It certainly seems like it could cause some security problems, depending on the clients that users are using. Do we have guidance on what qualifies for the security impact tag? | 23:15 |
kota_ | the security impact tag seems to used to notify the fix openstack security team | 23:15 |
kota_ | ah... I am missing the online docs right now. | 23:17 |
timburke | https://security.openstack.org/vmt-process.html maybe? | 23:17 |
kota_ | yup, but it doesn't suggest that we should use that tag for security issue. | 23:19 |
lyrrad | Presumably the security team would have been notified back in September when the launchpad bug was filed. | 23:19 |
lyrrad | I guess we could contact a member directly: https://launchpad.net/~openstack-vuln-mgmt/+members | 23:20 |
lyrrad | https://security.openstack.org/ suggests contacting Stanley, Cacqueray or Murphy. | 23:22 |
kota_ | oh, ok | 23:23 |
kota_ | the docs looks helpful to manage this | 23:23 |
kota_ | thanks! | 23:24 |
kota_ | k, let's move on next topic | 23:25 |
kota_ | OSIC works? | 23:25 |
kota_ | no one from OSIC still be here. | 23:26 |
kota_ | s/be/seems to be/ | 23:27 |
timburke | i'm not entirely sure what they're looking for, but maybe the non-ascii metadata would be a decent place for them to start? it should hopefully be a fairly small piece of work... | 23:27 |
kota_ | ic | 23:28 |
kota_ | sounds good idea. | 23:28 |
timburke | CORS or object POST would be nice, but probably more involved | 23:28 |
kota_ | timburke: heh, actually i want the work but exactly it will be a big ones. | 23:30 |
kota_ | or fixing small patches which conflict curent master(but still exist in gerrit) ? | 23:32 |
kota_ | either is fine to me tho. | 23:32 |
timburke | oh, good idea! patch 155221 would be good | 23:33 |
patchbot | timburke: https://review.openstack.org/#/c/155221/ - Fix Delete Multiple Objects process when multipart... | 23:33 |
kota_ | :-) | 23:33 |
timburke | i meant to circle back to that after reviving 155199 | 23:34 |
timburke | er, patch 155199 | 23:34 |
patchbot | timburke: https://review.openstack.org/#/c/155199/ - Fix DELETE Object to delete segments when it is mu... (MERGED) | 23:34 |
kota_ | yup | 23:35 |
kota_ | anyways, we could have some items to suggest when they're looking for | 23:36 |
kota_ | could we move on next? | 23:36 |
timburke | sounds good. recent updates! | 23:36 |
kota_ | timburke, lyrrad: do you have something? | 23:37 |
timburke | patch 248178 allows multipart DELETEs to work properly when using the aws-sdk-java library (which inserts a Content-Type: application/x-www-form-urlencoded header on DELETE). a related change to Swift (patch 248186) already landed, but if we fix swift3, operators won't have to upgrade swift to get the fix | 23:37 |
patchbot | timburke: https://review.openstack.org/#/c/248178/ - Ignore Content-Type from client when deleting mult... | 23:37 |
patchbot | timburke: https://review.openstack.org/#/c/248186/ - Ignore Content-Type from client on multipart-manif... (MERGED) | 23:37 |
lyrrad | I made the s3compat project public last week. No updates other than that though. | 23:39 |
kota_ | timburke: looks good from my quick view, i'll take a time to test that, thanks1 | 23:40 |
kota_ | lyrrad: ok | 23:40 |
kota_ | from me, nothing except i am working on the security patch discussed as a first topic. | 23:41 |
*** siva_krishnan has quit IRC | 23:42 | |
kota_ | as a coclusion, I have some homework about security patch, version bump, multi-delete...etc | 23:43 |
timburke | sounds good. thanks for your work there! i know there's a lot of policy/procedure stuff to dig through | 23:43 |
kota_ | I also appreciate you all work for swift3 well | 23:44 |
kota_ | thanks for working swift3, I expect we will have next meeting at 16th Dec. | 23:45 |
kota_ | thanks | 23:45 |
timburke | thanks kota_! enjoy the rest of your morning :) | 23:45 |
lyrrad | Bye! | 23:45 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!