Tuesday, 2021-02-09

« Monday, 2021-02-08 Index Wednesday, 2021-02-10 »
*** snir__ has quit IRC00:28
*** snir__ has joined #kata-dev00:29
*** amorenoz has quit IRC01:16
*** openstack has joined #kata-dev01:21
*** ChanServ sets mode: +o openstack01:21
*** egernst has quit IRC02:09
*** egernst has joined #kata-dev02:13
*** egernst has quit IRC02:17
*** egernst has joined #kata-dev02:31
*** egernst has quit IRC02:35
*** egernst has joined #kata-dev02:36
*** egernst has quit IRC02:40
*** fuentess has quit IRC02:49
kata-irc-bot<prabushyam> I am new to Kata and I am trying to have a kubernetes container process inside the vm connect to a process on the host using UDS (Kata 1.10.2 with qemu). Does Kata support UDS connection between a host process and a vm process?03:02
*** egernst has joined #kata-dev03:04
kata-irc-bot<eric.ernst> UDS is specific to the host it runs on (guest in your case).03:19
kata-irc-bot<eric.ernst> If you utilize a network connection you should be fine.03:20
kata-irc-bot<eric.ernst> Make sense, @prabushyam ?03:20
*** snir__ has quit IRC03:23
*** snir__ has joined #kata-dev03:24
*** iamweswilson has quit IRC03:26
*** iamweswilson has joined #kata-dev03:29
*** amorenoz has joined #kata-dev03:53
*** amorenoz has quit IRC04:01
*** amorenoz_ has joined #kata-dev04:01
*** egernst has quit IRC04:21
*** egernst has joined #kata-dev04:22
*** egernst has quit IRC04:27
*** angryangryhog has quit IRC04:29
kata-irc-bot<sureshv> you mean network connection using host ip?04:35
kata-irc-bot<sureshv> uds is specific to host where vm is running04:49
kata-irc-bot<sureshv> ```libnsock msevent_new(): msevent_new (IOD #1) (EID #8) libnsock nsock_connect_unixsock_stream(): UNIX domain socket (STREAM) connection requested to agent.sock (IOD #1) EID 8 libnsock nsp_add_event(): NSE #8: Adding event libnsock nsock_trace_handler_callback(): Callback: CONNECT ERROR [Connection refused (111)] for EID 8 [agent.sock]```04:51
kata-irc-bot<sureshv> process inside VM try to connect to process in the host via uds04:52
kata-irc-bot<sureshv> @eric.ernst04:52
*** egernst has joined #kata-dev05:01
*** egernst has quit IRC05:09
*** egernst has joined #kata-dev05:13
*** egernst has quit IRC05:18
kata-irc-bot<eric.ernst> Right. I don’t expect that to work.05:45
*** egernst has joined #kata-dev05:49
*** egernst_ has joined #kata-dev05:50
*** egernst__ has joined #kata-dev05:52
*** egerns___ has joined #kata-dev05:54
*** egernst has quit IRC05:54
*** egernst_ has quit IRC05:55
*** egernst__ has quit IRC05:57
kata-irc-bot<sureshv> *egernst*  [7:20 PM] If you utilize a network connection you should be fine.06:02
kata-irc-bot<sureshv> you mean use the host IP here?06:02
kata-irc-bot<sureshv> and not uds06:03
kata-irc-bot<sureshv> ?06:03
kata-irc-bot<eric.ernst> right, a unix domain socket is for inter process, on the same host (kernel).06:39
kata-irc-bot<eric.ernst> ie, if you had two processes running on two differnet machines, they coudln't communicate via UDS.06:39
kata-irc-bot<eric.ernst> That's what you're hitting.06:39
kata-irc-bot<eric.ernst> you want something like a tcp socket instead.06:40
kata-irc-bot<sureshv> we are not referring to 2 different hosts here06:42
kata-irc-bot<sureshv> [Host A --> VM in host A]06:42
kata-irc-bot<sureshv> VM in host A accessing underlying host A uds06:44
kata-irc-bot<sureshv> i see you point, they both are different kernel (vm kernel and host kernel) and cannot be share06:45
kata-irc-bot<sureshv> https://github.com/firecracker-microvm/firecracker/blob/master/docs/vsock.md06:53
*** egerns___ has quit IRC07:05
*** egernst has joined #kata-dev07:05
*** egernst has quit IRC07:11
*** egernst has joined #kata-dev07:13
*** egernst has quit IRC07:17
*** dklyle has quit IRC07:35
*** egernst has joined #kata-dev07:53
*** egernst has quit IRC08:02
*** fgiudici has joined #kata-dev08:05
*** sgarzare has joined #kata-dev08:18
kata-irc-bot<fidencio> Hey all, Today's AC meeting has been cancelled!  The backlog review meeting is still up!08:22
*** sameo has joined #kata-dev08:53
kata-irc-bot<fidencio> @james.o.hunt, @aadam, the bot seems to be labeling the issues in the wrong way, and that may be the reason of the discussion we had Yesterday. Take a look at those two pictures.  One shows that when I click on the labels, no label is selected at all, although the issue has a few (at least the "needs-review") ones.  Then when I select a label that's already present in the issue, it just removes the other ones.09:01
*** davidgiluk has joined #kata-dev09:02
*** ailan_ has joined #kata-dev09:03
*** ailan_ has quit IRC09:03
kata-irc-bot<aadam> So this is also something we encountered when reviewing the issues on part of the repositories. What we did was kind of remember what the labels where to start with. Then when we removed the needs-review everything was removed and we manually added back the original ones. I'm less familiar with the github black magic ;)09:09
*** sgarzare_ has joined #kata-dev09:12
*** sgarzare has quit IRC09:14
*** jodh has joined #kata-dev09:38
kata-irc-bot<fidencio> Yeah, the workaround helps, but I'm afraid something is wrong deep down the logic of our bot.09:40
*** brueckner has joined #kata-dev10:34
*** egernst has joined #kata-dev10:38
*** egernst has quit IRC10:43
*** ailan has joined #kata-dev11:46
*** sameo has quit IRC12:21
*** egernst has joined #kata-dev12:39
*** egernst has quit IRC12:44
*** sameo has joined #kata-dev12:57
*** devimc has joined #kata-dev13:16
*** egernst has joined #kata-dev13:38
*** egernst has quit IRC13:42
*** fuentess has joined #kata-dev13:54
*** ailan_ has joined #kata-dev13:55
*** ailan has quit IRC13:58
*** fuentess has quit IRC14:14
*** fuentess has joined #kata-dev14:14
*** crobinso has joined #kata-dev14:14
*** pcaruana has joined #kata-dev14:24
*** fuentess has quit IRC14:25
*** fuentess has joined #kata-dev14:26
*** devimc has quit IRC14:49
*** devimc has joined #kata-dev14:50
*** egernst has joined #kata-dev15:00
*** egernst has quit IRC15:01
*** egernst has joined #kata-dev15:01
*** egernst has quit IRC15:31
*** egernst has joined #kata-dev15:32
*** egernst has quit IRC15:37
*** dklyle has joined #kata-dev15:38
*** Val has joined #kata-dev16:01
ValHi16:01
*** egernst has joined #kata-dev16:03
ValJust saw issue #1367 (kata 2+ Installation for Debian 10). Has anyone started kata 2+ Debian packaging or should we start from the current version and try to update every components ?16:07
*** ailan__ has joined #kata-dev16:20
*** ailan_ has quit IRC16:22
*** crobinso has quit IRC16:37
*** egernst has quit IRC17:06
*** egernst has joined #kata-dev17:07
*** brueckner has quit IRC17:36
*** sgarzare_ has quit IRC17:52
*** davidgiluk has quit IRC17:52
*** jodh has quit IRC18:03
*** davidgiluk has joined #kata-dev18:16
*** davidgiluk has quit IRC18:20
*** Val has left #kata-dev19:47
*** crobinso has joined #kata-dev20:09
*** ailan__ has quit IRC20:26
*** fgiudici has quit IRC20:33
*** dklyle has quit IRC20:39
*** dklyle has joined #kata-dev20:39
*** egernst has quit IRC20:39
*** egernst_ has joined #kata-dev20:40
*** egernst_ has quit IRC20:45
*** devimc has quit IRC21:00
*** sameo has quit IRC21:00
*** devimc has joined #kata-dev21:01
*** fuentess has quit IRC21:13
*** fuentess1 has joined #kata-dev21:13
*** egernst has joined #kata-dev21:15
*** fuentess1 has quit IRC21:20
*** fuentess1 has joined #kata-dev21:20
*** crobinso has quit IRC21:40
*** devimc has quit IRC22:01
« Monday, 2021-02-08 Index Wednesday, 2021-02-10 »

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!