@Danp
ok i tried it on ubuntu 16.04 lts and it worked
when it got to the Updated version v4.16.0
then the vm rebooted itself and after then it started working

XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/

install script is same?

installation did not complete FULLY
although i was still able to login via GUI

root@xen-orchestra-5:~# curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
sudo: unable to resolve host xen-orchestra-5

> [email protected] build /opt/xo-web
> npm run build-indexes && NODE_ENV=production gulp build


> [email protected] build-indexes /opt/xo-web
> ./tools/generate-index src/common/intl/locales

[21:19:44] Using gulpfile /opt/xo-web/gulpfile.js
[21:19:44] Starting 'build'...
[21:19:44] Starting 'buildPages'...
[21:19:44] Starting 'buildScripts'...
[21:19:44] Starting 'buildStyles'...
[21:19:44] Starting 'copyAssets'...
[21:19:45] Finished 'buildPages' after 1.26 s
[21:19:48] Finished 'buildStyles' after 3.93 s
[21:19:48] Finished 'copyAssets' after 4.31 s
[21:21:37] Finished 'buildScripts' after 1.88 min
[21:21:37] Finished 'build' after 1.88 min
sudo: unable to resolve host xen-orchestra-5
sudo: unable to resolve host xen-orchestra-5
Created symlink from /etc/systemd/system/multi-user.target.wants/xo-server.service to /etc/systemd/system/xo-server.service.
sudo: unable to resolve host xen-orchestra-5
root@xen-orchestra-5:~# nano /etc/hosts
root@xen-orchestra-5:~# ping xen-orchestra-5
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.035 ms
^C
--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.027/0.032/0.035/0.006 ms
root@xen-orchestra-5:~# curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1172  100  1172    0     0   1333      0 --:--:-- --:--:-- --:--:--  1333
Reading package lists... Done
Building dependency tree
Reading state information... Done
nfs-common is already the newest version (1:1.2.8-9ubuntu12).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic
  linux-image-extra-4.4.0-21-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

## Installing the NodeSource Node.js v5.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 https://deb.nodesource.com/node_5.x xenial InRelease
Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [222 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [219 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [99.9 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [97.0 kB]
Fetched 732 kB in 1s (438 kB/s)
Reading package lists... Done

## Confirming "xenial" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dists/xenial/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK

## Creating apt sources list file for the NodeSource Node.js v5.x repo...

+ echo 'deb https://deb.nodesource.com/node_5.x xenial main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_5.x xenial main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 https://deb.nodesource.com/node_5.x xenial InRelease
Reading package lists... Done

## Run `apt-get install nodejs` (as root) to install Node.js v5.x and npm

Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (5.12.0-1nodesource1~xenial1).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic
  linux-image-extra-4.4.0-21-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 15243  100 15243    0     0  69684      0 --:--:-- --:--:-- --:--:-- 69922
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
git is already the newest version (1:2.7.4-0ubuntu1).
libpng12-dev is already the newest version (1.2.54-1ubuntu1).
python-minimal is already the newest version (2.7.11-1).
redis-server is already the newest version (2:3.0.6-1).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic
  linux-image-extra-4.4.0-21-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fatal: destination path 'xo-server' already exists and is not an empty directory.
fatal: destination path 'xo-web' already exists and is not an empty directory.
npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-server
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]

> [email protected] build /opt/xo-server
> npm run build-indexes && gulp build --production


> [email protected] build-indexes /opt/xo-server
> ./tools/generate-index src/api src/xapi/mixins src/xo-mixins

[21:24:00] Using gulpfile /opt/xo-server/gulpfile.js
[21:24:00] Starting 'build'...
[21:24:00] Starting 'buildCoffee'...
[21:24:00] Starting 'buildEs6'...
[21:24:09] Finished 'buildCoffee' after 9.54 s
[21:24:51] Finished 'buildEs6' after 51 s
[21:24:51] Finished 'build' after 51 s
[email protected] /opt/xo-web
└── [email protected]  extraneous

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-web
[email protected] /opt/xo-web
└── [email protected]  extraneous

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]

> [email protected] build /opt/xo-web
> npm run build-indexes && NODE_ENV=production gulp build


> [email protected] build-indexes /opt/xo-web
> ./tools/generate-index src/common/intl/locales

[21:25:42] Using gulpfile /opt/xo-web/gulpfile.js
[21:25:42] Starting 'build'...
[21:25:42] Starting 'buildPages'...
[21:25:42] Starting 'buildScripts'...
[21:25:42] Starting 'buildStyles'...
[21:25:42] Starting 'copyAssets'...
[21:25:43] Finished 'buildPages' after 1.21 s
[21:25:45] Finished 'buildStyles' after 3.71 s
[21:25:46] Finished 'copyAssets' after 4.58 s
[21:27:34] Finished 'buildScripts' after 1.87 min
[21:27:34] Finished 'build' after 1.87 min
root@xen-orchestra-5:~# cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
UBUNTU_CODENAME=xenial

@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/

install script is same?

The install script does work.

It's worth updating to the newest version of the install script though.

where is newest version of install script?

XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/

install script is same?

@olivier said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

What I said is to hear precise reasons: eg "too many clicks to do this or that."

Everyone has various tastes, personal opinions are less interesting than facts

i will come with more specifics soon

@olivier said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob I like constructive feedback: what do you mean by that?

Are you sure you need to go to some tabs each time you see a VM? I mean the "General" thing should be enough in 80% of the time.

Also, it was more a technical from scratch thing for now (as you can see in the recent perf tests here). We also built a lot of internal components, which will help to really modify the interface quickly after.

Its more of a UI thing for me
I like the UI of the v4 one compared to the v5(as of now)

I mean i think speed wise it is faster and i like the more detail graphs for monitoring, but i need to click many tabs to see things. Overall the UI can be made better.

Will be great if some great UI guys can help you with that, am not a UI person but i can tell if UI is good or not as a user pretty quickly

@Danp

Didn't like the version 5, switching back
too much tabs, didn't like it

I feel like he should have kept mostly the version 4 structure but add the good stats/monitoring in 5 to 4 and also a few more stuffs
the whole from scratch thing doesn't look too good TO ME at least

@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob Try this instead:

  sudo npm i
  sudo npm run build

root@xen-orchestra:/opt# cd xo-web
root@xen-orchestra:/opt/xo-web# npm i
npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] in-publish && npm run build || in-install /opt/xo-web
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
root@xen-orchestra:/opt/xo-web#

