summaryrefslogtreecommitdiff
path: root/opendc/opendc-compute/src/test
AgeCommit message (Collapse)Author
2020-04-08bug: Fix incorrect reporting of overcommissionFabian Mastenbroek
2020-03-26feat: Add cluster metadata to bare metal nodesFabian Mastenbroek
2020-03-25feat: Record hypervisor events during experimentFabian Mastenbroek
2020-03-25refactor: Add support for specifying VM nameFabian Mastenbroek
2020-03-25refactor: Migrate to Flow for event listenersFabian Mastenbroek
2020-03-25[ci skip] refactor: Refactor monitors into EventFlowFabian Mastenbroek
2020-03-25refactor: Rework monitor interfacesFabian Mastenbroek
2020-03-25[ci skip] feat: Add support for correlated failuresFabian Mastenbroek
2020-03-25feat: Track VM failures in SC20 experimentFabian Mastenbroek
2020-03-25feat: Add support for failing hypervisors in provisionerFabian Mastenbroek
2020-03-25feat: Make FaultInjector more genericFabian Mastenbroek
2020-03-25[ci skip] feat: Prototype design for FailureInjectorFabian Mastenbroek
2020-03-25feat: Propagate machine failure to VMFabian Mastenbroek
2020-03-25feat: Add infrastructure for failuresFabian Mastenbroek
2020-03-25feat: Revamp bare-metal state managementFabian Mastenbroek
2020-03-13refactor: Change burst to MFLOpsFabian Mastenbroek
2020-03-13feat: Divide workload equally over pCPUsFabian Mastenbroek
2020-03-11feat: Measure host CPU usage and power consumptionFabian Mastenbroek
2020-03-10feat: Implement basic power modelFabian Mastenbroek
2020-02-29refactor: Report CPU usage per serverFabian Mastenbroek
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.
2020-02-28refactor: Create distinction between CPU node and coreFabian Mastenbroek
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.
2020-02-28refactor: Change from logical processes to simulation domainsFabian Mastenbroek
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.
2020-02-26Model memory usage in VMsGeorgios Andreadis
2020-02-26Improve design of workload modellingFabian Mastenbroek
2020-02-21feat: Simplify tagging of cloud resourcesFabian Mastenbroek
2020-02-21feat: Add support for resource taggingFabian Mastenbroek
2020-02-20feat: Implement VM supportGeorgios Andreadis
This change adds support for virtual machines and hypervisors to the _opendc-compute_ module. Moreover, this change also includes VM trace reading capabilities.
2020-02-14style: Fix Ktlint issuesFabian Mastenbroek
2020-02-14refactor: Rename FakeBareMetalDriver to SimpleBareMetalDriverFabian Mastenbroek
2020-02-14refactor: Rename Flavor to ServerFlavorFabian Mastenbroek
This change renames Flavor to ServerFlavor to be more indicative of its function. The Flavor name follows the naming of the OpenStack project.
2020-02-14refactor: Integrate opendc-compute in existing modelFabian Mastenbroek
This change refactors the existing model to use the new interfaces from the opendc-compute module.
2020-02-14feat: Implement basic provisioner serviceFabian Mastenbroek
2020-02-14refactor: Remodel workloads and compute resourceFabian Mastenbroek
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.
generated by cgit v1.2.3 (git 2.25.1) at 2026-02-06 12:43:40 +0000