ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

    IT Discussion
    how to xen orchestra ubuntu 15.10 debian xen open source ubuntu linux xenserver
    24
    609
    281.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @Alex Sage
      last edited by

      @anonymous said:

      @scottalanmiller Do I have to remove the old version first?

      No but better if you do. It will keep being the default.

      1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @Alex Sage
        last edited by

        @anonymous said:

        Doh! NPM is out of date too. How do I update it?

        I think NVM will handle that too.

        1 Reply Last reply Reply Quote 0
        • A
          Alex Sage
          last edited by Alex Sage

          Updated NPM using:

           curl -L https://npmjs.com/install.sh | sh
          

          Still isn't working 😞

          npm ERR! Linux 3.10.0-327.el7.x86_64
          npm ERR! argv "/root/.nvm/v4.2.2/bin/node" "/root/.nvm/v4.2.2/bin/npm" "start"
          npm ERR! node v4.2.2
          npm ERR! npm  v3.5.3
          npm ERR! code ELIFECYCLE
          npm ERR! [email protected] start: `node bin/xo-server`
          npm ERR! Exit status 1
          npm ERR!
          npm ERR! Failed at the [email protected] start script 'node bin/xo-server'.
          npm ERR! Make sure you have the latest version of node.js and npm installed.
          npm ERR! If you do, this is most likely a problem with the xo-server package,
          npm ERR! not with npm itself.
          npm ERR! Tell the author that this fails on your system:
          npm ERR!     node bin/xo-server
          npm ERR! You can get information on how to open an issue for this project with:
          npm ERR!     npm bugs xo-server
          npm ERR! Or if that isn't available, you can get their info via:
          npm ERR!     npm owner ls xo-server
          npm ERR! There is likely additional logging output above.
          
          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller
            last edited by

            Did you do a fresh install using Node 4?

            A 1 Reply Last reply Reply Quote 0
            • A
              Alex Sage @scottalanmiller
              last edited by

              @scottalanmiller No, I can try that.

              1 Reply Last reply Reply Quote 0
              • A
                Alex Sage
                last edited by

                [xo@xo ~]$ sudo yum -y install build-essential redis-server libpng-dev git python-minima
                Loaded plugins: fastestmirror
                Loading mirror speeds from cached hostfile
                 * base: mirror.net.cen.ct.gov
                 * epel: mirror.cogentco.com
                 * extras: mirror.cc.columbia.edu
                 * updates: mirror.us.leaseweb.net
                No package build-essential available.
                No package redis-server available.
                No package libpng-dev available.
                Package git-1.8.3.1-6.el7.x86_64 already installed and latest version
                No package python-minima available.
                Nothing to do
                [xo@xo ~]$
                
                1 Reply Last reply Reply Quote 0
                • A
                  Alex Sage
                  last edited by

                  Any idea what the correct packages might be?

                  1 Reply Last reply Reply Quote 0
                  • A
                    Alex Sage
                    last edited by

                    [11:39:58] Using gulpfile ~/xo-server/gulpfile.js
                    [11:39:58] Starting 'build'...
                    [11:39:58] Starting 'buildCoffee'...
                    [11:39:58] Starting 'buildEs6'...
                    [11:39:59] 'buildEs6' errored after 925 ms
                    [11:39:59] Error: EACCES: permission denied, mkdir '/home/xo/xo-server/dist'
                    at Error (native)

                    [11:39:59] 'build' errored after 929 ms
                    [11:39:59] The following tasks did not complete: buildCoffee
                    [11:39:59] Did you forget to signal async completion?

                    npm ERR! Linux 3.10.0-327.el7.x86_64
                    npm ERR! argv "/home/xo/.nvm/versions/node/v4.2.2/bin/node" "/home/xo/.nvm/versions/node/v4.2.2/bin/npm" "run" "build"
                    npm ERR! node v4.2.2
                    npm ERR! npm v3.5.3
                    npm ERR! code ELIFECYCLE
                    npm ERR! [email protected] build: gulp build --production
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the [email protected] build script 'gulp build --production'.
                    npm ERR! Make sure you have the latest version of node.js and npm installed.
                    npm ERR! If you do, this is most likely a problem with the xo-server package,
                    npm ERR! not with npm itself.
                    npm ERR! Tell the author that this fails on your system:
                    npm ERR! gulp build --production
                    npm ERR! You can get information on how to open an issue for this project with:
                    npm ERR! npm bugs xo-server
                    npm ERR! Or if that isn't available, you can get their info via:
                    npm ERR! npm owner ls xo-server
                    npm ERR! There is likely additional logging output above.
                    npm ERR! Linux 3.10.0-327.el7.x86_64
                    npm ERR! argv "/home/xo/.nvm/versions/node/v4.2.2/bin/node" "/home/xo/.nvm/versions/node/v4.2.2/bin/npm" "run" "build"
                    npm ERR! node v4.2.2
                    npm ERR! npm v3.5.3
                    npm ERR! path npm-debug.log.1635463929
                    npm ERR! code EACCES
                    npm ERR! errno -13
                    npm ERR! syscall open

                    npm ERR! Error: EACCES: permission denied, open 'npm-debug.log.1635463929'
                    npm ERR! at Error (native)
                    npm ERR! { [Error: EACCES: permission denied, open 'npm-debug.log.1635463929']
                    npm ERR! errno: -13,
                    npm ERR! code: 'EACCES',
                    npm ERR! syscall: 'open',
                    npm ERR! path: 'npm-debug.log.1635463929' }
                    npm ERR!
                    npm ERR! Please try running this command again as root/Administrator.

                    npm ERR! Please include the following file with any support request:
                    npm ERR! /home/xo/xo-server/npm-debug.log
                    [xo@xo xo-server]$

                    1 Reply Last reply Reply Quote 0
                    • A
                      Alex Sage
                      last edited by Alex Sage

                      Guess I am headed back to Ubuntu.....

                      15.10 this time.....

                      1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller
                        last edited by

                        Did you install the EPEL before trying all that?

                        A 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller
                          last edited by

                          What OS does Dustin use in his how to? try that one.

                          1 Reply Last reply Reply Quote 0
                          • A
                            Alex Sage
                            last edited by

                            3rd command needs sudo

                            1 Reply Last reply Reply Quote 0
                            • A
                              Alex Sage @scottalanmiller
                              last edited by

                              @scottalanmiller said:

                              Did you install the EPEL before trying all that?

                              No..... 😞

                              1 Reply Last reply Reply Quote 0
                              • A
                                Alex Sage
                                last edited by

                                sudo npm -install -g npm does not work.

                                The correct command is:

                                 npm install -g npm
                                
                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller
                                  last edited by

                                  That would help. CentOS is designed for ultimate stability and only products full provided by and supported as part of the OS come by default. If you want to install anything beyond that, which is a LOT, you turn on the EPEL...

                                  yum -y install epel-release
                                  

                                  Once you do that the number of packages goes from a small, tight list to massive including everything in Fedora and more. It makes CentOS a lot more like Ubuntu. It's an extra step but it is there to make sure you know when you are leaving the "ultra testing and support" of the core packages and going the "community support and best effort support" of the EPEL.

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    Alex Sage @scottalanmiller
                                    last edited by

                                    @scottalanmiller Going to start over on CentOS 7 😞

                                    1 Reply Last reply Reply Quote 0
                                    • stacksofplatesS
                                      stacksofplates
                                      last edited by

                                      You're not completely destroying these VMs and recreating are you? Just make a default template of each to test with.

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        Alex Sage @stacksofplates
                                        last edited by

                                        @johnhooks Say what? 🙂

                                        stacksofplatesS 1 Reply Last reply Reply Quote 0
                                        • stacksofplatesS
                                          stacksofplates @Alex Sage
                                          last edited by

                                          @anonymous said:

                                          @johnhooks Say what? 🙂

                                          Just create a VM in xenserver and convert it to a template, then you can spin up a new VM from that template in about 5 seconds.

                                          A 1 Reply Last reply Reply Quote 2
                                          • A
                                            Alex Sage @stacksofplates
                                            last edited by

                                            @johnhooks I can't believe I never knew about this before!!! 😕

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 30
                                            • 31
                                            • 3 / 31
                                            • First post
                                              Last post