Bug 1316312 - [director] Need to add old version support information to docs
Summary: [director] Need to add old version support information to docs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 23:35 UTC by Mike Burns
Modified: 2016-05-03 16:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 16:55:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mike Burns 2016-03-09 23:35:51 UTC 
Description of problem:

With the release of OSPd 8, we'll have the ability to manage older versions of the overcloud.  The support matrix is as follows:

OSPd 8.0 will support updating OSP 7.0.4 and later overclouds to the latest 7.0.z updates.

OSPd 8.0 will support deploying the latest 7.0.z overcloud (>=7.0.4)

OSPd 8.0 will support scaling operations of 7.0.z overclouds >= 7.0.4

Important notes:  

Users must update their undercloud/overcloud to at least 7.3/7.0.4 prior to upgrading the undercloud to 8.0.  There will be no support for managing an overcloud older than 7.0.4 in OSPd 8.0.

Deployments with tuskar will need to stay on OSPd 7.3.  There is no support for tuskar in OSPd 8.0
Comment 1 Mike Burns 2016-03-09 23:36:20 UTC 
Jarda, can you confirm scope above?
Comment 3 Dan Macpherson 2016-05-03 03:30:36 UTC 
Hi Mike,

I think we've already discussed this, but the support matrix is here:

https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/director-installation-and-usage/chapter-10-upgrading-the-environment

Are there any further changes required for this item?
Comment 4 Mike Burns 2016-05-03 16:41:04 UTC 
looks good to me.
Note You need to log in before you can comment on or make changes to this bug.