From 1992842043393c597bf82142cf963b82cfa2ee59 Mon Sep 17 00:00:00 2001 From: Sean Pryor Date: Mon, 30 Oct 2017 19:30:37 +0530 Subject: Update README.md --- README.md | 37 ++----------------------------------- 1 file changed, 2 insertions(+), 35 deletions(-) diff --git a/README.md b/README.md index 6642cbe..a6c9256 100644 --- a/README.md +++ b/README.md @@ -1,35 +1,2 @@ -This is a repository of the files/tools we are developping around -integrating the sevone (monitoring software) into RH-OSP. - -This project includes several areas: -- Add policy files to the overcloud to restrict the 'readonly' role and prevent - update/create/delete operations. - -- Add tooling (OBSOLETE since this will be done through node-payload in the - osp10 templates) to push/update policies on the overcloud. - -- Provide a MOP (Method of procedure) to enable Sevone pre-requisites on - both the undercloud and overcloud. An ASCII version of the MOP is provided - in this repository. - -This work on the 'readonly' role was a request of the VZW HQ Planning group. - -Here is how it works: - -On the undercloud, as the 'stack' user perform the following steps: - - 1) source stackrc - 2) git clone https://gitlab.cee.redhat.com/vcojot/OSP-Readonly-Policies/tree/master - 3) ./policydir/files/push_readonly_policies_to_overcloud.sh - 4) source overcloudrc - 5) openstack role create readonly - -(this will auto-detect the controllers and push the appropriate policies) - -To restrict a user, then simply do add the 'readonly' role to the user, do a: - - openstack role add --project --user readonly - -To lift the restrictions and re-enable modifications to the overcloud, do a: - - openstack role remove --project --user readonly +This repo contains the current ongoing work of attempting to implement a +read-only role via policy.json in OSP10 \ No newline at end of file -- cgit