NuKVM/xen-orchestra
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update self_service.md

Browse Source
This commit is contained in:
Olivier Lambert 2016-02-19 17:04:18 +01:00
parent e845a14f26
commit 39387b828c
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
self_service.md
View File

@ -2,17 +2,21 @@
The self-service feature is the possibility for users to create new VMs. That's different from delegating existing resources to them, and it leads to a lot of side-effects. The self-service feature is the possibility for users to create new VMs. That's different from delegating existing resources to them, and it leads to a lot of side-effects.
> This feature is not yet available yet. Still, we already made efforts to design it, it should be done in the next months. > This feature is not yet available yet. However, it should be released very soon.
## Set of resources ## Set of resources
### Permiter
To allow people creating VMs as they want, we need to give them a *part* of your XenServer resources (disk space, CPUs, RAM). You can call this "general quotas" if you like. But you need first to decide how those quota applies in your infrastructure: To allow people creating VMs as they want, we need to give them a *part* of your XenServer resources (disk space, CPUs, RAM). You can call this "general quotas" if you like. But you need first to decide how those quota applies in your infrastructure:
* which Storage Repository could be used for this set? * which Storage Repository could be used for this set?
* which Networks? * which Networks?
* which Templates? * which Templates?
Then, you can limit resources for this set: ### Quotas
Only after this, you can limit resources for this set:
* maximum vCPUs, RAM and disk usage * maximum vCPUs, RAM and disk usage
* maximum number of VMs and VDIs * maximum number of VMs and VDIs