*** mingyu has quit IRC | 00:05 | |
*** bkopilov__ has joined #openstack-swift | 00:06 | |
*** bkopilov_ has joined #openstack-swift | 00:06 | |
*** mingyu has joined #openstack-swift | 00:09 | |
*** mingyu has quit IRC | 00:11 | |
*** gyee has quit IRC | 00:36 | |
spsurya | DHE: Will the swift work with only storage node installation ? | 00:50 |
---|---|---|
spsurya | https://docs.openstack.org/swift/latest/install/storage-install-ubuntu-debian.html | 00:50 |
DHE | spsurya: 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 |
spsurya | DHE: so i think i can have all on one storage node itself | 00:54 |
spsurya | right ? | 00:54 |
DHE | well, yes, that's sorta what SAIO is about | 00:55 |
DHE | but thtat's more intended for testing and experimentation. swift is designed as the no-single-point-of-failure object storage | 00:56 |
spsurya | DHE: yeah i am using for experiment only | 00:57 |
spsurya | but i cant't see about the configuration for swift-proxy on storage node | 00:59 |
DHE | you don't really. the proxy reads the ring file, sees what hosts are listed in it, and connects to them as needed | 01:00 |
DHE | proxy server usually doesn't require much configuration beyond authentication info | 01:00 |
spsurya | so `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 |
spsurya | DHE: | 01:02 |
DHE | the 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 machine | 01:02 |
DHE | in 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 SSDs | 01:03 |
spsurya | DHE: 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 that | 01:10 |
spsurya | i.e swift installed with SAIO and then woud be addiing new node | 01: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 |
mattoliverau | they are all daemons, but the storage nodes need access to drives. The proxy doesn't so it can live whereever. | 01:12 |
mattoliverau | many small clusters might use PACO (that is proxy, account, container and object) services on all nodes. | 01:12 |
mattoliverau | as the IO grows or the number of connections, you might think about splitting the proxy off so P-ACO | 01:13 |
mattoliverau | most 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-O | 01:14 |
mattoliverau | Swift can handle it's own auth. tmpauth shouldn't be used in production, but fine if your just testing. | 01:14 |
mattoliverau | others to look at are obviously keystone or swauth. Or roll your own :) | 01:15 |
*** armaan has quit IRC | 01:15 | |
*** armaan has joined #openstack-swift | 01:16 | |
mattoliverau | Many 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-swift | 01:21 | |
*** username_ has joined #openstack-swift | 01:23 | |
*** username_ is now known as username__ | 01:23 | |
spsurya | DHE: mattoliverau thanks a lot | 01:23 |
spsurya | for explanation | 01:24 |
mattoliverau | DHE: thanks for all your help lately in channel! where abouts you located? Cause you seem to share a similar timezone to me :) | 02:04 |
DHE | southern ontario | 02:05 |
*** psachin` has joined #openstack-swift | 02:10 | |
mattoliverau | DHE: 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 IRC | 02:26 | |
*** m_kazuhiro has joined #openstack-swift | 02:29 | |
m_kazuhiro | good morning | 02:29 |
*** username__ has quit IRC | 02:35 | |
mattoliverau | m_kazuhiro: mornign | 02:39 |
mattoliverau | *morning | 02:39 |
*** psachin has joined #openstack-swift | 02:42 | |
m_kazuhiro | mattoliverau: morning :) | 02:42 |
mattoliverau | m_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 reviews | 02:43 |
m_kazuhiro | mattoliverau: That's ok. Our current important task is sharding review :) | 02:46 |
*** rcernin has quit IRC | 03:14 | |
kota_ | good morning | 03:19 |
*** klamath has quit IRC | 03:35 | |
*** threestrands has joined #openstack-swift | 03:38 | |
*** links has joined #openstack-swift | 03:42 | |
*** gyan_ has joined #openstack-swift | 03:44 | |
*** m_kazuhiro_ has joined #openstack-swift | 03:45 | |
*** m_kazuhiro has quit IRC | 03:47 | |
*** klamath has joined #openstack-swift | 03:50 | |
*** cshastri has joined #openstack-swift | 04:00 | |
*** klamath has quit IRC | 04:27 | |
*** klamath has joined #openstack-swift | 05:00 | |
*** klamath has quit IRC | 05:12 | |
*** klamath has joined #openstack-swift | 05:28 | |
*** klamath has quit IRC | 05:32 | |
*** hoonetorg has quit IRC | 05:33 | |
*** hoonetorg has joined #openstack-swift | 05:44 | |
*** threestrands has quit IRC | 05:54 | |
*** geaaru has quit IRC | 05:56 | |
*** pcaruana has joined #openstack-swift | 05:57 | |
*** armaan has quit IRC | 06:05 | |
*** armaan has joined #openstack-swift | 06:05 | |
*** armaan_ has joined #openstack-swift | 06:13 | |
*** armaan has quit IRC | 06:16 | |
*** cbartz has joined #openstack-swift | 06:20 | |
*** silor has joined #openstack-swift | 06:23 | |
*** armaan_ has quit IRC | 06:33 | |
*** armaan has joined #openstack-swift | 06:34 | |
*** ccamacho has quit IRC | 06:38 | |
*** ccamacho has joined #openstack-swift | 06:39 | |
*** hseipp has joined #openstack-swift | 06:43 | |
*** m_kazuhiro_ has quit IRC | 06:49 | |
*** silor has quit IRC | 07:08 | |
*** tesseract has joined #openstack-swift | 07:22 | |
*** geaaru has joined #openstack-swift | 07:25 | |
*** armaan has quit IRC | 07:50 | |
*** armaan has joined #openstack-swift | 07:51 | |
*** armaan has quit IRC | 08:05 | |
*** armaan has joined #openstack-swift | 08:06 | |
*** bkopilov__ has quit IRC | 08:35 | |
*** bkopilov_ has quit IRC | 08:36 | |
*** bkopilov has joined #openstack-swift | 08:50 | |
*** bkopilov_ has joined #openstack-swift | 08:50 | |
*** gyankum has joined #openstack-swift | 08:55 | |
*** kei_yama has quit IRC | 08:57 | |
*** gkadam__ has joined #openstack-swift | 09:06 | |
*** mikecmpbll has joined #openstack-swift | 09:17 | |
*** cbartz has quit IRC | 10:03 | |
*** timur has quit IRC | 10:06 | |
*** timur has joined #openstack-swift | 10:07 | |
*** cbartz has joined #openstack-swift | 10:18 | |
*** NM has joined #openstack-swift | 10:30 | |
*** cbartz has quit IRC | 10:30 | |
*** NM has quit IRC | 10:48 | |
*** psachin` has joined #openstack-swift | 10:56 | |
*** psachin has quit IRC | 10:57 | |
*** gkadam_ has joined #openstack-swift | 10:59 | |
*** gkadam__ has quit IRC | 10:59 | |
*** hseipp has quit IRC | 11:19 | |
*** armaan has quit IRC | 11:41 | |
*** armaan has joined #openstack-swift | 11:41 | |
*** armaan has quit IRC | 12:16 | |
*** pcaruana has quit IRC | 12:21 | |
*** NM has joined #openstack-swift | 12:23 | |
*** vinsh_ has joined #openstack-swift | 12:27 | |
*** vinsh has quit IRC | 12:27 | |
*** vinsh_ has quit IRC | 12:27 | |
*** vinsh has joined #openstack-swift | 12:28 | |
*** armaan has joined #openstack-swift | 12:30 | |
*** gyan_ has quit IRC | 12:51 | |
*** gyankum has quit IRC | 12:51 | |
*** armaan has quit IRC | 12:54 | |
*** silor has joined #openstack-swift | 12:54 | |
*** cshastri has quit IRC | 12:56 | |
*** guimaluf has quit IRC | 13:01 | |
*** psachin` has quit IRC | 13:04 | |
*** klamath has joined #openstack-swift | 13:13 | |
*** klamath has quit IRC | 13:17 | |
*** drewn3ss has quit IRC | 13:22 | |
*** mingyu has joined #openstack-swift | 13:29 | |
*** drewn3ss has joined #openstack-swift | 13:30 | |
*** armaan has joined #openstack-swift | 13:34 | |
*** pcaruana has joined #openstack-swift | 13:40 | |
*** klamath has joined #openstack-swift | 13:54 | |
*** NM has left #openstack-swift | 14:02 | |
*** pcaruana has quit IRC | 14:05 | |
*** pcaruana has joined #openstack-swift | 14:08 | |
*** mingyu has quit IRC | 14:15 | |
*** mingyu has joined #openstack-swift | 14:19 | |
*** pcaruana has quit IRC | 14:25 | |
DHE | mattoliverau: vancouver is quite a ways away from me actually. like traveling from Detroit to Seattle... | 14:26 |
*** prometheanfire has joined #openstack-swift | 14:26 | |
*** pcaruana has joined #openstack-swift | 14:26 | |
prometheanfire | should generate_temp_url in swiftclient work with radosgw endpoints? | 14:28 |
prometheanfire | https://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 instead | 14:29 |
prometheanfire | https://github.com/openstack/python-swiftclient/commit/4c955751d340a8f71a2eebdb3c58d90b36874a66#diff-65fb059e01befb2bd60268c230a0c989R103 might be closer to it though... | 14:30 |
*** geaaru has quit IRC | 14:32 | |
prometheanfire | so, broken since ocata | 14:33 |
notmyname | good morning | 14:35 |
prometheanfire | notmyname: moin :D | 14:35 |
prometheanfire | updated https://bugs.launchpad.net/ironic/+bug/1747384 about it | 14:35 |
openstack | Launchpad bug 1747384 in python-swiftclient "fix tempurl's valid check" [Undecided,New] | 14:35 |
*** germs has joined #openstack-swift | 14:37 | |
*** germs has quit IRC | 14:37 | |
*** germs has joined #openstack-swift | 14:37 | |
prometheanfire | notmyname: 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 it | 14:38 |
notmyname | prometheanfire: 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 |
prometheanfire | I'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 |
prometheanfire | if swiftclient drops support for it, then I'm guessing that most of openstack will follow | 14:42 |
notmyname | if swiftclient drops support for radosgw? | 14:42 |
prometheanfire | yes | 14:43 |
notmyname | swiftclient has never claimed to support radosgw. it's up to radosgw to emulate swift. swiftclient should work against any swift endpoint | 14:44 |
prometheanfire | ok | 14:44 |
notmyname | seems 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 around | 14:45 |
prometheanfire | I get that, but it also seems like a step back was taken when that validation became overly strict | 14:45 |
*** germs has quit IRC | 14:46 | |
notmyname | ah, I see what you're getting at | 14:46 |
*** germs has joined #openstack-swift | 14:46 | |
*** germs has joined #openstack-swift | 14:46 | |
notmyname | no. there are no plans to revert that swiftclient change or to add tempurl support for alternative URL schemes | 14:50 |
prometheanfire | notmyname: ok, if you could respond to the bug and close it I'd appreciate it | 14:55 |
prometheanfire | I'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-swift | 15:02 | |
*** gyankum has joined #openstack-swift | 15:08 | |
*** gyan_ has joined #openstack-swift | 15:08 | |
notmyname | prometheanfire: done | 15:08 |
*** mingyu has quit IRC | 15:18 | |
*** silor has quit IRC | 15:23 | |
*** links has quit IRC | 15:25 | |
*** armaan has quit IRC | 15:25 | |
*** armaan has joined #openstack-swift | 15:26 | |
*** prometheanfire has quit IRC | 15:32 | |
*** cshastri has joined #openstack-swift | 15:35 | |
*** germs has quit IRC | 15:36 | |
*** germs has joined #openstack-swift | 15:37 | |
*** gyee has joined #openstack-swift | 15:38 | |
*** mingyu has joined #openstack-swift | 16:03 | |
remix_tj | tdasilva: 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 variables | 16:13 |
*** hseipp has quit IRC | 16:26 | |
*** gyankum has quit IRC | 16:33 | |
*** gyan_ has quit IRC | 16:34 | |
*** prometheanfire has joined #openstack-swift | 16:36 | |
prometheanfire | back... | 16:38 |
*** openstackgerrit has joined #openstack-swift | 16:42 | |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Refactoring, test infrastructure changes and cleanup https://review.openstack.org/565742 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Add ShardRange class https://review.openstack.org/565743 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Add support for sharding in ContainerBroker https://review.openstack.org/565744 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Add shard range support to container server https://review.openstack.org/565745 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Enable proxy to build listings from shards https://review.openstack.org/565746 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Redirect object updates to shard containers https://review.openstack.org/565747 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Add sharder daemon, manage_shard_ranges tool and probe tests https://review.openstack.org/565748 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: Add container sharding documentation https://review.openstack.org/565749 | 16:42 |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: SQUASH: Add existing_shard_replication_quorum option https://review.openstack.org/567286 | 16:42 |
*** mikecmpbll has quit IRC | 16:47 | |
*** mingyu has quit IRC | 16:52 | |
*** armaan has quit IRC | 16:55 | |
*** armaan has joined #openstack-swift | 16:55 | |
*** SkyRocknRoll has joined #openstack-swift | 16:56 | |
*** mingyu has joined #openstack-swift | 16:57 | |
*** prometheanfire has quit IRC | 17:06 | |
*** mingyu has quit IRC | 17:09 | |
*** tesseract has quit IRC | 17:15 | |
*** mingyu has joined #openstack-swift | 17:24 | |
*** mikecmpbll has joined #openstack-swift | 17:31 | |
*** germs has quit IRC | 17:37 | |
*** geaaru has joined #openstack-swift | 17:38 | |
*** germs has joined #openstack-swift | 17:38 | |
*** germs has quit IRC | 17:38 | |
*** germs has joined #openstack-swift | 17:38 | |
*** SkyRocknRoll has quit IRC | 17:38 | |
openstackgerrit | Alistair Coles proposed openstack/swift feature/deep-review: SQUASH: Add existing_shard_replication_quorum option https://review.openstack.org/567286 | 17:40 |
acoles | clayg: changed to cap bad quorum values rather than raise error ^^ | 17:42 |
*** gkadam_ has quit IRC | 17:43 | |
*** mingyu has quit IRC | 17:47 | |
*** ukaynar has joined #openstack-swift | 17:50 | |
*** hseipp has joined #openstack-swift | 17:57 | |
*** armaan has quit IRC | 18:00 | |
*** armaan has joined #openstack-swift | 18:00 | |
*** bkopilov has quit IRC | 18:01 | |
*** bkopilov_ has quit IRC | 18:02 | |
*** germs has quit IRC | 18:09 | |
*** germs has joined #openstack-swift | 18:10 | |
*** germs has joined #openstack-swift | 18:10 | |
*** germs has quit IRC | 18:12 | |
*** germs has joined #openstack-swift | 18:13 | |
*** germs has quit IRC | 18:13 | |
*** germs has joined #openstack-swift | 18:13 | |
*** bkopilov has joined #openstack-swift | 18:14 | |
*** germs has quit IRC | 18:17 | |
*** armaan has quit IRC | 18:17 | |
*** germs has joined #openstack-swift | 18:17 | |
*** germs has quit IRC | 18:17 | |
*** germs has joined #openstack-swift | 18:17 | |
*** armaan has joined #openstack-swift | 18:17 | |
*** armaan has quit IRC | 18:18 | |
*** armaan has joined #openstack-swift | 18:18 | |
*** mvenesio has quit IRC | 18:20 | |
*** mvenesio has joined #openstack-swift | 18:21 | |
*** germs has quit IRC | 18:21 | |
*** bkopilov has quit IRC | 18:24 | |
*** mvenesio has quit IRC | 18:25 | |
*** bkopilov_ has joined #openstack-swift | 18:29 | |
*** hseipp has quit IRC | 18:33 | |
*** d0ugal_ has joined #openstack-swift | 18:37 | |
*** d0ugal has quit IRC | 18:37 | |
*** bkopilov has joined #openstack-swift | 18:38 | |
*** ukaynar has quit IRC | 18:45 | |
*** mvenesio has joined #openstack-swift | 18:51 | |
*** mvenesio has quit IRC | 19:00 | |
*** cshastri has quit IRC | 19:00 | |
*** mvk has quit IRC | 19:13 | |
*** links has joined #openstack-swift | 19:22 | |
*** links has quit IRC | 19:45 | |
*** prometheanfire has joined #openstack-swift | 20:09 | |
*** prometheanfire has left #openstack-swift | 20:14 | |
clayg | acoles: did we get a config option in for the number of rows that get pulled out per cleave? | 20:16 |
*** germs has joined #openstack-swift | 20:18 | |
*** germs has quit IRC | 20:22 | |
clayg | acoles: nm, cleave_row_batch_size :D | 20:23 |
*** germs has joined #openstack-swift | 20:27 | |
*** germs has quit IRC | 20:27 | |
*** germs has joined #openstack-swift | 20:27 | |
*** germs has quit IRC | 20:27 | |
*** m_kazuhiro has joined #openstack-swift | 20:36 | |
kota_ | morning | 20:57 |
*** pcaruana has quit IRC | 20:59 | |
mattoliverau | Morning | 21:00 |
acoles | mattoliverau: kota_ o/ | 21:00 |
notmyname | meeting time in #openstack-meeting | 21:00 |
notmyname | can anyone see me typing in -meeting? | 21:01 |
kota_ | notmyname: nothing i can see at #openstack-meeting | 21:02 |
notmyname | wonderful | 21:02 |
acoles | notmyname: no | 21:02 |
notmyname | fungi: I've been banned from the -meeeting channel. can you please remove that ban | 21:02 |
notmyname | fungi: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2018-05-08.log.html#t2018-05-08T19:08:58-2 | 21:03 |
mattoliverau | Lol | 21:03 |
notmyname | corvus: ^ help | 21:04 |
clayg | notmyname: give it a few minutes and then start it in here? funny that banning patchbot got you banned tho! | 21:05 |
notmyname | same IP address. they added a blanket ban for the whole IP | 21:05 |
notmyname | do meeting commands work in here? | 21:05 |
clayg | respin your vm? | 21:05 |
notmyname | #startmeeting swift | 21:05 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:05 |
*** openstack changes topic to " (Meeting topic: swift)" | 21:05 | |
openstack | The meeting name has been set to 'swift' | 21:05 |
notmyname | whoa!! | 21:05 |
clayg | !!!??? | 21:05 |
openstack | clayg: Error: "!!???" is not a valid command. | 21:06 |
clayg | sorry | 21:06 |
acoles | we can meet here, it'll be like dublin airbnb all over again. swifters will prevail. | 21:06 |
notmyname | ok, meeting time is now and in here | 21:06 |
notmyname | #link https://wiki.openstack.org/wiki/Meetings/Swift | 21:06 |
notmyname | the agenda this week is simply to talk about feature/deep-review | 21:06 |
corvus | notmyname: i can remove that | 21:06 |
notmyname | #link https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:feature/deep-review | 21:06 |
notmyname | corvus: thank you | 21:07 |
notmyname | acoles: I've seen lots of new patch sets for the review banch this week. how is it going? | 21:07 |
acoles | notmyname: it's ok. thanks to those who have reviewed. | 21:08 |
notmyname | there have not been a lot of reviews | 21:08 |
notmyname | (granted, it's a huge topic) | 21:09 |
acoles | so far this week I have turned around review comments and pushed new patchsets daily. | 21:09 |
notmyname | thank you for that | 21:09 |
acoles | notmyname: but, yes, we're not making much headway up the chain of patches yet | 21:09 |
notmyname | given who we have available for reviews, I wrote a wall of text here in IRC earlier this week :-) | 21:10 |
acoles | thanks mattoliverau for helping with the docs | 21:10 |
*** mvenesio has joined #openstack-swift | 21:10 | |
fungi | notmyname: 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-meeting | 21:10 |
notmyname | acoles: where should we be focusing on for now? | 21:11 |
notmyname | should we start with the first refactoring patch? | 21:12 |
mattoliverau | I 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 :p | 21:12 |
acoles | notmyname: that's had quite a lot of review from timburke and kota, so no, skip that if you're starting | 21:12 |
fungi | aha, not in the akick list, it's a +b on the channel for your address mask | 21:12 |
fungi | i'll fix that | 21:12 |
fungi | nevermind, someone else already has | 21:13 |
notmyname | also, reminder to everyone: when leaving a comment, please include a diff with improvements | 21:13 |
notmyname | fungi: thanks | 21:13 |
acoles | I liked notmyname's suggestion that some start at top and some start at bottom of chain, but not sure how to coordinate that | 21:13 |
notmyname | I started with the docs and got as far as the "beyond here it needs to be updated" marker | 21:14 |
acoles | if you want to dive in, the final patch (docs) now has sufficient content to guide you through dpeloying and sharding | 21:14 |
notmyname | yeah, the docs look great | 21:15 |
notmyname | acoles: 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 |
acoles | notmyname: 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 |
notmyname | ok | 21:16 |
acoles | and I'm happy if anyone else wants to do that. | 21:17 |
notmyname | :-) | 21:17 |
notmyname | I would love to be able to do that during my tomorrow | 21:17 |
acoles | it'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 master | 21:18 |
notmyname | right | 21:18 |
notmyname | clayg: 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 |
acoles | plus, I have relatively large amount of comment in code | 21:19 |
clayg | notmyname: we're getting there! | 21:19 |
clayg | I'm playing with some of the knobs trying to figure out the right tuning | 21:19 |
notmyname | a week or two ago, I said something about it being pretty slow, but it looks like it's gotten a lot better since then | 21:19 |
mattoliverau | An explaination on the shard range states woukd be good. But yeah trimmming down the other under hood makes sense | 21:19 |
clayg | we're learning with a 140M row db on a cluster with only HDD - totally under water with out of sync db's and async pileups | 21:20 |
clayg | so this thing was a MESS - and it's WORKING!!! | 21:20 |
acoles | mattoliverau: yes, there is some new content I want to add too | 21:20 |
clayg | we've dug outself out of the whole and watching things just sort of settle down and clean up | 21:20 |
acoles | mattoliverau: states being one | 21:20 |
notmyname | clayg: that's really good news | 21:20 |
clayg | async's have made their way into the new shard db's and everything looks good | 21:20 |
clayg | still 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 configs | 21:21 |
clayg | this stuff is AMAZING | 21:21 |
clayg | total game changer for swift | 21:21 |
clayg | mattoliverau & acoles & timburke definately get some mad props here | 21:21 |
notmyname | kota_: m_kazuhiro: have either of you had a chance to run this feature branch yet? | 21:21 |
notmyname | clayg: yes, definitely! | 21:21 |
kota_ | notmyname: not yet playing. just run unit tests in my local at the refactoring patch. | 21:22 |
notmyname | kota_: that's good | 21:22 |
kota_ | i'll make it maybe in this week or the next. | 21:22 |
notmyname | thanks | 21:23 |
acoles | It would be great to start getting some review on https://review.openstack.org/565744 | 21:23 |
patchbot | patch 565744 - swift (feature/deep-review) - Add support for sharding in ContainerBroker | 21:23 |
mattoliverau | clayg \o/ | 21:23 |
kota_ | at least in the review process, I should do something to check the behaivor and performance | 21:23 |
notmyname | I'm still hoping that we can have the patch chain land at the end of next week | 21:23 |
notmyname | (remember that may 17 is swift's birthday) | 21:23 |
*** mvenesio has quit IRC | 21:24 | |
clayg | notmyname: I say if it's NOT landed we just go ahead and do it anyway - I trust Al | 21:24 |
clayg | this stuff is too awesome not to have | 21:24 |
notmyname | :-) | 21:24 |
acoles | clayg: do not trust anyone | 21:24 |
clayg | I mean you can glance at it or whatever - it works exactly how mattoliverau told you it did 3 years ago ;) | 21:24 |
clayg | well.. *mostly* :P | 21:24 |
m_kazuhiro | notmyname: not yet. but I will do. | 21:24 |
mattoliverau | Lol | 21:25 |
clayg | mattoliverau: 4? :P | 21:25 |
mattoliverau | With alot of polish from acoles and timburke | 21:25 |
notmyname | I'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 monday | 21:25 |
acoles | if any core wants to discuss patches with me in real time (voice/video) then I'll do my best to make that happen | 21:26 |
notmyname | seeing some reviews (positive and negative) will help us all get it landed sooner | 21:26 |
mattoliverau | clayg too early to math :p | 21:27 |
notmyname | I 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 |
notmyname | so 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 |
notmyname | is there anything else we need to talk about on this topic? | 21:29 |
notmyname | acoles: clayg: kota_: mattoliverau: you good? | 21:30 |
mattoliverau | Yup | 21:30 |
kota_ | yes | 21:30 |
acoles | notmyname: yes | 21:30 |
notmyname | ok, let's look forward just a little bit... | 21:30 |
clayg | i gotta bounce, I'll catch up on logs! | 21:31 |
notmyname | I'd like to tag a swift release after this feature branch lands | 21:31 |
mattoliverau | clayg: o/ | 21:31 |
notmyname | so 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 21st | 21:32 |
notmyname | that week is the week of the openstack summit in vancouver | 21:32 |
kota_ | ¥o/ | 21:32 |
notmyname | there's a lot of great stuff that's in swift that we'll be able to talk about there :-) | 21:33 |
notmyname | s3api and container sharding | 21:33 |
mattoliverau | That would be huge release | 21:33 |
notmyname | yep | 21:33 |
notmyname | there'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 |
mattoliverau | Yup I'll be there :) | 21:34 |
kota_ | oh, i didn't notice the onboarding session. I'll add it to my schedule | 21:34 |
notmyname | speaking of openstack events, please be sure to sign up for the PTG happening in september in Denver | 21:34 |
notmyname | kota_: it's immediately after the swift project update on thursday | 21:34 |
kota_ | (that means i didn't check the schedule in detail yet :P) | 21:35 |
notmyname | the PTG is $200 right now and the prices will go up at the end of next week | 21:35 |
notmyname | #link https://www.openstack.org/ptg | 21:35 |
notmyname | that's all I had for this week. feature/deep-review update. next swift release. sing up for the ptg | 21:36 |
notmyname | does anyone else have anything for the meeting this week? | 21:36 |
mattoliverau | Also 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 |
notmyname | hmmm | 21:36 |
notmyname | tdasilva should be back next week, too | 21:36 |
kota_ | ah, RedHad summit in Boston this week. | 21:37 |
notmyname | nah, he's on vacation this week | 21:37 |
notmyname | but there is a red hat summit. but in san francisco | 21:37 |
kota_ | oh, really | 21:37 |
mattoliverau | Damn phone auto complete, * try to keep up.. | 21:37 |
kota_ | ok, not in Boston | 21:37 |
kota_ | i saw takashi's activities. he joined it. | 21:38 |
notmyname | thank you for your work on swift. | 21:38 |
notmyname | #endmeeting | 21: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 | |
openstack | Meeting ended Wed May 9 21:38:50 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:38 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.html | 21:38 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.txt | 21:38 |
openstack | Log: http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-05-09-21.05.log.html | 21:38 |
notmyname | ....and we're still in the same channel. I'm not sure if this is great or terrible :-) | 21:39 |
mattoliverau | Breakfast time! | 21:39 |
mattoliverau | Lol | 21:39 |
kota_ | me too1 | 21:39 |
kota_ | too! | 21:39 |
acoles | good night | 21:41 |
*** m_kazuhiro has quit IRC | 21:47 | |
*** saltsa has joined #openstack-swift | 22:11 | |
*** zigo has quit IRC | 22:11 | |
*** zigo has joined #openstack-swift | 22:11 | |
*** mikecmpbll has quit IRC | 22:25 | |
*** mvk has joined #openstack-swift | 22:32 | |
*** threestrands has joined #openstack-swift | 22:33 | |
*** threestrands_ has joined #openstack-swift | 22:36 | |
*** threestrands_ has quit IRC | 22:36 | |
*** threestrands_ has joined #openstack-swift | 22:36 | |
*** threestrands has quit IRC | 22:38 | |
*** zaitcev has quit IRC | 22:46 | |
*** kei_yama has joined #openstack-swift | 23:10 | |
mattoliverau | morning again | 23:17 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!