Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
2.6. Allowing Read-Only Access to the History Database
To allow access to the history database without allowing edits, you must create a read-only PostgreSQL user that can log in to and read from the
ovirt_engine_history database. This procedure must be executed on the system on which the history database is installed.
Procedure 2.1. Allowing Read-Only Access to the History Database
- Create the user to be granted read-only access to the history database:
# psql -U postgres -c "CREATE ROLE [user name] WITH LOGIN ENCRYPTED PASSWORD '[password]';" -d ovirt_engine_history - Grant the newly created user permission to connect to the history database:
# psql -U postgres -c "GRANT CONNECT ON DATABASE ovirt_engine_history TO [user name];" - Grant the newly created user usage of the
publicschema:# psql -U postgres -c "GRANT USAGE ON SCHEMA public TO [user name];" ovirt_engine_history - Generate the rest of the permissions that will be granted to the newly created user and save them to a file:
# psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname || ' TO [user name];' FROM pg_class JOIN pg_namespace ON pg_namespace.oid = pg_class.relnamespace WHERE nspname = 'public' AND relkind IN ('r', 'v');" --pset=tuples_only=on ovirt_engine_history > grant.sql - Use the file you created in the previous step to grant permissions to the newly created user:
# psql -U postgres -f grant.sql ovirt_engine_history - Remove the file you used to grant permissions to the newly created user:
# rm grant.sql - Add the following lines for the newly created user to the
/var/lib/pgsql/data/pg_hba.conffile:# TYPE DATABASE USER ADDRESS METHOD host ovirt_engine_history [user name] 0.0.0.0/0 md5 host ovirt_engine_history [user name] ::0/0 md5 - Reload the PostgreSQL service:
# systemctl reload postgresql - You can test the read-only user's access permissions:
# psql -U [user name] ovirt_engine_history -h localhost Password for user [user name]: psql (9.2.23) Type "help" for help. ovirt_engine_history=> - To exit the
ovirt_engine_historydatabase, enter\q.
The read-only user's
SELECT statements against tables and views in the ovirt_engine_history database succeed, while modifications fail.