From cc5acd42f53a267e7f634104d1831c55a7312dc8 Mon Sep 17 00:00:00 2001 From: Enol Fernandez Date: Tue, 17 Oct 2023 15:09:00 +0100 Subject: [PATCH] Add information about the VO property --- .../cloud-compute/openstack/vo_config.md | 22 +++++++++---------- 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/content/en/providers/cloud-compute/openstack/vo_config.md b/content/en/providers/cloud-compute/openstack/vo_config.md index b893b983e2..a9c50430f0 100644 --- a/content/en/providers/cloud-compute/openstack/vo_config.md +++ b/content/en/providers/cloud-compute/openstack/vo_config.md @@ -15,18 +15,24 @@ The usual method of supporting a VO is by creating a local project for it. You should assign quotas to this project as agreed in the OLA defining the support for the given VO. -1. Create a group where users belonging to the VO will be mapped to: : +1. Create a group where users belonging to the VO will be mapped to: ```shell group_id=$(openstack group create -f value -c id ) ``` -1. Add that group to the desired local project: : +1. Add that group to the desired local project: ```shell $ openstack role add member --group $group_id --project ``` +1. Set the `VO` property to the name of the VO that you are supporting: + + ```shell + $ openstack project set --property VO= + ``` + ## Keystone Mapping Expand your `mapping.json` with the VO membership to the created group @@ -105,16 +111,8 @@ openstack role add member --user --project - auth: - project_id: -``` +If you are correctly setting the `VO` property to your projects, the configuration will +be automatically retrieved by the cloud-info-provider. ## VM Image Management