Add DVR scale issue to relnotes 7.0

Change-Id: Ic5a0fd036d96f943a5223ed80f3369837e1ba0b9
(cherry picked from commit baecfa7db6)
This commit is contained in:
evkonstantinov
2015-09-29 20:39:20 +03:00
committed by Evgeny Konstantinov
parent 17bcfe8b71
commit f6f0a5fdee
2 changed files with 24 additions and 0 deletions

View File

@@ -47,3 +47,4 @@ Known Issues
.. include:: /pages/release-notes/v7-0/fuel_issues/swift_copy_issue.rst
.. include:: /pages/release-notes/v7-0/fuel_issues/non_dynamic_images_known.rst
.. include:: /pages/release-notes/v7-0/fuel_issues/vbox_ssh_issue.rst
.. include:: /pages/release-notes/v7-0/fuel_issues/dvr_scale_issue.rst

View File

@@ -0,0 +1,23 @@
* With the Neutron DVR feature enabled, there are the following limitations:
* The rate of VM creation should be less than 3 VMs per minute.
* If the constant rate of VM creation is 3 VMs per minute,
the cloud can handle the load for a minimum of 6 hours [1]_.
If the constant load persists over 6 hours, the cloud will
experience intermittent issues which will affect the
Control Plane API availability and operations.
The 3 VMs per minute generation rate is not a regular occurrence across
the industry and is termed a "cloud storm load". For example, IBM QRadar,
which is a cloud security system, treats the 5 VMs per 30 minutes
generation rate as a severe offence [2]_.
The actual rate numbers depend on the number of active users, number of
tenants, and the type of activity patterns. In case of self-service usage of
the cloud, when users initiate VM provisioning manually, the rate of VM
creation is typically low and does not last long. If cloud API is
used by automation for VM creation, the load on the cloud infrastructure
should be carefully evaluated and throttled on the automation level.
.. [1] Data obtained for 200 nodes configuration with VLAN+DVR.
.. [2] See `IBM QRadar security article <http://www.ibm.com/developerworks/library/se-virtual-cloud-security/>`_.