Xen Orchestra - a web solution for XenServer

[olivier]

Don't forget to copy the vhd-util binary directly in xo-server/bin. The vhd-util-convert folder is useless after the make!

[DustinB3403]

Think I got it.

Have to test. Does that look correct?

[olivier]

Yep.

[olivier]

Due to problem with XAPI and metadata import, I decided it's more safe to write ourselve a solution to avoid use of those metadata. XAPI team told me that the code around this is not in a good shape...

So postponed for Monday. Sorry guys, there is some stuff we can't guess before we got trouble inside XAPI ^^

edit: at least our QA pass is useful ^^

[mlnews]

Maybe time to update XAPI

[olivier]

@mlnews Problem is also in next XenServer version. So we'll have better luck to write our own solution/workaround for this!

[DustinB3403]

@olivier question for you.

I Migrated a VM from a shit-box XenServer, and it's running on the other host, but Xen Orchestra doesn't see this VM on the Host.

Any ideas?

[DustinB3403]

So here is a system that I've been running with the Continuous Backup functionality.

Which I scheduled to run every 5 minutes. I would say it works unless the fulls in the 3rd picture should be completely gone.

I know the first picture says, "every hour on the hour" it's simply because I changed the frequency in which the backup runs.

[olivier]

I think because it was a previous delta job, it didn't modified some old files (I'm not certain of the behavior when changing in the middle of a previous delta job, I didn't personally coded this part ^^)

So is it still working or not?

If not, delete the old backup files, it will re-create the right things accordingly.

[DustinB3403]

@olivier I'll purge them and have them run every hour.

Will post some new picture tomorrow from home.

[DustinB3403]

Oh but that was a new backup job that I had built (completely new XO Server as well) so not sure that makes sense.

Maybe it's not compiled right.

[DustinB3403]

Anyways a new job is scheduled to run in 30 minutes, and then every hour on the hour.

[olivier]

If it's a new job, you shouldn't have multiple copies of a full VHD. Check your build!

[DustinB3403]

@olivier Is there somewhere specific I should be looking at to see if I'm "current" ?

[olivier]

@DustinB3403 your branch (git branch should be next-release), then be sure you get the latest commit with git log (Merge pull request #200).

npm i also to be sure you have every dependencies (and it will also build)

[DustinB3403]

git branch = next release (confirmed)

git log (lots of information, gonna read that later.... )

sudo npm i (is running now)

[olivier]

Just the first line will give you the last commit message, be sure it's my merge of a pull request 200.

[DustinB3403]

That is what I have..

[olivier]

You forgot to git pull to get last changes

[DustinB3403]

git pull

On the right pull (now)