Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
root@xen-orchestra:/opt/xo-server# curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 728 100 728 0 0 10154 0 --:--:-- --:--:-- --:--:-- 10253 Checking xo-server... Current version v4.17.0 remote: Counting objects: 11, done. remote: Total 11 (delta 7), reused 7 (delta 7), pack-reused 4 Unpacking objects: 100% (11/11), done. From https://github.com/vatesfr/xo-server dd62bef..22ff330 next-release -> origin/next-release * [new branch] vif-set -> origin/vif-set 18 updates available Updating from source... Updating dd62bef..22ff330 Fast-forward package.json | 1 + 1 file changed, 1 insertion(+) npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-server [email protected] /opt/xo-server └─┬ @marsaud/[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] > [email protected] build /opt/xo-server > npm run build-indexes && gulp build --production > [email protected] build-indexes /opt/xo-server > ./tools/generate-index src/api src/xapi-mixins src/xo-mixins [12:28:10] Using gulpfile /opt/xo-server/gulpfile.js [12:28:10] Starting 'build'... [12:28:10] Starting 'buildCoffee'... [12:28:10] Starting 'buildEs6'... [12:28:19] Finished 'buildCoffee' after 8.35 s [12:28:58] Finished 'buildEs6' after 48 s [12:28:58] Finished 'build' after 48 s Updated version v4.17.0 Checking xo-web... Current version v4.16.0 remote: Counting objects: 565, done. remote: Compressing objects: 100% (251/251), done. remote: Total 565 (delta 304), reused 156 (delta 156), pack-reused 147 Receiving objects: 100% (565/565), 166.19 KiB | 0 bytes/s, done. Resolving deltas: 100% (353/353), completed with 33 local objects. From https://github.com/vatesfr/xo-web * [new branch] abhamonr-v5.x-select-component-limit -> origin/abhamonr-v5.x-select-component-limit * [new branch] marsaudf-job-creator -> origin/marsaudf-job-creator * [new branch] marsaudf-restore-rework -> origin/marsaudf-restore-rework + 1881ba5...9112bea pierre-v5-new-vm -> origin/pierre-v5-new-vm (forced update) 970fc16..29ac883 v5.x -> origin/v5.x + 5d8ca0e...5a8df93 xoa-updater -> origin/xoa-updater (forced update) 2 updates available Updating from source... Already up-to-date. 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] > [email protected] build /opt/xo-web > gulp distclean && gulp build --production (node:16305) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version. [12:29:28] Using gulpfile /opt/xo-web/gulpfile.js [12:29:28] Starting 'clean'... [12:29:28] Finished 'clean' after 20 ms [12:29:28] Starting 'distclean'... [12:29:28] Finished 'distclean' after 379 μs (node:16315) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version. [12:29:28] Using gulpfile /opt/xo-web/gulpfile.js [12:29:28] Starting 'buildPages'... [12:29:29] Starting 'installBowerComponents'... [12:29:29] Starting 'copyFontMfizz'... [12:29:29] Finished 'buildPages' after 1.16 s [12:29:30] Finished 'copyFontMfizz' after 269 ms [12:29:30] Finished 'installBowerComponents' after 1.02 s [12:29:30] Starting 'buildScripts'... [12:29:30] Starting 'buildStyles'... [12:29:30] Starting 'copyAssets'... [12:29:34] Finished 'buildStyles' after 3.86 s [12:29:35] gulp-imagemin: Minified 11 images (saved 13.05 kB - 13.3%) [12:29:47] Finished 'copyAssets' after 16 s [12:30:44] Finished 'buildScripts' after 1.23 min [12:30:44] Starting 'build'... [12:30:44] Finished 'build' after 11 μs Updated version v4.16.0 -
Ok.... is it working now. If not, what's the output when you try to run xo-server?
-
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?
-
@xogurunoob Are you still trying this with Debian? I just rebuilt a new XO install using Ubuntu 16.04 without issue.
-
@Danp
ok will delete the debian vm and start fresh with ubuntu 16.04 LTS now and see what happens -
@Danp
when you tried with ubuntu 16.04 what version of xo-web did it update to? v4.16.0? -
@Danp
ok i tried it on ubuntu 16.04 lts and it worked
when it got to theUpdated version v4.16.0
then the vm rebooted itself and after then it started working -
I have a quick question for you
If i want to test out the latest version 5 for xo-web
can i just dogit checkout v5.xand then run your update script?Will that work?
will like to follow the version 5 for xo-web and see how its lookingthanks man
-
@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...
-
Just tried this myself. XO 5 interface appears to be very fast when compared to the 4.x interface.
-
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.
-
@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.
-
@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?
-
@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.
-
@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?
-
@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?
-
@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.
-
@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
-
@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?
-
@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.
