You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/plugins/ovs-plugin.rst
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,6 +286,12 @@ Agent configuration
286
286
287
287
Agent should be restarted for actions to take effect.
288
288
289
+
When the host agent connects to the management server, it sends the list of hosts capabilities. When DPDK support is enabled on the host, the capability with name 'dpdk' is sent to the management server. The list of host capabilities are persisted on the 'capabilities' column on 'hosts' table, and can be retrieved by the 'listHosts' API method:
290
+
291
+
::
292
+
293
+
list hosts id=HOST_ID filter=capabilities
294
+
289
295
Additional VM configurations
290
296
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
291
297
In order to enable DPDK on VM deployments, users should pass addition configuration to VMs. The required configurations are listed on the next section. Administrators can allow users to pass additional configurations to their VMs by the account scoped setting:
@@ -410,6 +416,21 @@ By default, the server mode is assumed if it is not passed as a service offering
It is possible to perform live migrations of DPDK enabled VMs since CloudStack version 4.13. DPDK enabled VMs can be migrated between hosts in the same cluster which are both DPDK enabled.
422
+
423
+
CloudStack determinates that a VM is a DPDK enabled VM when the following conditions are met:
424
+
425
+
- The VM is a user VM
426
+
- The VM state is Running
427
+
- The host in which the VM is running is a DPDK enabled host (i.e. host contains the 'dpdk' capability as part of its capabilities. Check `Agent configuration for DPDK support`_.)
428
+
- The VM acquires the DPDK required configurations via VM details or service offering details. DPDK required additional configurations are additional configurations with name:
429
+
- 'extraconfig-dpdk-numa'
430
+
- 'extraconfig-dpdk-hugepages'
431
+
432
+
DPDK enabled VMs can only be migrated between DPDK enabled hosts. Therefore the 'findHostsForMigration' API method excludes non-DPDK enabled hosts from the list of suitable hosts to migrate DPDK enabled VMs.
433
+
413
434
DPDK ports
414
435
~~~~~~~~~~
415
436
When VM is created or started, CloudStack creates ports with DPDK support with format: "csdpdk-N" where N is a number, incremented on new ports creation. This port is set into the 'source' property of the 'interface' tag on the XML domain of the VM, prepended by the value of the OVS path set on the property:
0 commit comments