To remove duplicated data this patch introduce common json fragments for the instance related notifications and refactors the sample file of instance.delete.start and instance.delete.end. The common sample fragments define an active instance as that is the most common state in the instance action notifications. This way we can minimize the difference between the common sample and the generated notification. Still there will be differences. For example instance.delete.end notification will contain different instance status and some other deletion related fields are also set. To make sure the the sample matches with the generated notification we have to override some of the fields coming from the common sample fragment. Such overrides could be added in the test case directly to the _verify_notification() call as it is done in case of dynamic values like instance uuid. However the sample files not only used in the functional tests but also during the generation of the notification dev-ref. To have meaningful samples in the doc we have to do such overrides during the reference resolving and not directly in the test case. Change-Id: I0669a075c94ba2a435116791e3391d8d745bc639
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: