ubicloud/rhizome/host/spec
Maciek Sarnowicz 82ce73988c Rhizome part - Retaining bursting limits after VM restart
Vm restart was simply calling systemctl directly and that was wiping out the cpu burst limit from a cgroup settings. Those settings are not persisted anywhere and have to be re-set every time the service restarts. This was handled for the host restart, but not for the VM restart.

To fix, I added a new method in the vm_setup and call it from setup-vm master script. The nexus will call that script.
2025-02-19 09:20:28 -08:00
..
boot_image_spec.rb Make sha256 sum calculation faster. 2024-05-17 15:21:56 -07:00
cert_server_setup_spec.rb Refactor setup and stop_and_remove steps into cert_server_setup 2025-01-09 16:44:52 +01:00
cloud_hypervisor_spec.rb Introduce new CloudHypervisor version class 2024-06-13 17:11:42 +02:00
slice_setup_spec.rb Add rspec tests for SliceSetup. 2025-01-10 19:21:41 -08:00
spdk_rpc_spec.rb Enable setting IO rate limits in Rhizome's storage volume 2024-11-20 13:26:27 -08:00
spdk_setup_spec.rb Support OS specific SPDK in the rhizome side. 2024-11-21 11:50:30 -08:00
storage_key_encryption_spec.rb Restructure rhizome folder to accommodate new services 2023-09-06 00:51:26 +03:00
storage_key_tool_spec.rb Add rhizome multi-device storage abstractions 2024-01-24 09:19:33 -08:00
storage_volume_spec.rb Enable setting IO rate limits in Rhizome's storage volume 2024-11-20 13:26:27 -08:00
vm_path_spec.rb Update rubocop-rspec to 2.26.0 and fix new style checks 2024-01-05 09:23:40 +03:00
vm_setup_spec.rb Rhizome part - Retaining bursting limits after VM restart 2025-02-19 09:20:28 -08:00