Set IPAddress parameter, fixing Rancher 2.0 issue

[fabiorauber]

When the VM is created and its IP Address is collected, the XenServer machine driver was not setting the IPAddress parameter, expected by Rancher 2.0. This parameter comes from the base machine driver, so it should be set.

[jonathon2nd]

@facioraber

Have you used this or your fork in Rancher UI?

[fabiorauber]

@jonathon2nd, i'm using my fork within Rancher, to create VMs in Rancher node pools: https://github.com/interlegis/docker-machine-driver-xcp

[jonathon2nd]

@facioraber is there a guide which I can refer to for using your fork in Rancher? I have added the node driver from here and I am looking at "XCP URL for boot2docker image" now. Is that referring to this: https://github.com/boot2docker/boot2docker/releases/tag/v19.03.12?

I won't actually be able to use this the way I intended. I was going to use this driver as part of a hybrid cluster, with the Openstack driver for public cloud. But I found out you currently can not mix them https://github.com/rancher/rancher/issues/26330. I may use this later for purely 'on prem'. Thank you for the assistance.

[fabiorauber]

Answering your question @jonathon2nd, it refers to a valid boot2docker ISO image file URL. If you specify a different OS Template name with --xcp-os-template variable, then the boot2docker URL is not used. I'm currently using it for purely on-prem clusters.