| Age | Commit message (Collapse) | Author |
|---|
|
This change refactors the codebase so that the CPU usage of the server
is only reported per server, instead of per CPU reducing the total
amount of messages needed and additionally simplifying synchronization
of various computations.
|
|
This change updates the terminology in the `opendc-compute` module to
make a distinction between CPU node and CPU core, where we primarly work
with CPU cores. However, if needed, we also provide information for the
different CPU nodes.
|
|
This change moves the simulator terminology from logical processes to
simulation domains. This prevents the clash with "processes" that we are
trying to simulate.
In addition, simulation domains allows us to reduce the amount of
boilerplate and instead allows for simulation modelled using standard
techniques.
|
|
|
|
|
|
|
|
|
|
This change adds support for virtual machines and hypervisors to the
_opendc-compute_ module. Moreover, this change also includes VM trace
reading capabilities.
|
|
|
|
|
|
This change renames Flavor to ServerFlavor to be more indicative of its
function. The Flavor name follows the naming of the OpenStack project.
|
|
This change refactors the existing model to use the new interfaces from
the opendc-compute module.
|
|
|
|
This change remodels our model for workloads and compute resources in
order to support VM/container functionality where multiple workloads run
on a single machine.
In particular, we make the following changes:
- Move the compute-related source code into the `opendc-compute` module.
- Change from application-based model to image-based model, where the
image has exclusive access over the machine, instead of applications
that share the machine. We may model in the future again
applications/operating system, but at the moment, we do not need this
granularity, given that the workload traces can be simulated using VMs.
|
