# VOneCloud - Multi Tenancy

**URL:** https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253
**Category:** Product Support
**Created:** [May 9, 2023, 3:46pm UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253 "2023-05-09T15:46:43Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![peno](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/peno/32/7673_2.png) [@peno](https://forum.opennebula.io/u/peno)
#### Post date: [May 9, 2023, 3:46pm UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/1 "2023-05-09T15:46:43Z")

</div>

I have two questions:  
Question 1.

I´m trying to enable multi tenantcy by creating VDC´s and only give group admins access to it.  
Created VDC: tenant1  
Created tenant1-group and tenant1-admin user. Give full access and try to define available resources from vCenter (tenants are divived by datacenter → Cluster (Tenant1-CL1)  
But I see no resources show, when I log on as tenant1-admin. What am I doing wrong ?

1. I have no control panel as show in the guides, is that because i´m testing with f community edition of the vOneCloud ?

Thanks

* * *

**Versions of the related components and OS (frontend, hypervisors, VMs):**

**Steps to reproduce:**

**Current results:**

**Expected results:**

---

<div class="post-metadata">

### Author: ![tinova](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tinova/32/25_2.png) [@tinova](https://forum.opennebula.io/u/tinova)
#### Post date: [May 9, 2023, 4:30pm UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/2 "2023-05-09T16:30:36Z")

</div>

Hi Peter,

Question 1. Not sure what is going on, [this](https://support.opennebula.pro/hc/en-us/articles/360018778938-Cloud-Provisioning-Models-and-User-Roles) might prove useful.

Question 2. It’s been a while since we dumped the control panel, which guide are you using? I suggest using only the official [OpenNebula documentation](https://docs.opennebula.io/6.6/).

---

<div class="post-metadata">

### Author: ![peno](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/peno/32/7673_2.png) [@peno](https://forum.opennebula.io/u/peno)
#### Post date: [May 20, 2023, 4:33pm UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/3 "2023-05-20T16:33:25Z")

</div>

Hi Tinova  
so I will try to separate tentants with VDC´s and own users ?  
Hopefully I can archive multi tenantcy that way, so all tenants gets their own “private” datacenter-\> cluster-Network and storage setup, not viewable or accessble by anyone else but them selves and the oneadmin

Thanks

---

<div class="post-metadata">

### Author: ![tinova](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tinova/32/25_2.png) [@tinova](https://forum.opennebula.io/u/tinova)
#### Post date: [May 22, 2023, 8:41am UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/4 "2023-05-22T08:41:49Z")

</div>

Hi Peter, yes, that’s within the scope of OpenNebula capabilities. One thing you may want to remove is the default VDC that gives access to all resources by default.

---

<div class="post-metadata">

### Author: ![peno](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/peno/32/7673_2.png) [@peno](https://forum.opennebula.io/u/peno)
#### Post date: [May 22, 2023, 4:55pm UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/5 "2023-05-22T16:55:50Z")

</div>

Hi Tino  
If I remove all default (including default VDC) wouldn’t that cut of my own global access with the oneadmin account or ?

I have been reading a lot in the documentation - and in my test setup I have created admin groups - and assigned the customer resources in the VDC creation. But I need a coupling between VDC´s and groups (if any) to make sure that IF I log in as a customer admin, then I would only see the resources assigned to that particular customer VDC

Can you exxplain - or direct me to the documentation that describes that in details ?

In short, how can I, separate each customer with VDC - and admin groups, so when they log in, they can only see own resources - and NOT other customer resources

Hopefully you get my point - otherwise please get back to me - and I will try to explain in more detail  
THanks

---

<div class="post-metadata">

### Author: ![tinova](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/tinova/32/25_2.png) [@tinova](https://forum.opennebula.io/u/tinova)
#### Post date: [May 24, 2023, 8:52am UTC](https://forum.opennebula.io/t/vonecloud-multi-tenancy/11253/6 "2023-05-24T08:52:01Z")

</div>

> [@peno](#):
>
> If I remove all default (including default VDC) wouldn’t that cut of my own global access with the oneadmin account or ?

oneadmin can always see and use all resources, removing default VDC avoid new users to have the same reach

> I have been reading a lot in the documentation - and in my test setup I have created admin groups - and assigned the customer resources in the VDC creation. But I need a coupling between VDC´s and groups (if any) to make sure that IF I log in as a customer admin, then I would only see the resources assigned to that particular customer VDC  
> In short, how can I, separate each customer with VDC - and admin groups, so when they log in, they can only see own resources - and NOT other customer resources

this is the default mode on which OpenNebula operates, provided you delete the default VDC

> Can you exxplain - or direct me to the documentation that describes that in details ?

you can find more info in this WP [Cloud Access Model and Roles — OpenNebula 6.6.3 documentation](https://docs.opennebula.io/6.6/overview/solutions_and_best_practices/cloud_access_model_and_roles.html)

please let me know if you have problems implementing this behaviour, it should be straightforward:

- remove default VDC
- create a new group
- add a user to the group
- create a VDC
- assign a cluster to the VDC with at least a host, vnet and image and system datastores
- assign a VM Template to the group

when the user logs in, he only sees the VM Template assigned, and can deploy it only in the cluster assigned to the VDC
