sync from testing branch for release 7.1 #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When executing a pagination query a "next" link is included in the API reply when there are more items then the specified limit. See pagination documentation for more information: http://docs.openstack.org/api/openstack-compute/2/content/ Paginated_Collections-d1e664.html The caller should be able to invoke the "next" link (without having to re-format it) in order to get the next page of data. The documentation states "Subsequent links will honor the initial page size. Thus, a client may follow links to traverse a paginated collection without having to input the marker parameter." The problem is that the "next" link is always scoped to the non-detailed query for flavors and images. For example, if you execute "/v2/<tenant>/flavors/detail?limit=1", the "next" link does not have the URL for a detailed query and is formatted as "/v2/<tenant>/flavors?limit=1&marker=<marker>". In this case the "next" link needs to be scoped to "/v2/<tenant>/flavors/detail". Change Ib06a6cc6e2dd5e2c8c16986ee256a58752626eb9 fixed this for servers only. This change applies the same fix for the other APIs, specifically flavors and images. The user could work around this issue my manually inserting '/details' into the "next" link URL. APIImpact Closes-bug: 1410431 Change-Id: I8e57464374051de64a72919c3ddbabd45caecf6f (cherry picked from commit f233c65) Bug-ES #9566 http://192.168.15.2/issues/9566 (cherry picked from commit f182827)
Signed-off-by: Zhao Chao <[email protected]> (cherry picked from commit 4ee2b21)
This commit implemented get/update user_data feature. Signed-off-by: blkart <[email protected]> (cherry picked from commit bcc3b2a)
Testing nova 2014.2-7.0 for eayunstack 3.0
When detaching block devices on rebuild we only notify Cinder it's safe to detach a volume, but don't actually tell the driver to do that first. Closes-Bug: #1440762 Change-Id: I017bf749f426717dc76cf99a387102848fb1c541 (cherry picked from commit 337471b) --------------------------------------------------------------------- squashed with another change that fixes a bug introduced in the first --------------------------------------------------------------------- rebuild: fix rebuild of server with volume attached This was meant to be fixed by I017bf749f426717dc76cf99a387102848fb1c541 , but it didn't take into account that BDM entry was destroyed, which caused the rebuild to fail when spawning the instance. Add a new parameter to detach_volume() to bypass destroying of BDM, as we just want to detach a volume first and then re-attach it again. A Tempest test is added in I50557c69b54003d3409c8e977966f5332f4fe690 to make sure this is actually tested in the gate. Closes-Bug: #1440762 Co-Authored-By: melanie witt <[email protected]> Conflicts: nova/tests/unit/compute/test_compute.py nova/tests/unit/compute/test_compute_mgr.py NOTE(mriedem): The tests were moved under nova/tests/unit in Kilo. Change-Id: I9134fbf5ce72c32cca91de90001c09e00b4e19e8 (cherry picked from commit 25f15b0) (cherry picked from commit eb3b1c8) (cherry picked from commit 5cf20f3) (cherry picked from commit 8f5e491)
If the instance was booted from volume, then rebuild will only change the image, but the instance will still boot from the original volume. Create a new volume from the image then replace the old root volume with it. In case of evacuation leave the root volume untouched. Closes-Bug: #1482040 Closes-Bug: #1378689 Closes-Bug: #1474253 Related upstream commit: a93efff2f025fa824f669836be0794a62103b2f0 Signed-off-by: blkart <[email protected]> (cherry picked from commit a216540)
Currently, we detach block devices before an instance is shut down, which means all the data, which hasn't been fsynced yet, will possibly be lost. Closes-Bug: #1471216 Related-Bug: #1440762 Related upstream commit: 7fe20e9 Signed-off-by: blkart <[email protected]> (cherry picked from commit 54565dd)
Testing nova 2014.2-7.1 for eayunstack 3.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.