Terminology¶
vPoller Proxy
- ZeroMQ proxy which distributes tasks and load balances client
requests. The application running the
vPoller Proxy
isvpoller-proxy
. vPoller Worker
- Worker application which processes tasks, such as discovery and
polling of vSphere object properties. The
vPoller Worker
receives new tasks for processing from thebackend
endpoint of avPoller Proxy
. The application running thevPoller Worker
isvpoller-worker
. vPoller Client
- Client application used for sending task requests and receiving
of results. The
vPoller Client
sends task requests to thefrontend
endpoint of avPoller Proxy
. The application running thevPoller Client
isvpoller-client
andvpoller-cclient
, which is the client application written in C. vSphere Agent
- The
vSphere Agents
are the ones that take care of establishing connections to the vSphere hosts and perform discovery and polling of vSphere objects. ThevSphere Agents
are running on thevPoller Workers
and a singlevPoller Worker
can have as manyvSphere Agents
as you’d like.vSphere Agents
are configured and managed by thevconnector-cli
tool.
On the image below you can see how each vPoller component relates to the others.
Here is what happens when you send a client task request:
- A
vPoller Client
sends a task request to thefrontend
endpoint of avPoller Proxy
. - Task request is received on the
vPoller Proxy
and is dispatched to any connectedvPoller Workers
on thebackend
endpoint. - The task request is received on the
vPoller Worker
and given to avSphere Agent
which is taking care of the requested vSphere host for processing the request through the VMware vSphere API. - The
vSphere Agent
returns any result from the operation to thevPoller Worker
which in turn sends the result through thevPoller Proxy
back to the client which requested the task.