kloudbuster

History

Yichen Wang 6d2152767a Initial commit to use Pecan for RestAPI service Change-Id: Ie1fd9dbec8a5163a2959846c6ca845572ce23b12		2015-06-30 14:33:08 -07:00
..
dib	Add support to do periodical report	2015-06-19 14:18:11 -07:00
kb_server	Initial commit to use Pecan for RestAPI service	2015-06-30 14:33:08 -07:00
README	Preliminary version of Kloudbuster	2015-03-17 14:21:24 -07:00
base_compute.py	Add support to do VM placements based on roles	2015-06-04 15:20:32 -07:00
base_network.py	Add support to do periodical report	2015-06-19 14:18:11 -07:00
cfg.scale.yaml	Add support to do periodical report	2015-06-19 14:18:11 -07:00
cfg.topo.yaml	Add support to do VM placements based on roles	2015-06-04 15:20:32 -07:00
credentials.py	Change to use oslo for CLI parsing and logging	2015-04-16 16:05:43 -07:00
kb_config.py	Initial commit to use Pecan for RestAPI service	2015-06-30 14:33:08 -07:00
kb_gen_chart.py	Generate charts with line rate greater than 10GE	2015-06-03 17:56:47 -07:00
kb_runner.py	Add support to do periodical report	2015-06-19 14:18:11 -07:00
kb_scheduler.py	Add support to do VM placements based on roles	2015-06-04 15:20:32 -07:00
kb_tpl.jinja	Chart generation supports multiple json	2015-05-12 09:16:21 -07:00
kb_vm_agent.py	Add support to do VM placements based on roles	2015-06-04 15:20:32 -07:00
kb_wrk2.lua	Integrating KloudBuster with DIB	2015-06-05 00:29:32 -07:00
kloudbuster.py	Initial commit to use Pecan for RestAPI service	2015-06-30 14:33:08 -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
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	Move redis-server to a dedicated VM	2015-05-14 16:38:09 -07:00
wrk_tool.py	Add support to do periodical report	2015-06-19 14:18:11 -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)