Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

stacksofplates

Ok, here's the updated playbook. Just add your hostname in /etc/ansible/hosts and your username in the variables file, it will do the rest.

https://app.box.com/s/w84npeu4xu4m3jhphs4fn91cnfxoii9y

olivier

@anonymous Experience ^^ (if the build fails).

In general, when there is a new big release of Node, dependencies can't catch the breaking changes for a time. That's why Node 5 broke the build for a time.

You can use the LTS version of Node to be safe: https://nodejs.org/en/blog/release/v4.2.0/

scottalanmiller

Hopefully LTS means more for Node than it does for ubuntu.

olivier

@scottalanmiller hahaha

JaredBusch

I lost track of if @anonymous is using CentOS or Ubuntu now..

Here is the guide for nodejs on CentOS 7

http://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm

scottalanmiller

@JaredBusch said:

I lost track of if @anonymous is using CentOS or Ubuntu now..

Here is the guide for nodejs on CentOS 7

http://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm

I updated that this morning to cover Ubuntu too. Tested and working there as well.

olivier

It should also work on MacOS and Windows ^^

scottalanmiller

@olivier said:

It should also work on MacOS and Windows ^^

But... who cares

olivier

Build should be back on track on next-release branch.

DustinB3403

@olivier said:

Build should be back on track on next-release branch.

From the individual folders of xo-server and xo-web

git checkout next-release

git fetch; git pull

olivier

If you want to stick on stable, a workaround would be npm i [email protected]

DustinB3403

At @olivier this is what I'm getting now, attempting this install.

scottalanmiller

Same here, even after installing GULP.

DustinB3403

@scottalanmiller Are you running stable as well, or "next release" ?

scottalanmiller

@DustinB3403 said:

@scottalanmiller Are you running stable as well, or "next release" ?

I'm running from your how-to

olivier

That's because the install process went bad, due to lodash issue (we reported it here)

So before the npm i, do a npm i [email protected].

DustinB3403

Yeah I got it sorted, getting the updated guide sorted out

Thank you

Dashrender

@olivier said:

That's because the install process went bad, due to lodash issue (we reported it here)

So before the npm i, do a npm i [email protected].

you are the man, you know that! Not only reporting on your own pages, but coming here and reporting as well... that's just awesome!

scottalanmiller

Okay, here we go. I took @DustinB3403's working process and turned it into a script. I'm going to blow everything away and see if this works from scratch. Just take this, copy into a file like /opt/xoinstaller.sh, chmod +x /opt/xoinstaller.sh and then run it /opt/xoinstaller.sh

#!/bin/bash
cd /opt
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install --yes nodejs
curl -o /usr/local/bin/n https://raw.githubusercontent.com/visionmedia/n/master/bin/n
chmod +x /usr/local/bin/n
n stable
node -v
npm -v
sudo apt-get install --yes build-essential redis-server libpng12-dev git python-minimal
git clone -b stable https://github.com/vatesfr/xo-server
git clone -b stable https://github.com/vatesfr/xo-web
cd xo-server
sudo npm install && npm run build
cp xo-server/sample.config.yaml xo-server/.xo-server.yaml
sed /mounts/a\\"    '/': '/opt/xo-web/dist'" xo-server/.xo-server.yaml
cd /opt/xo-web
sudo npm i [email protected]
sudo npm install
sudo npm run build
cd /opt/xo-server
sudo npm start

olivier

The lodash specific stuff won't be necessary after the 4.12