Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

xogurunoob

if looks like an unfinished installation, when you go to the ip in browser, it shows like a mobile version and doesn't show certain things like css is missing or something and not completely installed.

output of what command? and from what wording directory should i run the command?

Danp

@xogurunoob Are you still trying this with Debian? I just rebuilt a new XO install using Ubuntu 16.04 without issue.

xogurunoob

@Danp
ok will delete the debian vm and start fresh with ubuntu 16.04 LTS now and see what happens

xogurunoob

@Danp
when you tried with ubuntu 16.04 what version of xo-web did it update to? v4.16.0?

xogurunoob

@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

xogurunoob

@Danp

I have a quick question for you

If i want to test out the latest version 5 for xo-web
can i just do git checkout v5.x and then run your update script?

Will that work?
will like to follow the version 5 for xo-web and see how its looking

thanks man

Danp

@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...

Danp

Just tried this myself. XO 5 interface appears to be very fast when compared to the 4.x interface.

BRRABill

As a new user to all this stuff, this thread has me a little confused.

I am on 4.14.1.

Can I update to the latest stable version? Or is the installer currently broken, and I have to stay on my version for now.

DustinB3403

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

As a new user to all this stuff, this thread has me a little confused.

I am on 4.14.1.

Can I update to the latest stable version? Or is the installer currently broken, and I have to stay on my version for now.

Staying on the stable branch (which the installer does for you) is the recommended solution. I generally check once a week or two for XO and see if anything breaks as I upgrade.

The XO software has dependencies that get broken from time to time, which is completely out of @olivier hands to control.

BRRABill

@DustinB3403 said

The XO software has dependencies that get broken from time to time, which is completely out of @olivier hands to control.

Didn't he say above it is currently broken?

That's what I mean ... will updating today break things?

Also, if I want to check out the new (next?) release, can I just move back to the previous one?

Danp

@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.

xogurunoob

@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?

BRRABill

@Danp said

@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.

Is "next release" the next MAJOR release, such as from 4 to 5? Or is the next release candidate, which like he said will be stable next week?

Is that a typical Linux nomenclature? Or does it vary from program to program?

DustinB3403

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

@Danp said

@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.

Is "next release" the next MAJOR release, such as from 4 to 5? Or is the next release candidate, which like he said will be stable next week?

Is that a typical Linux nomenclature? Or does it vary from program to program?

next-release (with regards to XO) is what is up for release for the following week. (or as they get migrated to stable).

I'm not sure if its a Linux nomenclature or just a translation from Olivier or what.

DustinB3403

@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

BRRABill

@DustinB3403 said

next-release (with regards to XO) is what is up for release for the following week. (or as they get migrated to stable).

So they are releasing the new version next week? Version 5, I mean?

Because that is what next-release currently gives you, right?

DustinB3403

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

@DustinB3403 said

next-release (with regards to XO) is what is up for release for the following week. (or as they get migrated to stable).

So they are releasing the new version next week? Version 5, I mean?

Because that is what next-release currently gives you, right?

The next-release time table is subject to Olivier and his team, so it could be next week, or it could be in two weeks. Though they try and stick to the weekly updates IIRC.

BRRABill

@DustinB3403 said

The next-release time table is subject to Olivier and his team, so it could be next week, or it could be in two weeks. Though they try and stick to the weekly updates IIRC.

But people on this thread were talking about version 5, so isn't that what next-release got them? How else would they have gotten it?

I'm going to try it in a little bit. Just always trying to expand the old knowledge base.

xogurunoob

@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#