Get desktop application:
View/edit binary Protocol Buffers messages
Controller is the service that workers will connect to to register themselves, and poll for actions to perform. Workers can be behind NAT or firewalls, or not have an IP address. The entire protocol is designed around workers connecting to an controller.
The client will invoke Download when the server requests the client to upload a file.
Client downloads a file from the server, as a result of a processing an ActionDownload.
Poll is the first request performed by the client. It is our main control channel. The client parses loops over the PollResponses, and performs the action requested.
Sent only once, when the client first connects.
Sent periodicially, the server just replies with an ActionPong.
Sent after completing an operation on behalf of the server.
Response to a ClientRegister.
Response to a ClientPing.
Starts an independent session.
Send a file.
Receive a file.
The client will invoke Upload when the server requests the client to upload a file.
Client sends a file to the server, as a result of processing an ActionUpload.
required in the first request only.
optional. If it is provided, it is processed in the first request only.
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
Used in:
Not implemented yet - TODO: at enrollment time, a certificate is issued. The token is generated from the certificate, the name and tags become obsolete.
Name of the machine.
Tags assigned to this machine.
IP Addresses to be allocated to the node
Used in:
(message has no fields)