Adjust default values
1. Adjust default values; 2. Remove the comment which causes confusion of GiB and GB; 3. Slight format on cleanup.rst; Change-Id: Iefae4498187e2ac20b89dc2dbd96a9e754f9100b
This commit is contained in:
Yichen Wang
parent
7daeb66ca0
commit
6b1326a9b1
|
|
@ -95,6 +95,7 @@ Limitations and Non-Goals
|
|||
-------------------------
|
||||
|
||||
* Requires Neutron networking (does not support Nova networking)
|
||||
|
||||
* Only supports HTTP and storage traffic in this version
|
||||
|
||||
Unlike some other scaling test frameworks, KloudBuster does *not* attempt to:
|
||||
|
|
@ -102,16 +103,15 @@ Unlike some other scaling test frameworks, KloudBuster does *not* attempt to:
|
|||
* provide a scale test framework that works across different cloud technologies
|
||||
(OpenStack + AWS + Google Cloud + ...) - we are only focusing on OpenStack
|
||||
|
||||
* provide a scale test framework that is flexible and programmable to do everything -
|
||||
* provide a scale test framework that is flexible and programmable to do everything -
|
||||
we just focus on opinionated and well targeted performance and scale areas
|
||||
with sensible use cases and available in a fully integrated and easy to consume
|
||||
packaged format
|
||||
|
||||
* replace bare metal and domain specific native performance and scale frameworks
|
||||
* replace bare metal and domain specific native performance and scale frameworks
|
||||
(line level traffic generators, ceph specific performance and scale tools...)
|
||||
|
||||
|
||||
|
||||
Contributions and Feedbacks
|
||||
---------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -43,8 +43,8 @@ that matches a given regular expression:
|
|||
* users
|
||||
* tenants
|
||||
|
||||
In some cases, because of timing reasons, you may have to run the force_cleanup script a few times
|
||||
to get rid of all selected resources.
|
||||
In some cases, because of timing reasons, you may have to run the force_cleanup
|
||||
script a few times to get rid of all selected resources.
|
||||
|
||||
How to Select Resources to Delete
|
||||
---------------------------------
|
||||
|
|
@ -139,16 +139,23 @@ of the kloudbuster installation method to install the script.
|
|||
Known Issues and Limitations
|
||||
----------------------------
|
||||
|
||||
Volumes attached to instances that are no longer present cannot be deleted thorugh the Nova or Cinder APIs.
|
||||
Such volumes will show up as attached to "None" and in the "in-use" or "available" state in the Horizon dashboard.
|
||||
In this case, the script will print a warning with the volume ID:
|
||||
Volumes attached to instances that are no longer present cannot be deleted
|
||||
thorugh Nova or Cinder APIs. Such volumes will show up as attached to "None"
|
||||
and in the "in-use" or "available" state from the Horizon dashboard. In this
|
||||
case, the script will print a warning with the volume ID::
|
||||
|
||||
WARNING: Volume 6080fdce-f894-4c41-9bc0-70120e8560a8 attached to an instance that no longer exists (will require manual cleanup of the database)
|
||||
|
||||
Cleanup of such volumes will require first setting the attach_status of the corresponding volume to "detached" in the Ciner database directly
|
||||
(using a mysql cli such as "MariaDB [cinder]> UPDATE volumes SET attach_status='detached' WHERE id='18ed7f10-be49-4569-9e04-2fc4a654efee';")
|
||||
then re-run the script (or manually delete the volume from Horizon).
|
||||
Cleanup of such volumes will require first setting the attach_status of the
|
||||
corresponding volume to "detached" in the Cinder database directly. You have
|
||||
to SSH to the controller host, and login to the MySQL shell:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
[root@gg34-2 ~]# mysql cinder
|
||||
MariaDB [cinder]> UPDATE volumes SET attach_status='detached' WHERE id='18ed7f10-be49-4569-9e04-2fc4a654efee';
|
||||
|
||||
Then re-run the script (or manually delete the volume from Horizon).
|
||||
|
||||
|
||||
Examples
|
||||
|
|
@ -156,7 +163,7 @@ Examples
|
|||
|
||||
KloudBuster resources cleanup::
|
||||
|
||||
$ python force_cleanup.py -r admin-oper.sh
|
||||
$ python force_cleanup.py -r admin-openrc.sh
|
||||
Please enter your OpenStack Password:
|
||||
Discovering Storage resources...
|
||||
Discovering Compute resources...
|
||||
|
|
@ -273,7 +280,7 @@ KloudBuster resources cleanup::
|
|||
|
||||
Delete all resources with a name starting with "HA"::
|
||||
|
||||
$ python force_cleanup.py -r admin-openrc.sh --filter 'HA'
|
||||
$ python force_cleanup.py -r admin-openrc.sh --filter 'HA'
|
||||
Discovering Storage resources...
|
||||
Discovering Compute resources...
|
||||
Discovering Network resources...
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ server:
|
|||
# Memory for the flavor in MB
|
||||
ram: 2048
|
||||
# Size of local disk in GB
|
||||
disk: 20
|
||||
disk: 0
|
||||
|
||||
# Number of tenants to be created on the cloud
|
||||
# KloudBuster will also create 1 user automatically for each tenant
|
||||
|
|
@ -165,7 +165,7 @@ client:
|
|||
# Memory for the flavor in MB
|
||||
ram: 2048
|
||||
# Size of local disk in GB
|
||||
disk: 20
|
||||
disk: 0
|
||||
|
||||
# Traffic shaping - VM Placement hint
|
||||
# Availability zone to use for clients in the client cloud
|
||||
|
|
@ -291,11 +291,6 @@ client:
|
|||
|
||||
# The size of the test file for running IO tests in GB. Must be less or
|
||||
# equal than disk_size.
|
||||
#
|
||||
# Note: Due to the unit calculation difference and the overhead of the
|
||||
# filesystem, the actual available space for data will be smaller than the
|
||||
# volume size. So we picked GiB as the unit for laying out the test file,
|
||||
# which normally should be fine.
|
||||
io_file_size: 1
|
||||
|
||||
# Prompt before running benchmarking tools
|
||||
|
|
|
|||
|
|
@ -263,6 +263,7 @@ class KloudBuster(object):
|
|||
self.kb_runner = None
|
||||
self.fp_logfile = None
|
||||
self.kloud = None
|
||||
self.testing_kloud = None
|
||||
|
||||
def get_hypervisor_list(self, cred):
|
||||
creden_nova = {}
|
||||
|
|
|
|||
Loading…
Reference in New Issue