Bug 905858

Summary: [RFE] Installer should ask whether to set up remote access and r/o user in the history database
Product: Red Hat Enterprise Virtualization Manager Reporter: Dan Yasny <dyasny>
Component: ovirt-engine-setupAssignee: Moran Goldboim <mgoldboi>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: high    
Version: 3.1.1CC: acathrow, bazulay, dyasny, iheim, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.3.0Flags: sgrinber: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-09 12:17:22 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: 737598, 975620, 978236, 978237, 978238    

Description Dan Yasny 2013-01-30 10:32:55 UTC
Description of problem:

When DWH and reports are installed, external access may be required, as described in https://bugzilla.redhat.com/show_bug.cgi?id=875500

Besides, for external polling we should set up a readonly user in the database automatically.


Requirements:
Installer reaching the database user/password settings
- Would you like to configure the database for remote access? (configure pg_hba accordingly, and if a "yes" is chosen here...)
- Would you like to configure a read-only database user:
- Username
- Password
(run the GRANT SELECT ON ... procedure here)


In case of remoteDB:
- no need to ask for remote access confirmation
- spew out something like:
If a read-only user access is required please run the following in your remote Database:
- command to create new user and set up password
- command to grant readonly privileges on the history db tables

Comment 1 Andrew Cathrow 2013-02-28 16:50:20 UTC
We should also provide a script in dbscripts for 3.3 to allow a customer to create a r/o user on an existing installation.

Comment 2 Itamar Heim 2013-06-09 12:17:22 UTC

*** This bug has been marked as a duplicate of bug 737598 ***