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

Update administration.md

Browse Source
This commit is contained in:
Olivier Lambert 2015-11-12 22:15:57 +01:00
parent cea08dba5a
commit 0b40b77802
1 changed files with 21 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
administration.md
View File

@ -94,4 +94,24 @@ You can edit your VM RAM or CPUs in live, like you edit a VM name or description
* each VM has a vCPU maximum number. This value can't be change while the VM is running. You can reduce the number of vCPUs, but can't assign more than max. In XO, while your VM is halted, allow the max vCPUs you would need, then boot it. Now you can reduce it and then expand it later to this maximum.
* the same limitation apply for the RAM.
You can learn more about XenServer resource management here: https://wiki.xenserver.org/XCP_FAQ_Dynamic_Memory_Control
You can learn more about XenServer resource management here: https://wiki.xenserver.org/XCP_FAQ_Dynamic_Memory_Control
### Docker management
Thanks to the plugin developed [recently](http://xenserver.org/partners/docker.html?id=159) as a "preview" by Citrix in XenServer, we started to work something to expose those data in Xen Orchestra.
First thing first, we now detect which VMs are "Docker ready", meaning connected to XenServer and its plugin to send more info.
This is visible in the home page of XO, VM with a small ship blue logo:
![](https://xen-orchestra.com/blog/content/images/2015/05/docker.png)
By clicking on this VM, you'll have some new stuff visible, first the Docker version:
![](https://xen-orchestra.com/blog/content/images/2015/05/docker2.png)
Also, a new panel is now displaying the containers on the VM:
![](https://xen-orchestra.com/blog/content/images/2015/05/docker3.png)
You can Stop, Start, Pause, Resume or Restart a Docker container from there.