On 21/02/16 03:57, Andrew Wilkins wrote: > The lxd/<host> format has not been implemented yet. That will come later, > along with support for remote lxd, which AFAIK does not exist in the > provider.
I'm not sure it will be appropriate to do that way now that we have made the assumption of a single credential working in every region of a cloud. The foo/bar syntax iirc was for cloud/region and upon reflection I don't think we can consider all the different LXD hosts as different regions of a common cloud because they will have different identity spaces. Subsequent to the design work on bootstrap, we made the simplifying decision to treat all regions of a cloud as having the same credential. That works for all the big public clouds but it would break for a world where LXD is a single cloud of many regions. Instead, I think we'll need to special-case your OWN lxd as a cloud that you have immediate access to, and allow people to define remote hosts as explicit lxd clouds. They could, in theory, have a LXD cloud with many regions (each host being a region :)) as long as they all can share a credential, which I think is straightforward and actually quite exciting as a way to enable teams to simulate multi-region deployments. Damn, this stuff is exciting :) Mark -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
