Bug 1111972
| Summary: | Rename staypuft-installer to osp-installer for downstream distribution | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Arthur Berezin <aberezin> |
| Component: | rhel-osp-installer | Assignee: | Mike Burns <mburns> |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.0 (RHEL 7) | CC: | aberezin, apevec, dnavale, mburns, nbarcet, rhos-maint |
| Target Milestone: | ga | ||
| Target Release: | 5.0 (RHEL 6) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhel-osp-installer-0.0.25-3.el6ost | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-04 18:34:58 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
Arthur Berezin
2014-06-22 12:42:16 UTC
Arthur, I can change the script that people use from staypuft-installer to osp-installer (simple change). Do we want to change answer-files? Do we want to change RPM names? Or are those acceptable as they are? Ideally all RPMs and commands that are part of the main install flow should have downstream name rhel-osp-installer, where Staypuft is upstream name. so we do want to change the RPM name, and installer command. How much work would it require to change(and maintain) a downstream name for the answer-file ? if that's insignificant, than ideally we would want to change the answer file name as well. Verified with: rhel-osp-installer-0.0.25-5.el6ost.noarch RPM name : rhel-osp-installer-0.0.25-5.el6ost.noarch Installer name: rhel-osp-installer Answer files: /etc/foreman/rhel-osp-installer.answers.yaml /etc/foreman/rhel-osp-installer.yaml 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. http://rhn.redhat.com/errata/RHEA-2014-1003.html |