LXD cloud naming conflict

[Simon Richardson]

It's possible to name your clouds in LXD with add-cloud "localhost" or "lxd", which can cause all sorts of mayhem. We should possibly discuss a blacklist approach to prevent any surprises for the user when they're creating clouds for LXD.

Names to be considered "harmful":

 - "localhost"
 - "lxd"

[John A Meinel (jameinel)]

I actively use the name "lxd" because I reconfigure my LXD provider to use
my apt-http-proxy settings.
It would be fair to say that you can only name an "lxd" cloud type to lxd,
but there should be a way to provide your configuration for lxd somewhere.

On Fri, Aug 10, 2018 at 4:45 PM, Simon Richardson <
<email address hidden>> wrote:

> Public bug reported:
>
> It's possible to name your clouds in LXD with add-cloud "localhost" or
> "lxd", which can cause all sorts of mayhem. We should possibly discuss a
> blacklist approach to prevent any surprises for the user when they're
> creating clouds for LXD.
>
> Names to be considered "harmful":
>
> - "localhost"
> - "lxd"
>
> ** Affects: juju
> Importance: Medium
> Status: Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1786470
>
> Title:
> LXD cloud naming conflict
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1786470/+subscriptions
>