Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

DustinB3403

@DustinB3403 said:

Directly from the Hypervisor's crontab job

Or the cli to do it directly.

You can get to the CLI from the VM the same as from wherever you are getting to it from.

Putty and XC.

scottalanmiller

@DustinB3403 said:

@scottalanmiller said:

@DustinB3403 said:

Directly from the Hypervisor's crontab job

Or the cli to do it directly.

You can get to the CLI from the VM the same as from wherever you are getting to it from.

Putty and XC.

So SSH.

The script can use SSH just like Putty can.

Dashrender

is there any reason that this whole script couldn't be run from the XC server itself? Everything done over SSH, etc?

DustinB3403

@Dashrender do you mean run XO from Xen directly?

Rather than in it's own VM?

Dashrender

@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.

DustinB3403

@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.

Danp

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

DustinB3403

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.

travisdh1

@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.

DustinB3403

@travisdh1 Already tried it.

Doesn't appear to work.

Dashrender

@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?

DustinB3403

@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

Dashrender

@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?

DustinB3403

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

Danp

@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

DustinB3403

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

DustinB3403

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

I've reboot several times to confirm.

DustinB3403

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

scottalanmiller

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.

scottalanmiller

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.