Xen Orchestra - Community Edition - Installing with Yarn

DustinB3403

Carl Holzhauer if you're reading this, this is the "Community" edition, all features that we have access too, are enabled and free for you to use.

XOA is the paid appliance you would get from xen-orchestra.com and is simply, the professionally supported version. It kind of mimics ESXi's licensing model (sadly).

scottalanmiller

Hi Carl..... waves

Danp

Tried updating to the latest version of XO earlier today and ran into a few issues, such as the following warning --

[4/5] Linking dependencies...
warning "[email protected]" has incorrect peer dependency "eslint@>=3.19.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-import@>=2.2.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-node@>=4.2.2".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-promise@>=3.5.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-standard@>=3.0.0".

Reviewing the upgrade process, found the following error during apt-get update --

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Some index files failed to download. They have been ignored, or old ones used instead.

Turns out that the the Yarn public key was expiring soon and they've issued a new key as described here.

Haven't figured out the proper way to resolve this as part of the update script. However, I have tried both of the following with success --

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

This just manually issues the command from the script to add the correct key.

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E074D16EB6FF4DE3

This method works as well by retrieving the key directly from the key server.

Danp

After upgrading to Yarn 1.1.0, the majority of the warnings are gone. For me, all that remains is

[4/5] Linking dependencies...
warning "[email protected]" has unmet peer dependency "prop-types@^15.5.4".
warning The case-insensitive file /opt/xo-web/node_modules/react-bootstrap-4/node_modules shouldn't be copied twice in one bulk copy

and I haven't investigated those yet.

Danp

Updated the script earlier today to deal with a change in the yarn build process.

Sid

@dustinb3403 Hi, I'm new here and I want to try this XO community edition for my laboratory. these are the command i need to run on fresh install ubuntu server 17.04?

DustinB3403

@sid it should install just fine. I haven't had much time to work on this install for the past several months.

Give the process a try and let us know.

bnrstnr

@Sid Yes, the following should do it. I would start with Ubuntu 17.10 though. I'm testing it out right now, about 3/4 of the way done. I'll let you know if there are any snags.

sudo bash
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

geek-baba

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

DustinB3403

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

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.

Can you provide a link to the github of it and we can look into it. Also post any information in a code block.

scottalanmiller

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

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

Hi - anyone tried XOSAN with XO Community edition? I use a Adaptec raid controller and I keep having issues with it.

At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.

Can you provide a link to the github of it and we can look into it. Also post any information in a code block.

That would be great to add in.

bnrstnr

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

At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.

Looks like XCP-ng has already reached it's stretch goal for "bundled gluster support."
If their scheduling is accurate you could essentially have XO-SAN built into XCP-ng by the end of this year.

scottalanmiller

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

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

At the time of this post the XOSAN functionality wasn't open sourced so we were unable to test / implement it.

Looks like XCP-ng has already reached it's stretch goal for "bundled gluster support."
If their scheduling is accurate you could essentially have XO-SAN built into XCP-ng by the end of this year.

That would not surprise me at all.

Kju

how can i update to 5.18 ?
the script for updating
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
stays on 5.17

hobbit666

Can't you update through the web gui?

Danp

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

Can't you update through the web gui?

Only if you are running the pre-built appliance (XOA). There isn't an updater available in the GUI when built from source.

Danp

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

how can i update to 5.18 ?
the script for updating
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
stays on 5.17

Not enough details here to know how to help. You could post the output from the console window showing the results from running the above command.

Also, show us the contents of the /opt directory.

hobbit666

@danp ah ok

DustinB3403

Are you being prompted to identify yourself to git?

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

Danp

@dustinb3403 Good call... I had forgotten about that issue.