Right now all logic responsible for destroying VM on compute site is located inside Atmosphere::VirtualMachine model class. I propose to move this logic from Atmosphere::VirtualMachine into Atmosphere::Cloud::VmDestroyWorker. As a conclusion ORM VM model manipulation will not have any side effects.
@tbartynski, @nowakowski, @bwilk - what do you think?
Right now all logic responsible for destroying VM on compute site is located inside
Atmosphere::VirtualMachine
model class. I propose to move this logic fromAtmosphere::VirtualMachine
intoAtmosphere::Cloud::VmDestroyWorker
. As a conclusion ORM VM model manipulation will not have any side effects.@tbartynski, @nowakowski, @bwilk - what do you think?