summaryrefslogtreecommitdiff
path: root/doc/notification_samples/instance-create-error.json
Commit message (Collapse)AuthorAgeFilesLines
* Add full traceback to ExceptionPayload in versioned notificationsKevin_Zheng2018-06-191-2/+3
| | | | | | | | | | | | | | | | | | | | This patch adds full traceback to ExceptionPayload in versioned notifications. The instance fault field and instance-action REST API has already provide the traceback to the admin users (controlable through policy) and the notifications are also admin only things as they are emitted to the message bus by default. So it is assumed that security is not a bigger concern for the notification than for the REST API. On the ML [1] post there was no objection to add new string field to the ExceptionPayload that will hold the serialized traceback object. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128105.html Implements: blueprint add-full-traceback-to-error-notifications Change-Id: Id587967ea4f9980c292492e2f659bf55fb037b28
* Deduplicate instance.create notification samplesBalazs Gibizer2017-11-281-70/+6
| | | | | | | | | This patch refactors the sample files of instance.create notifications. As these notifications use a different payload class as the most of the instance notifications a new common payload sample fragment was also needed. Change-Id: I7a8e9507ee30d404e075a46e48070a0f94276e33
* Add FlavorPayload.description for versioned notificationsMatt Riedemann2017-11-141-2/+3
| | | | | | | | | | This adds the description field to the FlavorPayload for versioned notifications on flavor create/update/delete notifications. Part of blueprint flavor-description Change-Id: I9a5dc8b603b5e4e0d37c59cf2749e3ffc217580c
* Add 'updated_at' field to InstancePayload in notificationsTakashi NATSUME2017-07-251-1/+2
| | | | | | Change-Id: Iddc5ec3b5053ddf5dce73c86edca26c4552d451b Implements: bp versioned-notification-transformation-pike Closes-Bug: #1684860
* Add tags to instance.create NotificationKevin_Zheng2017-07-241-1/+2
| | | | | | | | | This patch added a new field 'tags' to InstanceCreatePayload. Partial-implement: bp additional-notification-fields-for-searchlight Partial-implement: blueprint support-tag-instance-when-boot Change-Id: Iefaa9da4e136fd5e823bf7b11c8aa5b4cd6d7de8
* Add BDM to InstancePayloadBalazs Gibizer2017-07-121-1/+2
| | | | | | | | | | | | This patch adds bdm related data to InstancePayload. As loading BDM can be expensive a new configuration flag 'bdms_in_notifications' is introduced. If this is set to false (as by default) then the instance notifications will contain 'null' value in block_devices field. If this configuration flag is set to true then the block devices will be loaded from the db and will be included in the notification payload. Implements: bp additional-notification-fields-for-searchlight Change-Id: I18e7483ec9a484a660e1d306fdc0986e1d5f952b
* Add key_name field to InstancePayloadBalazs Gibizer2017-06-281-1/+2
| | | | | | | | Add key_name field to InstancePayload which means every instance.<action> notification now have key_name field based on the instance.key_name. Change-Id: I39059c5077c790aa85dff6b4563f581c54536b86 Implements: bp additional-notification-fields-for-searchlight
* Add keypairs field to InstanceCreatePayloadBalazs Gibizer2017-06-281-1/+13
| | | | | | | | Add keypairs field to instance.create notifications based on instance.keypairs field. Change-Id: I30e068d4de4b45f34308665de37d4cb9d6502111 Implements: bp additional-notification-fields-for-searchlight
* Add separate instance.create payload typeBalazs Gibizer2017-06-161-1/+1
| | | | | | | | | | | | | | | | | There are two parallel efforts to add new fields to the instance.create notification only. Currently instance.create notification uses the generic InstanceActionPayload ovo as the payload type. This patch creates a separate InstanceCreatePayload ovo so that fields like keypairs and tags can be added only to this specific payload class later in separate patches. The keypair and tags field are not added directly to the base InstancePayload class because both field need extra db query to fetch. So sending them at every instance action (e.g. reboot) could cause db load. The version of the instance.create payload is not bumped as the content of the payload is the same just the name of the type is changed. Change-Id: I90fb7beb450100de8f4e542921b99f043c529a0f
* Adding auto_disk_config field to InstancePayloadSujitha2017-04-211-1/+2
| | | | | | | | | Add auto_disk_config field to InstancePayload based on instance.auto_disk_config boolean value. If true, set it to AUTO else MANUAL. Implements: bp additional-notification-fields-for-searchlight Change-Id: I18af99479562e2fe5e74e6e1252b804b074fee58
* Set instance.availability_zone whenever we scheduleDan Smith2017-03-231-1/+1
| | | | | | | | | | | | This ensures that instance.availability_zone reflects what AZ the instance is actually in. In the case where no AZ was requested at boot, previously this would always be some default value, which isn't as useful to the things that need to consider what AZ the instance is actually in (without doing all the aggregate math to determine it on the fly). Related to blueprint cells-aware-api Change-Id: I8d426f2635232ffc4b510548a905794ca88d7f99
* handle uninited fields in notification payloadBalazs Gibizer2017-03-031-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to the not strict handling of uninitialized fields during notification payload population it is possible that the emitted notification missing some of the fields defined in the schema. There are two problematic cases: 1) no load tirggered for lazy loaded fields. If the field was not loaded it is not added to the payload. 2) uninitialized, not lazy loadable fields are not added to the payload. This patch makes sure that lazy load is triggered. If the field is not lazy loadable and also not initialized then related payload field will be set to None. If the payload field is not nullable the code will fail to make sure that the inconsistency is detected. The following changes cannot be split to different commits because as soon as the generic schema population code is fixed every listed notification starts behaving differently. In some cases the availability_zone field of the Service object is left unitialized by both the constructor and the obj_load_attr function this caused that the availability_zone field of the service.update notification was missing from the emitted notification payload. The extra_specs field of the Flavor object is not lazy loadable and not initialized in the Flavor destroy case. So the extra_specs field of the FlavorPayload needed to be made nullable. The projects field of the Flavor object is lazy loaded but when the Flavor object is loaded as part of an Instance object Flavor is orphaned and no lazy load is allowed on that Flavor object. In this case the projects field of the FlavorPayload will be set to None to signal that the information is not available. This also means that the projects field of the FlavorPayload needed to be changed to nullable. The hosts and id fields of the Aggregate object is not initialized during the create of the Aggregate before the aggregate.create.start needs to be sent. Therefore these fields needs to be nullable. Closes-Bug: #1653221 Change-Id: Ib122cd98ee0cc31938d5ff1d5c753053267a3bd4
* Merge "Improve flavor sample in notification sample tests"Jenkins2017-01-231-1/+3
|\
| * Improve flavor sample in notification sample testsBalazs Gibizer2017-01-111-1/+3
| | | | | | | | | | | | | | | | This patch adds an extra_specs key to the flavor used in the instance action sample test to make the samples more realistic. Change-Id: I5ec2b536469daaea16efb1ef1537a951dc52997a Implements: bp flavor-notifications
* | Merge "Update notification for flavor"Jenkins2017-01-111-1/+2
|\ \ | |/
| * Update notification for flavorMatt Riedemann2017-01-111-1/+2
| | | | | | | | | | | | | | | | This patch adds versioned notification for flavor update operation. Implement blueprint: flavor-notifications Change-Id: I770e3c0c1675bbb7844b13826f3fdc48ad5491a2
* | Merge "Notifications for flavor operations"Jenkins2017-01-111-2/+8
|\ \ | |/
| * Notifications for flavor operationsliyingjun2017-01-091-3/+9
| | | | | | | | | | | | | | | | | | This patch implements the versioned notifications for flavor create and destroy. Implement blueprint: flavor-notifications Change-Id: Icc2169b87ffba4e7e2079076a82029156c584c6a
* | Add more field's in InstancePayloadAnusha Unnam2016-12-291-2/+4
|/ | | | | | | | | Add instance's locked field and instance's display_description field in InstancePayload. Implements: bp additional-notification-fields-for-searchlight Change-Id: Iceae25ca8a0d7f2e5f22cab1364215bda2fae93c
* Transform instance.create.error notificationGábor Antal2016-11-221-0/+59
Along with the transformation changes, I modified notify_about_instance_action method so it can handle errors now. (It wraps the exception object into an ExceptionPayload.) Implements: bp versioned-notification-transformation-ocata Change-Id: I171990290c8de529c9521a5ee556f97b18b741b0
View Lorry Controller Status