juju devel 2.0-beta1 is available for testing

[Andrew Wilkins]

On Sun, Feb 21, 2016 at 2:06 PM Mark Shuttleworth <mark at ubuntu.com> wrote:

> 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.
>

That sounds useful to me. We could consider the remotes registered with
your local lxd as regions. There's one client certificate for the local
lxd, which is uploaded to each registered remote, so you could then:
    * lxc remote add foobar https://foo.bar:8443 --accept-certificate
--password=..."
    * juju bootstrap lxc/foobar

It does mean that the name and credentials aren't really portable, though.
Also, I think we would still need to enable per-region credentials so we
have somewhere to stick the server certificates.

Damn, this stuff is exciting :)
>
> Mark
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160222/07099f29/attachment.html>