| Age | Commit message (Collapse) | Author |
|
This change extracts the API for the OpenDC Compute service into a separate
module to establish a clearer boundary between the interface meant for
consumers and interfaces meant for the the serve implementation.
|
|
This change converts the Server data class which can be used as a
stateful object to control an instance running in the cloud.
|
|
This change refactors the OpenDC Compute module so that the
VirtProvisioningService is now responsible for managing the lifecycle of
Server objects as opposed to the VirtDriver and BareMetalDriver
previously.
|
|
This change removes the use of ServiceRegistry in the OpenDC compute
module. It was not actually being used by any of the code and we are
moving to another interface in the future.
|
|
This change separates the cloud compute layer in OpenDC (e.g., Server)
from the bare-metal layer (e.g., Node), such that Node and
BareMetalDriver are unaware of the existence of Server and co.
|
|
This change removes the SimWorkloadImage implementation and changes
Image to a data class without workload. Simulation workloads should now
be pased via image metadata as the image storage should be unaware of
any simulation details.
|
|
This commit implements the energy models that are present in CloudSim:
1. Constant
2. Linear
3. Cubic
4. Square root
5. Interpolation based on data.
|
|
This change allows users to select the hypervisor scheduler to use when
deploying hypervisors onto bare-metal machines.
|
|
This change adds a new hypervisor implementation that supports virtual
machine that have exclusive access to resources (e.g., CPU).
|
|
This change converts the low-level workload model to be pull-based. This
reduces the overhead that we experienced with our previous co-routine
based approach.
|
|
This change updates the workflow service to delegate the resource
scheduling logic to the virtualized resource provisioner.
|
|
|
|
|
|
|
|
|
|
This change splits the opendc-compute module into two modules:
1. opendc-compute-core
The interfaces and APIs that represent a IaaS platform.
2. opendc-compute-simulator
The implementation of these interfaces using simulation components
from opendc-simulator-compute.
|