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.0k
    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.
    • D
      DustinB3403
      last edited by

      @Dashrender do you mean run XO from Xen directly?

      Rather than in it's own VM?

      D 1 Reply Last reply Reply Quote 0
      • D
        Dashrender @DustinB3403
        last edited by

        @DustinB3403 said:

        @Dashrender do you mean run XO from Xen directly?

        Rather than in it's own VM?

        No, run the scripts that update XO, and kick off the backup/snap/etc of XO from XC/Xen directly.

        D 1 Reply Last reply Reply Quote 0
        • D
          DustinB3403 @Dashrender
          last edited by

          @Dashrender said:

          @DustinB3403 said:

          @Dashrender do you mean run XO from Xen directly?

          Rather than in it's own VM?

          No, run the scripts that update XO, and kick off the backup/snap/etc of XO from XC/Xen directly.

          But why?

          You can run a scheduled backup from within XO to backup your XO VM on any schedule you set. Once that completes run the xo-update.sh script and confirm all is functional.

          This would also allow you to take advantage of the Continuous delta capabilities. Rather than having to build a full every time you want to update.

          It would be much easier to set a backup to run weekly for just the XO VM, stop the services, run the update, reboot XO VM, and restart the services.

          D 1 Reply Last reply Reply Quote 1
          • D
            Danp
            last edited by

            You could use xo-cli to make the backup or create a snapshot.

            1 Reply Last reply Reply Quote 0
            • D
              DustinB3403
              last edited by

              Just so everyone is aware, this installation runs from an Active SSH Connection.

              I'm still trying to figure out how to get it to run at boot, without needing an Active Connection.

              T 1 Reply Last reply Reply Quote 0
              • T
                travisdh1 @DustinB3403
                last edited by

                @DustinB3403 said:

                Just so everyone is aware, this installation runs from an Active SSH Connection.

                I'm still trying to figure out how to get it to run at boot, without needing an Active Connection.

                make a cron job with @restart for the "when to run" fields.

                D 1 Reply Last reply Reply Quote 0
                • D
                  DustinB3403 @travisdh1
                  last edited by

                  @travisdh1 Already tried it.

                  Doesn't appear to work.

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    Dashrender @DustinB3403
                    last edited by

                    @DustinB3403 said:

                    @Dashrender said:

                    @DustinB3403 said:

                    @Dashrender do you mean run XO from Xen directly?

                    Rather than in it's own VM?

                    No, run the scripts that update XO, and kick off the backup/snap/etc of XO from XC/Xen directly.

                    But why?

                    You can run a scheduled backup from within XO to backup your XO VM on any schedule you set. Once that completes run the xo-update.sh script and confirm all is functional.

                    This would also allow you to take advantage of the Continuous delta capabilities. Rather than having to build a full every time you want to update.

                    It would be much easier to set a backup to run weekly for just the XO VM, stop the services, run the update, reboot XO VM, and restart the services.

                    The problem on relying on the delta from within XO is what if the update breaks XO? How do you now roll the delta back?

                    D 1 Reply Last reply Reply Quote 0
                    • D
                      DustinB3403 @Dashrender
                      last edited by

                      @Dashrender said:

                      @DustinB3403 said:

                      @Dashrender said:

                      @DustinB3403 said:

                      @Dashrender do you mean run XO from Xen directly?

                      Rather than in it's own VM?

                      No, run the scripts that update XO, and kick off the backup/snap/etc of XO from XC/Xen directly.

                      But why?

                      You can run a scheduled backup from within XO to backup your XO VM on any schedule you set. Once that completes run the xo-update.sh script and confirm all is functional.

                      This would also allow you to take advantage of the Continuous delta capabilities. Rather than having to build a full every time you want to update.

                      It would be much easier to set a backup to run weekly for just the XO VM, stop the services, run the update, reboot XO VM, and restart the services.

                      The problem on relying on the delta from within XO is what if the update breaks XO? How do you now roll the delta back?

                      You don't backup to the XO vDisk you backup to a separate NFS target

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        Dashrender @DustinB3403
                        last edited by

                        @DustinB3403 said:

                        @Dashrender said:

                        @DustinB3403 said:

                        @Dashrender said:

                        @DustinB3403 said:

                        @Dashrender do you mean run XO from Xen directly?

                        Rather than in it's own VM?

                        No, run the scripts that update XO, and kick off the backup/snap/etc of XO from XC/Xen directly.

                        But why?

                        You can run a scheduled backup from within XO to backup your XO VM on any schedule you set. Once that completes run the xo-update.sh script and confirm all is functional.

                        This would also allow you to take advantage of the Continuous delta capabilities. Rather than having to build a full every time you want to update.

                        It would be much easier to set a backup to run weekly for just the XO VM, stop the services, run the update, reboot XO VM, and restart the services.

                        The problem on relying on the delta from within XO is what if the update breaks XO? How do you now roll the delta back?

                        You don't backup to the XO vDisk you backup to a separate NFS target

                        Sure, but what does the restoration? it's XO, right? So if XO is broken you can't run the store, right?

                        1 Reply Last reply Reply Quote 0
                        • D
                          DustinB3403
                          last edited by

                          You can export from the NFS Share using WinSCP and import directly into XenCenter if things are horribly broken.

                          1 Reply Last reply Reply Quote 1
                          • D
                            Danp @DustinB3403
                            last edited by

                            @DustinB3403 said:

                            Already tried it.

                            Doesn't appear to work.

                            Post your cron entry here.

                            Also may want to review these options:
                            https://www.npmjs.com/package/node-crontab
                            https://www.npmjs.com/package/forever

                            1 Reply Last reply Reply Quote 0
                            • D
                              DustinB3403
                              last edited by

                              Ok So here is what I've done to get XO to run at boot.

                              I made a script in /etc/ named "xo-start.sh" marked it as executable.

                              cd  /etc
                              nano xo-start.sh
                              
                              
                              #!/bin/sh
                              cd /opt/xo-server
                              sudo npm start
                              
                               ctrl+o
                               ctrl+x
                              
                              sudo nano /etc/crontab
                              
                              #
                               shit ton of comments
                              #
                              @reboot cd /etc && ./xo-start.sh
                              
                              ctrl+o
                              ctrl+x
                              
                              sudo reboot now
                              
                              1 Reply Last reply Reply Quote 1
                              • D
                                DustinB3403
                                last edited by

                                That should be all you need to get XO to run at startup of your XO VM.

                                I've reboot several times to confirm.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  DustinB3403
                                  last edited by

                                  So the last question is, how do we get XO to stop so we can manually run our updates.

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

                                    If you are firing up from cron, which is pretty normal for a low key service such as this, then you would kill it using the kill command.

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

                                      Problem is, with processes that run via npm or similar, their name never appears and there is no universal standard for stopping them. Doing so manually is super simple, but in a script is dangerous and ill advised. If you are very brave you can use ps and look for npm, but if the server is running anything else, you might kill the wrong thing.

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

                                        And to complicate things, there is no stop script for xo-server 🙂

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          travisdh1 @scottalanmiller
                                          last edited by

                                          @scottalanmiller said:

                                          Problem is, with processes that run via npm or similar, their name never appears and there is no universal standard for stopping them. Doing so manually is super simple, but in a script is dangerous and ill advised. If you are very brave you can use ps and look for npm, but if the server is running anything else, you might kill the wrong thing.

                                          Doesn't 'cd /install/location' 'npm stop' work? Why make it difficult?

                                          scottalanmillerS D 2 Replies Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @travisdh1
                                            last edited by

                                            @travisdh1 said:

                                            @scottalanmiller said:

                                            Problem is, with processes that run via npm or similar, their name never appears and there is no universal standard for stopping them. Doing so manually is super simple, but in a script is dangerous and ill advised. If you are very brave you can use ps and look for npm, but if the server is running anything else, you might kill the wrong thing.

                                            Doesn't 'cd /install/location' 'npm stop' work? Why make it difficult?

                                            No, there is no stop script.

                                            T 1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 8
                                            • 9
                                            • 10
                                            • 11
                                            • 12
                                            • 30
                                            • 31
                                            • 10 / 31
                                            • First post
                                              Last post