Bug 1417403
| Summary: | [RFE] TripleO UI to expose JS options | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | arkady kanevsky <arkady_kanevsky> |
| Component: | openstack-tripleo-ui | Assignee: | Jiri Tomasek <jtomasek> |
| Status: | CLOSED WONTFIX | QA Contact: | Amit Ugol <augol> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 12.0 (Pike) | CC: | arkady_kanevsky, augol, beth.white, brault, cdevine, christopher_dearborn, dcain, dmatthew, dprince, jbuchta, jcoufal, jjoyce, John_walsh, jrist, jschluet, kbasil, kholtz, kurt_hey, mbarnett, mburns, morazi, rajini.karthik, randy_perryman, slinaber, sumedh_sathaye, tvignaud |
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | NeedsAllocation | ||
| Fixed In Version: | openstack-tripleo-ui-9.3.1-0.20180909174557.1a18ba7.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-24 13:15:10 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: | 1476902, 1577362 | ||
|
Description
arkady kanevsky
2017-01-28 18:15:17 UTC
I think the requirement here is to provide a mechanism so that you can upload custom "default" templates as part of undercloud post install configuration. We already have a Mistral workflow called tripleo.plan_management.v1.create_deployment_plan which might be able to be used to do this. This workflow is exposed via the Mistral API and has parameters to be able to use a custom source_url and swift container. Sorry, I'm afraid I don't really understand this RFE. What are "JS options"? Adding custom default templates seems like a strange requirement to me - could a custom t-h-t package be provided? How would users let the undercloud install where the custom templates are? but yes, all we need is a plan name and a directory or git repo to retrieve the templates from - then we can create the plans. Arkady can you elaborate on this RFE more, please? Do you have mockups or anything similar? Also do you have anything we can test this on if we are able to expose it? This seems like 4 different RFEs. Perhaps some of this has been exposed already? If possible I'd like to split this into 4 RFEs for consideration in a later release. Sumedh, can you respond to Jason? I believe most of what is being asked for here is already available, but will confirm with the partner. TripleO UI to expose JS options: * Instance HA, This is being introduced in OSP 13 in BZ 1264181 * cinder options Ceph/EQL/CMPL/ScaleIO, Ceph is already fully supported and integrated with OSPd. For the rest of the Dell EMC storage offerings, they would need to have the appropriate OOO patches merged upstream if not already. ScaleIO is being done in BZ 1385391. * Ephemeral storage options: compute local/shared backend storage Not sure what is being asked here. * Expose automatic role assignment to overcloud nodes by type Not sure of the ask here, but bare-metal nodes can already be detected and automatically assigned a custom role based on the profile detected. Need more info from Sumedh. All the cinder patches for OOO are already upstream for EQL/CMPL/VNX etc All requested features are available now With TripleO UI being deprecated upstream is this really needed? That tells me that for OSP16 UI will be dropped. Is this correct? Dropped in OSP15. UI has been deprecated as of OSP 14. |