Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@BRRABill said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
I just did this myself today. Woooohooo!
As a Linux noob it took me a while to realize I needed SUDO before the commands. But I got it finally.
sudo - don't use CAPS in linux, lol.
-
@BRRABill We just finished the new VM import stuff, which get:
- multiple XVA support
- pool/SR select
- drag and drop
We'll also include a progress bar for each file I think (sooner or later)
-
@aaronstuder said
sudo - don't use CAPS in linux, lol.
I was yelling.
-
-
@BRRABill There is no "official" support anywhere else XOA. We don't have the resources to validate multiple distros. But because Xen Orchestra use a very small number of system dependencies, it should work everywhere. I just cannot guarantee this.
-
@BRRABill said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@olivier said
@BRRABill We just finished the new VM import stuff, which get:
- multiple XVA support
- pool/SR select
- drag and drop
We'll also include a progress bar for each file I think (sooner or later)
XO4 is awesome. Can't wait to see XO5.
Hey, BTW is XO4 officially supported on 16.04?
People on this community have installed XO into Ubuntu 16.04, yes.
Only XOA comes with support from @olivier. Everything else is "community"
-
@DustinB3403 said
People on this community have installed XO into Ubuntu 16.04, yes.
Only XOA comes with support from @olivier. Everything else is "community"
Got it!
-
XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/
install script is same?
-
@xogurunoob said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/
install script is same?
The install script does work.
It's worth updating to the newest version of the install script though.
-
@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@xogurunoob said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
XO 5 is officially out https://xen-orchestra.com/blog/xen-orchestra-5-0/
install script is same?
The install script does work.
It's worth updating to the newest version of the install script though.
where is newest version of install script?
-
@xogurunoob Run the command in the first post on this thread.
-
installation did not complete FULLY
although i was still able to login via GUIroot@xen-orchestra-5:~# curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: [email protected] sudo: unable to resolve host xen-orchestra-5 > [email protected] build /opt/xo-web > npm run build-indexes && NODE_ENV=production gulp build > [email protected] build-indexes /opt/xo-web > ./tools/generate-index src/common/intl/locales [21:19:44] Using gulpfile /opt/xo-web/gulpfile.js [21:19:44] Starting 'build'... [21:19:44] Starting 'buildPages'... [21:19:44] Starting 'buildScripts'... [21:19:44] Starting 'buildStyles'... [21:19:44] Starting 'copyAssets'... [21:19:45] Finished 'buildPages' after 1.26 s [21:19:48] Finished 'buildStyles' after 3.93 s [21:19:48] Finished 'copyAssets' after 4.31 s [21:21:37] Finished 'buildScripts' after 1.88 min [21:21:37] Finished 'build' after 1.88 min sudo: unable to resolve host xen-orchestra-5 sudo: unable to resolve host xen-orchestra-5 Created symlink from /etc/systemd/system/multi-user.target.wants/xo-server.service to /etc/systemd/system/xo-server.service. sudo: unable to resolve host xen-orchestra-5 root@xen-orchestra-5:~# nano /etc/hosts root@xen-orchestra-5:~# ping xen-orchestra-5 PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.027 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.035 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.035 ms ^C --- localhost ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.027/0.032/0.035/0.006 ms root@xen-orchestra-5:~# curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1172 100 1172 0 0 1333 0 --:--:-- --:--:-- --:--:-- 1333 Reading package lists... Done Building dependency tree Reading state information... Done nfs-common is already the newest version (1:1.2.8-9ubuntu12). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic linux-image-extra-4.4.0-21-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ## Installing the NodeSource Node.js v5.x repo... ## Populating apt-get cache... + apt-get update Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB] Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:5 https://deb.nodesource.com/node_5.x xenial InRelease Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [222 kB] Get:7 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [219 kB] Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [99.9 kB] Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [97.0 kB] Fetched 732 kB in 1s (438 kB/s) Reading package lists... Done ## Confirming "xenial" is supported... + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dists/xenial/Release' ## Adding the NodeSource signing key to your keyring... + curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add - OK ## Creating apt sources list file for the NodeSource Node.js v5.x repo... + echo 'deb https://deb.nodesource.com/node_5.x xenial main' > /etc/apt/sources.list.d/nodesource.list + echo 'deb-src https://deb.nodesource.com/node_5.x xenial main' >> /etc/apt/sources.list.d/nodesource.list ## Running `apt-get update` for you... + apt-get update Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:5 https://deb.nodesource.com/node_5.x xenial InRelease Reading package lists... Done ## Run `apt-get install nodejs` (as root) to install Node.js v5.x and npm Reading package lists... Done Building dependency tree Reading state information... Done nodejs is already the newest version (5.12.0-1nodesource1~xenial1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic linux-image-extra-4.4.0-21-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 15243 100 15243 0 0 69684 0 --:--:-- --:--:-- --:--:-- 69922 Reading package lists... Done Building dependency tree Reading state information... Done build-essential is already the newest version (12.1ubuntu2). git is already the newest version (1:2.7.4-0ubuntu1). libpng12-dev is already the newest version (1.2.54-1ubuntu1). python-minimal is already the newest version (2.7.11-1). redis-server is already the newest version (2:3.0.6-1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-21-generic linux-image-extra-4.4.0-21-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. fatal: destination path 'xo-server' already exists and is not an empty directory. fatal: destination path 'xo-web' already exists and is not an empty directory. npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-server 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 [21:24:00] Using gulpfile /opt/xo-server/gulpfile.js [21:24:00] Starting 'build'... [21:24:00] Starting 'buildCoffee'... [21:24:00] Starting 'buildEs6'... [21:24:09] Finished 'buildCoffee' after 9.54 s [21:24:51] Finished 'buildEs6' after 51 s [21:24:51] Finished 'build' after 51 s [email protected] /opt/xo-web āāā [email protected] extraneous npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: [email protected] npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-web [email protected] /opt/xo-web āāā [email protected] extraneous 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 > npm run build-indexes && NODE_ENV=production gulp build > [email protected] build-indexes /opt/xo-web > ./tools/generate-index src/common/intl/locales [21:25:42] Using gulpfile /opt/xo-web/gulpfile.js [21:25:42] Starting 'build'... [21:25:42] Starting 'buildPages'... [21:25:42] Starting 'buildScripts'... [21:25:42] Starting 'buildStyles'... [21:25:42] Starting 'copyAssets'... [21:25:43] Finished 'buildPages' after 1.21 s [21:25:45] Finished 'buildStyles' after 3.71 s [21:25:46] Finished 'copyAssets' after 4.58 s [21:27:34] Finished 'buildScripts' after 1.87 min [21:27:34] Finished 'build' after 1.87 min root@xen-orchestra-5:~# cat /etc/*release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" NAME="Ubuntu" VERSION="16.04 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" UBUNTU_CODENAME=xenial -
@xogurunoob Looks like it worked after you edited the hosts file, correct? What changes did you make there.
fatal: destination path 'xo-server' already exists and is not an empty directory.
fatal: destination path 'xo-web' already exists and is not an empty directory.I wouldn't worry about that. The directory already existed and was populated during your first attempt.
-
sudo should be removed from the script. Your running it as root anyways, and it forces you to install sudo on a minimal Debian install.
-
@olivier New web interface isn't working on my iPhone
-
@aaronstuder That's a Safari issue. We opened an issue on GH.
Really, Safari is the new IE... https://nolanlawson.com/2015/06/30/safari-is-the-new-ie
-
@olivier Thanks for the reply!
-
This may be more of a GitHUb question, but ... how do you know what the latest version is?
A thread on the XO forum said that version 5.0.2 was out. I updated, no problems.
Except xo-server is still on 5.0.0. I would think that was weird, but I know in 4.X that sometimes happened.
Anyway, how do I find out what the latest version is, so I know when to freak out and when not to freak out.
-
@BRRABill You would watch the XO github site.
-
@DustinB3403 said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@BRRABill You would watch the XO github site.
So, I am on that page, and not finding what I am looking for.
I see there are separate xo-server and xo-web pages.
But still not seeing how to tell what the latest version of each is.
I am sure it's not a XO issue, just my unfamiliarity with GitHub.
