Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
FINALLY GOT IT!
The problem was the npm -install -g npm - was using a wrong version of npm (should have read the output closer)
The full version of XO is sooooooooo nice!
My next steps are:
- Create a script for installing in Ubuntu
- Try to get working in CentOS7
-
CentOS7 still seems to be missing the needed packages.....
-
So I created an Ansible playbook for installing Xen Orchestra. All you should need to do is add the host to your /etc/ansible/hosts file, type the hostname from the ansible hosts file in the setup.yml file, add your username in the setup.yml file, and then replace user with your username in the main.yml tasks file.
This playbook only sets up Xen-Orchestra, so you will need to set the server up with ssh and python before you run it.
**Edit:**I uploaded a new file below, it has changes.
-
Why is there a special repo for Redis?
-
I've retested, and updated this how-to.
The same guidelines as above apply, but included are a few details to installing specific versions of NPM.
See the guide for the notes. (not noted, but updated)
Confirmed working with Ubuntu Server 15.10
-
@scottalanmiller said:
Why is there a special repo for Redis?
I'll change my playbook, I was just following this. I see the documentation just uses the one in the Ubuntu repo.
-
@scottalanmiller That was a part of the guide I had seen when I was first setting this up....
double checking now
-
-
@DustinB3403 said:
@scottalanmiller That was a part of the guide I had seen when I was first setting this up....
double checking now
I'm testing without it and with Node 4.2.4.
-
@DustinB3403 said:
Install version 3.3.12
sudo npm -install -g [email protected]This line has a typo. The command is install not -install. Is there a reason that you are going for that specific version rather than just updating to current?
npm install -g npm -
@scottalanmiller the most recent version was unsupported.
So it had to be >=2.27 but less than version 5
-
@DustinB3403 said:
@scottalanmiller the most recent version was unsupported.
So it had to be >=2.27 but less than version 5
3.5.3 is current.
-
I don't see a user explanation in the instructions. Where does the user come from and what role does it play?
-
Don't mix
nodeandnpmversion.BTW, it should work with latest
nodeversion now. -
@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?
-
@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.
-
@scottalanmiller said:
@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.
-
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
-
Something is different or changed...
-
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.
