summaryrefslogtreecommitdiff
path: root/opendc/opendc-compute/src
AgeCommit message (Collapse)Author
2020-03-09feat: Define key for performance interference model of imageFabian Mastenbroek
2020-03-04Fix rebaseGeorgios Andreadis
2020-03-04Make onExit suspendingGeorgios Andreadis
2020-03-04Give vCPUs access to their hosted VMGeorgios Andreadis
This should make performance interference based onn the colocated VMs possible.
2020-03-03refactor: Rename maxUsage to limitFabian Mastenbroek
This change renames the `maxUsage` parameter to `limit` in order to align terminology with other products/projects such as VMWare vSphere.
2020-03-03feat: Re-add support for hypervisor monitorFabian Mastenbroek
2020-02-29refactor: Store remainder in burst arrayFabian Mastenbroek
This change modifies the API of ServerContext to store the remainder burst into the input burst array instead of returning a new array.
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-28Fix NPEGeorgios Andreadis
2020-02-28Change to push-based node status communicationGeorgios Andreadis
2020-02-28Factor out allocation policy and add memory-aware policyGeorgios Andreadis
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-28bug: Fix timing issues to to unit differencesFabian Mastenbroek
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-14bug: Apply requested cpu time correctlyFabian Mastenbroek
This change fixes an issue where the runtime of an image that requested cpu time was not properly computed.
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.