From cc5acd42f53a267e7f634104d1831c55a7312dc8 Mon Sep 17 00:00:00 2001
From: Enol Fernandez <enol.fernandez@egi.eu>
Date: Tue, 17 Oct 2023 15:09:00 +0100
Subject: [PATCH 1/2] 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 <new_group>)
    ```
 
-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 <your project>
    ```
 
+1. Set the `VO` property to the name of the VO that you are supporting:
+
+   ```shell
+   $ openstack project set --property VO=<name of the VO> <your project>
+   ```
+
 ## Keystone Mapping
 
 Expand your `mapping.json` with the VO membership to the created group
@@ -105,16 +111,8 @@ openstack role add member --user <your caso user> --project <your new vo project
 
 ## Information system
 
-Add the mapping to your site configuration with a new Pull Request to the
-[fedcloud-catchall-operations repository](https://github.com/EGI-Federation/fedcloud-catchall-operations)
-
-```yaml
----
-vos:
-  - name: <vo name>
-    auth:
-      project_id: <your new vo project>
-```
+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
 

From af8a8526e4733d36f95bc82c761bdc901a60c51d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Enol=20Fern=C3=A1ndez?= <enol.fernandez@egi.eu>
Date: Tue, 24 Oct 2023 12:33:24 +0100
Subject: [PATCH 2/2] Apply suggestions from code review

Co-authored-by: Sebastian Luna-Valero <sebastian-luna-valero@users.noreply.github.com>
---
 content/en/providers/cloud-compute/openstack/vo_config.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/en/providers/cloud-compute/openstack/vo_config.md b/content/en/providers/cloud-compute/openstack/vo_config.md
index a9c50430f0..b97058f25b 100644
--- a/content/en/providers/cloud-compute/openstack/vo_config.md
+++ b/content/en/providers/cloud-compute/openstack/vo_config.md
@@ -27,10 +27,10 @@ for the given VO.
    $ openstack role add member --group $group_id --project <your project>
    ```
 
-1. Set the `VO` property to the name of the VO that you are supporting:
+1. Set the `egi.VO` property to the name of the VO that you are supporting:
 
    ```shell
-   $ openstack project set --property VO=<name of the VO> <your project>
+   $ openstack project set --property egi.VO=<name of the VO> <your project>
    ```
 
 ## Keystone Mapping
@@ -111,7 +111,7 @@ openstack role add member --user <your caso user> --project <your new vo project
 
 ## Information system
 
-If you are correctly setting the `VO` property to your projects, the configuration will
+If you are correctly setting the `egi.VO` property to your projects, the configuration will
 be automatically retrieved by the cloud-info-provider.
 
 ## VM Image Management