Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1194812

Summary: Release notes talk about experimental nova v3 but it does not exist
Product: Red Hat OpenStack Reporter: David Kranz <dkranz>
Component: doc-Release_NotesAssignee: Don Domingo <ddomingo>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0 (Juno)CC: dasmith, dkranz, sgordon, yeylon
Target Milestone: gaKeywords: Documentation
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 07:23:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1190788, 1199866    

Description David Kranz 2015-02-20 19:51:25 UTC
Description of problem:


There is a reference to nova v3 at the bottom of 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Release_Notes/ch02s02.html

v3 is "no longer operative" and should not be mentioned.

Comment 3 Stephen Gordon 2015-02-22 09:30:40 UTC
(In reply to David Kranz from comment #0)
> Description of problem:
> 
> 
> There is a reference to nova v3 at the bottom of 
> 
> https://access.redhat.com/documentation/en-US/
> Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Release_Notes/ch02s02.html
> 
> v3 is "no longer operative" and should not be mentioned.

Are you sure about that? Because I know of at least customer using it (I believe on OSP6), which is why I requested the explicit note.

Comment 4 David Kranz 2015-02-23 14:11:11 UTC
Sorry for not being specific enough. OSP6 (Juno) does indeed have a nova v3 endpoint. But that code, and its incompatible changes, has already been removed in kilo in favor of a v2.1 and microversions. Any one who is writing code to the v3 api will have to change it with kilo. The release note about tech preview  makes it sound like v3 is the next thing you can get an early start on. I think it would be better to say that v3 exists but should not be used. Adding Dan Smith to correct me if I am wrong about any of this.

Comment 5 Andrew Dahms 2015-03-12 05:10:20 UTC
Assigning to Don for review.