x/kloudbuster
Code Issues Proposed changes

Bugfixes on the Rest get default config API

Browse Source 
Change-Id: I32c62fbcc39df53ab88930c09561ef9014ecba3a
This commit is contained in:
Yichen Wang 2015-09-09 14:35:23 -07:00
parent f64ab431f9
commit 72ba7c655d
2 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
kb_server/kb_server/controllers/api_cfg.py
View File

@ -37,8 +37,6 @@ class ConfigController(object):
kb_config = KBConfig()
pdict = eval(str(kb_config.config_scale))
# Normally we don't allow the clients to change below configs
pdict['client'].pop('tp_tool')
pdict['client'].pop('http_tool')
return json.dumps(pdict)
@expose(generic=True)

9
kloudbuster/cfg.tenants.yaml
View File

@ -8,13 +8,10 @@
# Settings in this file has higher priority than user configs. It determines
# the final count of tenants and useres that KloudBuster will use.
#
# If running under tenant/user reusing mode, KloudBuster will use *only* one
# tenant to hold the resources for both server cloud and client cloud.
#
# NOTE:
# (1) Under tenant/user resuing mode, all resources will be sitting under
# the same tenant, so there will be fixed *ONLY* one user for holding
# client side resources;
# If running under tenant/user reusing mode, KloudBuster will use *only* one
# tenant to hold the resources for both server cloud and client cloud. But
# each cloud will have its dedicated user.
tenant_name: demo_tenant
server_user: