I was moving to juju.2.0-alpha2-xenial-amd64 and I noticed that I can not bootstrap my KVM environment when I moved my configuration from 1.25 to 2.0-alpha2
I realize the "local" provider is going away in 2.0. Talking with KVM on my local system is a feature I use very much, and removing that feature may upset some customers.
Of course there are ways to talk to libvirt deamons on different systems qemu+ssh://IP-address/system. Is it possible we are going to get a libvirt provider that is "non-local"? If so please tell me how to properly configure that.
If there are no plans for KVM in 2.0 that is a big feature of a popular virtualization technology that we are removing from Juju. KVM works very well on Linux and I can imagine many users making use of the KVM type in previous versions of Juju (as I was using it EVERY day).
I currently use local KVM provider as a much faster way of validating SDN charms. Removing this support breaks my current workflow and makes testing cycles that much longer.
I think it's a mistake to remove this without drop-in replacement functionality.