Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

stacksofplates

@johnhooks said:

@scottalanmiller said:

I don't see a user explanation in the instructions. Where does the user come from and what role does it play?

Is this for me?

It's for Dustin who wrote the instructions.

Oh ok. I had a "user" in my playbook that needs replaced. I thought you were referring to that. I am using a variable for it now so you can just change the variable.

DustinB3403

What is there to understand about it?

Following a base install of the server OS, i built a user named "xoadmin" which the mount directory uses /home/xoadmin/xo-web/dist/ in the .xo-sample.yaml file

DustinB3403

Something is different or changed...

olivier

And now you discover why we release appliance with an updater and validated updates

Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.

This stuff is sadly not very uncommon.

DustinB3403

@olivier said:

And now you discover why we release appliance with an updater and validated updates

Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.

This stuff is sadly not very uncommon.

How dare they break it!

scottalanmiller

@DustinB3403 said:

What is there to understand about it?

Following a base install of the server OS, i built a user named "xoadmin" which the mount directory uses /home/xoadmin/xo-web/dist/ in the .xo-sample.yaml file

Well the part ot understand is that you manually made a user and it wasn't made by the installer like most software does. If you are making a how to, you have to include the steps or else things are missing.

Alex Sage

@olivier What's the best way to know what Node and NPM version should be used?

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 lodash.trim@3.0.1

DustinB3403

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

scottalanmiller

Same here, even after installing GULP.