Bug 1198107
Summary: | [RFE] Add wrapper for js-import and js-export | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Shirly Radco <sradco> | |
Component: | ovirt-engine-reports | Assignee: | Yedidyah Bar David <didi> | |
Status: | CLOSED ERRATA | QA Contact: | Karolína Hajná <khajna> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.6.0 | CC: | didi, gklein, iheim, juwu, lsurette, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, sradco, yeylon, ykaul, ylavi | |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature | |
Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1236757 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-09 21:16:54 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1232822, 1232825, 1258789 | |||
Bug Blocks: | 1119603 |
Description
Shirly Radco
2015-03-03 12:05:06 UTC
Wrapper should set also PATH, see bug 1211709 . Following a discussion with Yaniv and Shirly, we are going to add a script /usr/bin/ovirt-engine-reports-tool with the following options: --export-ad-hoc-reports --import-ad-hoc-reports --change-admin-password --help Patches are mostly ready. Few questions: 1. Should we stop reportsd at beginning and start at end? 2. Should be backup at beginning and restore if we fail? 3. How can I test with the pro version? (In reply to Yedidyah Bar David from comment #4) > Patches are mostly ready. Few questions: > > 1. Should we stop reportsd at beginning and start at end? no > > 2. Should be backup at beginning and restore if we fail? not needed. > > 3. How can I test with the pro version? Sradco will provide a env for that. ovirt-3.6.0-3 release For this bug and for bug 956226 we added a new tool, part of the reports-setup package, called ovirt-engine-reports-tool. When ran without options, it asks what to do. Currently there are 3 options: 1. Change the reports admin password 2. Export saved/adhoc reports - You are prompted for a filename to export to - You can copy this file to some other installation of reports (of the same version) and import it using the next option 3. Import saved/adhoc reports It's based on the same framework of engine-setup. This means, in particular, that it has similar logs, and generates an answerfile which can be used with the option '--config-append=file', in order to run unattended. julie - we might want this in the main documentation, and/or doctext, not sure. If former we should probably open another bug to track this. Please advice and/or handle. Thanks! (In reply to Yedidyah Bar David from comment #7) > For this bug and for bug 956226 we added a new tool, part of the > reports-setup package, called ovirt-engine-reports-tool. When ran without > options, it asks what to do. Currently there are 3 options: > > 1. Change the reports admin password > > 2. Export saved/adhoc reports > - You are prompted for a filename to export to > - You can copy this file to some other installation of reports (of the same > version) and import it using the next option > > 3. Import saved/adhoc reports > > It's based on the same framework of engine-setup. This means, in particular, > that it has similar logs, and generates an answerfile which can be used with > the option '--config-append=file', in order to run unattended. > > julie - we might want this in the main documentation, and/or doctext, not > sure. If former we should probably open another bug to track this. Please > advice and/or handle. Thanks! Hey Didi, Thanks for the need_info. Since it's a new tool with important functions, we should include it in the main documentation. I have opened a docs bug (BZ#1236757) to track the work. Just a few questions: * Is this tool only available from 3.6 onwards? * Which subscription manager repo contains this package and which internal repo contains this package(for internal testing)? * Are there existing documents for this tool? Many thanks, Julie (In reply to Julie from comment #8) > Hey Didi, > Thanks for the need_info. Since it's a new tool with important functions, > we should include it in the main documentation. I have opened a docs bug > (BZ#1236757) to track the work. > > Just a few questions: > * Is this tool only available from 3.6 onwards? Yes. > * Which subscription manager repo contains this package and which internal > repo contains this package(for internal testing)? It's currently part of the existing package ovirt-engine-reports-setup (downstream rhevm-reports-setup). For testing you can use the alpha release [1]. [1] http://lists.ovirt.org/pipermail/users/2015-June/033473.html > * Are there existing documents for this tool? Nothing except this bug. Docs for this bug are covered in bug 1236757. Verified on rhevm-3.6.1.3-0.1.el6.noarch (build 3.6.1-4) 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-0425.html |