The global orchestration solution to manage and backup XCP-ng and XenServer.
1a71cc9223
API methods can now have some of their objects automatically fetched:
```
method.resolve = {
vm: ['vm', 'VM'],
};
```
The key is the name of the property with which the object will be
attached in the parameters dictionary, the first entry of the array is
the name of the parameter to use to fetch the object and the second
the expected type/types of the object.
Note that permissions are automatically checked via the ACLs.
|
||
|---|---|---|
| bin | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .jshintrc | ||
| coffeelint.json | ||
| index.js | ||
| package.json | ||
| README.md | ||
| run-tests | ||
| sample.config.yaml | ||
| xo-server.service | ||
Xen Orchestra Server
XO-Server is part of Xen Orchestra, a web interface for XenServer or XAPI enabled hosts.
It contains all the logic of XO and handles:
- connections to all XAPI servers/pools;
- a cache system to provide the best response time possible;
- users authentication and authorizations (work in progress);
- a JSON-RPC based interface for XO clients (i.e. XO-Web).
Installation
Manual install procedure is available here
How to report a bug?
If you are certain the bug is exclusively related to XO-Server, you may use the bugtracker of this repository.
Otherwise, please consider using the bugtracker of the general repository.