Comment 1 for bug 1060147

juju normally does use one provider resources based on env name, the
security group naming (which should be local to the tenant) which is one
per env, and one per machine typically.

looking through the source of the openstack provider, it also sets the
instance name (not id)

         name="juju %s instance %s" %
                (self._provider.environment_name, machine_id,),

effectively though this could be a random string, juju doesn't care about
it per se, its just a reference for the user when looking through other
provider tools. the reverse dns on instance name is bound to conflict
though with normal usage of a cloud provider, so this sounds like a bug in
the canoistack setup. If you'd like we can mitigate via some uuid/rand
string insertion here, but this should get fixed in canonistack as well, as
this name clash is not specific to anything juju is doing, its an inherent
issue.

-k

On Tue, Oct 2, 2012 at 10:59 AM, Haw Loeung <email address hidden>wrote:

> ** Tags added: canonical-webops-juju
>
> --
> You received this bug notification because you are subscribed to juju.
> https://bugs.launchpad.net/bugs/1060147
>
> Title:
> Multiple users with same environment names causing clash
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1060147/+subscriptions
>