When XO crashes on XO Appliance, we need to ssh on it, and do a "xo service restart". Using "https://github.com/nodejitsu/forever" may solve the problem.

It's still "To be continued...", so I figured it wouldn't hurt to make an issue where the status of fleshing out this doc can be tracked properly. :)

https://github.com/vatesfr/xo/blob/master/installation.md

Consoles does not work when XO-Web is served over XO-Server.
This is because consoles are still contacted over HTTP which is deemed as insecure.

Firefox error message: SecurityError: The operation is insecure..

Consoles should be accessed through XO-Server.

Guys, please advice, how i can change or create new user on XOA? I'm pretty sure, there is a way to add new user with admin privileges, without parsing .js files (i.e. xo-server/src/xo.js)

Hi

Today I installed the xo-server / xo-web as per readme all went perfect while I start the xo-server I could see error below pasted. Kindly let me know how to solve this issue.

Error

./xo-server
[Warn] HTTP server could not listen on 0.0.0.0:80
[Warning] No users, creating “[email protected]” with password “admin”

/tmp/xo/xo-server/node_modules/q/q.js:126
throw e;
^
Error: missing callback
at Object.hash (/tmp/xo/xo-server/node_modules/hashy/index.js:92:13)
at Model.extend.setPassword (/tmp/xo/xo-server/src/xo.js:101:16)
at RedisCollection.extend.create (/tmp/xo/xo-server/src/xo.js:152:16)
at /tmp/xo/xo-server/src/main.js:446:19
at _fulfilled (/tmp/xo/xo-server/node_modules/q/q.js:798:54)
at self.promiseDispatch.done (/tmp/xo/xo-server/node_modules/q/q.js:827:30)
at Promise.promise.promiseDispatch (/tmp/xo/xo-server/node_modules/q/q.js:760:13)
at /tmp/xo/xo-server/node_modules/q/q.js:574:44
at flush (/tmp/xo/xo-server/node_modules/q/q.js:108:17)
at process._tickCallback (node.js:415:13)

When creating a new user, could we please either have an option to unmask the password when creating it or prompt for a second time around so that way we can verify that we didn't fat finger it :)

Am i right to assume that suspend/resume is currently unsupported in XO?
if so, is it planned to be added some day?

Hi,

I've notices that XO-web reports wrong state of HA. I have VM that has HA policy restart. But web reports false state.
Can you please chek it out.

Dubravko

Hi

After I added my Xenserver 6.2 host after a few minitues I could see my xen11 and xen12 added where both are same cluster group.

But where HP Blade Server (80x Intel(R) Xeon(R) CPU E7- 4870 @ 2.40GHz) After the VM created I could see the stats are little odd.

vCPUs/CPU usage:
88/80

RAM used:
40%

Running VMs:
38

How Vcpu will be 88

It will be great that if we have a static list where can show Total CPU and allocated CPU free CPU and the same way Memory and Storage will be good.

So that by see this we can know still how much resources are avaliable and can allocate.

And also it will be great if you could collect the RRD statics of the usage of total usage of Xenserver Interface / CPU / Memory

When trying to create a VM using a template, you can't leave the ISO/DVD empty.... When you click on the Create VM button you are prompted to select an option from ISO/DVD. This isn't needed when using a template to build a VM.

Hi

Today Installed the xo-server and xo-web in my Fedora 20 all went smooth but when I started the bin/xo-server I could see service started but I could not able to login via default username and password.

bin/xo-server

WebServer listening on http://0.0.0.0:80

Hi,

I have tried both root/root root/xoa but I cant login to the console.

Any ideas why this might be occuring?

When adding a server with credentials that don't work the GUI should report an error and should also not store the entry.

Possible wrong credentials could be:

• Host can not be resolved
• Host down
• Username wrong
• Password wrong

If one of those things come up, the UI should tell the user what is wrong with a meaningful error message instead of failing silently and adding the broken server to the server list.

XO-Server plugin to plan jobs.

A job:

• is a list of XO API calls;
• belongs to a user;
• runs at a specific date or at regular dates.

Dev resources:

• https://github.com/rschmukler/agenda

TODO:

• Create a plugin architecture in XO-Server
• Specify xo-scheduler
  • Job behavior
  • API

Hi

After successful installation I have added my xenserver's But when I click any of the VM's console I didn't see any response in the webpage.

Do I need to install any plugin or any specific browser.

