I guess there is a copy of this structure somewhere in the vSwarm repo. Can you import it directly from there so we avoid duplicating structures and maintain consistency?

Yes, this is the same file, hut importing it from vSwarm directly had some issues with the go.mod file since this isn't directly declared as a package under the vSwarm repo

I would give this another try?

There is a lot of core repetition between this and the regular gRPC invoker. Consider extracting the common code and putting interface for the different part of the code. Same for the changes to pkg/driver/clients/invoker.go.

I had done that before, with both invokers essentially integrated into the same function switched by the flag, but @leokondrashov had asked me to create two separate files for two different invokers, or maybe I am misunderstanding something

There is no contradiction. IIRC, I asked you to separate the two because you confusingly intermixed them. The proper way would be to make a general gRPC invoker call the actual gRPC with the correct protobuf (which you need to abstract away). Differences exist only in the Invoke function, which creates the protobuf and extracts the results. So, you need to make a gRPC client that uses the interface to make an actual call and extract the instance name, memory consumption, and actual duration.

I apologize if I caused confusion.

Hi @cvetkovic @leokondrashov I have addressed your comments earlier and integrated the two invokers by extracting the common code and using an interface to execute the different RPCs. Please let me know if you have any other thoughts.

LGTM.