Bumping this up. I've also upgraded to beta3 (from beta1). I still had the
beta1 packages in my cache, but downgrading (dpkg -i ) hangs. Are the
beta2 packages archived somewhere?
On Sun, Feb 21, 2016 at 9:42 AM Andreas Hasenack
wrote:
> On Sun, Feb 21, 2016 at 11:35 AM,
On Sun, Feb 21, 2016 at 2:06 PM Mark Shuttleworth wrote:
> On 21/02/16 03:57, Andrew Wilkins wrote:
> > The lxd/ 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
On Sun, Feb 21, 2016 at 11:35 AM, Rick Harding
wrote:
> Andreas, yes that's the known bug Ian mentioned due to an API change in
> the latest lxd beta3. We'll get that updated ASAP. It works with the lxd
> beta2.
>
>
Thanks
Is beta2 archived somewhere? All of lxd
Andreas, yes that's the known bug Ian mentioned due to an API change in
the latest lxd beta3. We'll get that updated ASAP. It works with the lxd
beta2.
On Sun, Feb 21, 2016, 9:29 AM Andreas Hasenack
wrote:
> On Sat, Feb 20, 2016 at 9:18 PM, Ian Booth
On Sat, Feb 20, 2016 at 9:18 PM, Ian Booth wrote:
> The lxd cloud works on Juju 2.0 beta1 out of the box.
>
> $ juju bootstrap mycontroller lxd
>
> There is no need to edit any clouds.yaml. It Just Works.
>
It does not work for me:
andreas@duo:~$ juju bootstrap
On 21/02/16 00:18, Ian Booth wrote:
> It seems the confusion comes from not seeing lxd in the output of juju
> list-clouds. list-clouds ostensibly shows available public clouds (aws, azure
> etc) and any private clouds (maas, openstack etc) added by the user. The lxd
> cloud is just built-in to
On 21/02/16 03:57, Andrew Wilkins wrote:
> The lxd/ 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
To specify a different LXD host:
$ juju bootstrap mycontroller lxd/
For now, just localhost (the default) has been fully tested and is guaranteed to
work with this beta1.
There's no need to edit any clouds.yaml file for the LXD cloud. It's meant to be
really easy to use!
On 21/02/16 09:21,
Won't the user be able to create different LXD clouds by specifying a
remote LXD host though?
On Sun, Feb 21, 2016, 12:19 AM Ian Booth wrote:
> The lxd cloud works on Juju 2.0 beta1 out of the box.
>
> $ juju bootstrap mycontroller lxd
>
> There is no need to edit any
The lxd cloud works on Juju 2.0 beta1 out of the box.
$ juju bootstrap mycontroller lxd
There is no need to edit any clouds.yaml. It Just Works.
It seems the confusion comes from not seeing lxd in the output of juju
list-clouds. list-clouds ostensibly shows available public clouds (aws, azure
I tested this on xenial and it's not there. I've filed a bug for it.
https://bugs.launchpad.net/juju-core/+bug/1547966
To get it going I first created a lxd.yaml file with the config for the lxd
'cloud'.
clouds:
lxd:
type: lxd
Then I added that with
juju add-cloud lxd lxd.yaml
Awesome, a nice weekend present!
I updated and LXD is not listed when I `juju list-clouds`. Rick and I
were guessing that maybe because the machine I am testing on is on
trusty that we exclude that cloud on purpose. If I was on a xenial
machine I would assume lxd would be available?
What's an
# juju-core 2.0-beta1
A new development release of Juju, juju-core 2.0-beta1, is now available.
This release replaces version 2.0-alpha2.
## Getting Juju
juju-core 2.0-beta1 is available for Xenial and backported to earlier
series in the following PPA:
13 matches
Mail list logo