summaryrefslogtreecommitdiff
path: root/doc/notification_samples
Commit message (Collapse)AuthorAgeFilesLines
* libvirt: Add vIOMMU device to guestStephen Finucane2022-09-011-1/+1
| | | | | | | | | | | | | | Implementation for BP/libvirt-viommu-device. With provide `hw:viommu_model` property to extra_specs or `hw_viommu_model` to image property. will enable viommu to libvirt guest. [1] https://www.berrange.com/posts/2017/02/16/setting-up-a-nested-kvm-guest-for-developing-testing-pci-device-assignment-with-numa/ [2] https://review.opendev.org/c/openstack/nova-specs/+/840310 Implements: blueprint libvirt-viommu-device Change-Id: Ief9c550292788160433a28a7a1c36ba38a6bc849 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Add locked_memory extra spec and image propertySean Mooney2022-08-241-1/+1
| | | | | | | | | | | | This change adds a new hw:locked_memory extra spec and hw_locked_memory image property to contol preventing guest memory from swapping. This change adds docs and extend the flavor validators for the new extra spec. Also add new image property. Blueprint: libvirt-viommu-device Change-Id: Id3779594f0078a5045031aded2ed68ee4301abbd
* image_meta: Add ephemeral encryption propertiesLee Yarwood2022-08-021-1/+1
| | | | | | | Add the `hw_ephemeral_encryption` and `hw_ephemeral_encryption_format` image properties. Change-Id: Ida3edbdd664fbc3ac23516b1ff5b67edae43ea79
* object/notification for Adds Pick guest CPU architecture based on hostJonathan Race2022-02-241-1/+1
| | | | | | | | | | | | | | | | | | | | arch in libvirt driver support This is split 1 of 3 for the architecture emulation feature. This adds the 'hw_emulation_architecture' property to the image meta properties, allowing for operator to define whether they will use emulation or not. This adds the capability as a feature to ensure no impact to normal operations or functionality. Account for object versioning has been added to raise exceptions and handle proper Implements: blueprint pick-guest-arch-based-on-host-arch-in-libvirt-driver Signed-off-by: Jonathan Race <jrace@augusta.edu> Change-Id: If4f598c0d3f9e64617beb54450faa04e7d20dd20
* objects: Remove 'bandwidth' fields from notificationsStephen Finucane2021-11-032-6/+4
| | | | | | | | | | Finish up removing these entries from the versioned instance notifications. They're useless since we dropped support for the XenAPI virt driver. The underlying model is retained for now: that will be handled separately. Change-Id: I774c50fca99bc655ca5010e3b9d8247b739293b3 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Allow 'bochs' as a display device optionKashyap Chamarthy2021-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 'bochs' display device is a recommended[1] safe option for UEFI guests. This is supported in libvirt from version 5.6.0; Nova's current MIN_LIBVIRT_VERSION (6.0.0) satisfies this requirement. Partially quoting the "bochs display device" section from a post written by a QEMU graphics maintainer[1]: [...] Main advantage over standard VGA is that this device is alot simpler. The code size and complexity needed to emulate this device is an order of magnitude smaller, resulting in a reduced attack surface. Another nice feature is that you can place this device in a PCI Express slot. For UEFI guests it is safe to use the bochs display device instead of the standard VGA device. The firmware will setup a linear framebuffer as GOP anyway and never use any legacy VGA features. For BIOS guests this device might be useable as well, depending on whenever they depend on direct VGA hardware access or not. There is a vgabios which supports text rendering on a linear framebuffer, so software which uses the vgabios services for text output will continue to work. Linux bootloaders typically fall into this category. The linux text mode console (vgacon) uses direct hardware access and does not work. The framebuffer console (fbcon running on vesafb or bochs-drm) works. [1] https://www.kraxel.org/blog/2019/09/display-devices-in-qemu/ Implements: blueprint add-bochs-display-device Change-Id: Id194028f5d2cbaac1c5e699b71fd9751f87f5da5 Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
* libvirt: Add support for virtio-based input devicesStephen Finucane2021-03-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The USB-based tablet is often the only USB device in an x86 instance, while the USB-based keyboard is often the only such device in an AArch64 instance (x86 have PS2 keyboards and mice). Replacing these with virtio-based devices can eliminate the need to have a USB host adapter in the instance. Enable just that possibility by adding a new value image metadata property, 'hw_input_bus'. This allows us to specify not only virtio-based pointer and keyboard input devices but also USB equivalents. Note that this also fixes one instance of a particular class of bugs, whereby we have checks for *guest* architecture-specific behavior that are being toggled based on the *host* architecture. In this instance, we were attempting to add a keyboard device on AArch64 guests since they don't have one by default, but we were determining the architecture by looking at the CPU architecture reported in the host capabilities. By replacing this check of the host capabilities with a call to the 'nova.virt.libvirt.utils.get_arch' helper, we correctly handle requests to create non-host architecture guests via the 'hw_architecture' image metadata property. There are many other instances of this bug and those can be resolved separately. Change-Id: If9f3ede3e8449f9a6c8d1da927974c0a73923d51 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* objects: Add 'socket' PCI NUMA affinityArtom Lifshitz2021-02-241-1/+1
| | | | | | | | | | | | This patch adds the 'socket' value to the allowed PCI NUMA affinity policies, both to the 'hw:pci_numa_affinity_policy' flavor extra spec, and the 'hw_pci_numa_affinity_policy' image property. For now the new value is a no-op and remains undocumented. It will be wired-in in a subsequent patch. Implements: blueprint pci-socket-affinity Change-Id: I0680d4e21f3e317ac702b55afef4c87e8acbfc3a
* virt: Remove 'get_all_bw_counters' APIStephen Finucane2020-11-242-13/+1
| | | | | | | | | This one is a little more involved because there are persistent objects and versioned notifications to worry about, neither of which we can remove right now. Change-Id: Ic7c330ee1cccdc44a2a555c16cb6090eecbf6ce1 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* scheduler: Request vTPM trait based on flavor or imageStephen Finucane2020-07-161-1/+1
| | | | | | | | | | | | | Add support for the 'hw:tpm_version' and 'hw:tpm_model' flavor extra specs along with the equivalent image metadata properties. These are picked up by the scheduler and transformed into trait requests. This is effectively a no-op for now since we don't yet have a driver that reports these traits. Part of blueprint add-emulated-virtual-tpm Change-Id: I8645c31b4ecb18afea592b2a5b360b0165626009 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* objects: Introduce the 'CPUAllocationPolicy.MIXED' enumWang Huaqiang2020-07-152-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* notifications: add the pcpuset info to instance numa cell payloadWang Huaqiang2020-07-151-1/+2
| | | | | | | | | | Update the versioned object notification for 'InstanceNUMACell' object to reflect the change of a new 'pcpuset' field. Part of blueprint use-pcpu-and-vcpu-in-one-instance Change-Id: Ifeb21b9eff828952f67002172c8500f738e9984c Signed-off-by: Wang Huaqiang <huaqiang.wang@intel.com>
* partial support for live migration with specific resourcesLuyaoZhong2020-04-073-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | 1. Claim allocations from placement first, then claim specific resources in Resource Tracker on destination to populate migration_context.new_resources 3. cleanup specific resources when live migration succeeds/fails Because we store specific resources in migration_context during live migration, to ensure cleanup correctly we can't drop migration_context before cleanup is complete: a) when post live migration, we move source host cleanup before destination cleanup(post_live_migration_at_destination will apply migration_context and drop it) b) when rollback live migration, we drop migration_context after rollback operations are complete For different specific resource, we might need driver specific support, such as vpmem. This change just ensures that new claimed specific resources are populated to migration_context and migration_context is not droped before cleanup is complete. Change-Id: I44ad826f0edb39d770bb3201c675dff78154cbf3 Implements: blueprint support-live-migration-with-virtual-persistent-memory
* trivial: Use recognized extra specs in testsStephen Finucane2020-02-191-2/+1
| | | | | | | | Tests were previously using arbitrary keys that weren't published anywhere in the codebase. Switch to using meaningful ones. Change-Id: I8da84b48e4d630eeb91d92346aa2323e25e28e3b Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* FakeDriver: adding and removing instances on live migration.Lorenzo Affetti2019-12-202-2/+0
| | | | | | | | | | | | | There was no code in FakeDriver that updated the internal dict `self.instances` when a FakeInstance was live migrated. This commit fills this gap. As a result, a couple of versioned notification samples get updated since we are now properly tracking a live migrated instance on the destination host as running vs pending power state. Closes-Bug: 1426433 Change-Id: I9562e1bcbb18c7d543d5a6b36011fa28c13dfa79
* Sync ImageMetaPropsPayload fieldsSean Mooney2019-12-131-1/+1
| | | | | | | | | | | | | This change adds missing fields to the image metadata notification object and adds a unit tests to assert that the notification object and nova object stay in sync. This change also adds unit tests to assert the notification schema and fields are in sync and that the schema is valid. Change-Id: I36ea5d5e677ab3e6c88223b20f5377e9471c55db Closes-Bug: #1856100
* support pci numa affinity policies in flavor and imageSean Mooney2019-12-111-1/+1
| | | | | | | | | | | | | This addresses bug #1795920 by adding support for defining a pci numa affinity policy via the flavor extra specs or image metadata properties enabling the policies to be applied to neutron sriov port including hardware offloaded ovs. Closes-Bug: #1795920 Related-Bug: #1805891 Implements: blueprint vm-scoped-sriov-numa-affinity Change-Id: Ibd62b24c2bd2dd208d0f804378d4e4f2bbfdaed6
* Add Aggregate image caching progress notificationsDan Smith2019-10-291-0/+20
| | | | | | | | | | | | This adds AggregateCacheNotification, related payload, and code in conductor to emit this per-compute with progress information. This also adds a "progress" phase to NotificationPhase, which allows for start..progress..progress..end information for a single operation (cache_images in this case). Related to blueprint image-precache-support Change-Id: I69ae26d4caf4b56ab2c4864455bfe9b5b736dbf3
* Add notification sample test for aggregate.cache_images.start|endMatt Riedemann2019-10-252-0/+22
| | | | | | | | | | | | | | | | This adds the functional notification sample test for the aggregate.cache_images.start and aggregate.cache_images.end versioned notifications. I also added a comment to the docs builder code since it took me a bit to figure out how to get the notification sample linked into the docs, and for whatever reason figured that out by looking through code rather than our nicely detailed docs that already explain it. Part of blueprint image-precache-support Change-Id: I0869979a1b8a0966f0e7b49e5a5984f76d7d67cd
* trivial: Change name of network provided by NeutronFixtureStephen Finucane2019-10-054-6/+6
| | | | | | | | | | | We do this because most of our sample tests are currently using a fake network cache due to 'stub_compute_with_ips', and that fake cache uses the name 'private' instead of 'private-network'. When we remove that in a future change, there's going to be a lot of refactoring. Head some of that off by just using the same name. Change-Id: I6339005a0d49a6dfd376523d3f9e145a00cfc3bd Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Merge "Enhance service restart in functional env"Zuul2019-06-271-1/+1
|\
| * Enhance service restart in functional envBalazs Gibizer2019-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bugfix Icaf1bae8cb040b939f916a19ce026031ddb84af7 showed that restarting a compute service in the functional env is unrealistic causing faults to slip through. During that bug fix only the minimal change was done in the functional env regarding compute service restart to reproduce the reported fault. However the restart of the compute service could be made even more realistic. This patch simulates a compute service restart in the functional env by stopping the original compute service and starting a totally new compute service for the same host and node. This way we can make sure that we get a brand new ComputeManager in the new service and no state can leak between the old and the new service. This change revealed another shortcoming of the functional env. In the real world the nova-compute service could be restarted without loosing any running servers on the compute host. But with the naive implementation of this change the compute service is re-created. This means that a new ComputeManager is instantiated that loads a new FakeDriver instance as well. That new FakeDriver instance then reports an empty hypervisor. This behavior is not totally unrealistic as it simulates such a compute host restart that cleans the hypervisor state as well (e.g. compute host redeployment). However this type of restart shows another bug in the code path that destroys and deallocates evacuated instance from the source host. Therefore this patch implements the compute service restart in a way that simulates only a service restart and not a full compute restart. A subsequent patch will add a test that uses the clean hypervisor case to reproduces the revealed bug. Related-Bug: #1724172 Change-Id: I9d6cd6259659a35383c0c9c21db72a9434ba86b1
* | extend libvirt video model supportSean Mooney2019-06-211-1/+1
|/ | | | | | | | | | | | | | | | - This change extends the VideoModel field object to allow 3 new values (virtio, gop, none) - This change makes the libvirt driver use ALL tuple from the nova.fields.VideoModel object instead of declaring a second tuple inline for validation. - This change allows the virtio video model to now be used for all architectures when explicitly requested via the hw_video_model image metadata property - This change introduces unit tests and a release note for the new capablities. Change-Id: I2830ccfc81cfa9654cfeac7ad5effc294f523552 Implements: blueprint libvirt-video-device-models
* Microversion 2.73: Support adding the reason behind a server lockSurya Seetharaman2019-05-1113-13/+27
| | | | | | | | | | | | | | | | | | | | | | This patch adds a new parameter ``locked_reason`` to ``POST /servers/{server_id}/action`` request where the action is lock. It enables the user to specify a reason when locking a server. The locked_reason will be exposed through ``GET servers/{server_id}``, ``GET /servers/detail``, ``POST /servers/{server_id}/action`` where the action is rebuild and ``PUT servers/{server_id}`` requests' responses. The InstanceActionNotification will emit the locked_reason along with the other instance details. This patch hence changes the payload object to include the "locked_reason" field. Note that "locked" will be allowed as a valid filtering/sorting parameter for ``GET /servers/detail`` and ``GET /servers`` from this new microversion. Implements blueprint add-locked-reason Change-Id: I46edd595e7417c584106487123774a73c6dbe65e
* The field instance_name was added to InstanceCreatePayloadIfat Afek2019-01-151-2/+3
| | | | | | | | The field instance_name was missing from Nova instance notifications. It was added to instance.create.* notifications, as discussed in: http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001141.html Change-Id: I52f3186d1bcda0c23a471f9bfd2c55763262658f
* Transform scheduler.select_destinations notificationElőd Illés2018-11-304-13/+38
| | | | | | | | | Transform the scheduler.select_destinations.start and scheduler.select_destinations.end notifications to the versioned notification framework. Change-Id: I019e88fabd1d386c0d6395a7b1969315873485fd Implements: bp versioned-notification-transformation-stein
* Transform compute_task notificationsAlex Szarka2018-11-2111-0/+146
| | | | | | | | | | | | | The following notifications have been transformed to the versioned notification framework. * compute_task.build_instances * compute_task.migrate_server * compute_task.rebuild_server Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: Ibfb0a6db5920d921c4fc7cabf3f4d2838ea7f421 Implements: bp versioned-notification-transformation-stein
* Transform volume.usage notificationTakashi NATSUME2018-10-091-0/+22
| | | | | | | | The volume.usage notification has been transformed to the versioned notification framework. Change-Id: Ica45a95d26b602f9a149d42516baf4b84fc01cec Implements: bp versioned-notification-transformation-stein
* Merge "Follow up for Ib6f95c22ffd3ea235b60db4da32094d49c2efa2a"Zuul2018-10-022-2/+2
|\
| * Follow up for Ib6f95c22ffd3ea235b60db4da32094d49c2efa2aBalazs Gibizer2018-09-272-2/+2
| | | | | | | | | | | | | | | | | | This patch removes the host parameter of the notify_about_instance_delete() call as it is always filled with CONF.host value. Change-Id: Iff3b605b9410d5a097b53f532870df65780bc1e4 Implements: bp versioned-notification-transformation-stein
* | Null out instance.availability_zone on shelve offloadMatt Riedemann2018-09-273-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a user shelve offloads a server, the compute manager nulls out the instance host and node attributes. However the availability_zone attribute is left set on the instance so the API will show the instance as in an AZ when really it's not, because an instance that is not on a host is not in a host aggregate so it can't be in an AZ. Keep in mind that there are two ways an instance can be in an AZ: 1. The user specifically requests to create the server in the AZ. 2. The user does not request an AZ and one is assigned via the selected host during server create (or resize, etc). For the first case, the server will always remain in the user-requested AZ even after shelve/unshelve. But in the second case, unshelving the server can result in the server being spawned on a new host in a different AZ - the scheduler does not restrict the AZ in that second case. This change nulls out the instance.availability_zone just like the host and node fields on shelve offload since it's confusing to show a shelved offloaded server in an AZ that doesn't have a host. Final note: the _nil_out_instance_obj_host_and_node method is also called during server create if the build fails and is aborted or rescheduled to another host, and in the case that unshelve fails. In the case of a server build reschedule, conductor will set the instance.availability_zone appropriately based on the alternate host for the reschedule. In the other failure cases, leaving the instance AZ null is appropriate. Change-Id: I25a4f36027390def83cfe25f4f3b4af9660da502 Closes-Bug: #1790221
* | Merge "Transform missing delete notifications"Zuul2018-09-264-0/+63
|\ \ | |/
| * Transform missing delete notificationsBalazs Gibizer2018-08-294-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Iddbe50ce0ad3c14562df800bbc09ec5a7e840485 patch only considered instance delete in the happy case when the instance is scheduled to a compute successfully and the compute is available when the delete action is executed. If the instance is never scheduled to a compute or the compute is not available when the instance is deleted legacy delete notifications are emitted from different places, compute.api instead of compute.manager. The original patch missed these places. There will be subsequent patch(es) handling the same edge cases for soft_delete and force_delete. Change-Id: If0693eab2ed31b5fbfe6cbafa5d67b69c2ed8442 Implements: bp versioned-notification-transformation-stein
* | Transform libvirt.error notificationGábor Antal2018-09-181-0/+25
|/ | | | | | | | | The libvirt.error notification has been transformed to the versioned notification framework. Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: I7d2287ce06d77c0afdef0ea8bdfb70f6c52d3c50 Implements: bp versioned-notification-transformation-stein
* Transform metrics.update notificationTakashi NATSUME2018-07-181-0/+137
| | | | | | | | The metrics.update notification has been transformed to the versioned notification framework. Change-Id: I2f6aba0c032baf181b103d2a16b8e768815170c9 Implements: bp versioned-notification-transformation-rocky
* Merge "Transform instance.live_migration_force_complete notification"Zuul2018-07-162-0/+24
|\
| * Transform instance.live_migration_force_complete notificationGábor Antal2018-07-162-0/+24
| | | | | | | | | | | | | | | | | | | | The instance.live_migration_force_complete.start and instance.live_migration_force_complete.end notifications have been transformed to the versioned notification framework. Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: I2e9a474457a7597a9febc111b13a67ddcf45f29e Implements: bp versioned-notification-transformation-rocky
* | Merge "Microversion 2.64 - Use new format policy in server group"Zuul2018-07-161-1/+1
|\ \ | |/ |/|
| * Microversion 2.64 - Use new format policy in server groupYikun Jiang2018-07-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable users to define the policy rules on server group policy to meet more advanced policy requirement. This microversion brings the following changes in server group APIs: * Add ``policy`` and ``rules`` fields in the request of POST ``/os-server-groups``. * The ``policy`` and ``rules`` fields will be returned in response body of POST, GET ``/os-server-groups`` API and GET ``/os-server-groups/{server_group_id}`` API. * The ``policies`` and ``metadata`` fields have been removed from the response body of POST, GET ``/os-server-groups`` API and GET ``/os-server-groups/{server_group_id}`` API. Part of blueprint: complex-anti-affinity-policies Change-Id: I6911e97bd7f8df92511e90518dba21c127e106a5
* | Transform aggregate.update_prop notificationGábor Antal2018-07-152-0/+22
| | | | | | | | | | | | | | | | | | | | The aggregate.update_prop.start and aggregate.update_prop.end notifications has been transformed to the versioned notification framework. Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: I37b19573b6d0e1131c446fcec361f01fa2560f82 Implements: bp versioned-notification-transformation-rocky
* | Merge "Transform instance.live_migration_rollback_dest notification"Zuul2018-07-152-0/+22
|\ \
| * | Transform instance.live_migration_rollback_dest notificationGábor Antal2018-07-052-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The instance.live_migration_rollback_dest.start and instance.live_migration_rollback_dest.end notifications has been transformed to the versioned notification framework. Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: I8129cbd1785133d4cc1b70bbba6bd7fcc1d21f4a Implements: bp versioned-notification-transformation-rocky
* | | Merge "Transform instance.live_migration_post notification"Zuul2018-07-152-0/+24
|\ \ \
| * | | Transform instance.live_migration_post notificationBéla Vancsics2018-07-052-0/+24
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The instance.live_migration_post.start and instance.live_migration_post.end notifications have been transformed to the versioned notification framework. Co-Authored-By: Alex Szarka <szarka@inf.u-szeged.hu> Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: If9993d5edab5a2f141387a8eb294a9645667ee6b Implements: bp versioned-notification-transformation-rocky
* | | Merge "Transform instance.rebuild_scheduled notification"Zuul2018-07-145-12/+15
|\ \ \ | |_|/ |/| |
| * | Transform instance.rebuild_scheduled notificationGábor Antal2018-07-095-12/+15
| |/ | | | | | | | | | | | | | | | | The instance.rebuild_scheduled notification has been transformed to the versioned notification framework. Co-Authored-By: Takashi Natsume <natsume.takashi@lab.ntt.co.jp> Change-Id: I640562b8dd049ff5b6fea9286dc3082b9d837ed3 Implements: bp versioned-notification-transformation-rocky
* | Add policy field to ServerGroup notification objectYikun Jiang2018-07-121-1/+3
|/ | | | | | | | | | | In this patch, the ServerGroupPayload is updated to include the new ``policy`` field; the ``policies`` field is deprecated for removal but still put into the notification payload for backward compatibility. Related to blueprint complex-anti-affinity-policies Change-Id: Ie739ee8dec4685cd70e735ff83f7f30bc7e95a57
* Add action initiator attribute to the instance payloadshuangyang.qian2018-07-0320-21/+40
| | | | | | | | | | | | | | | The instance action notifications contain the user id and the project id of the owner of the instance. However an instance action might be initiated by another user. It could be another user from the same project or can be an admin from the admin project. To be able to distinguish between the user who initiated the instance action from the user owning the instance we need to add two new fields to the instance action notifications, action_initiator_user and action_initiator_project Change-Id: I649d8a27baa8840bc1bb567fef027c749c663432 Closes-bug: #1744658 Blueprint: add-action-initiator-to-instance-action-notifications
* Remove unnecessary execute permissions of a fileTakashi NATSUME2018-07-021-0/+0
| | | | | TrivialFix Change-Id: I7d014d62878e91b59bf9a52b0e1fe0f9c0c0cad0
* Add instance.unlock notificationYikun Jiang2018-06-251-0/+8
| | | | | | | | | | | The instance.unlock versioned notification is introduced in this patch. The unlock operation just changes the instance.locked to False in API, we send the notification after db operation. Change-Id: Ic750c33b4f88ba9c62ea8cba86915c6010f2cd6f blueprint: trigger-notifications-when-lock-unlock-instances
View Lorry Controller Status