Tuesday, 2018-05-08

*** mingyu_ has joined #openstack-swift00:24
*** mingyu has quit IRC00:26
spsuryahi....swifters            can i add new storage node in SAIO installed node ?00:27
claygprobably... I mean... anything is possible.  As with most things you'll find going from 1 -> 2 is harder than going from 2 -> 300:32
claygyou might want to spin up some vms or something and setup a multinode cluster so you know how that *works* - then come up with a plan to migrate whatever setup/tooling you have for this existing setup...00:33
DHEspsurya: well, yes. SAIO just means you are simulating multiple "nodes" by using different TCP ports rather than different IPs.00:43
DHEspsurya: are you still in a 'testing' mode or do you want to actually make this a real redundant installation?00:44
spsuryaDHE: for now I am trying to install swift with SAIO and then create object with/without user then want add new node00:46
spsuryathen want to access that object from new node00:46
spsuryaSo looking for the configuration  regarding ip:port, new device mount points etc00:48
spsuryawhere i have to change00:49
spsuryathanks clayg for I wiil try00:49
DHEis that a bot?00:49
spsuryaDHE: couldn't parse00:50
DHEn/m i'm wrong00:50
DHEadding new storage nodes is half running the services on them and half building/distributing the new ring files to all hosts so they agree it is a cluster member00:52
spsuryaDHE: yes00:56
openstackgerritMerged openstack/slogging master: This commit remove dead link in Readme  https://review.openstack.org/56676200:56
DHEyes.. and SAIO doesn't really change that. you're just running one node that sorta simulates many.00:57
spsuryaDHE: yes01:01
*** gholt has quit IRC01:04
*** bkopilov_ has quit IRC01:35
*** bkopilov__ has quit IRC01:35
*** m_kazuhiro has joined #openstack-swift01:35
m_kazuhirogood morning01:35
kota_notmyname: should i go patch 3-7 in the feature deep patch chain first?01:58
patchbotNo data found for patch 301:58
kota_thanks patchbot for the answer.01:59
*** psachin` has joined #openstack-swift02:13
*** klamath has joined #openstack-swift02:30
*** klamath_ has quit IRC02:33
*** bkopilov_ has joined #openstack-swift02:55
*** bkopilov__ has joined #openstack-swift02:56
*** two_tired has joined #openstack-swift03:05
*** klamath has quit IRC03:18
*** two_tired has quit IRC03:23
notmynamekota_: no, no. I was just using random numbers as examples03:26
*** gyankum has joined #openstack-swift03:41
kota_notmyname: ok :-)03:47
*** gyee has quit IRC03:48
*** m_kazuhiro has quit IRC03:53
*** mingyu_ has quit IRC04:06
*** m_kazuhiro has joined #openstack-swift04:09
*** gyee has joined #openstack-swift04:17
*** gyee has quit IRC04:24
*** cshastri has joined #openstack-swift04:31
*** links has joined #openstack-swift04:38
*** mingyu has joined #openstack-swift05:11
*** klamath has joined #openstack-swift05:18
*** klamath has quit IRC05:37
*** ccamacho has joined #openstack-swift05:41
*** pcaruana has joined #openstack-swift06:01
*** cshastri has quit IRC06:03
*** armaan has joined #openstack-swift06:07
*** klamath has joined #openstack-swift06:11
*** armaan has quit IRC06:11
*** armaan has joined #openstack-swift06:12
*** klamath has quit IRC06:15
*** cshastri has joined #openstack-swift06:19
*** armaan has quit IRC06:24
*** armaan has joined #openstack-swift06:25
*** cshastri has quit IRC06:26
*** mingyu_ has joined #openstack-swift06:37
*** mingyu has quit IRC06:37
*** cshastri has joined #openstack-swift06:41
*** mingyu_ has quit IRC06:42
*** hseipp has joined #openstack-swift06:43
*** rcernin has quit IRC07:08
*** m_kazuhiro has quit IRC07:11
*** armaan has quit IRC07:14
*** klamath has joined #openstack-swift07:25
*** klamath has quit IRC07:29
*** geaaru has joined #openstack-swift07:40
acolesgood morning08:01
acolesI think notmyname's comments in here yesterday are useful input for deep-review reviewers.08:08
acolesI'd add, if anyone core reviewer would like high bandwidth discussion with me (voice/video) then just ask08:08
openstackgerritHCLTech-SSW proposed openstack/swift master: Implemented the fix to handle the HTTP request methods other than GET.  https://review.openstack.org/56680608:10
*** neonpastor has joined #openstack-swift08:31
*** zigo_ has quit IRC08:40
*** linkmark has quit IRC08:41
*** linkmark has joined #openstack-swift08:42
*** zigo has joined #openstack-swift08:45
*** d0ugal__ has quit IRC08:57
*** d0ugal has joined #openstack-swift08:58
*** armaan has joined #openstack-swift09:01
*** armaan has quit IRC09:08
*** gkadam has joined #openstack-swift09:19
*** klamath has joined #openstack-swift09:26
*** klamath has quit IRC09:31
*** mingyu has joined #openstack-swift09:33
*** mingyu has quit IRC09:35
*** mingyu_ has joined #openstack-swift09:35
mattoliverauacoles: I'm doing a diagram for sharding GET.. And just want to clarify. container listing while sharding. If ranges have sharded, then go visit the shard containers. If hitting beyond where cleaving is up to, then just grab the retiring db's records ignore the shards.09:39
*** bkopilov__ has quit IRC09:39
*** bkopilov_ has quit IRC09:39
acolesmattoliverau: correct. specifically, only shard ranges in one of the SHARD_LISTING_STATES https://github.com/openstack/swift/blob/d0424c2dd3e8f9a0fd54f87e9928b8f4cab11d61/swift/container/backend.py#L62 are used for listings - any 'gap' is filled by the retiring db.09:41
acolesmattoliverau: and thanks for working on the diagram!09:42
mattoliverauacoles: ta.. cool, that's what got from reading the code, just wanted to confirm. It's alright the diagram just points to where it looks. I haven't bothered with updating words yet.09:43
*** armaan has joined #openstack-swift10:04
* kota_ is still half of the patch 1 yet :/10:05
patchbothttps://review.openstack.org/#/c/1/ - openstack-infra/system-config - Add puppet module for ssh that installs an sshd_co... (MERGED)10:05
kota_no patchbot!10:05
acoleslol!10:05
kota_but it looks interesting that is the first patch in the openstack world.10:05
acoleskota_ is reviewing openstack from the beggining :)10:05
acolesugh, beginning*10:06
kota_lol10:07
kota_hmm... it's over 7 pm my local time.10:07
kota_let's push my current comments there.10:07
acoleskota_: thanks!10:08
kota_acoles: added10:11
*** kei_yama has quit IRC10:14
* kota_ is preparing to head for my home.10:17
*** mingyu_ has quit IRC10:19
*** rcernin has joined #openstack-swift10:35
mattoliverauacoles: ok, I think I have all the diagrams updated, do you mind if I push up a new version of the docs?10:37
acolesmattoliverau: no, please do - did you base on the changes I pushed yesterday?10:38
mattoliverauI think so.. but let me double check :)10:38
acolescommit 65c46a10:39
acolesmattoliverau: I added list of ShardRange states in that version10:40
mattoliverauJust pulled it elsewhere, the head it 65c46a and when diffed against my new one only a bunch of svg (all xml) is added and some renames in the doc.. so looks good.10:44
acolesmattoliverau: cool, thanks for checking10:44
openstackgerritMatthew Oliver proposed openstack/swift feature/deep-review: Add container sharding documentation  https://review.openstack.org/56574910:46
mattoliveraumake all the digarms continue to build up and so all use the same example data10:47
mattoliverauand I've been editting them in inkscape, which is OSS, in case anyone wants to change anything... or just ask me too :)10:48
mattoliveraukk, time to go spend some time with the family. Night10:48
mattoliverauacoles: let me know if any of the digrams are incorrect10:49
acolesthank mattoliverau10:49
acolesyou!10:49
acolestimburke: if you get chance to comment https://review.openstack.org/#/c/565742/1/swift/common/db.py@41410:53
patchbotpatch 565742 - swift (feature/deep-review) - Refactoring, test infrastructure changes and cleanup10:53
*** mrjk_ has quit IRC11:27
*** mrjk_ has joined #openstack-swift11:28
*** mingyu has joined #openstack-swift11:46
acolesclayg: could you handle timburke's comments here https://review.openstack.org/#/c/565742/1/swift/common/db.py11:50
patchbotpatch 565742 - swift (feature/deep-review) - Refactoring, test infrastructure changes and cleanup11:50
*** cbartz has joined #openstack-swift11:52
*** bkopilov_ has joined #openstack-swift12:25
*** bkopilov__ has joined #openstack-swift12:27
*** Supun has joined #openstack-swift12:41
remix_tjtdasilva: hi, are you still maintaining this? https://github.com/thiagodasilva/ansible-saio i'm having some errors with ansible 2.4.3.0 which i'm fixing and i'd like to provide feedback if the tool is still alive12:47
*** cbartz has quit IRC12:49
*** openstackgerrit has quit IRC12:49
*** gyankum has quit IRC12:53
*** NM has joined #openstack-swift13:03
*** armaan has quit IRC13:05
*** gkadam_ has joined #openstack-swift13:05
*** armaan has joined #openstack-swift13:06
*** gkadam has quit IRC13:07
*** cshastri has quit IRC13:09
*** vinsh_ has joined #openstack-swift13:12
*** vinsh has quit IRC13:12
*** mvenesio has joined #openstack-swift13:13
*** vinsh_ has quit IRC13:14
*** bswrchrd has joined #openstack-swift13:14
*** vinsh has joined #openstack-swift13:14
*** armaan has quit IRC13:23
*** mingyu has quit IRC13:23
*** armaan has joined #openstack-swift13:23
*** klamath has joined #openstack-swift13:28
*** bswrchrd has quit IRC13:32
*** klamath has quit IRC13:32
*** bswrchrd has joined #openstack-swift13:32
*** klamath has joined #openstack-swift13:39
*** NM has quit IRC13:54
*** NM has joined #openstack-swift13:55
*** ccamacho has quit IRC14:00
*** ccamacho1 has joined #openstack-swift14:00
*** ccamacho1 has quit IRC14:00
*** ccamacho has joined #openstack-swift14:00
*** armaan has quit IRC14:07
*** armaan has joined #openstack-swift14:07
*** psachin` has quit IRC14:07
*** mingyu has joined #openstack-swift14:14
*** armaan has quit IRC14:25
*** armaan has joined #openstack-swift14:26
*** geaaru has quit IRC14:31
*** rcernin has quit IRC14:47
*** gyankum has joined #openstack-swift15:00
*** NM has quit IRC15:02
acoles@notmyname and others: I'm wondering how much 'under the hood' detail we want in the sharding docs. I think descriptions of processes and interactions are good but I am inclined to not include much description of code e.g. classes, methods, but rather leave that to docstrings where it is more likely to be maintained. That implies deleting some of the current doc rather than updating it. Any opinions?15:05
*** links has quit IRC15:08
*** cbartz has joined #openstack-swift15:13
*** Supun has quit IRC15:16
*** ukaynar has joined #openstack-swift15:22
*** cbartz has quit IRC15:28
*** Supun has joined #openstack-swift15:33
*** gkadam__ has joined #openstack-swift15:43
*** ukaynar has quit IRC15:44
notmynamegood morning15:44
notmynameacoles: I think that sounds like a good idea (trimming the docs to not have the code docs in there15:44
*** ukaynar has joined #openstack-swift15:46
*** gkadam_ has quit IRC15:46
*** zaitcev has joined #openstack-swift15:49
*** ChanServ sets mode: +v zaitcev15:49
*** ccamacho has quit IRC15:49
*** gyan_ has joined #openstack-swift15:51
notmynameacoles: are you pushing up any more patch set revisions tonight?15:54
*** gyankum has quit IRC15:54
acolesnotmyname: yes, within next hour15:54
notmynameok, thanks15:54
*** openstackgerrit has joined #openstack-swift15:57
openstackgerritGage Hugo proposed openstack/python-swiftclient master: WIP - Migrate to using keystoneauth session  https://review.openstack.org/56013815:57
*** gyee has joined #openstack-swift16:04
*** Supun has quit IRC16:06
*** Supun has joined #openstack-swift16:07
*** SkyRocknRoll has joined #openstack-swift16:25
*** ccamacho has joined #openstack-swift16:28
*** hseipp has quit IRC16:28
zaitcevI was just shown a cluster where one container has sqlite db 23GB long. You've read that right: 23 Gigabytes. Apparently there's no constraint on the number of objects in a container. Should there be? Sharding is on its way, I know, but this is just unreasonable, don't you think?16:30
*** SkyRocknRoll has quit IRC16:33
*** Supun has quit IRC16:35
*** gkadam__ has quit IRC16:42
notmynameeventlet bug filed for the utf8 stuff that came up yesterday https://github.com/eventlet/eventlet/issues/48816:43
*** cshastri has joined #openstack-swift16:45
*** SkyRocknRoll has joined #openstack-swift16:45
*** silor has joined #openstack-swift16:46
*** NM has joined #openstack-swift16:48
*** mingyu has quit IRC16:49
*** mingyu has joined #openstack-swift16:49
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Refactoring, test infrastructure changes and cleanup  https://review.openstack.org/56574216:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add ShardRange class  https://review.openstack.org/56574316:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add support for sharding in ContainerBroker  https://review.openstack.org/56574416:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add shard range support to container server  https://review.openstack.org/56574516:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Enable proxy to build listings from shards  https://review.openstack.org/56574616:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Redirect object updates to shard containers  https://review.openstack.org/56574716:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add sharder daemon, manage_shard_ranges tool and probe tests  https://review.openstack.org/56574816:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep-review: Add container sharding documentation  https://review.openstack.org/56574916:51
notmynamezaitcev: quotas are the only way to control it. otherwise, encourage users to spread objects across containers. and get feature/deep-review landed ;-)16:52
*** gyan_ has quit IRC16:52
*** NM has quit IRC16:53
*** NM has joined #openstack-swift16:55
*** ccamacho has quit IRC16:58
*** ccamacho has joined #openstack-swift16:58
*** geaaru has joined #openstack-swift17:08
*** gyee has quit IRC17:17
*** hseipp has joined #openstack-swift17:18
*** hseipp has quit IRC17:20
*** cshastri has quit IRC17:32
*** geaaru has quit IRC17:36
*** geaaru has joined #openstack-swift17:39
*** jlvillal is now known as jlvacation17:51
*** hseipp has joined #openstack-swift18:06
DHEhttps://docs.openstack.org/swift/latest/deployment_guide.html says "Currently it is recommended to use 3 [replicas] (as this is the only value that has been tested)". Surely that can't be true, right?18:13
notmyname$ git show 9916adb | grep Date18:14
notmynameDate:   Fri Jul 23 17:15:29 2010 -050018:14
notmynameyeah. that's a *bit* dated18:15
DHEgood because I'm considering something like 4 to 8 (replicas, not related to EC)18:17
*** gyee has joined #openstack-swift18:19
*** NM has quit IRC18:24
notmynameas with nearly everything in swift, the answer is "it depends"18:26
notmynamereplicas are great for smaller objects, objects that require lower time-to-first-byte latency, objects frequently accessed, and objects distributed across a wide geographic area18:27
notmynameEC is better for bigger objects that aren't accessed as frequently18:28
notmyname(note that "frequent access" in my mind is measured in req/sec, not "this super popular object is accessed a couple times an hour")18:28
*** SkyRocknRoll has quit IRC18:29
notmynamefor objects that are bigger than about 1MB, EC can give you better efficiency in storage space. with bigger objects, it can give you better speed, if you're otherwise network constrained18:29
notmyname4 replicas may be good for smaller objects stored in a couple of regions18:30
notmynameI'd seriously investigate some edge caching system before putting 8 replicas across 8 regions in a single cluster18:31
notmynamebut again. it all depends18:31
*** psachin` has joined #openstack-swift18:33
*** guimaluf has joined #openstack-swift18:34
*** ukaynar has quit IRC18:35
*** ukaynar has joined #openstack-swift18:35
DHEThe use case I'm looking at is multi-region and the most extensive abuse of composite rings I can possibly perform18:40
DHEso 1-2 replicas per-region18:40
*** ukaynar has quit IRC18:40
*** ukaynar has joined #openstack-swift18:45
zaitcevGuys, have swift-object-info ever worked on container objects? I seem to recall that it did, but now it says "Invalid metadata".18:47
*** openstackgerrit has quit IRC18:49
acoleszaitcev: swift-container-info ?18:57
*** NM has joined #openstack-swift19:20
*** silor has quit IRC19:23
*** hseipp has quit IRC19:28
*** psachin` has quit IRC19:30
tdasilvaremix_tj: i'm still maintaining that repo and would definetely welcome any PRs you may have...20:05
notmynametdasilva: what would you think of including more of that repo in swift upstream?20:16
notmyname(in general, just the idea. not necessarily "import it all in right now")20:17
tdasilvanotmyname: absolutely, i'm all for it, althought not sure what parts you have in mind...20:18
tdasilvabtw..the probe tests ansible scripts was largely a copy of it....20:19
*** pcaruana has quit IRC20:21
notmynameafter sharding lands, I've got some ansible stuff I'd like to propose upstream. mostly a reorg of the probe tests one, but slightly different. related to the swift-in-a-container stuff I was doing20:21
tdasilvaawesome! looking forward to it....20:23
tdasilvanotmyname: it would be cool to do more with the ansible scripts...thinking of multi-node upgrade tests20:24
notmynameyep!20:28
* tdasilva goes back on vacation mode, see you all on monday20:34
*** ianychoi has quit IRC21:15
*** NM has quit IRC21:27
mattoliverauacoles: +1 re doc. All the extra under the hood was to help fellow swift devs understand the POCs.. we probably don't have to be as detailed, cause then we'd have to maintain it21:42
notmynameI just got through all the docs above the "beyond here be dragons" part. looks god21:43
notmyname*good21:43
*** ukaynar has quit IRC21:50
*** rcernin has joined #openstack-swift22:25
*** kei_yama has joined #openstack-swift23:09
*** bkopilov_ has quit IRC23:31
*** bkopilov__ has quit IRC23:32
*** bkopilov__ has joined #openstack-swift23:44
*** bkopilov_ has joined #openstack-swift23:44
*** bkopilov__ has quit IRC23:52
*** bkopilov_ has quit IRC23:52

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