python-novaclient/novaclient/v2/contrib
Artom Lifshitz 3d9c01b2d3 Option to specify max servers for live evacuate
The current behaviour of live evacuate is to naively request that all
servers on the hypervisor be evacuated. The more VMs are migrated
simultaneously, the more bandwidth is required. Once a certain number
of migrating VMs is reached, there is not enough bandwidth to cope
with the rate at which they dirty their memory. The migrations will
thus never complete.

The correct solution to this would be a whole lot of work on the Nova
side. As a stopgap measure, this patch introduces a --max-servers
option to host-evacuate-live. With this option, the user can control
the number of VMs that are live-migrated at the same time, thus
allowing the user to avoid the dirty memory scenario described above.

Change-Id: I17bad5f3253d6657fc1e6610159fc8e3921e6ea4
2015-09-02 17:13:47 +00:00
..
__init__.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
assisted_volume_snapshots.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
baremetal.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
cells.py Fix description of parameters in nova-client functions 2015-02-27 16:56:28 +03:00
deferred_delete.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
host_evacuate.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
host_evacuate_live.py Option to specify max servers for live evacuate 2015-09-02 17:13:47 +00:00
host_servers_migrate.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
instance_action.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
list_extensions.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
metadata_extensions.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
migrations.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
server_external_events.py Rename v1_1 to v2 2015-02-04 17:40:46 +02:00
tenant_networks.py Change commands name from net-* to tenant-network-* 2015-02-13 17:47:18 +09:00