search

malawski / cloudworkflowsimulator

Other
24 stars 20 forks source link

Avoid using the Environment class where easily possible because it forces homogeneous VM types #135

Closed davidshepherd7 closed 9 years ago

davidshepherd7 commented 9 years ago

I'm trying to work with heterogeneous VMs, but this is difficult because the vm properties are often obtained from an Environment instead of from the VM. So I've tried to replace this where possible with the use of VMType instead (which can be easily obtained from a given VM).

It seems like a lot of the current scheduling algorithms rely on the assumption that all VMs are the same, so I think I'll try to create a separate type of algorithm that doesn't have this assumption. Possibly they can be merged to some extent eventually...

bryk commented 9 years ago

Thanks! A few minor comments after first glimpse. Will look further later.

Re all VMs are the same: yes, this is the assumption and it is hardcoded in a couple of places. Sometimes there are assertions about VM-s being single core, so this should help with your work.

bryk commented 9 years ago

Perfect, thanks!