Hi,

xo-server works fine, but xo-web not working.

php error message: PHP Parse error: syntax error, unexpected '[' in /var/www/xo/public/index.php on line 69

Possibility to live migrate VM by batch.

• external auth providers in xo-server

session.getExternalProviders()
{
  "oauth2.GitHub": {
    "name": "GitHub",
    "url": "https://github.com/login/oauth/authorize?client_id=dfoi"
  },
  "saml.MyCompany": {
    "name": "MyCompagny SAML",
    "url": "https://saml.my-compagny.net/signin/"
  }
}

• ability to select an external authentication provider in xo-web
• be redirected to this provider
• handle the user return with the proof
• connect to xo-server and transmit the proof
• make xo-server check the proof

For each external auth providers there should be an xo-server plugin:

• auth-saml

not sure if its possible but would love to be able to adjust the size of the console window so I could view it a bit better.

I everybody

For test purpose, i've just installed XO with manual installation on debian 7.0

All seems allright but when i start ./bin/xo-server
root@orchestra:/usr/share/orchestra/xo-server# ./bin/xo-server
WebServer listening on http://0.0.0.0:80

I can see a webpage ( see attached )

But impossible to login anywhere on this page...

Thanks for you help

This is more of a feature request/ question. Is there a programatic way to get usage info? For example in a shared lab environment to be able to limit the amount of hours a user gets per month or for the business minded folks a way to tie into a billing system

Hi, I tried to install XO-Server and XO-Web on a fresh debian 7.8 VM in Hyper-V. I can't figure out where it fails. The 'dist' directory exists, and I modified the path regarding the documentation. Already met this error? Would be nice to receive some help on this.

List of files/directories which will be served.

mounts:
'/': '/opt/xo-web/dist/'

root@xoa:/opt/xo-server# npm start

[email protected] start /opt/xo-server
node bin/xo-server

Error: Cannot find module './dist'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/opt/xo-server/index.js:14:18)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/opt/xo-server/bin/xo-server:7:25)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node bin/xo-server
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'node bin/xo-server'.
npm ERR! This is most likely a problem with the xo-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node bin/xo-server
npm ERR! You can get their info via:
npm ERR! npm owner ls xo-server
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /opt/xo-server/npm-debug.log
root@xoa:/opt/xo-server# cat /opt/xo-server/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart [email protected]
6 info start [email protected]
7 verbose unsafe-perm in lifecycle true
8 info [email protected] Failed to exec start script
9 verbose stack Error: [email protected] start: node bin/xo-server
9 verbose stack Exit status 1
9 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
9 verbose stack at EventEmitter.emit (events.js:110:17)
9 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:14:12)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid [email protected]
11 verbose cwd /opt/xo-server
12 error Linux 3.2.0-4-amd64
13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
14 error node v0.12.2
15 error npm v2.7.4
16 error code ELIFECYCLE
17 error [email protected] start: node bin/xo-server
17 error Exit status 1
18 error Failed at the [email protected] start script 'node bin/xo-server'.
18 error This is most likely a problem with the xo-server package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error node bin/xo-server
18 error You can get their info via:
18 error npm owner ls xo-server
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

Implement a search system to easily find any object. Use of special words can be a nice possibility (like Gmail and its label). Don't forget to use "tags" existing in the XAPI

Hi

I would like to bring up new idea about the acls. There should be acls only to view the VM and storage rather that acls should not have any action buttons to be disable.

I would like to give only view access to the orch

jpf-host-01:/opt/xo-server # ./xo-server
node: symbol lookup error: /opt/xo-server/node_modules/ws/build/Release/bufferutil.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPFNS_6HandleINS_5ValueEEERKNS_9ArgumentsEES3_NS1_INS_9SignatureEEE

I apologize if this is the wrong area for this type of issue. I was rather impressed with the
screen shots I saw of XO and want to do a report on it.

I've followed the install guide on the XO site, but run into this error when I try to launch xo-server:

NULLPHP Fatal error: Invalid response in /var/www/xo-server/lib/XCP.php on line 86

I've got everything installed on a Debian 6.0 64bit VM.

Installed as documented in the manual, however I can't login with [email protected] / admin:

