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

chore(all): move assets

Browse Source
This commit is contained in:
Olivier Lambert
2016-07-06 15:00:34 +02:00
parent 5b3f11d09b
commit 5574747054
61 changed files with 280 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+2 -2
View File
@@ -12,11 +12,11 @@ This is the easiest way to try Xen Orchestra in a minute.
Your XOA is connected to all your hosts, or on the pool master only if you are using Pools in XenServer:
![](https://xen-orchestra.com/assets/partner2.jpg)
![](./assets/partner2.jpg)
## Xen Orchestra (XO)
![](../assets/xo-arch.jpg)
![](./assets/xo-arch.jpg)
Xen Orchestra itself is built as a modular solution. Each part has its role:
- the core is "[xo-server](https://github.com/vatesfr/xo-server)", a daemon dealing directly with XenServer or XAPI capable hosts. This is where users are stored, and it's the center point for talking to your whole Xen infrastructure.