From 9884c39d9d3487192e77309b2ed0bc26e9489a12 Mon Sep 17 00:00:00 2001 From: "Nicolas Barcet (nijaba)" Date: Sat, 6 Oct 2012 17:12:31 +0200 Subject: [PATCH] add quantum release note Found this note in the quantum notification code, think it is worth being in the release notes. Change-Id: I6e30d47e1f50fb0f7fda6e0923d5836a2b133110 --- ReleaseNotes | 5 +++++ doc/source/releasenotes/folsom.rst | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/ReleaseNotes b/ReleaseNotes index 2a31ad54aa..9769c83e49 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -15,6 +15,11 @@ to support nova-volume in favor of Cinder. A detailed list of meters covered per component can be found at: xxxx +Quantum delete notifications do not include the same metadata as the other +messages, so we ignore them for now. This isn't ideal, since it may mean we +miss charging for some amount of time, but it is better than throwing away the +existing metadata for a resource when it is deleted. + The only tested and complete database backend is currently MongoDB, the SQLAlchemy one is still work in progress. diff --git a/doc/source/releasenotes/folsom.rst b/doc/source/releasenotes/folsom.rst index c9b94cb9d2..e208d19410 100644 --- a/doc/source/releasenotes/folsom.rst +++ b/doc/source/releasenotes/folsom.rst @@ -31,6 +31,11 @@ to support nova-volume in favor of Cinder. A detailed list of meters covered per component can be found at: xxxx +Quantum delete notifications do not include the same metadata as the other +messages, so we ignore them for now. This isn't ideal, since it may mean we +miss charging for some amount of time, but it is better than throwing away the +existing metadata for a resource when it is deleted. + The only tested and complete database backend is currently MongoDB, the SQLAlchemy one is still work in progress.