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
    280.9k
    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.
    • olivierO
      olivier
      last edited by olivier

      And now you discover why we release appliance with an updater and validated updates 😉

      Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.

      This stuff is sadly not very uncommon.

      1 Reply Last reply Reply Quote 2
      • DustinB3403D
        DustinB3403
        last edited by

        @olivier said:

        And now you discover why we release appliance with an updater and validated updates 😉

        Lodash team made a release 6 hours ago, and it broke everything. We are working on a way to avoid that, or reported this to them.

        This stuff is sadly not very uncommon.

        How dare they break it!

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

          @DustinB3403 said:

          What is there to understand about it?

          Following a base install of the server OS, i built a user named "xoadmin" which the mount directory uses /home/xoadmin/xo-web/dist/ in the .xo-sample.yaml file

          Well the part ot understand is that you manually made a user and it wasn't made by the installer like most software does. If you are making a how to, you have to include the steps or else things are missing.

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

            @olivier What's the best way to know what Node and NPM version should be used?

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

              Ok, here's the updated playbook. Just add your hostname in /etc/ansible/hosts and your username in the variables file, it will do the rest.

              https://app.box.com/s/w84npeu4xu4m3jhphs4fn91cnfxoii9y

              1 Reply Last reply Reply Quote 0
              • olivierO
                olivier @Alex Sage
                last edited by

                @anonymous Experience ^^ (if the build fails).

                In general, when there is a new big release of Node, dependencies can't catch the breaking changes for a time. That's why Node 5 broke the build for a time.

                You can use the LTS version of Node to be safe: https://nodejs.org/en/blog/release/v4.2.0/

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

                  Hopefully LTS means more for Node than it does for ubuntu.

                  olivierO 1 Reply Last reply Reply Quote 0
                  • olivierO
                    olivier @scottalanmiller
                    last edited by

                    @scottalanmiller hahaha 😄

                    1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      I lost track of if @anonymous is using CentOS or Ubuntu now..

                      Here is the guide for nodejs on CentOS 7

                      http://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm

                      scottalanmillerS 1 Reply Last reply Reply Quote 1
                      • scottalanmillerS
                        scottalanmiller @JaredBusch
                        last edited by

                        @JaredBusch said:

                        I lost track of if @anonymous is using CentOS or Ubuntu now..

                        Here is the guide for nodejs on CentOS 7

                        http://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm

                        I updated that this morning to cover Ubuntu too. Tested and working there as well.

                        1 Reply Last reply Reply Quote 0
                        • olivierO
                          olivier
                          last edited by

                          It should also work on MacOS and Windows ^^

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

                            @olivier said:

                            It should also work on MacOS and Windows ^^

                            But... who cares 😉

                            1 Reply Last reply Reply Quote 0
                            • olivierO
                              olivier
                              last edited by

                              Build should be back on track on next-release branch.

                              DustinB3403D 1 Reply Last reply Reply Quote 4
                              • DustinB3403D
                                DustinB3403 @olivier
                                last edited by

                                @olivier said:

                                Build should be back on track on next-release branch.

                                From the individual folders of xo-server and xo-web

                                git checkout next-release
                                
                                git fetch; git pull
                                
                                1 Reply Last reply Reply Quote 1
                                • olivierO
                                  olivier
                                  last edited by

                                  If you want to stick on stable, a workaround would be npm i lodash.trim@3.0.1

                                  1 Reply Last reply Reply Quote 1
                                  • DustinB3403D
                                    DustinB3403
                                    last edited by

                                    At @olivier this is what I'm getting now, attempting this install.

                                    0_1452704902568_XenCenter_2016-01-13_12-07-42.png

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

                                      Same here, even after installing GULP.

                                      DustinB3403D 1 Reply Last reply Reply Quote 0
                                      • DustinB3403D
                                        DustinB3403 @scottalanmiller
                                        last edited by

                                        @scottalanmiller Are you running stable as well, or "next release" ?

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

                                          @DustinB3403 said:

                                          @scottalanmiller Are you running stable as well, or "next release" ?

                                          I'm running from your how-to

                                          1 Reply Last reply Reply Quote 0
                                          • olivierO
                                            olivier
                                            last edited by

                                            That's because the install process went bad, due to lodash issue (we reported it here)

                                            So before the npm i, do a npm i lodash.trim@3.0.1.

                                            DashrenderD 1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 6
                                            • 7
                                            • 8
                                            • 9
                                            • 10
                                            • 30
                                            • 31
                                            • 8 / 31
                                            • First post
                                              Last post