juju bootstrap fails with vSphere 6.0

[Mark Shuttleworth]

I think Ed is using vSphere with Juju in the only way one could before
Juju grew a native vSphere provider, and assumed Michael was doing the
same :)

MAAS has a (not recommended) ability to drive VMs on vSphere, based on
an (equally not recommended) ability to drive VMs through libvirt. If
you daisy chain all of that you can use the Juju provider to drive
vSphere, by making it think its driving MAAS, making MAAS think it's
driving libvirt. Phew, possible, not recommended :)

Nowadays we have a (brand new) native Juju provider for vSphere, which I
believe Michael is trying, and that's got some bugs to shake out. Sergey
would be the best person to help.

Mark

On 05/11/15 12:34, Forstner Michael wrote:
> Hi Ed,
>
> Thanks for the hints, but to be honest I do not really get what you’re talking about :-)
> My vSphere 6 Environment is not hosted by myself (or my company). We’re renting a complete package consisting of one vSphere datacenter (2 Hosts and 2 Storages). I am controlling the vSphere datacenter from my MacBook via VMWare Horizon and via the vSphere Client running inside a local Windows VM.
>
> As already mentioned, the API access to the vSphere API seems to work as VMWare’s go client is able to fetch information from the environment.
> Since I am getting some XML parsing error from the ‘juju bootstrap’ command I was wondering how can I enable further debugging options in order to trace down the problem.
>
> Thanks and regards,
> Michael
>