| Age | Commit message (Collapse) | Author |
|
Improve design of workload modelling
See merge request opendc/opendc-simulator!29
|
|
|
|
Incorporate extensions to workflow scheduler
See merge request opendc/opendc-simulator!27
|
|
|
|
This change adds support for workflow tasks that have a known duration.
This allows the workflow scheduler to employ heuristics for a faster
schedule.
|
|
This change incorporate a number of extensions and improvements to the
workflow scheduler. These are a result of the Design Space Exploration
for Datacenter Schedulers work.
|
|
Add support for resource tagging
See merge request opendc/opendc-simulator!26
|
|
|
|
|
|
Add VM support
Closes #20
See merge request opendc/opendc-simulator!25
|
|
This change adds support for virtual machines and hypervisors to the
_opendc-compute_ module. Moreover, this change also includes VM trace
reading capabilities.
|
|
Write up basic documentation on architecture and toolchain
Closes #25
See merge request opendc/opendc-simulator!24
|
|
Adds missing fullstop
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add basis for VM modeling and fractional space-sharing
See merge request opendc/opendc-simulator!23
|
|
This change fixes an issue where the runtime of an image that requested
cpu time was not properly computed.
|
|
|
|
These experiments were originally designed for the SC18 paper.
|
|
|
|
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.
|
|
This change makes the ProcessContext implement the CoroutineScope in
order to launch local coroutines bound to the lifecycle of the logical
process.
|
|
This change adds a log property to the ProcessContext which allows the
user to access a Logger instance that is tied to a particular logical
process.
|
|
Reimplement OpenDC model using 2.x API
See merge request opendc/opendc-simulator!21
|
|
Add missing dots
|
|
|
|
Add missing dot
|
|
|
|
This change adds helper methods for simplifying the request-response
pattern commonly used in models.
|
|
This change fixes the issue where messages are not delivered in FIFO
order due to the internal priority not guaranteeing insertion order. For
now, we fix this issue by adding a unique increasing identifier to each
event in the queue.
|
|
Add support for Gitlab CI
See merge request opendc/opendc-simulator!22
|
|
This change adds the configuration of Gitlab CI in order to test on our
internal Gitlab instance.
|
|
This change adds experimental support for selecting on ports. This
allows the user to receive messages from multiple channels at the same
time.
|
|
This change adds a prototype implementation of the revised version of
the API of version 2.0 of the simulator.
|
|
This change introduces the revised API design for version 2.0 of the
OpenDC simulator. This version drops built-in support for Java and
instead opts to build on Kotlin coroutines to simplify the API surface.
During development of and experimentation with the previous API for version
2.x, we found that the design based on Akka Typed was too limiting and caused
too much boilerplate for the models we needed to implement. Essential
patterns such as request-response were found to be hard to implement
with only a single mailbox. Moveover, limiting each actor's mailbox to a
single type hindered composition and often resulted in unchecked casts
or the type being changed to `Any`, eliminating the type-safety of the
API.
In this revised API design, a simulation is now represented as the interplay of
logical processes that communicate via multiple message passing channels.
We use Kotlin coroutines to describe the behavior of the processes.
The API has been design from the start to take into account
distributed/parallel simulations by disallowing messages from arbitrary
processes, which was possible in the previous design. Instead, the
'communication graph' is known during runtime as procsses must register
themselves before being able to send/receive messages to/from channels.
We are still figuring out process/channel identity and supervision. Currently,
all logical processes run on a single level, instead of being
hierachical. However, this might change in the future.
|
|
This change renames the main module of the odcsim library to odcsim-api,
since it mainly contains the interfaces to be used by consumers of the
API and implemented by the various frameworks.
|
|
|
|
|
|
|
|
This change ensures that the batch file for invoking the Gradle wrapper
is treated as a file with Windows line endings.
|