The global orchestration solution to manage and backup XCP-ng and XenServer.
Go to file
2015-06-10 16:59:03 +02:00
bin Use standard style. 2015-04-13 18:33:15 +02:00
src Better stack traces in tests and production. 2015-06-10 16:59:03 +02:00
.babelrc Add Babel plugin for closure elimination (disabled for now). 2015-06-10 16:59:03 +02:00
.editorconfig Update EditorConfig. 2015-02-12 18:03:50 +01:00
.gitignore Also ignore npm-debug.log.* 2015-06-10 16:59:03 +02:00
.jshintrc Update .jshintrc. 2015-02-03 15:38:07 +01:00
.mocha.opts Better stack traces in tests and production. 2015-06-10 16:59:03 +02:00
gulpfile.js No longer use fibers. 2015-06-05 18:34:04 +02:00
index.js Better stack traces in tests and production. 2015-06-10 16:59:03 +02:00
package.json Better stack traces in tests and production. 2015-06-10 16:59:03 +02:00
README.md Update README.md 2015-05-07 19:42:34 +02:00
sample.config.yaml Remove discouraged path for the config file from the doc. 2015-05-15 11:47:18 +02:00
xo-server.service Set debug to xo:main only in production. 2015-05-28 14:57:04 +02:00

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).

Dependency Status devDependency Status


Installation

Manual install procedure is available here.

Compilation

Production build:

$ npm run build

Development build:

$ npm run dev

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.