Volume Scheduler
The class "vVolume" is implemented to resemble a volume that can be attached to a container in Docker or Kubernetes which consumes the ROM from "vHost". A "vContainer" could be attached with multiple "vVolume" and those "vVolume" could be allocated on different "vHost" rather than the "vHost" where the "vContainer" is hosted. The "vVolume" must be allocated first before a "vContainer" is scheduled. If any "vVolume" is failed to be allocated onto "vHost", the schedule of its associated "vContainer" will be on hold.
BestfitVolumeScheduler
Bases: VolumeScheduler
Bestfit volume scheduler. It will return the host with the least amount of resources.
Source code in PyCloudSim\scheduler\volume_scheduler.py
69 70 71 72 73 74 75 76 77 78 79 |
|
DefaultVolumeScheduler
Bases: VolumeScheduler
Default volume scheduler. It will return the first available host.
Source code in PyCloudSim\scheduler\volume_scheduler.py
57 58 59 60 61 62 63 64 65 66 |
|
VolumeScheduler
Bases: ABC
, Entity
Base for all container schedulers.
Source code in PyCloudSim\scheduler\volume_scheduler.py
15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 |
|
WorstfitVolumeScheduler
Bases: VolumeScheduler
Worstfit volume scheduler. It will return the host with the most amount of resources.
Source code in PyCloudSim\scheduler\volume_scheduler.py
82 83 84 85 86 87 88 89 90 91 92 |
|