Correct firecracker process management

[alexandrebrg]

What needs to be done ?

• firepilot VM stop method isn't properly killing the process of the VM (process stays alive)
• firepilot VM start is blocking, it should be running in a separate process handled by firepilot
• firepilot start of VM should return an object that can manage the VM, it shouldn't return a String
• firepilot uses a complete configuration and process it as a JSON, we should be using the API of the firecracker socket

We got a few solution for this, we can either continuing developing firepilot and improve it to match our needs, or, we could go for a different crate like firec.

Why it needs to be done ?

• We can hardly manage the mVM
• We cannot configure it beforehand and then run it in a second step (e.g create TAP, configure IP and then run the mVM)
• We cannot properly stop the VM

[alexandrebrg]

IMHO, we could continue developing firepilot by using a pre-generated SDK based on the OpenAPI. The additional cost of development could be worth it, as we could create a reliable mVM manager for Firecracker.