385b4b7723
add_tenants logic:
a) allow add tenant only if flavor already assigned to region(s)
b) each tenant in the request will be validated against the
regions assigned to flavor - at least ONE tenant must
pass validation:
i. if NO tenant in tenant list is associated with any of the
regions assigned to the flavor, Ranger will reject the
request entirely and user will be prompted to submit new
request with valid tenants.
ii. only the tenants in tenant list that pass validation will
be kept in flavor tenant list; those that failed
validation will be DROPPED from the tenant list.
delete_region logic (only for flavors with tenants):
a) if a tenant is associated only with the deleted region, the
delete_region logic will delete the tenant from fms table
and the tenant is dropped from the tenant list.
However, if the tenant is associated with other regions still
assigned to the flavor, the tenant stays in the list.
Change-Id: I31935477733c8597741cf7c7c57350ab1e2b4452
Ranger
Ranger is an OpenStack Resource Management tool capable of managing different types of clouds into one platform. Here are the following of what it provides:
- Multi-region common resource management.
- Light weight, stateless and interface with external self-service portals.
- Runs on DCP.
- Resource agents will run on LCP to orchestrate and keep resources in sync from a
centralized repository.
Before Setting Up
Make sure ranger-agent is running before installing and running ranger since that is required for connecting with Openstack.
Devstack Installation
- Add the following line in local.conf to include ranger repository in your devstack.
-
enable_plugin ranger https://git.openstack.org/openstack/ranger
- Make sure MYSQL_PASSWORD is included for creating and accessing the database.
- Run ./stack.sh from devstack directory.
Installation
- 1. Navigate to ranger/tools directory:
-
$ cd /opt/stack/ranger/tools
- 2. To make changes to the port numbers and other configurations, please go to base_config.py under
-
the orm folder before continuing to the next steps.
- Run ./ranger_create_db.sh to create ranger databases.
- Run ./setup_apache.sh to create conf files for each of the services to apache.
- Run stack_orm.sh to set up ranger.
- If stack_orm.sh is not running properly, navigate to /opt/stack/ranger and run the following:
-
- sudo pip install -r requirements.txt
- sudo python setup.py develop 2>&1 | tee $root_dir/tools/install.log
Generate ranger.conf file
$tox -e genconfig
A blank configuration file will be generated at etc/ranger.conf
Running Ranger Services
- To run each of the services, type in these commands in order to run each of the services.
-
- Audit: orm-audit
- Uuidgen: orm-uuidgen
- RDS (Resource Distributor Service): orm-rds
- RMS (Resource Management Service): orm-rms
- FMS (Flavor Management Service): orm-fms
- CMS (Customer Management Service): orm-cms
- IMS (Image Management Service): orm-ims
For RMS, FMS, CMS, and IMS to be running, Audit, Uuidgen, and RDS must also be running properly as well in order to use them.
Docker Container:
- $ cd ranger
- Update /ranger/tools/.ssh/ranger with your ssh key to your git repo containing heat templates. You can clone https://github.com/ranger , but pull requests won't be accepted.
- $ sudo docker build -t ranger .
- $ sudo docker run -h "ranger" --net host -it --privileged ranger bash Creating docker image and publish will be done by deployment jobs. For Refernce and validation manually image could push using. a). $ docker login <docker_user_id> b). $ docker tag ranger <docker_user_id>/ranger:0.1.0 c). $ docker push <docker_user_id>/ranger:0.1.0
- This docker container will be used by helm chart in order to deploy ranger.