cbtool
cbtool copied to clipboard
ibmcb
Cloud Rapid Experimentation and Analysis Toolkit
Hello. As part of a master's thesis, I would like to perform some experiments in GCE cloud via CBTOOL. My first aim is to run `nullworkload` appliction with the usage...
There's a race condition (thread safety issue) in the libcloud code when attaching block storage volumes. We need to get that fixed. This is just a placeholder issue for when...
At the completion of the scale out test, all the AIs and VMs are destroyed. I have set the detach_parallelism to 3 for vm_defaults, aidrs_defaults, and ai_defaults in the osgcloud_rules.yaml...
I am trying to get cbtool to work with Openstack train but I have several questions regarding its config file. My attempts so far have got no further than errors...
Trying to do something like: ./cb cldalter vm_templates fio=size:32gb,imageids:1,imageid1:00726830 results in an error: ############################# Executing command "imageids:1" (specified on the command line) *** Unknown syntax: imageids:1 ############################# Executing command "imageid1:15101"...
We want to add support for AzureStack, Microsoft's hybrid cloud. However the [documentation](https://github.com/ibmcb/cbtool/wiki/FAQ-D) in the Wiki on doing this is not clear. Also, all the comments are TBD for each...
So, if you start a fresh container running cbtool from a Dockerfile, this happens: > $ ./cb -f > $ ./cb # reset is forced anyway, even though it wasn't...
`configs/templates/PUBLIC_dependencies.txt` uses `python` prefix for keys of python-setuptools. However, `docker/workload/Dockerfile-ubuntu_cb_nullworkload` uses `python3` prefix for keys of python-setuptools. The mismatch leads to the following error when running install script. The error...
While I use CBTOOL console, I observe this error message very often although it shouldn't appear: Domain not found: no domain with matching name 'cb-centos-MYPLM-vm3-tinyvm' The message is emitted by...
ycsb vm can't start on PLM backend, because there is no entry for "4(vcpu)-16384(vmem)" vm configuration in `lib/clouds/plm_cloud_ops.py` and `configs/templates/_plm.txt`. My fix: lib/clouds/plm_cloud_ops.py: self.vhw_config["04-16384"] = { "vcpus" : "4", "vmem"...