Xen Orchestra - Community Edition - Installing with Yarn

noelweston

@DustinB3403 - I just signed up to say a massive thank you for this - I've been struggling with the previous instructions and going round in circles with no success. I've now used your script to build successfully on a ubuntu 16.04 server and am up and running.

I did find a couple of issues along the way - firstly, is there a typo in the command line? I think the correct path should be github.com/Jarli01/xenorchestra_installer/master/xo_install.sh - I only got it working in the first place by downloading the script and running locally.

Secondly, on my system at least, yarn wasn't installed, so the first run of the script failed - it was an easy enough correction to make, but could be checked and covered within the script?

Anyway, thanks again

Noel Weston

scottalanmiller

@noelweston welcome to MangoLassi!

Danp

@noelweston I believe the path should actually be -- https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh

noelweston

@Danp - OK - as I said, I've got round it - but I think there's a spare "edit" in the first post / instructions?

@scottalanmiller - thanks!

Danp

@noelweston said in Xen Orchestra - Community Edition - Installing with Yarn:

Secondly, on my system at least, yarn wasn't installed

Looks like the actual command to install is missing. According to their website, the proper command would be sudo apt-get update && sudo apt-get install yarn.

noelweston

@Danp - Yes, that's what I ended up doing. Might just be worth either adding to the script (if that doesn't cause other issues) or at least warning for noobs like me?

Danp

I'm sure @DustinB3403 will get it fixed up shortly.

DustinB3403

I've updated the script (sorry, not sure how I forgot the yarn install portion...) and tested both the installation, and then the force to enable the added functionality.

All is working as intended.

Also @noelweston welcome to the community, and I'm glad that I made your life a bit easier.

geek-baba

Hi @DustinB3403

I am trying to update the xo community install however after running the script successfully the xo web and server version remains old. I can see the master stable source is updated with latest version.
https://github.com/vatesfr/xo-web - 5.10.4
https://github.com/vatesfr/xo-server - 5.10.0

After running the updater script my xo is still at xo-server 5.8.0 and xo-web 5.9.0.

Danp

@shwetkprabhat Can you show us the console output from running the update script?

Also, show us the exact command you issued to perform the upgrade.

CloudKnight

Excellent post, thanks for the update Dustin.
The Xen Orchestra install script should be a sticky on this forum so its easy to find I think.

geek-baba

@Danp
I have tried 2 of them:

sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -b next-release

Output of 1:
root@xo:~# sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2624 100 2624 0 0 9088 0 --:--:-- --:--:-- --:--:-- 9079
Stopping xo-server...
Checking for Yarn package...
Checking for Yarn update...
Reading package lists... Done
Building dependency tree
Reading state information... Done
yarn is already the newest version (0.27.5-1).
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic linux-headers-4.4.0-78
linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-image-4.4.0-62-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic linux-image-4.4.0-78-generic
linux-image-4.4.0-79-generic linux-image-extra-4.4.0-62-generic linux-image-extra-4.4.0-72-generic linux-image-extra-4.4.0-75-generic linux-image-extra-4.4.0-78-generic
linux-image-extra-4.4.0-79-generic rlwrap
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Checking xo-server...
Current branch stable
Current version v5.8.0
91 updates available
Updating from source...

*** Please tell me who you are.

Run

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

[email protected] prebuild /opt/xo-server
index-modules src/api src/xapi/mixins src/xo-mixins

index generated src/api/index.js
index generated src/xapi/mixins/index.js
index generated src/xo-mixins/index.js

[email protected] build /opt/xo-server
gulp build --production

[05:39:08] Using gulpfile /opt/xo-server/gulpfile.js
[05:39:08] Starting 'build'...
[05:39:08] Starting 'clean'...
[05:39:08] Finished 'clean' after 6.08 ms
[05:39:08] Starting 'buildCoffee'...
[05:39:08] Starting 'buildEs6'...
[05:39:13] Finished 'buildCoffee' after 5.01 s
[05:39:32] Finished 'buildEs6' after 24 s
[05:39:32] Finished 'build' after 24 s
Done in 46.71s.
Updated version v5.8.0
Checking xo-web...
Current branch stable
Current version v5.8.3
44 updates available
Updating from source...

*** Please tell me who you are.

Run

git config --global user.email "[email protected]"
git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'root@xo.(none)')
Cannot save the current index state
Updating 9199784..2ee7333
error: Your local changes to the following files would be overwritten by merge:
yarn.lock
Please, commit your changes or stash them before you can merge.
Aborting
Clearing directories...
Installing...
yarn install v0.27.5
[1/4] Resolving packages...
[2/4] Fetching packages...
warning [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Rebuilding all packages...
success Saved lockfile.
$ npm run build

[email protected] build /opt/xo-web
npm run build-indexes && NODE_ENV=production gulp build

[email protected] build-indexes /opt/xo-web
index-modules --auto src

index generated src/common/intl/locales/index.js
index generated src/common/themes/index.js
[05:40:06] Using gulpfile /opt/xo-web/gulpfile.js
[05:40:06] Starting 'build'...
[05:40:06] Starting 'buildPages'...
[05:40:06] Starting 'buildScripts'...
[05:40:06] Starting 'buildStyles'...
[05:40:06] Starting 'copyAssets'...
[05:40:10] Finished 'buildPages' after 4.21 s
[05:40:15] Finished 'buildStyles' after 8.84 s
[05:40:16] Finished 'copyAssets' after 9.74 s
[05:42:42] Finished 'buildScripts' after 2.6 min
[05:42:42] Finished 'build' after 2.6 min
Done in 181.81s.
Updated version v5.8.3
Restarting xo-server...

Danp

@shwetkprabhat said in Xen Orchestra - Community Edition - Installing with Yarn:

*** Please tell me who you are.
Run
git config --global user.email "[email protected]"
git config --global user.name "Your Name"

You need to address this issue before it will build successfully.

DustinB3403

Before you proceed with that change, make sure to take a snapshot.

Danp

@DustinB3403 Isn't that a given for any upgrade?

hobbit666

What's the easiest way to see what the latest version is of XO-Web and server?

DustinB3403

@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 Isn't that a given for any upgrade?

You'd think that but often people need a reminder.

Danp

@hobbit666 Check github --

https://github.com/vatesfr/xo-web/releases

https://github.com/vatesfr/xo-server/releases

hobbit666

@Danp said in Xen Orchestra - Community Edition - Installing with Yarn:

@hobbit666 Check github --

https://github.com/vatesfr/xo-web/releases

https://github.com/vatesfr/xo-server/releases

Thx Bookmarked
I'm a bit old according to this lol (running 5.7.0)

CloudKnight

a few deprecated messages on some packages, node.js, and fspromise...