Wednesday, 2018-05-09

*** mingyu has quit IRC00:05
*** bkopilov__ has joined #openstack-swift00:06
*** bkopilov_ has joined #openstack-swift00:06
*** mingyu has joined #openstack-swift00:09
*** mingyu has quit IRC00:11
*** gyee has quit IRC00:36
spsuryaDHE: Will the swift work with only storage node installation ?00:50
spsuryahttps://docs.openstack.org/swift/latest/install/storage-install-ubuntu-debian.html00:50
DHEspsurya: you really need at least one of each component... account, container, object, and proxy. and the 3 storage types are really intended to have at least 3 drives each for replica purposes.00:51
spsuryaDHE: so i think i can have all on one storage node itself00:54
spsuryaright ?00:54
DHEwell, yes, that's sorta what SAIO is about00:55
DHEbut thtat's more intended for testing and experimentation. swift is designed as the no-single-point-of-failure object storage00:56
spsuryaDHE: yeah i am using for experiment only00:57
spsuryabut i cant't see about the configuration for swift-proxy  on storage node00:59
DHEyou don't really. the proxy reads the ring file, sees what hosts are listed in it, and connects to them as needed01:00
DHEproxy server usually doesn't require much configuration beyond authentication info01:00
spsuryaso `apt-get install swift swift-account swift-container swift-object` can be run as `apt-get install swift swift-account swift-container swift-object swift-proxy`01:01
spsuryaDHE:01:02
DHEthe install guide puts swift's proxy server onto the "openstack controller" node (the one they suggest running keystone on, etc) and puts the storage stuff onto a different, presumably dedicated, storage machine01:02
DHEin reality these are 4 largely independent services. you can spread them out as you see fit. for example the account and container servers might do well on SSDs01:03
spsuryaDHE: i won't use auth as swift provide this facility too, I would be going with SAIO installation, then my motive is to add new node into that01:10
spsuryai.e swift installed with SAIO and then woud be addiing new node01:11
mattoliverau^what DHE says :) You can  put it all on one server (for testing as as DHE points out you don't have much reduncancy). But you must that more devices (disks) then replicas. All the rings can point to the same devices. So long as there are enough devices for the max number of replicas in all the rings. ie. if the account container and object rings are all 3 replicas you'd need at least 3 devices.01:11
mattoliverauthey are all daemons, but the storage nodes need access to drives. The proxy doesn't so it can live whereever.01:12
mattoliveraumany small clusters might use PACO (that is proxy, account, container and object) services on all nodes.01:12
mattoliverauas the IO grows or the number of connections, you might think about splitting the proxy off so P-ACO01:13
mattoliveraumost io will be on the object services, and will probably hold like 99% of the data, so larger clusters tend to seperate that off so either P-AC-O or I've seen PAC-O01:14
mattoliverauSwift can handle it's own auth. tmpauth shouldn't be used in production, but fine if your just testing.01:14
mattoliverauothers to look at are obviously keystone or swauth. Or roll your own :)01:15
*** armaan has quit IRC01:15
*** armaan has joined #openstack-swift01:16
mattoliverauMany openstack deployments will move the proxy to the controller nodes, as it's really the external api to the cluster, and is just a daemon.. that needs access to rings. So rings need to be copied to every storage node and proxy server.01:16
*** ianychoi has joined #openstack-swift01:21
*** username_ has joined #openstack-swift01:23
*** username_ is now known as username__01:23
spsuryaDHE: mattoliverau thanks a lot01:23
spsuryafor explanation01:24
mattoliverauDHE: thanks for all your help lately in channel! where abouts you located? Cause you seem to share a similar timezone to me :)02:04
DHEsouthern ontario02:05
*** psachin` has joined #openstack-swift02:10
mattoliverauDHE: oh cool.. so not really the same timezone then, your just a night owl ;) Will you be coming to the summit in Vancouver seeing as it's over in your neck of the woods?02:12
*** psachin` has quit IRC02:26
*** m_kazuhiro has joined #openstack-swift02:29
m_kazuhirogood morning02:29
*** username__ has quit IRC02:35
mattoliveraum_kazuhiro: mornign02:39
mattoliverau*morning02:39
*** psachin has joined #openstack-swift02:42
m_kazuhiromattoliverau: morning :)02:42
mattoliveraum_kazuhiro: sorry I haven't had a chance to look at your patches, been crazy busy, but I promise to get to them when I get a chance, which might not be till after all the sharding reviews02:43
m_kazuhiromattoliverau: That's ok. Our current important task is sharding review :)02:46
*** rcernin has quit IRC03:14
kota_good morning03:19
*** klamath has quit IRC03:35
*** threestrands has joined #openstack-swift03:38
*** links has joined #openstack-swift03:42
*** gyan_ has joined #openstack-swift03:44
*** m_kazuhiro_ has joined #openstack-swift03:45
*** m_kazuhiro has quit IRC03:47
*** klamath has joined #openstack-swift03:50
*** cshastri has joined #openstack-swift04:00
*** klamath has quit IRC04:27
*** klamath has joined #openstack-swift05:00
*** klamath has quit IRC05:12
*** klamath has joined #openstack-swift05:28
*** klamath has quit IRC05:32
*** hoonetorg has quit IRC05:33
*** hoonetorg has joined #openstack-swift05:44
*** threestrands has quit IRC05:54
*** geaaru has quit IRC05:56
*** pcaruana has joined #openstack-swift05:57
*** armaan has quit IRC06:05
*** armaan has joined #openstack-swift06:05
*** armaan_ has joined #openstack-swift06:13
*** armaan has quit IRC06:16
*** cbartz has joined #openstack-swift06:20
*** silor has joined #openstack-swift06:23
*** armaan_ has quit IRC06:33
*** armaan has joined #openstack-swift06:34
*** ccamacho has quit IRC06:38
*** ccamacho has joined #openstack-swift06:39
*** hseipp has joined #openstack-swift06:43
*** m_kazuhiro_ has quit IRC06:49
*** silor has quit IRC07:08
*** tesseract has joined #openstack-swift07:22
*** geaaru has joined #openstack-swift07:25
*** armaan has quit IRC07:50
*** armaan has joined #openstack-swift07:51
*** armaan has quit IRC08:05
*** armaan has joined #openstack-swift08:06
*** bkopilov__ has quit IRC08:35
*** bkopilov_ has quit IRC08:36
*** bkopilov has joined #openstack-swift08:50
*** bkopilov_ has joined #openstack-swift08:50
*** gyankum has joined #openstack-swift08:55
*** kei_yama has quit IRC08:57
*** gkadam__ has joined #openstack-swift09:06
*** mikecmpbll has joined #openstack-swift09:17
*** cbartz has quit IRC10:03
*** timur has quit IRC10:06
*** timur has joined #openstack-swift10:07
*** cbartz has joined #openstack-swift10:18
*** NM has joined #openstack-swift10:30
*** cbartz has quit IRC10:30
*** NM has quit IRC10:48
*** psachin` has joined #openstack-swift10:56
*** psachin has quit IRC10:57
*** gkadam_ has joined #openstack-swift10:59
*** gkadam__ has quit IRC10:59
*** hseipp has quit IRC11:19
*** armaan has quit IRC11:41
*** armaan has joined #openstack-swift11:41
*** armaan has quit IRC12:16
*** pcaruana has quit IRC12:21
*** NM has joined #openstack-swift12:23
*** vinsh_ has joined #openstack-swift12:27
*** vinsh has quit IRC12:27
*** vinsh_ has quit IRC12:27
*** vinsh has joined #openstack-swift12:28
*** armaan has joined #openstack-swift12:30
*** gyan_ has quit IRC12:51
*** gyankum has quit IRC12:51
*** armaan has quit IRC12:54
*** silor has joined #openstack-swift12:54
*** cshastri has quit IRC12:56
*** guimaluf has quit IRC13:01
*** psachin` has quit IRC13:04
*** klamath has joined #openstack-swift13:13
*** klamath has quit IRC13:17
*** drewn3ss has quit IRC13:22
*** mingyu has joined #openstack-swift13:29
*** drewn3ss has joined #openstack-swift13:30
*** armaan has joined #openstack-swift13:34
*** pcaruana has joined #openstack-swift13:40
*** klamath has joined #openstack-swift13:54
*** NM has left #openstack-swift14:02
*** pcaruana has quit IRC14:05
*** pcaruana has joined #openstack-swift14:08
*** mingyu has quit IRC14:15
*** mingyu has joined #openstack-swift14:19
*** pcaruana has quit IRC14:25
DHEmattoliverau: vancouver is quite a ways away from me actually. like traveling from Detroit to Seattle...14:26
*** prometheanfire has joined #openstack-swift14:26
*** pcaruana has joined #openstack-swift14:26
prometheanfireshould generate_temp_url in swiftclient work with radosgw endpoints?14:28
prometheanfirehttps://github.com/openstack/python-swiftclient/commit/3934bd606acc2333ee9ae63a40baa35928ef908d#diff-65fb059e01befb2bd60268c230a0c989R109 seems to break it, since radosgw doesn't use the /v1/account/container/object path but uses the /v1/container/object path instead14:29
prometheanfirehttps://github.com/openstack/python-swiftclient/commit/4c955751d340a8f71a2eebdb3c58d90b36874a66#diff-65fb059e01befb2bd60268c230a0c989R103 might be closer to it though...14:30
*** geaaru has quit IRC14:32
prometheanfireso, broken since ocata14:33
notmynamegood morning14:35
prometheanfirenotmyname: moin :D14:35
prometheanfireupdated https://bugs.launchpad.net/ironic/+bug/1747384 about it14:35
openstackLaunchpad bug 1747384 in python-swiftclient "fix tempurl's valid check" [Undecided,New]14:35
*** germs has joined #openstack-swift14:37
*** germs has quit IRC14:37
*** germs has joined #openstack-swift14:37
prometheanfirenotmyname: if I get an ack that this is something to be fixed and altering the validation to work with radosgw as well as swift(proper) is acked I'll start working on it14:38
notmynameprometheanfire: I'm not entirely sure what you're looking for. you're asking swift devs if a swift feature works in a different system that partially implements a swift api?14:39
prometheanfireI'm asking if swiftclient should be expected to work with radosgw, that validation breaks support that previously worked (prior to 3.3.0)14:41
prometheanfireif swiftclient drops support for it, then I'm guessing that most of openstack will follow14:42
notmynameif swiftclient drops support for radosgw?14:42
prometheanfireyes14:43
notmynameswiftclient has never claimed to support radosgw. it's up to radosgw to emulate swift. swiftclient should work against any swift endpoint14:44
prometheanfireok14:44
notmynameseems similar to asking if amazon will update boto to support swift's emulation of the s3 api. that's *our* job to emulate s3 good enough to work with s3 clients. not the other way around14:45
prometheanfireI get that, but it also seems like a step back was taken when that validation became overly strict14:45
*** germs has quit IRC14:46
notmynameah, I see what you're getting at14:46
*** germs has joined #openstack-swift14:46
*** germs has joined #openstack-swift14:46
notmynameno. there are no plans to revert that swiftclient change or to add tempurl support for alternative URL schemes14:50
prometheanfirenotmyname: ok, if you could respond to the bug and close it I'd appreciate it14:55
prometheanfireI'm probably going to email openstack-dev about it, just so the policy is clear (and I want to be clear that I understand why it is as you say it is, just makes my job much harder, I either have to get ceph to support the account portion of the path (they can probably just drop it) or fork swiftclient)14:56
*** hseipp has joined #openstack-swift15:02
*** gyankum has joined #openstack-swift15:08
*** gyan_ has joined #openstack-swift15:08
notmynameprometheanfire: done15:08
*** mingyu has quit IRC15:18
*** silor has quit IRC15:23
*** links has quit IRC15:25
*** armaan has quit IRC15:25
*** armaan has joined #openstack-swift15:26
*** prometheanfire has quit IRC15:32
*** cshastri has joined #openstack-swift15:35
*** germs has quit IRC15:36
*** germs has joined #openstack-swift15:37
*** gyee has joined #openstack-swift15:38
*** mingyu has joined #openstack-swift16:03
remix_tjtdasilva: i've pushed one PR for fixing the ansible part. Now i'm testing a little change to vagrantfile for supporting libvirt and another change to the playbook for undefined variables16:13
*** hseipp has quit IRC16:26
*** gyankum has quit IRC16:33
*** gyan_ has quit IRC16:34
*** prometheanfire has joined #openstack-swift16:36
prometheanfireback...16:38
*** openstackgerrit has joined #openstack-swift16:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Refactoring, test infrastructure changes and cleanup  https://review.openstack.org/56574216:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add ShardRange class  https://review.openstack.org/56574316:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add support for sharding in ContainerBroker  https://review.openstack.org/56574416:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add shard range support to container server  https://review.openstack.org/56574516:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Enable proxy to build listings from shards  https://review.openstack.org/56574616:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Redirect object updates to shard containers  https://review.openstack.org/56574716:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add sharder daemon, manage_shard_ranges tool and probe tests  https://review.openstack.org/56574816:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add container sharding documentation  https://review.openstack.org/56574916:42
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: SQUASH: Add existing_shard_replication_quorum option  https://review.openstack.org/56728616:42
*** mikecmpbll has quit IRC16:47
*** mingyu has quit IRC16:52
*** armaan has quit IRC16:55
*** armaan has joined #openstack-swift16:55
*** SkyRocknRoll has joined #openstack-swift16:56
*** mingyu has joined #openstack-swift16:57
*** prometheanfire has quit IRC17:06
*** mingyu has quit IRC17:09
*** tesseract has quit IRC17:15
*** mingyu has joined #openstack-swift17:24
*** mikecmpbll has joined #openstack-swift17:31
*** germs has quit IRC17:37
*** geaaru has joined #openstack-swift17:38
*** germs has joined #openstack-swift17:38
*** germs has quit IRC17:38
*** germs has joined #openstack-swift17:38
*** SkyRocknRoll has quit IRC17:38
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: SQUASH: Add existing_shard_replication_quorum option  https://review.openstack.org/56728617:40
acolesclayg: changed to cap bad quorum values rather than raise error ^^17:42
*** gkadam_ has quit IRC17:43
*** mingyu has quit IRC17:47
*** ukaynar has joined #openstack-swift17:50
*** hseipp has joined #openstack-swift17:57
*** armaan has quit IRC18:00
*** armaan has joined #openstack-swift18:00
*** bkopilov has quit IRC18:01
*** bkopilov_ has quit IRC18:02
*** germs has quit IRC18:09
*** germs has joined #openstack-swift18:10
*** germs has joined #openstack-swift18:10
*** germs has quit IRC18:12
*** germs has joined #openstack-swift18:13
*** germs has quit IRC18:13
*** germs has joined #openstack-swift18:13
*** bkopilov has joined #openstack-swift18:14
*** germs has quit IRC18:17
*** armaan has quit IRC18:17
*** germs has joined #openstack-swift18:17
*** germs has quit IRC18:17
*** germs has joined #openstack-swift18:17
*** armaan has joined #openstack-swift18:17
*** armaan has quit IRC18:18
*** armaan has joined #openstack-swift18:18
*** mvenesio has quit IRC18:20
*** mvenesio has joined #openstack-swift18:21
*** germs has quit IRC18:21
*** bkopilov has quit IRC18:24
*** mvenesio has quit IRC18:25
*** bkopilov_ has joined #openstack-swift18:29
*** hseipp has quit IRC18:33
*** d0ugal_ has joined #openstack-swift18:37
*** d0ugal has quit IRC18:37
*** bkopilov has joined #openstack-swift18:38
*** ukaynar has quit IRC18:45
*** mvenesio has joined #openstack-swift18:51
*** mvenesio has quit IRC19:00
*** cshastri has quit IRC19:00
*** mvk has quit IRC19:13
*** links has joined #openstack-swift19:22
*** links has quit IRC19:45
*** prometheanfire has joined #openstack-swift20:09
*** prometheanfire has left #openstack-swift20:14
claygacoles: did we get a config option in for the number of rows that get pulled out per cleave?20:16
*** germs has joined #openstack-swift20:18
*** germs has quit IRC20:22
claygacoles: nm, cleave_row_batch_size :D20:23
*** germs has joined #openstack-swift20:27
*** germs has quit IRC20:27
*** germs has joined #openstack-swift20:27
*** germs has quit IRC20:27
*** m_kazuhiro has joined #openstack-swift20:36
kota_morning20:57
*** pcaruana has quit IRC20:59
mattoliverauMorning21:00
acolesmattoliverau: kota_ o/21:00
notmynamemeeting time in #openstack-meeting21:00
notmynamecan anyone see me typing in -meeting?21:01
kota_notmyname: nothing i can see at #openstack-meeting21:02
notmynamewonderful21:02
acolesnotmyname: no21:02
notmynamefungi: I've been banned from the -meeeting channel. can you please remove that ban21:02
notmynamefungi: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2018-05-08.log.html#t2018-05-08T19:08:58-221:03
mattoliverauLol21:03
notmynamecorvus: ^ help21:04
claygnotmyname: give it a few minutes and then start it in here?  funny that banning patchbot got you banned tho!21:05
notmynamesame IP address. they added a blanket ban for the whole IP21:05
notmynamedo meeting commands work in here?21:05
claygrespin your vm?21:05
notmyname#startmeeting swift21:05
openstackMeeting started Wed May  9 21:05:51 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
*** openstack changes topic to " (Meeting topic: swift)"21:05
openstackThe meeting name has been set to 'swift'21:05
notmynamewhoa!!21:05
clayg!!!???21:05
openstackclayg: Error: "!!???" is not a valid command.21:06
claygsorry21:06
acoleswe can meet here, it'll be like dublin airbnb all over again. swifters will prevail.21:06
notmynameok, meeting time is now and in here21:06
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:06
notmynamethe agenda this week is simply to talk about feature/deep-review21:06
corvusnotmyname: i can remove that21:06
notmyname#link https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:feature/deep-review21:06
notmynamecorvus: thank you21:07
notmynameacoles: I've seen lots of new patch sets for the review banch this week. how is it going?21:07
acolesnotmyname: it's ok. thanks to those who have reviewed.21:08
notmynamethere have not been a lot of reviews21:08
notmyname(granted, it's a huge topic)21:09
acolesso far this week I have turned around review comments and pushed new patchsets daily.21:09
notmynamethank you for that21:09
acolesnotmyname: but, yes, we're not making much headway up the chain of patches yet21:09
notmynamegiven who we have available for reviews, I wrote a wall of text here in IRC earlier this week :-)21:10
acolesthanks mattoliverau for helping with the docs21:10
*** mvenesio has joined #openstack-swift21:10
funginotmyname: reviewing the akick entries, i don't see any ban for your ip address. looks like one was added to #openstack-meeting for the "patchbot" nick specifically but not by address mask. also i see your notmyname nick present in #openstack-meeting21:10
notmynameacoles: where should we be focusing on for now?21:11
notmynameshould we start with the first refactoring patch?21:12
mattoliverauI got sidetracked with the diagrams/doc.  But will do a good review over the next 2 days.  Tho have looked at the code alot over the last while,  and probably a little code blind,  except for acoles better code that is :p21:12
acolesnotmyname: that's had quite a lot of review from timburke and kota, so no, skip that if you're starting21:12
fungiaha, not in the akick list, it's a +b on the channel for your address mask21:12
fungii'll fix that21:12
funginevermind, someone else already has21:13
notmynamealso, reminder to everyone: when leaving a comment, please include a diff with improvements21:13
notmynamefungi: thanks21:13
acolesI liked notmyname's suggestion that some start at top and some start at bottom of chain, but not sure how to coordinate that21:13
notmynameI started with the docs and got as far as the "beyond here it needs to be updated" marker21:14
acolesif you want to dive in, the final patch (docs) now has sufficient content to guide you through dpeloying and sharding21:14
notmynameyeah, the docs look great21:15
notmynameacoles: you mentioned something earlier this week about dropping some stuff from the docs. has that happened already, or is that something someone else can do?21:15
acolesnotmyname: no I was hoping to work on that tomorrow - everything should stay up to the obvious 'below here is outdated' heading , but beyond that I think we can trim down the content.21:16
notmynameok21:16
acolesand I'm happy if anyone else wants to do that.21:17
notmyname:-)21:17
notmynameI would love to be able to do that during my tomorrow21:17
acolesit's great to have plenty of explanation but not if it slows us down by needing to review lots of text - we can always add to it on master21:18
notmynameright21:18
notmynameclayg: can you give a quick update of what we've seen with this feature branch on the really big DB in our test clusteR?21:19
acolesplus, I have relatively large amount of comment in code21:19
claygnotmyname: we're getting there!21:19
claygI'm playing with some of the knobs trying to figure out the right tuning21:19
notmynamea week or two ago, I said something about it being pretty slow, but it looks like it's gotten a lot better since then21:19
mattoliverauAn explaination on the shard range states woukd be good. But yeah trimmming down the other under hood makes sense21:19
claygwe're learning with a 140M row db on a cluster with only HDD - totally under water with out of sync db's and async pileups21:20
claygso this thing was a MESS - and it's WORKING!!!21:20
acolesmattoliverau: yes, there is some new content I want to add too21:20
claygwe've dug outself out of the whole and watching things just sort of settle down and clean up21:20
acolesmattoliverau: states being one21:20
notmynameclayg: that's really good news21:20
claygasync's have made their way into the new shard db's and everything looks good21:20
claygstill waiting for the final unlinks to happen on a couple of replicas - then we're moving on to more testing on some new/different datasets and different hardware configs21:21
claygthis stuff is AMAZING21:21
claygtotal game changer for swift21:21
claygmattoliverau & acoles & timburke definately get some mad props here21:21
notmynamekota_: m_kazuhiro: have either of you had a chance to run this feature branch yet?21:21
notmynameclayg: yes, definitely!21:21
kota_notmyname: not yet playing. just run unit tests in my local at the refactoring patch.21:22
notmynamekota_: that's good21:22
kota_i'll make it maybe in this week or the next.21:22
notmynamethanks21:23
acolesIt would be great to start getting some review on https://review.openstack.org/56574421:23
patchbotpatch 565744 - swift (feature/deep-review) - Add support for sharding in ContainerBroker21:23
mattoliverauclayg \o/21:23
kota_at least in the review process, I should do something to check the behaivor and performance21:23
notmynameI'm still hoping that we can have the patch chain land at the end of next week21:23
notmyname(remember that may 17 is swift's birthday)21:23
*** mvenesio has quit IRC21:24
claygnotmyname: I say if it's NOT landed we just go ahead and do it anyway - I trust Al21:24
claygthis stuff is too awesome not to have21:24
notmyname:-)21:24
acolesclayg: do not trust anyone21:24
claygI mean you can glance at it or whatever - it works exactly how mattoliverau told you it did 3 years ago ;)21:24
claygwell.. *mostly* :P21:24
m_kazuhironotmyname: not yet. but I will do.21:24
mattoliverauLol21:25
claygmattoliverau: 4?  :P21:25
mattoliverauWith alot of polish from acoles and timburke21:25
notmynameI'm not super worried yet about not having a lot of visible reviews on the patch chain, if everything is actually mostly ok. but I'd like to see some by friday or monday21:25
acolesif any core wants to discuss patches with me in real time (voice/video) then I'll do my best to make that happen21:26
notmynameseeing some reviews (positive and negative) will help us all get it landed sooner21:26
mattoliverauclayg too early to math :p21:27
notmynameI know for a fact we can still make improvements to container sharding. there's still a lot of opportunity to do more (eg automatic sharding is something we're leaving to do later)21:27
notmynameso this comes down to (1) does it make users' lives better? (2) is it maintainable? (3) is it written so we can keep making it better?21:28
notmynameis there anything else we need to talk about on this topic?21:29
notmynameacoles: clayg: kota_: mattoliverau: you good?21:30
mattoliverauYup21:30
kota_yes21:30
acolesnotmyname: yes21:30
notmynameok, let's look forward just a little bit...21:30
claygi gotta bounce, I'll catch up on logs!21:31
notmynameI'd like to tag a swift release after this feature branch lands21:31
mattoliverauclayg: o/21:31
notmynameso if it lands next week, that means a new swift release will be the end of next week or, more likely, the beginning of the week of the 21st21:32
notmynamethat week is the week of the openstack summit in vancouver21:32
kota_¥o/21:32
notmynamethere's a lot of great stuff that's in swift that we'll be able to talk about there :-)21:33
notmynames3api and container sharding21:33
mattoliverauThat would be  huge release21:33
notmynameyep21:33
notmynamethere's also an onboarding sessions that a few people have signed up for. I'll be leading that (and I hope with a lot of help from kota_ and mattoliverau :-)21:33
mattoliverauYup I'll be there :)21:34
kota_oh, i didn't notice the onboarding session. I'll add it to my schedule21:34
notmynamespeaking of openstack events, please be sure to sign up for the PTG happening in september in Denver21:34
notmynamekota_: it's immediately after the swift project update on thursday21:34
kota_(that means i didn't check the schedule in detail yet :P)21:35
notmynamethe PTG is $200 right now and the prices will go up at the end of next week21:35
notmyname#link https://www.openstack.org/ptg21:35
notmynamethat's all I had for this week. feature/deep-review update. next swift release. sing up for the ptg21:36
notmynamedoes anyone else have anything for the meeting this week?21:36
mattoliverauAlso to be a little annoying, ill be in Fiji next week for a family holiday,  so will review as much as i can before i leave,  and try among keep up with what ever internet i end up getting.21:36
notmynamehmmm21:36
notmynametdasilva should be back next week, too21:36
kota_ah, RedHad summit in Boston this week.21:37
notmynamenah, he's on vacation this week21:37
notmynamebut there is a red hat summit. but in san francisco21:37
kota_oh, really21:37
mattoliverauDamn phone auto complete, * try to keep up..21:37
kota_ok, not in Boston21:37
kota_i saw takashi's activities. he joined it.21:38
notmynamethank you for your work on swift.21:38
notmyname#endmeeting21:38
*** openstack changes topic to "master is frozen while we review feature/deep-review | https://etherpad.openstack.org/p/deep-review | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Review Dashboard: http://not.mn/reviews.html"21:38
openstackMeeting ended Wed May  9 21:38:50 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.html21:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.txt21:38
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.log.html21:38
notmyname....and we're still in the same channel. I'm not sure if this is great or terrible :-)21:39
mattoliverauBreakfast time!21:39
mattoliverauLol21:39
kota_me too121:39
kota_too!21:39
acolesgood night21:41
*** m_kazuhiro has quit IRC21:47
*** saltsa has joined #openstack-swift22:11
*** zigo has quit IRC22:11
*** zigo has joined #openstack-swift22:11
*** mikecmpbll has quit IRC22:25
*** mvk has joined #openstack-swift22:32
*** threestrands has joined #openstack-swift22:33
*** threestrands_ has joined #openstack-swift22:36
*** threestrands_ has quit IRC22:36
*** threestrands_ has joined #openstack-swift22:36
*** threestrands has quit IRC22:38
*** zaitcev has quit IRC22:46
*** kei_yama has joined #openstack-swift23:10
mattoliveraumorning again23:17

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