RMS has three rules which were not included into
the top level policy.json. These rules have been
moved to the top level in order to fix 403 against
uuid server. RMS specific policy.json was not
pointed at by any code, so with this fix
the file has been removed.
Change-Id: I8bf507a6336b8b07885e3e11490f1324bf29c5d4
changed ranger policy.json to allow
use of expected project when running
tempest tests against ranger
Change-Id: I1319404899a68140443517a818497ac0856746f5
When an image is created with a url that is in excess
of 240 characters, the transacations table in ranger
audit database throws error "sqlalchemy.exc.DataError:
(MySQLdb._exceptions.DataError) (1406, "Data too long
for column 'event_details' at row 1")". By removing
this url from the log, we prevent this error while
maintaining other important data. Also restored ranger
to allowed projects in ranger policy.json
Change-Id: I4af73beed9bd40054f8d1e7281bc6f9216fdd243
Ranger region now includes a field which declares
which openstack domain a resource should be deployed
in. This change updates rds to create resources in
that domain via the heat template
Change-Id: I43144eb75a34661fae15399b9d32842d65327621
Refactor ranger to allow domain
for resource deployment to be
defined in create region api call,
rather than only being retrieved
from ranger configuration.
Change-Id: I1b481c49d4402438c8aa91a8ebd8b6dbe797997b
policy.json will be updated to become
monolithic under orm/ directory, maintaining
all previous rules. Also update policy.json to
allow for ranger project as an authorized project
to use for authing through ranger. Also removes
unused git classes.
Change-Id: I547cb601318b507f759c264644c781743673be72
Update Ranger to remove logic to stage heat template to git repo.
Instead, pass heat template directly to ranger-agent.
Added logic to create/update/delete heat template entry in rds database.
Remove git repo logic from ranger.
Ranger to pass token to ranger-agent for request authentication.
Reintroduce commit #693590 changes that were inadvertently removed.
Change-Id: If95076e8343bbb50a7231b74fd4a80906b2a0785
Logging level can now be set from conf file using debug_level.
Default setting is ERROR. Use debug_level to override the setting.
Valid choices are CRITICAL, DEBUG, ERROR, INFO and WARNING
Change-Id: Idcd81bdb6b909a3f168bae11bfa0c283ec0d757c
Cleanup Ranger logging logic and allow the following logging option:
- logging to console only
- logging to logfile only
= logging to console AND logfile
Also cleanup authentication logic as well.
Change-Id: I8e422a1c9e44c4f58078d93d4f2a5a009df91ba1
Created scripts for setting up ranger as well as
modifying the service files as part of the setup.
Change-Id: Ic1d77dd03fa2287097f35f3de5e890cfb768f71b