some cases you can work around Juju like adding storage to
> the root disk by upgrading the instance through the cloud tooling.
>
> On Fri, Jun 8, 2018 at 7:58 AM Daniel Bidwell
> wrote:
> > I have a vmware server that I am using as the target for deploying
> > vms
>
updates.
--
Daniel Bidwell
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
is
not available at this time, could it be considered for the future?
--
Daniel Bidwell
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
github.com/juju/juju/api/apiclient.go:924:
I am a little baffled at what the problem might be. This controller has no vm
associated with it.
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
involved with?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
> On 05/02/18 12:38, Daniel Bidwell wrote:
> >
> > Is there anyway to make the vsphere controller to deploy vms with
> > hardware vm version 13 instead of version 10?
> >
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Is there anyway to make the vsphere controller to deploy vms with
hardware vm version 13 instead of version 10?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
at either (after hours
> > or
> > days).
> >
> > What is the secret sauce for making these thing work? For some
> > reason,
> > whenever I have trouble with my juju environment, I have to destory
> > it
> > and set up the controllers from scrap. I guess I jus
and deploy them though.
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
of testing and
developemnt is hard on vms/containers, but throwing away the vm and
reinstalling ubuntu is probably not the desired behaviour.
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/
)...
Waiting on model to be removed, 4 machine(s)...
Waiting on model to be removed, 4 machine(s)...
How do I kill this sucker so I can move on?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/m
ead of lxd containers.
What do I need to do differently to get juju to use the lxc launch
containers?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
What do I have to put in my .juju/environment.yaml to get juju-1.25.6-
xenial-amd64 to use lxc containers?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
failed? I don't see anything helpful on the maas
server in /var/log/maas.
From watching the console as it runs through everything it looks ok,
what I can see as it flies by. Then it powers itself down.
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
ontrollers returns:
CONCONTROLLER MODELUSER CLOUD/REGION
local.wp* default admin@local
Is there a way for me to "get it back" or do I just need to blow it
away and start again?
Should I be dropping back to juju 1.25.x for this?
--
Daniel Bidwell <drbidw...@gmail.com&
t; See also some notes I wrote:
> https://github.com/reedobrien/juju-notes/blob/master/writing-a-ci-tes
> t.md#install-lxd
>
> Cheers,
> Reed
>
> On Wed, May 11, 2016 at 1:35 PM, Daniel Bidwell <drbidw...@gmail.com>
> wrote:
> > I just upgraded a machine to 16.
I just upgraded a machine to 16.04 and tried to do an "lxd init" and
received an err of "LXD init cannot be used at this time". What causes
this? What do I have to clear out to make it work correctly?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
won't work. LXD bindings require a
> golang version that's too new for Trusty.
>
> On Sun, Feb 14, 2016 at 6:14 PM Daniel Bidwell <drbidw...@gmail.com>
> wrote:
> > I am trying to bootstrap lxd.
> >
> > I started with 'juju init' and then 'juju -v --de
n tells me that lxd is already
deployed. I can 'ssh ubuntu@10.0.3.x' and get into the container just
fine, but not 'juju ssh 0'.
What am I missing?
--
Daniel Bidwell <drbidw...@gmail.com>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://li
19 matches
Mail list logo