Wednesday, 2018-07-25

openstackgerritMerged openstack/python-swiftclient master: Remove unnecessary calls to parse_header_string().  https://review.openstack.org/58551500:25
notmynameswiftclient release tag request made: https://review.openstack.org/#/c/585575/01:05
patchbotpatch 585575 - releases - python-swiftclient 3.6.001:05
openstackgerritNguyen Hai proposed openstack/swift master: add lower-constraints job  https://review.openstack.org/55625501:16
*** links has joined #openstack-swift01:30
timburkeyay! https://review.openstack.org/#/c/585568/ shows all clear!01:39
patchbotpatch 585568 - swift - Lower the required version of ipaddress01:39
timburkeprobetests are still good01:40
*** gyee has quit IRC01:55
openstackgerritTim Burke proposed openstack/swift master: Add support for multiple root encryption secrets  https://review.openstack.org/57787402:04
kota_morning02:13
kota_tdasilva: could you have a time to look at https://review.openstack.org/#/c/447129/ ?02:13
patchbotpatch 447129 - swift - Configure diskfile per storage policy02:13
*** m_kazuhiro has joined #openstack-swift02:13
kota_i briefly looked at the patch yesterday and i'm realizing i'd like to hear your opinion,02:14
kota_that patch attempt to involve the diskfile extension for losf but IIRC you already maintains custom diskfile on swift-on-file.02:15
kota_if that patch helps your swift-on-file project, that would be nice to have but I'm not sure the technic (e.g. configuration format) would be nicer for swift-on-file way.02:16
timburkeyay! thanks for looking at p 578075, mattoliverau! now i need to propose a follow-on to p 577874 to make the kmip keymaster multi-key too...02:30
patchbothttps://review.openstack.org/#/c/578075/ - swift - Add keymaster to fetch root secret from KMIP service02:30
patchbothttps://review.openstack.org/#/c/577874/ - swift - Add support for multiple root encryption secrets02:30
*** StevenK has quit IRC02:35
*** StevenK has joined #openstack-swift02:35
*** seongsoocho has joined #openstack-swift02:52
*** kei_yama has quit IRC03:07
*** armaan has joined #openstack-swift03:13
openstackgerritMerged openstack/swift master: Add keymaster to fetch root secret from KMIP service  https://review.openstack.org/57807503:49
*** psachin` has joined #openstack-swift04:00
*** psachin`` has joined #openstack-swift04:06
*** psachin` has quit IRC04:07
*** armaan has quit IRC04:19
*** armaan has joined #openstack-swift04:20
*** armaan has quit IRC04:56
*** armaan has joined #openstack-swift04:56
*** armaan has quit IRC05:17
*** armaan has joined #openstack-swift05:18
*** armaan has quit IRC05:32
*** armaan has joined #openstack-swift05:32
*** hoonetorg has quit IRC06:01
*** armaan has quit IRC06:04
*** armaan has joined #openstack-swift06:05
*** ccamacho has joined #openstack-swift06:09
*** cshastri has joined #openstack-swift06:14
*** hoonetorg has joined #openstack-swift06:17
*** armaan has quit IRC06:22
*** armaan has joined #openstack-swift06:22
*** psachin`` has quit IRC06:24
*** pcaruana has joined #openstack-swift06:33
*** rcernin has quit IRC06:59
*** armaan has quit IRC07:09
*** armaan has joined #openstack-swift07:10
*** armaan has quit IRC07:14
*** gkadam has joined #openstack-swift07:16
*** tesseract has joined #openstack-swift07:16
*** DHE has quit IRC07:24
*** DHE has joined #openstack-swift07:25
*** geaaru has joined #openstack-swift07:26
*** geaaru_ has joined #openstack-swift07:27
*** geaaru_ has quit IRC07:40
seongsoochoHi. Is there a way to change the storage policy to existing container?07:44
mattoliverauseongsoocho: not that the moment. There is work on policy migration but it hasn't landed yet. There are some cowboy ways you can try and do it, involving changing the policy manaully in the container (editing the sqlite dbs) and waiting for the reconciler to work trhough them.07:47
seongsoochomattoliverau:  oh I got it.  To changing the policy manually is not dangerous? I think it might be rollback by replicator.07:50
mattoliverauoh I'm sure it could be considered dangerous, which is why policy migration is worked on.08:01
*** mikecmpbll has joined #openstack-swift08:01
kota_it's hard problem to change the policy in the working real cluster, I'm sure.08:03
openstackgerritRomain LE DISEZ proposed openstack/swift master: Configure diskfile per storage policy  https://review.openstack.org/44712908:03
kota_it's not just a db change but also it requires data translation if you want to change it from replication to something like EC.08:04
*** armaan has joined #openstack-swift08:05
seongsoochokota_:  Yes that's right. When i change db, the existed data is a problem. Because I will  make new storage policy with new ring.08:06
mattoliverauseongsoocho: yeah, it's better to start with a new policy and a new container. Then if required migrate things, or just start using the new container and refer back to the old one when needed. You could also use symlinks for the older objects with you didn't need to or want to move them.08:14
mattoliverauie, space isn't the issue08:14
*** stephen_m has joined #openstack-swift08:20
*** rcernin has joined #openstack-swift08:29
*** stephen_m has quit IRC08:37
*** stephen_m has joined #openstack-swift08:38
*** armaan has quit IRC08:46
*** armaan has joined #openstack-swift08:47
*** openstackgerrit has quit IRC08:48
*** armaan has quit IRC08:51
*** armaan has joined #openstack-swift09:11
*** notmyname has quit IRC09:16
*** notmyname has joined #openstack-swift09:17
*** ChanServ sets mode: +v notmyname09:17
*** armaan has quit IRC09:26
*** armaan has joined #openstack-swift09:26
*** armaan has quit IRC09:30
*** d0ugal has joined #openstack-swift09:36
*** d0ugal has quit IRC09:36
*** d0ugal has joined #openstack-swift09:36
*** m_kazuhiro has quit IRC09:37
*** lifeless has quit IRC09:37
*** openstackgerrit has joined #openstack-swift09:48
openstackgerritAlexander Bolshakov proposed openstack/python-swiftclient master: Fix update when PUT on containers not allowed  https://review.openstack.org/58532509:48
openstackgerritRomain LE DISEZ proposed openstack/swift master: Configure diskfile per storage policy  https://review.openstack.org/44712910:08
*** d0ugal has quit IRC10:21
*** kukacz_ has quit IRC10:23
*** kukacz_ has joined #openstack-swift10:23
*** lifeless has joined #openstack-swift10:23
*** armaan has joined #openstack-swift10:45
*** armaan has quit IRC10:55
*** armaan has joined #openstack-swift10:56
*** armaan has quit IRC10:56
*** armaan has joined #openstack-swift11:07
*** rcernin has quit IRC11:21
*** armaan has quit IRC11:27
*** armaan has joined #openstack-swift11:27
*** armaan has quit IRC11:29
*** armaan has joined #openstack-swift11:30
*** ccamacho has quit IRC11:38
*** ccamacho has joined #openstack-swift11:44
*** armaan has quit IRC12:03
*** armaan has joined #openstack-swift12:04
*** armaan has quit IRC12:06
*** armaan has joined #openstack-swift12:07
*** armaan has quit IRC12:11
*** armaan has joined #openstack-swift13:18
*** armaan has quit IRC13:25
*** d0ugal has joined #openstack-swift13:28
*** d0ugal has quit IRC13:45
*** armaan has joined #openstack-swift14:17
*** armaan_ has joined #openstack-swift14:19
*** armaan has quit IRC14:21
*** stephen_m has quit IRC14:29
*** armaan_ has quit IRC14:31
*** armaan has joined #openstack-swift14:32
*** armaan has quit IRC14:32
*** links has quit IRC14:33
*** stephen_m has joined #openstack-swift14:35
*** armaan has joined #openstack-swift14:37
*** armaan has quit IRC14:42
*** pcaruana has quit IRC14:52
*** armaan has joined #openstack-swift15:02
*** armaan has quit IRC15:14
*** armaan has joined #openstack-swift15:14
*** armaan has quit IRC15:14
*** cshastri has quit IRC15:16
*** gyee has joined #openstack-swift15:29
*** armaan has joined #openstack-swift15:29
*** kei-ichi has quit IRC15:45
*** kei-ichi has joined #openstack-swift15:46
*** itlinux has joined #openstack-swift15:49
timburkegood morning15:50
notmynamegood morning15:51
*** gkadam has quit IRC15:52
*** armaan has quit IRC15:58
*** armaan has joined #openstack-swift15:58
*** armaan has quit IRC15:59
*** armaan has joined #openstack-swift16:00
DHEis 135 hard drives on a single object server too much? (somewhat serious question... it's a machine with 3x 45-drive enclosures attached)16:00
timburkei think the largest i've heard about previously was 90... 135 seems like a lot... but what do i know?16:03
notmynameDHE: it's not what I'd choose ;-)16:03
DHE90 in a chassis with both server+disks is the most I've seen in that form factor. This is more retrofitting an existing machine into an object storage server. It's a 1U server + 3 external enclosures16:04
notmynameup to a point, it's a matter of drive:core ratios16:05
DHEdual socket 8-core HT intels16:05
notmynamenormally the highest ratio I've seen is 4:116:05
DHEwell that's ~8:1, or 4.2:1 if you consider hyperthreads to be cores16:06
timburkei'd really worry about not having enough resources per drive. 135 spindles gets you a lot of disk IO, so you'll almost certainly have a bottleneck at the NIC. xfs inode cache for all those drives is going to put a lot of strain on your memory, too. and yeah, gotta worry about having enough cycles for all those processes16:08
*** ccamacho has quit IRC16:12
DHEand it would probably do double duty as a proxy... ugh...16:13
DHEmaybe I'll get some 1U server for each enclosure then..16:14
timburkehow many boxes in the cluster? was it just going to be the one otherwise?16:15
*** armaan has quit IRC16:16
DHEI'm still in the planning and business case phase. I have my eyes on this machine, two more with 90 drives, and two more with ~30 drives. Most will be located in various different cities as a sort of CDN16:16
*** armaan has joined #openstack-swift16:16
DHEthese machines already exist and will be (slowly) repurposed16:16
*** mikecmpbll has quit IRC16:33
openstackgerritOpenStack Release Bot proposed openstack/python-swiftclient master: Update reno for stable/rocky  https://review.openstack.org/58582316:51
*** tesseract has quit IRC16:53
zaitcevGuys17:02
zaitcevOur object auditor does not check for dark data, does it?17:02
zaitcevI mean, it does not do any get_info() things versus container and account.17:02
timburkenope, don't believe so17:02
zaitcevIt does not even know where your memcacheds are...17:03
zaitcevJust making sure, because often I read the code and miss the obvious.17:03
zaitcevSo, here's a problem17:03
timburkemight be an interesting application for https://review.openstack.org/#/c/212824/ ...17:04
patchbotpatch 212824 - swift - Let developers/operators add watchers to object audit17:04
zaitcevI know someone who has a cluster, 4 nodes with 12 6TB drives. So, about 90TB, replication is 3.17:04
zaitcevThey put it in a corner and left it rot until it started falling apart.17:05
zaitcevI found that a while back a few drives overflowed. When that happens, XFS can sometimes detect internal inconsistency and then it panics. When it does so, it marks the mount as suspect and all I/O to that volume returns EIO.17:06
zaitcevThe idea is to let the administrator unmount and remount it, so the kernel does fsck.17:06
zaitcevIt's a kernel 3.x, which is pretty ancient stuff that we shipped in RHEL 7.17:07
zaitcevThe bad part is, their drives stayed locked like this for a very long time, and remember that they were overflowed. Basically, completely frozen. When they tried to delete some objects, nothing happened to them.17:08
zaitcevYou see where this is going17:08
zaitcevOnce they rebooted - months since the overflow and Oops, possibly, the old data all came back17:09
zaitcevWell, at least I'm concerned that it did17:09
zaitcevAnd, I'm afraid it came back as dark data, because all the tombstones and container entries were cleared out long time ago at the working part of the cluster.17:10
zaitcevI'm thinking about hacking the auditor to find how much dark data they have now.17:11
timburkeyeah, that seems likely. if even one replica accepted the delete, the container would've gotten updated and that update would get replicated separately...17:11
timburkei feel like clayg may have hacked something together to look for dark data before...17:11
zaitcevYeah17:12
zaitcevIn my friend's case it's a well founded concern, I think.17:12
zaitcevI had some on my testbed in the lab, but that might be caused by some of my PUT+POST and other test patches not working right.17:13
claygugh, swift-integrity, it's about as elegant as one might imagine - would take some work to get it out on a license17:13
*** bharath1234 has joined #openstack-swift17:14
*** itlinux has quit IRC17:47
*** itlinux has joined #openstack-swift17:51
*** juggsmcb has joined #openstack-swift17:58
*** juggsmcb has quit IRC18:01
*** geaaru has quit IRC18:06
*** rcernin has joined #openstack-swift18:09
*** kazsh has quit IRC18:52
*** kazsh has joined #openstack-swift18:52
*** rcernin has quit IRC18:53
*** kota_ has quit IRC18:54
*** ktsuyuzaki has joined #openstack-swift18:54
*** ChanServ sets mode: +v ktsuyuzaki18:54
*** rcernin has joined #openstack-swift19:10
*** d0ugal has joined #openstack-swift19:11
*** rcernin has quit IRC19:16
*** bharath1234 has quit IRC19:19
*** d0ugal has quit IRC19:46
tdasilvais there are meeting today?19:56
notmynametdasilva: ya, but I think it should be brief19:57
tdasilvaack19:59
openstackgerritJohn Dickinson proposed openstack/swift master: added docker test target tools  https://review.openstack.org/57746720:20
timburkeoh yeah, we should totally go land https://review.openstack.org/#/c/585568/ -- probe tests pass again!20:23
patchbotpatch 585568 - swift - Lower the required version of ipaddress20:23
notmynamenice!20:23
notmynamealso, we should make probe tests voting20:23
timburkeyeah, we definitely seem to be getting pretty good signal from them20:24
ktsuyuzakimorning20:52
notmynamehello ktsuyuzaki20:53
ktsuyuzakioh, my nick was changed...20:53
notmynameI see that20:53
ktsuyuzakihello notmyname20:53
notmynameyou lose your password or soemthing?20:53
*** ktsuyuzaki is now known as kota_20:54
kota_no?20:54
notmynamelol20:54
notmynameok :-)20:54
notmynameoh, I was just wondering why you chnged your nick. I'm fine either way :-)20:54
kota_I may have to check my irc bouncer (or irc client) configuration20:55
notmynamekota_: you were on vacation, right? I hope it was relazing20:56
notmyname*relaxing20:56
kota_notmyname: yes, in the last whole week. it was completely fine to me.20:57
*** m_kazuhiro has joined #openstack-swift20:58
notmynameswift team meeting time in #openstack-meeting20:59
*** openstackgerrit has quit IRC21:04
*** mrjk has quit IRC21:05
*** mrjk has joined #openstack-swift21:06
*** m_kazuhiro has quit IRC21:27
*** itlinux has quit IRC21:31
*** itlinux has joined #openstack-swift21:36
tdasilvagotta love it...so...to install python-pip in centos7, there's a dependency on python-ipaddress which as timburke mentioned centos ships 1.0.16, but then to install python-openstackclient, that has a dependency on 1.0.17 and everthing fails21:44
timburkewhomp whomp21:45
timburkethe crazy thing (to me) is that *we installed 1.0.22*: http://logs.openstack.org/74/577874/4/check/swift-probetests-centos-7/8f8a67c/job-output.txt.gz#_2018-07-25_02_10_02_45054821:47
tdasilvayep! really crazy!21:47
timburkebut then we somehow still got stuck with the system package21:47
timburkeit was stuff like that that made me avoid adding a dep on ipaddress in https://review.openstack.org/#/c/581906/ ... but swift already had ipaddress as a transitive dep via cryptography21:51
patchbotpatch 581906 - python-swiftclient - Add more validation for ip_range args21:51
tdasilvatimburke: i think i figured it out for my ansible script. with centos I guess we are not supposed to use the epel repo anymore and should just use the cloud sig repo now21:52
tdasilvatimburke: current one being: centos-release-openstack-queens21:53
tdasilvai don't think we need this anymore: https://github.com/openstack/swift/blob/master/tools/playbooks/saio_single_node_setup/install_dependencies.yaml#L18,L4221:55
tdasilvaneed to test...21:55
timburkeoh good! i didn't exactly like doing https://github.com/openstack/swift/commit/37dafa021:58
*** openstackgerrit has joined #openstack-swift22:08
openstackgerritThiago da Silva proposed openstack/swift master: Remove contentdir hack  https://review.openstack.org/58589422:08
openstackgerritThiago da Silva proposed openstack/swift master: make probe tests voting in the gate  https://review.openstack.org/58590022:19
*** eandersson has quit IRC22:22
*** eandersson has joined #openstack-swift22:24
*** itlinux has quit IRC22:25
*** mtreinish has quit IRC22:33
*** mtreinish has joined #openstack-swift22:36
*** ukaynar_ has joined #openstack-swift23:00
*** stephen_m has quit IRC23:06
*** mikecmpbll has joined #openstack-swift23:07
*** kei_yama has joined #openstack-swift23:08
openstackgerritTim Burke proposed openstack/swift master: Remove some unnecessary SkipTests  https://review.openstack.org/58591023:15
*** itlinux has joined #openstack-swift23:44
mattoliveraumorning... again23:47
*** ukaynar_ has quit IRC23:54
*** ukaynar has joined #openstack-swift23:55
notmynameonce upon a time, we partially implemented containers as having an internal uuid with an external human-readable name. this allowed for renaming containers without copying all the data. we later abandoned the idea after we couldn't figure out some consistency issues23:56
*** ukaynar has quit IRC23:56
*** ukaynar has joined #openstack-swift23:56
notmynamehowever, given than we've done crazy stuff since then, like fast POST, it makes me wonder if such a thing would be possible, given enough time to think about it23:56
notmynamecertainly it's waaay down on a list of important stuff to do next, but still... I wonder if it's possible23:57

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