Saturday, 2018-12-08

*** openstack has quit IRC00:12
*** openstack has joined #kata-dev00:18
*** ChanServ sets mode: +o openstack00:18
*** shrasool has joined #kata-dev00:28
*** eernst has joined #kata-dev01:48
*** eernst has quit IRC01:54
*** eernst has joined #kata-dev01:54
*** eernst has quit IRC02:13
*** shrasool has quit IRC02:38
*** shrasool has joined #kata-dev11:31
*** shrasool has quit IRC11:51
*** shrasool has joined #kata-dev11:55
*** shrasool has quit IRC12:15
*** shrasool has joined #kata-dev13:11
*** shrasool has quit IRC13:31
kata-irc-bot<xu> I thought the PR didn’t change the default behavior.  On the other hand, from a cloud provider’s view, I don’t think we should add any extra local cache layer for a container, i.e. once a user got the ack that the block had been written down to the disk, the block should be written (either locally or to multiple replicas). Otherwise, a power-loss or other failure may cause unexpected data loss.13:52
*** dklyle has quit IRC15:49
*** shrasool has joined #kata-dev16:46
*** shrasool_ has joined #kata-dev17:34
*** shrasool has quit IRC17:35
*** shrasool_ is now known as shrasool17:35
*** shrasool has quit IRC17:44
*** shrasool has joined #kata-dev18:55
*** shrasool has quit IRC19:34
*** dklyle has joined #kata-dev19:36
*** shrasool has joined #kata-dev20:07
*** shrasool has quit IRC20:56
*** eernst has joined #kata-dev21:02
*** eernst has quit IRC21:08
*** shrasool has joined #kata-dev21:21
*** shrasool has quit IRC21:37
*** shrasool has joined #kata-dev21:42
*** eernst has joined #kata-dev21:43
*** shrasool has quit IRC21:49
*** eernst has quit IRC23:08
*** dklyle has quit IRC23:11
*** shrasool has joined #kata-dev23:28
*** shrasool has quit IRC23:59

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