Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

BRRABill

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#

xogurunoob

@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

Danp

@xogurunoob Try this instead:

  sudo npm i
  sudo npm run build

Danp

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

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?

No. v5.x is the new interface that they have been implementing over the past few months. Next-release is still based on the older 4.x interface.

xogurunoob

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

xogurunoob

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

xogurunoob

@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

BRRABill

@xogurunoob said

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?

Ahhhhh....I missed this.

Linux NOOB!

Danp

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

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

I'm sure it will take some adjustment, but you'll eventually like it.

olivier

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

xogurunoob

@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