> [email protected] start /opt/xo_orchestra/xo-server
> node bin/xo-server

  app-conf /opt/xo_orchestra/xo-server/.xo-server.yaml +0ms
  xo:main Configuration loaded. +9ms
  xo:main Web server listening on http://[::]:80 +9ms
  xo:main Setting up / → /opt/xo_orchestra/xo-web/dist +242ms
  xo:perf blocked for 178ms +2ms
  xo:main - WebSocket connection +1m
  xo:main + WebSocket connection +10s
  xo:main + WebSocket connection +22s
  xo:api session.signOut(...) +15s
  xo:api session.signInWithPassword(...) +4ms
use session.signIn() instead
Error: unsupported algorithm
    at verify (/opt/xo_orchestra/xo-server/node_modules/hashy/index.js:216:9)
From previous event:
    at asyncWrapper (/opt/xo_orchestra/xo-server/node_modules/hashy/index.js:102:24)
    at User.checkPassword$ (/source/models/user.js:22:47)
    at tryCatch (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/                                                     runtime.js:100:21)
    at invoke (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at enqueueResult (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:167:17)
    at Promise.exp (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/node_modules/core-js/library/modules/$.def.js:38:36)
    at AsyncIterator.enqueue (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:166:16)
    at AsyncIterator.prototype.(anonymous function) [as next] (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:10                                                     0:21)
    at Object.runtime.async (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:192:12)
    at User.checkPassword (/source/models/user.js:20:15)
    at passwordAuthenticationProvider$ (/source/index.js:335:54)
    at tryCatch (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/                                                     runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (/opt/xo_orchestra/xo-server/node_modules/babel-runtime/regenerator/runtime.js:136:37)
  xo:api Error: session.signInWithPassword(...) → InvalidCredential: invalid credential +8ms
  xo:main - WebSocket connection +6s

General specification:

• provide a restricted access for users that are not admin
• only an admin can assign VM's to users
• these users can only interact/see their assigned VM's
• provide groups permissions
• provide roles permissions

Specification questions:

• see this blog post for details

Technical implementation:

• permissions are stored in xo-server, thus unified for any clients (xo-web, xo-cli, any other future clients)
• admin users need an interface for assign permissions and groups in the VM view

Workload

• first estimation: 20 man-day

Do I understand it correctly that currently we run ./gulp instead of manually ./bower install && ./grunt? If I do, please update the installation guide. It made me fail at this point for a while.

Hi

Today I installed the xo-server and xo-web as per the document after installation I configured the config.yaml and changed the port 80 to 8080 but I could see when I start the xo-server its not reading my configuration file its assigning it default port with 80.

Installed OS CentOS 6.5
Installed Path : /opt/xo/xo-server
Installed Path : /opt/xo/xo-server/xo-web

> ./bin/xo-server 
  xo:runner Loading CoffeeScript... +0ms
  xo:runner Loading Babel (ES6 support)... +49ms
  xo:runner Loading main module... +1s
  xo:main Configuration loaded. +3s
  xo:main Web server listening on http://[::]:80 +9ms
  xo:main Setting up / → xo-server/xo-web/dist/ +623ms

config.yaml

# Example XO-Server configuration.

# This file is automatically looking for at the following places:
# - `./.xo-server.yaml` up to `/.xo-server.yaml`
# - `$HOME/.config/xo-server/config.yaml`
# - `/etc/xo-server/config.yaml`
#
# The first entries have priority.

# Note: paths are relative to the configuration file.

#=====================================================================

# It may be necessary to run XO-Server as a privileged user (e.g.
# `root`) for instance to allow the HTTP server to listen on a
# [privileged ports](http://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html).
#
# To avoid security issues, XO-Server can drop its privileges by
# changing the user and the group is running with.
#
# Note: XO-Server will change them just after reading the
# configuration.

# User to run XO-Server as.
#
# Note: The user can be specified using either its name or its numeric
# identifier.
#
# Default: undefined
#user: 'nobody'

# Group to run XO-Server as.
#
# Note: The group can be specified using either its name or its
# numeric identifier.
#
# Default: undefined
#group: 'nogroup'

#=====================================================================

# Configuration of the embedded HTTP server.
http:

  # Hosts & ports on which to listen.
  #
  # By default, the server listens on 0.0.0.0:80.
  listen:
    # Basic HTTP.
    -
      # Address on which the server is listening on.
      #
      # Sets it to '127.0.0.1' to listen only on the local host.
      #
      # Default: '0.0.0.0' (all addresses)
      #hostname: '127.0.0.1'

      # Port on which the server is listening on.
      #
      # Default: undefined
      port:8080

      # Instead of `host` and `port` a path to a UNIX socket may be
      # specified (overrides `host` and `port`).
      #
      # Default: undefined
      #socket: './http.sock'

    # Basic HTTPS.
    # -
    #   # The only difference is the presence of the certificate and the
    #   # key.

    #   #hostname: '127.0.0.1'
    #   port: 443

    #   # File containing the certificate (PEM format).
    #   #
    #   # Default: undefined
    #   certificate: './certificate.pem'

    #   # File containing the private key (PEM format).
    #   #
    #   # If the key is encrypted, the passphrase will be asked at
    #   # server startup.
    #   #
    #   # Default: undefined
    #   key: './key.pem'

  # List of files/directories which will be served.
  mounts:
    '/': 'xo-server/xo-web/dist/'

#=====================================================================

# Connection to the Redis server.
redis:
    # Syntax: tcp://[db[:password]@]hostname[:port]
    #
    # Default: tcp://localhost:6379
    #uri: ''

root@xoa:~# xoa-updater --upgrade
Successfully connected to xoa-updater-service
Checking new versions...ok ✔
New packages available:
  xo-server 4.0.2
  xo-web-free 4.0.2
Downloading packages...
  xo-web-free .................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. ok ✔
  xo-server ....................................................................................................................................................................................... ok ✔
Installing new packages...
  xo-web-free ✔
  xo-server ✔
xo-server will be restarted...
Restarting xo-server ✔

✔ Your XOA has been successfully upgraded.

update seemed to run successfully

root@xoa:~# xoa-updater
Successfully connected to xoa-updater-service
Checking new versions...ok ✔

ℹ All up to date

everythings upto date, but the servers not responding

root@xoa:~# systemctl restart xo-server.service

still not working...

root@xoa:~# systemctl status xo-server.service
xo-server.service - XO Server
   Loaded: loaded (/etc/systemd/system/xo-server.service; enabled)
   Active: failed (Result: start-limit) since Sun 2015-06-07 04:20:58 CEST; 12s ago
  Process: 6414 ExecStart=/usr/local/bin/xo-server (code=exited, status=1/FAILURE)

Jun 07 04:20:58 xoa systemd[1]: Unit xo-server.service entered failed state.
Jun 07 04:20:58 xoa systemd[1]: xo-server.service holdoff time over, schedu...t.
Jun 07 04:20:58 xoa systemd[1]: Stopping XO Server...
Jun 07 04:20:58 xoa systemd[1]: Starting XO Server...
Jun 07 04:20:58 xoa systemd[1]: xo-server.service start request repeated to...t.
Jun 07 04:20:58 xoa systemd[1]: Failed to start XO Server.
Jun 07 04:20:58 xoa systemd[1]: Unit xo-server.service entered failed state.

trying to start the server manually...

root@xoa:~# /usr/local/bin/xo-server
  xo:main Configuration loaded. +0ms
✖ Cannot read property 'http' of undefined
TypeError: Cannot read property 'http' of undefined
    at main$ (/source/index.js:391:27)
    at tryCatch (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at invoke (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at /usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:165:16
    at runMicrotasksCallback (node.js:337:7)
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
From previous event:
    at execPromise (/usr/local/lib/node_modules/xo-server/node_modules/exec-promise/index.js:59:22)
    at Object.<anonymous> (/usr/local/lib/node_modules/xo-server/bin/xo-server:7:24)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3
root@xoa:~# vi /etc/systemd/system/xo-server.service
root@xoa:~# /usr/local/bin/xo-server
  xo:main Configuration loaded. +0ms
✖ Cannot read property 'http' of undefined
TypeError: Cannot read property 'http' of undefined
    at main$ (/source/index.js:391:27)
    at tryCatch (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at invoke (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at /usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:165:16
    at runMicrotasksCallback (node.js:337:7)
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
From previous event:
    at execPromise (/usr/local/lib/node_modules/xo-server/node_modules/exec-promise/index.js:59:22)
    at Object.<anonymous> (/usr/local/lib/node_modules/xo-server/bin/xo-server:7:24)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

Investigate the Secure Remote Password protocol and see whether it is better than the current system.

If it is, implements it.

If I add a server in "Connected servers" on the XO Settings page and later delete it, it is removed from the settings page but remains in the tree and flat views.

Currently XO-Web fetches up-to-date data regularly from XO-Server.

Instead it should subscribe to events on given objects and be notified of any changes.

Refresh web clients when a new event appears (new Vm , new host etc.)

Hi
I wanted to wait before submitting this bug, but even after the latest update the issue still persists.

Xen Orchestra is unable to create a new VM in any way. Since the first time I installed it, I was never able to do it properly without using XenCenter.

I have a pool with just one server (latest XenServer), and I try to create a VM from the server dropdown menu (otherwise I cannot select internal disks). Unfortunately when saving an error message is displayed, and just a template is created (I believe in the wrong place).

As you can see at the bottom of the screenshot, two templates are created before failing.

I have no idea on where to look for logs. The problem is always reproducible though.

Hi,
I'm following this https://github.com/vatesfr/xo/blob/master/doc/installation/manual_installation.md to get xo installed manually.

When I execute:

 root@myserver:~/xoa/xo-web# ./gulp --production
[20:10:51] Using gulpfile ~/xoa/xo-web/gulpfile.js
[20:10:51] Starting 'build-pages'...
[20:10:51] Starting 'install-bower-components'...
[20:10:53] Finished 'build-pages' after 1.69 s
[20:10:58] 'install-bower-components' errored after 6.58 s
[20:10:58] angular: Unable to find suitable version for angular
    at createError (/root/xoa/xo-web/node_modules/bower/lib/util/createError.js:4:15)
    at Manager._electSuitable (/root/xoa/xo-web/node_modules/bower/lib/core/Manager.js:763:15)
    at /root/xoa/xo-web/node_modules/bower/lib/core/Manager.js:558:25
    at _fulfilled (/root/xoa/xo-web/node_modules/bower/node_modules/q/q.js:787:54)
    at self.promiseDispatch.done (/root/xoa/xo-web/node_modules/bower/node_modules/q/q.js:816:30)
    at Promise.promise.promiseDispatch (/root/xoa/xo-web/node_modules/bower/node_modules/q/q.js:749:13)
    at /root/xoa/xo-web/node_modules/bower/node_modules/q/q.js:509:49
    at flush (/root/xoa/xo-web/node_modules/bower/node_modules/q/q.js:108:17)
    at process._tickCallback (node.js:419:13)

What am I doing wrong? Any ideas?
Thanks so much!

It seems that XO have problems dealing with HTTP Proxies. Indeed, xo-web and xo-server communication is done by using Websocket. Therefore, websocket is not HTTP, and this combination cause troubles. For example, Firefox debugger said:
"Firefox can't establish a connection to the server at ws://ip.address/api/"

A first workaround is to bypass explicitly the Xo-server address in your browser. But it can be great to avoid any changes, so we are reporting it here to find a better solution.

Another idea is to try HTTPS connection, it can avoid (maybe) the problem.

Hi

I am so impressed about this tool. I have some idea to add more features into.

How about giving complete Network Monitoring Information. For example.

Add another Tab [Monitor] Under that

It should list all the added xenservers.

By clicking any of the listed xenserver host it should open page with

Graphic View
Total CPU Usage / Memory Usage / DiskUsage [NFS] / Network Usage /

On the above page it should have [ VM Monitor ] By Click that it should list all the VM's that below to the particular xenserver by click any of the listed vm's it view the graphic view of

Total CPU Usage / Memory Usage / DiskUsage / Network Usage /

With reference issue #45

While tested the latest build of [email protected]. I created the user with permission User I choose an object vm node. But this users could able to proceed all the actions.

Still I could not see any ACLs just users only able to view not to do any action item. He should have only the VM console rather than reboot / stop VM /.

Even created users could not able to view the graphic report.

The title says it all I think.

I connected the image with XO and installed the tools, then rebooted the VM.
After that it wasn't able to boot properly, and the image couldn't be ejected with the web UI, I had to disconnect it from the xen terminal.

You can reproduce the problem by:

• connecting the xen tools image to a vm
• reboot the vm
• it shouldn't be able to boot or eject the image

I hope it's reproducible in your installation

VMs created on hosts out of a pool are listed under the host they were created on. After creating a pool; say including server1 and server2, VMs created from the CLi on server2 are then displayed under server1 in the VM view.

Allow XO to send order to XAPI hosts, like pause, start or add a VM.

Hi,

I have imported the XVA file via xencenter and the vm has booted.

Logging in though I cant see any XO services that are running or to restart? Is there anything else you need to do once the VM has loaded in xencentre that I am missing.

Hello,

I have been trying out XO running in a VM on the pool it is connected to.

I am using xo-server 89596591e965c09a71c724148b4fa57f0c3ba6ed and xo-web 84e6f71416a3851f75df0c0b160df9b076a8f022

Every single web page request hangs for a minute or more before loading. When the pages do eventually load, the information is correct. Firebug indicates that it is the initial get request that waits for a long time; subsequent requets for the js/css/images return in under a second.

Unfortunatly, the log files from either xo-web or xo-server have no indication of anything going wrong. I assume that something is timing out somewhere, but do you have any guidence as to how best to debug the issue?

After the successful installation I could able to coonect my xenservers but when I click the I couldn't see the console in browser.

I tried in my Chrome 38.0.2125.111 / Firefox 33.0 / IE 11

Do I need anything to install to view the console.

Hi

It will be great that if you could add disk & network io graphi will help to see the performance of the disk.

I followed exactly the installation procedure, but when issueing the "gulp --production" command, this leads to this error - any idea how to fix that?
[11:34:53] Finished 'copyAssets' after 5.07 s /root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/build/es5/ng-annotate-main.js:330 target.$methodName = method.name; ^ TypeError: Cannot assign to read only property '$methodName' of false at matchRegular (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/build/es5/ng-annotate-main.js:330:24) at match (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/build/es5/ng-annotate-main.js:36:66) at traverse.post (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/build/es5/ng-annotate-main.js:995:23) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:50:13) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:44:21) at visit (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:41:25) at traverse (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/node_modules/ordered-ast-traverse/ordered-ast-traverse.js:54:5) at ngAnnotate (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/ng-annotate/build/es5/ng-annotate-main.js:989:5) at Transform._transform (/root/xo-web/node_modules/gulp-ng-annotate/index.js:28:15) at Transform._read (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:184:10) at Transform._write (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:172:12) at doWrite (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:237:10) at writeOrBuffer (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:227:5) at Transform.Writable.write (/root/xo-web/node_modules/gulp-ng-annotate/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:194:11) at PassThrough.ondata (_stream_readable.js:540:20) at PassThrough.emit (events.js:107:17) at readableAddChunk (_stream_readable.js:163:16) at PassThrough.Readable.push (_stream_readable.js:126:10) at PassThrough.Transform.push (_stream_transform.js:140:32) at afterTransform (_stream_transform.js:96:12) at TransformState.afterTransform (_stream_transform.js:74:12) at PassThrough._transform (_stream_passthrough.js:40:3) at PassThrough.Transform._read (_stream_transform.js:179:10) at PassThrough.Transform._write (_stream_transform.js:167:12) at doWrite (_stream_writable.js:301:12) at writeOrBuffer (_stream_writable.js:288:5) at PassThrough.Writable.write (_stream_writable.js:217:11) at PassThrough.Writable.end (_stream_writable.js:449:10) at onBundleComplete (/root/xo-web/gulpfile.js:112:7) at /root/xo-web/node_modules/browserify/index.js:686:13 at ConcatStream.<anonymous> (/root/xo-web/node_modules/browserify/node_modules/concat-stream/index.js:32:43) at ConcatStream.emit (events.js:129:20) at finishMaybe (/root/xo-web/node_modules/browserify/node_modules/concat-stream/node_modules/readable-stream/lib/_stream_writable.js:460:14) at endWritable (/root/xo-web/node_modules/browserify/node_modules/concat-stream/node_modules/readable-stream/lib/_stream_writable.js:469:3) at ConcatStream.Writable.end (/root/xo-web/node_modules/browserify/node_modules/concat-stream/node_modules/readable-stream/lib/_stream_writable.js:436:5) at Labeled.onend (/root/xo-web/node_modules/browserify/node_modules/labeled-stream-splicer/node_modules/stream-splicer/node_modules/readable-stream/lib/_stream_readable.js:537:10) at Labeled.g (events.js:199:16) at Labeled.emit (events.js:129:20) at /root/xo-web/node_modules/browserify/node_modules/labeled-stream-splicer/node_modules/stream-splicer/node_modules/readable-stream/lib/_stream_readable.js:934:16 at process._tickCallback (node.js:355:11)