yes, that workaround works, also you can change /etc/default/lxd-bridge and
restart the lxd-bridge service.
On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall wrote:
> On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
> alexis.bruem...@canonical.com> wrote:
>
>>
>> Hi All,
>>
>> As recently highligh
I am about to land a change in the way we persist user permissions in juju
core master, this will not change API but existing models/controllers will
stop working so please be aware of this before pulling the latest version
of the code and trying to upgrade to it.
Cheers and sorry for the inconveni
This just landed fyi.
On Tue, Jun 21, 2016 at 8:36 AM, Horacio Duran
wrote:
> I am about to land a change in the way we persist user permissions in juju
> core master, this will not change API but existing models/controllers will
> stop working so please be aware of this before pu
Chance seems to be in the right path there.
In the example "dc0" is the name of our data center, to figure out yours
you can access the vsphere web client and in there go to:
Home->Vcenter inventory lists->Resources->Datacenters (all this in the
left tree like menu)
And you will be presented with
Beware, current release has a bug that might affect you where many
connections are open and never closed to the vcenter, it is being worked as
we speak and will most likely be included in the next release, sorry for
that.
On Mon, Oct 24, 2016 at 1:19 PM, Horacio Duran
wrote:
> Chance seems
This is how mine looks
clouds:
vsphere:
type: vsphere
auth-types: [userpass]
endpoint:
regions:
dc0: {}
On Mon, Oct 24, 2016 at 2:10 PM, Peter Petrakis
wrote:
> On Mon, Oct 24, 2016 at 12:19 PM, Horacio Duran
> wrote:
> > Chance seems to be in the righ
