kloudbuster

History

ahothan 7478a3676e Chart generation supports multiple json

Add multiple curves to latency chart - 1 per json file
Switch to jQuery dataTable to represent 1 row per json file

Change-Id: Ie10cfbda5604444a655e9bb71b6a8f4d9edd2d5b

2015-05-12 09:16:21 -07:00

ssh

Add the support to run wrk tool

2015-03-30 15:22:22 -07:00

tools

Add the support to run wrk tool

2015-03-30 15:22:22 -07:00

base_compute.py

Add support for VM placement (AZ)

2015-05-06 12:40:24 -07:00

base_network.py

Multiple enhancements and bugfixes

2015-05-07 19:04:34 -07:00

cfg.scale.yaml

Multiple enhancements and bugfixes

2015-05-07 19:04:34 -07:00

credentials.py

Change to use oslo for CLI parsing and logging

2015-04-16 16:05:43 -07:00

kb_gen_chart.py

Chart generation supports multiple json

2015-05-12 09:16:21 -07:00

kb_scheduler.py

Bugfixes and small enhancements

2015-05-06 01:08:09 -07:00

kb_tpl.jinja

Chart generation supports multiple json

2015-05-12 09:16:21 -07:00

kb_vm_agent.py

Support to fetch and consolidate latency data

2015-05-07 08:34:07 +00:00

kb.lua

Support to fetch and consolidate latency data

2015-05-07 08:34:07 +00:00

kloudbuster.py

Multiple enhancements and bugfixes

2015-05-07 19:04:34 -07:00

log.py

Use redis as the communication protocol

2015-04-21 13:08:39 -07:00

perf_instance.py

Simplify cfg and ssh + key pairs, switch to wrk2

2015-05-05 17:35:03 -07:00

perf_tool.py

Multiple enhancements and bugfixes

2015-05-07 19:04:34 -07:00

README

Preliminary version of Kloudbuster

2015-03-17 14:21:24 -07:00

sshutils.py

Backport sshutils and move redis init earlier

2015-05-04 07:37:33 -07:00

tenant.py

Optimization on redis communication

2015-04-23 15:47:41 -07:00

users.py

Simplify cfg and ssh + key pairs, switch to wrk2

2015-05-05 17:35:03 -07:00

wrk_tool.py

Multiple enhancements and bugfixes

2015-05-07 19:04:34 -07:00

README

This is for VMTP scale testing
This is work in progress for now
The idea is to be able to 
1. Create tenant and users to load the cloud
2. Create routers within a User in a tenant
3. Create N networks per router
4. Create N VMs per network
5. Clean up all resources by default (Provide ability to avoid cleanup)