Saturday, 2018-07-28

*** gyee has quit IRC00:05
*** itlinux has joined #openstack-swift00:33
timburkeso i know we've established a precedent of subclassing the trivial/insecure KeyMaster implementation, first in KmsKeyMaster and now KmipKeyMaster... how committed are we to leaving that open for 3rd party libs?00:35
timburke'cause i'm realizing that i *really* don't like having https://github.com/openstack/swift/blob/2.18.0/swift/common/middleware/crypto/keymaster.py#L130-L137 in _get_root_secret... it seems like some pretty horrible conflation of concerns...00:36
*** itlinux_ has joined #openstack-swift00:54
*** linkmark has quit IRC00:54
*** itlinux_ has quit IRC00:55
*** itlinux_ has joined #openstack-swift00:55
*** itlinux_ has quit IRC00:55
*** itlinux__ has joined #openstack-swift00:56
*** zaitcev has quit IRC01:18
*** openstackstatus has quit IRC01:46
*** prasen has joined #openstack-swift01:48
*** openstackstatus has joined #openstack-swift01:49
*** ChanServ sets mode: +v openstackstatus01:49
*** hoonetorg has quit IRC01:49
*** hoonetorg has joined #openstack-swift02:06
*** ianychoi has quit IRC02:11
*** hoonetorg has quit IRC02:19
*** ianychoi has joined #openstack-swift03:22
*** nguyenhai_ has joined #openstack-swift04:50
*** nguyenhai has quit IRC04:53
*** links has joined #openstack-swift05:02
*** itlinu___ has joined #openstack-swift06:08
*** itlinu___ has quit IRC06:13
*** ccamacho1 has quit IRC06:35
*** gkadam has joined #openstack-swift06:43
*** silor has joined #openstack-swift06:48
*** silor has quit IRC07:16
*** prasen has quit IRC07:54
*** hoonetorg has joined #openstack-swift08:47
*** geaaru_ has joined #openstack-swift08:49
*** geaaru has quit IRC08:51
*** mikecmpbll has joined #openstack-swift09:03
*** prasen has joined #openstack-swift09:26
*** silor has joined #openstack-swift11:40
*** linkmark has joined #openstack-swift11:42
*** geaaru__ has joined #openstack-swift11:45
*** geaaru_ has quit IRC11:46
*** hoonetorg has quit IRC11:49
*** hoonetorg has joined #openstack-swift11:54
*** hoonetorg has quit IRC12:22
*** hoonetorg has joined #openstack-swift12:33
*** silor has quit IRC12:57
*** silor has joined #openstack-swift12:58
*** silor has quit IRC13:25
*** mvenesio has joined #openstack-swift14:10
*** prasen has quit IRC14:11
mvenesiohi guys14:14
mvenesiocan i decrease the replica size on a running cluster, without affect the service ?14:18
*** silor has joined #openstack-swift14:19
mvenesiowe have a cluster almost at 98%14:19
mvenesioanother question is, do you think that adding more nodes at this moment can move the data in some way can increase the disk utilization temporary that fill the cluster up14:32
*** links has quit IRC14:49
*** silor has quit IRC14:59
*** silor1 has joined #openstack-swift14:59
*** silor1 is now known as silor15:01
DHEfor replication based storage policies you can reduce the replica factor, including fractions if you just want to buy some space...15:03
DHEbut... you want to add more storage nodes only temporarily?15:05
*** prasen has joined #openstack-swift15:23
*** itlinux has quit IRC15:29
*** gkadam has quit IRC15:58
DHEmvenesio: ^^16:42
*** nicodemus_ has joined #openstack-swift16:46
*** silor has quit IRC16:54
mvenesioDHE: no, i will add more nodes forever of course, but the question is, if adding more nodes to a zone can create temporary items in the nearly full nodes that the zone already have17:15
*** nguyenhai_ has quit IRC17:20
*** nguyenhai_ has joined #openstack-swift17:20
*** nicodemus_ has quit IRC17:22
DHEwell the ring builder will move some data off current nodes to the new nodes, and then the replicators will actually do the data migrations17:24
DHEbut for a little while space usage will be increased globally since there will be n+1 copies of objects for a little while as replication runs before the old locations delete their copies17:24
DHEmake sense?17:25
mvenesioDHE: yes make sense but the problem is, this can full fill my disks completely17:36
DHEyes that is a distinct possibility.17:38
mvenesioDHE: and can i delete something manually ?17:40
mvenesiolike the.ts17:40
DHEthe .ts is a tombstone. it should be 0 bytes and deleting it wouldn't save any substantial space17:42
DHEin fact it can increase disk usage becaues the replication system depends on it to not accidentally replicate a full object back into place of a deleted object17:43
mvenesioI can prevent in some way, that in the rebalance the discs that are now at 98%, fill up completely17:45
DHEnothing comes to mind. I believe the ring builder will strictly move data onto the new hard drives, but you can't prevent, for example, if some hard drive dies during the process the handoff disk could be a full disk17:47
*** prasen has quit IRC18:17
*** geaaru_ has joined #openstack-swift18:19
*** geaaru__ has quit IRC18:21
*** hoonetorg has quit IRC18:27
*** mvenesio has quit IRC18:30
*** mvenesio has joined #openstack-swift18:41
mvenesioDHE: thanks for your help18:42
mvenesioi'm adding the new nodes and see go it goes18:42
*** mvenesio has quit IRC19:12
*** itlinux has joined #openstack-swift19:16
*** armaan has joined #openstack-swift19:20
*** geaaru__ has joined #openstack-swift19:25
*** geaaru_ has quit IRC19:28
*** silor has joined #openstack-swift19:45
*** ^andrea^ has joined #openstack-swift20:07
*** itlinux has quit IRC20:07
*** itlinux has joined #openstack-swift20:10
*** silor has quit IRC20:16
*** nguyenhai93 has joined #openstack-swift20:59
*** nguyenhai_ has quit IRC21:02
*** ^andrea^ has quit IRC21:29
*** armaan has quit IRC21:32
*** armaan has joined #openstack-swift21:32
*** ejat has quit IRC21:36
*** armaan has quit IRC21:37
*** itlinux__ has quit IRC21:37
*** ^andrea^ has joined #openstack-swift21:40
*** geaaru__ has quit IRC22:26
*** mikecmpbll has quit IRC23:48

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