Bug 1341761

Summary: Move Packstack to Red Hat OpenStack Developer Tools channel
Product: Red Hat OpenStack Reporter: Alan Pevec <apevec>
Component: openstack-packstackAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Jason Joyce <jjoyce>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: abregman, aortega, ftaylor, jjoyce, jschluet, jtrowbri, lhh, markmc, mburns, mpryc, nbarcet, nlevinki, pmyers, rrussell, sclewis, sgordon, srevivo
Target Milestone: rcKeywords: FutureFeature, Reopened, Triaged
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-9.0.0-0.20160922140727.3f43120.1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 15:35:51 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:

Description Alan Pevec 2016-06-01 17:34:52 UTC 
TripleO is the supported installer for production installations and to make that clear Packstack should not be included in the OSP distribution.

Packstack use-case for proof-of-concept installations and quick on-boarding will continue to be served within RDO community[1] as an upstream project.
It will be still possible to use packages from OSP repositories from Red Hat CDN[2] using upstream Packstack version, so if needed, it could be used as any other upstream installation project against OSP.


[1] https://www.rdoproject.org/install/quickstart/
[2] https://github.com/openstack/packstack/blob/0862eb732ba7464c7f58dc018f505630e14a4c01/docs/packstack.rst#rhel-config
Comment 16 RHEL Program Management 2016-07-01 21:35:22 UTC 
Product Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 26 errata-xmlrpc 2016-12-14 15:35:51 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2948.html