Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@xogurunoob The details can be found in this post from the XO site.
Another option is this script, which was written by Dustin.
-
@Danp
so after git checkout , i should ran that script? -
@xogurunoob Yes. After you switch to the desired branch using
git checkoutand then run the update script. -
@Danp
the update script does not complete
it hangs at the last line below> [email protected] build /opt/xo-web > gulp distclean && gulp build --production (node:935) 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:41:24] Using gulpfile /opt/xo-web/gulpfile.js [12:41:24] Starting 'clean'... [12:41:24] Finished 'clean' after 47 ms [12:41:24] Starting 'distclean'... [12:41:24] Finished 'distclean' after 379 μs (node:945) 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:41:24] Using gulpfile /opt/xo-web/gulpfile.js [12:41:24] Starting 'buildPages'... [12:41:25] Starting 'installBowerComponents'... [12:41:27] Starting 'copyFontMfizz'... [12:41:28] Finished 'buildPages' after 3.31 s [12:41:28] Finished 'copyFontMfizz' after 324 ms [12:41:28] Finished 'installBowerComponents' after 2.4 s [12:41:28] Starting 'buildScripts'... [12:41:28] Starting 'buildStyles'... [12:41:29] Starting 'copyAssets'... [12:41:38] Finished 'buildStyles' after 9.34 s [12:41:44] gulp-imagemin: Minified 11 images (saved 13.05 kB - 13.3%) [12:41:51] Finished 'copyAssets' after 21 s [12:42:49] Finished 'buildScripts' after 1.33 min [12:42:49] Starting 'build'... [12:42:49] Finished 'build' after 8.8 μs Updated version v4.16.0 -
-
It would have been nice if you has posted the complete console output
-
What happens when you reboot?
-
-
Updated version v4.16.0This doesn't make sense. It should be showing 4.16.1.
-
@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
It would have been nice if you has posted the complete console output
Doing so would have shown us the repo settings for both xo-web and xo-server. As is, we have no idea if you have switched to the correct repo.
-
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?
