Hi all, Does kata-agent still send a READY message to the proxy like cc-agent does? Or is the protocol different? Also, would the agent protocol messages be seen on kata.sock in the host, or do they use some other channel? (To clarify, I'm not talking about the agent logs, but rather the protocol buffer messages between the agent and the proxy.) Thanks for any info you can provide. Sincerely, Jesse
Hi Jesse, kata-agent does not send a READY message, the gRPC protocol is internally handling the handshake. Also, for kata-agent, we only need one socket versus cc-agent which was using two different sockets (one for control and one for IO). Thanks, Sebastien ________________________________ From: Larrew, Jesse [Jesse.Larrew@amd.com] Sent: Sunday, April 29, 2018 1:19 PM To: kata-dev@lists.katacontainers.io Subject: [kata-dev] agent <-> proxy protocol Hi all, Does kata-agent still send a READY message to the proxy like cc-agent does? Or is the protocol different? Also, would the agent protocol messages be seen on kata.sock in the host, or do they use some other channel? (To clarify, I’m not talking about the agent logs, but rather the protocol buffer messages between the agent and the proxy.) Thanks for any info you can provide. Sincerely, Jesse
On Mon, Apr 30, 2018 at 4:19 AM, Larrew, Jesse <Jesse.Larrew@amd.com> wrote:
Hi all,
Does kata-agent still send a READY message to the proxy like cc-agent does? Or is the protocol different?
If you need to actively know if agent is up running, there is health.Check() API to do it.
Also, would the agent protocol messages be seen on kata.sock in the host, or do they use some other channel? (To clarify, I’m not talking about the agent logs, but rather the protocol buffer messages between the agent and the proxy.)
There are two cases: 1. if vsock is supported, the messages are present on kata.sock directly. This requires host/guest vsock support and it is still WiP in kata. 2. if vsock is not supported, kata-proxy is spawned to act like a broker for agent calls. The messages going through kata.sock is wrapped over with the yamux protocol (https://github.com/hashicorp/yamux). If you test kata right now, it is always the case at the moment. I think this is the "some other channel" you were asking ;) Cheers, Tao -- bergwolf@hyper.sh
participants (3)
-
Boeuf, Sebastien
-
Larrew, Jesse
-
Tao Peng