diff options
| author | Wang Huaqiang <huaqiang.wang@intel.com> | 2020-05-14 15:55:24 +0800 |
|---|---|---|
| committer | Wang Huaqiang <huaqiang.wang@intel.com> | 2020-07-15 00:39:46 +0800 |
| commit | ba3388d666ad344e87de3bbf8f76ab494bb4421f (patch) | |
| tree | 618a955a6074ccecca71c4233b34ffa037eecc55 /nova/tests/unit/notifications | |
| parent | d992eb2f5a58e0a589b68384ceb02c880489e135 (diff) | |
| download | nova-ba3388d666ad344e87de3bbf8f76ab494bb4421f.tar.gz | |
objects: Introduce the 'CPUAllocationPolicy.MIXED' enum
Introduce a 'mixed' instance CPU allocation policy and
will be worked with upcoming patches, for purpose of
creating an instance combined shared CPUs with dedicated
or realtime CPUs.
In an instance mixed with different type of CPUs, the shared CPU
shared CPU time slots with other instances, and also might be a
CPU with less or un-guaranteed hardware resources, which implies
to have no guarantee for the behavior of the workload running on
it. If we call the shared CPU as 'low priority' CPU, then the
realtime or dedicated CPU could be called as 'high priority' CPU,
user could assign more hardware CPU resources or place some
guaranteed resource to it to let the workload to entail high
performance or stable service quality.
Based on https://review.opendev.org/714704
Part of blueprint use-pcpu-and-vcpu-in-one-instance
Change-Id: I99cfee14bb105a8792651129426c0c5a3749796d
Signed-off-by: Wang Huaqiang <huaqiang.wang@intel.com>
Diffstat (limited to 'nova/tests/unit/notifications')
| -rw-r--r-- | nova/tests/unit/notifications/objects/test_notification.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/nova/tests/unit/notifications/objects/test_notification.py b/nova/tests/unit/notifications/objects/test_notification.py index 07d3ba3349..277d9ffb49 100644 --- a/nova/tests/unit/notifications/objects/test_notification.py +++ b/nova/tests/unit/notifications/objects/test_notification.py @@ -387,7 +387,7 @@ notification_object_data = { # ImageMetaProps, so when you see a fail here for that reason, you must # *also* bump the version of ImageMetaPropsPayload. See its docstring for # more information. - 'ImageMetaPropsPayload': '1.3-9c200c895932163a4e14e6bb385fa1e0', + 'ImageMetaPropsPayload': '1.4-036c794843b95a3a39ee70830f5f6557', 'InstanceActionNotification': '1.0-a73147b93b520ff0061865849d3dfa56', 'InstanceActionPayload': '1.8-4fa3da9cbf0761f1f700ae578f36dc2f', 'InstanceActionRebuildNotification': @@ -411,7 +411,7 @@ notification_object_data = { 'InstanceActionSnapshotPayload': '1.9-c3e0bbaaefafdfa2f8e6e504c2c9b12c', 'InstanceExistsNotification': '1.0-a73147b93b520ff0061865849d3dfa56', 'InstanceExistsPayload': '1.2-e082c02438ee57164829afaeee3bf7f8', - 'InstanceNUMACellPayload': '1.1-2a24ab42bf5e8dfa98291402725bf278', + 'InstanceNUMACellPayload': '1.2-a367add3378c71c21c817ab2b23db3bf', 'InstanceNUMATopologyPayload': '1.0-247361b152047c18ae9ad1da2544a3c9', 'InstancePCIRequestPayload': '1.0-12d0d61baf183daaafd93cbeeed2956f', 'InstancePCIRequestsPayload': '1.0-6751cffe0c0fabd212aad624f672429a', |