forgot i switched back to next-release from above ^
so switched back to v5.x

root@xen-orchestra:/opt/xo-web# git checkout v5.x
Switched to branch 'v5.x'
Your branch is up-to-date with 'origin/v5.x'.
root@xen-orchestra:/opt/xo-web# npm i
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

> [email protected] install /opt/xo-web/node_modules/ghooks
> opt --out ghooks-install --exec "node ./bin/install"

npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-web
- [email protected] node_modules/ast-traverse
- [email protected] node_modules/ast-types
- [email protected] node_modules/babel-core/node_modules/bluebird
- [email protected] node_modules/babel-eslint/node_modules/lodash.assign
- [email protected] node_modules/babel-plugin-constant-folding


<lots of stuffs here>



│   ├── [email protected]
│   └── [email protected]
├── [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ └─┬ [email protected]
│   └── [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └─┬ [email protected]
│ │   └── [email protected]
│ └── [email protected]
└── [email protected]

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
root@xen-orchestra:/opt/xo-web#

Actually worked!!!
forgot the last command,was thinking there were errors

root@xen-orchestra:/opt/xo-web# npm run build

> [email protected] build /opt/xo-web
> NODE_ENV=production gulp build

[21:31:09] Using gulpfile /opt/xo-web/gulpfile.js
[21:31:09] Starting 'build'...
[21:31:09] Starting 'buildPages'...
[21:31:09] Starting 'buildScripts'...
[21:31:09] Starting 'buildStyles'...
[21:31:09] Starting 'copyAssets'...
[21:31:11] Finished 'buildPages' after 1.35 s
[21:31:13] Finished 'buildStyles' after 4.26 s
[21:31:14] Finished 'copyAssets' after 4.27 s
[21:32:25] Finished 'buildScripts' after 1.25 min
[21:32:25] Finished 'build' after 1.25 min
root@xen-orchestra:/opt/xo-web#

@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob Try this instead:

  sudo npm i
  sudo npm run build

does it matter what directory/path am in when running the command?

@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob Yes, that is how you would switch to their development branch and check out the new interface. It's been a while since I tried it myself, so please report back and let us know how it goes...

not working
http://mangolassi.it/topic/7349/xen-orchestra-on-ubuntu-15-10-complete-installation-instructions/399

@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@xogurunoob said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@BRRABill Yes, he did state that it was broken. I believe the fix has been applied to the next-release branch of xo-server. However, I used the script within the last few days and it worked fine.

Yes, you can switch back and forth between the branches. You just need to rebuild each time.

how does one rebuild after switching to the dev version 5 branch?

cd /opt/xo-server

npm run build

cd /opt/xo-web

npm run build

root@xen-orchestra:/opt/xo-web# git branch
* next-release
  stable
root@xen-orchestra:/opt/xo-web# git checkout v5.x
Branch v5.x set up to track remote branch v5.x from origin.
Switched to a new branch 'v5.x'
root@xen-orchestra:/opt/xo-web# git branch
  next-release
  stable
* v5.x
root@xen-orchestra:/opt/xo-web# npm run build

> [email protected] build /opt/xo-web
> NODE_ENV=production gulp build

/opt/xo-web/node_modules/orchestrator/index.js:41
			throw new Error('Task requires a name that is a string');
			^

Error: Task requires a name that is a string
    at Gulp.Orchestrator.add (/opt/xo-web/node_modules/orchestrator/index.js:41:10)
    at Object.<anonymous> (/opt/xo-web/gulpfile.js:248:6)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Liftoff.handleArguments (/opt/xo-web/node_modules/gulp/bin/gulp.js:116:3)

npm ERR! Linux 4.4.0-22-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `NODE_ENV=production gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script 'NODE_ENV=production gulp build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the xo-web package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=production gulp build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs xo-web
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls xo-web
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /opt/xo-web/npm-debug.log
root@xen-orchestra:/opt/xo-web#