Bug 1875810
| Summary: | [RHOSP 16.1] [RFE] New component: tripleo-powerflex (Powerflex integration with TripleO) | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | arkady kanevsky <arkady_kanevsky> |
| Component: | ansible-tripleo-powerflex | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16.1 (Train) | CC: | abishop, a.stripeikis, brault, christopher_dearborn, emilien, gael_rehault, gcharot, gfidente, Ivan.Pchelintsev, jeanpierre.roquesalane, jjoyce, jvisser, kholtz, kurt_hey, mburns, morazi, pgrist, rajini.karthik, sam.wan, Sam.Wan, shrjoshi, spower, vladislav.belogrudov |
| Target Milestone: | z3 | Keywords: | FutureFeature, OtherQA, Triaged |
| Target Release: | 16.1 (Train on RHEL 8.2) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ansible-tripleo-powerflex-0.0.1-1.20201118113650.66f52a0.el8ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-15 18:36:32 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: | 1877881 | ||
| Bug Blocks: | 1595325, 1715964 | ||
|
Description
arkady kanevsky
2020-09-04 12:38:43 UTC
Rajini, please, check if any other patches also need to be included. I think that all other TripleO patches are already have BZs and are targeted for z2. Expect that we can land it in z3 so we can release it by year end. The first step to get the package in OSP is to add it to RDO. Please follow the process show in: https://www.rdoproject.org/documentation/add-packages/#how-to-add-a-new-openstack-package-to-rdo-trunk Thanks Alfredo. Adding Chris to guide us to follow what wad done for out of tree python-drac-client repo for https://github.com/dell/tripleo-powerflex. (In reply to arkady kanevsky from comment #1) > Rajini, > please, check if any other patches also need to be included. > I think that all other TripleO patches are already have BZs and are targeted > for z2. Yes, all patches needed are targeted for Z2 (In reply to arkady kanevsky from comment #1) > Rajini, > please, check if any other patches also need to be included. > I think that all other TripleO patches are already have BZs and are targeted > for z2. Yes, all patches needed are targeted for Z2 https://bugzilla.redhat.com/show_bug.cgi?id=1877881 - RDO Package Review BZ Can we get a drop release candidate of z3 with this BZ in it to test before GA? Two questions: - Who'll be in charge of maintaining this repo and push any future release? - How is the release model of this kind of RDO repository? I confirmed ansible-tripleo-powerflex-0.0.1-1.20201118113650.66f52a0.el8ost.noarch.rpm is available in OSP-16.1 composes starting with RHOS-16.1-RHEL-8-20201124.n.0. The Dell EMC team should have access via DCI. As for JP's questions in comment #12, the package will now follow the same workflow as the rest of the OSP packages. Generally speaking, package updates will flow into OSP via RDO. It will be Dell EMC's responsibility for maintaining things in RDO, which means submitting RDO patches to get updates you make into RDO. From there, the RDO updates will flow down into OSP. I think this means Dell EMC will need to "cut a release" (bump the semantic version), then submit a patch to RDO to adopt the new version in the appropriate RDO release(s). We also have the ability to handle downstream updates, but the usual rules apply (patches must be "upstream first"). 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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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://access.redhat.com/errata/RHEA-2020:5413 |