Realtime event driven VM staus

[sai-kumar-peddireddy]

Description

• Implemented a new Event Monitor function in the current DevOps Parallels Desktop service.
• This will read the output of the Event Monitor from prlctl and update the cached list of VMs depending on the state.
• Now the whole ParallelsService uses event emitter to get real-time status of Vm's
• Now in API/Orchestrator will have the real-time VM status
• PARALLELS_DESKTOP_REFRESH_INTERVAL config is deprecated, vm status is always real-time

Fixes 315
Fixes 317

Type of change

• Documentation Change
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update
• Updated packages

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have run tests that prove my fix is effective or that my feature works
• I have updated the CHANGELOG.md file accordingly

[sai-kumar-peddireddy]

k6 run loadtest/machines.js

     /\      Grafana   /‾‾/  
/\  /  \     |\  __   /  /   

/ / \ | |/ / / ‾‾\
/ \ | ( | (‾) |
/ __________ \ ||_\ ____/

 execution: local
    script: loadtest/machines.js
    output: -

 scenarios: (100.00%) 1 scenario, 50 max VUs, 11m0s max duration (incl. graceful stop):
          * contacts: Up to 500.00 iterations/s for 10m30s over 3 stages (maxVUs: 50, gracefulStop: 30s)

WARN[0012] Insufficient VUs, reached 50 active VUs and cannot initialize more executor=ramping-arrival-rate scenario=contacts

█ TOTAL RESULTS

checks_total.......: 201816  171.906201/s
checks_succeeded...: 100.00% 201816 out of 201816
checks_failed......: 0.00%   0 out of 201816

✓ success login

HTTP
http_req_duration..............: avg=121.91ms min=190µs    med=81.68ms  max=9m4s  p(90)=213.68ms p(95)=240.25ms
  { expected_response:true }...: avg=121.91ms min=190µs    med=81.68ms  max=9m4s  p(90)=213.68ms p(95)=240.25ms
http_req_failed................: 0.00%  0 out of 201816
http_reqs......................: 201816 171.906201/s

EXECUTION
dropped_iterations.............: 202842 172.780145/s
iteration_duration.............: avg=302.03ms min=159.13ms med=299.07ms max=1.26s p(90)=373.01ms p(95)=407.35ms
iterations.....................: 100908 85.953101/s
vus............................: 50     min=9           max=50
vus_max........................: 50     min=50          max=50

NETWORK
data_received..................: 1.5 GB 1.3 MB/s
data_sent......................: 198 MB 169 kB/s

running (19m34.0s), 00/50 VUs, 100908 complete and 0 interrupted iterations
contacts ✓ [======================================] 00/50 VUs 10m30s 500.00 iters/s