Re: Unable to kill-controller

On 05/04/16 11:12, Andrew Wilkins wrote: > On Mon, Apr 4, 2016 at 8:32 PM Rick Harding > wrote: > >> On Sun, Apr 3, 2016 at 6:56 PM Andrew Wilkins < >> andrew.wilk...@canonical.com> wrote: >> >>> In a non-beta release we would make sure that the config changes

Re: Unable to kill-controller

On Mon, Apr 4, 2016 at 8:32 PM Rick Harding wrote: > On Sun, Apr 3, 2016 at 6:56 PM Andrew Wilkins < > andrew.wilk...@canonical.com> wrote: > >> In a non-beta release we would make sure that the config changes aren't >> backwards incompatible. >> > > I think this is

Re: Charm layers & Windows

On Mon, Apr 4, 2016 at 10:42 PM Marco Ceppi wrote: > There are two things that need to be done. The first, we need the reactive > framework to be ported to powershell - that way we can have charms written > in powershell and compiled as such. I know the cloud base

Re: Unable to kill-controller

Relevant bug: https://bugs.launchpad.net/juju-core/+bug/1553059 We should provide a way to clean up controllers without making the user manually edit juju's files. On Mon, Apr 4, 2016 at 7:05 AM, Nate Finch wrote: > This just happened to me, too. Kill-controller

Re: Action return value too long for commandline

Hi Stuart Thanks for this explanation. 16MB is definitely a step in the right direction. However, in the future I'll need to transfer even bigger files. Is there a possibility for using resources for this in the future? It would be great if an action could upload a file to the resources server

Re: Charm layers & Windows

At least... according to the core code, but it occurs to me I may well be mistaken about what's allowed by the charm authoring tools and/or charmstore. On Mon, Apr 4, 2016 at 10:16 AM Nate Finch wrote: > BTW, I don't believe this is true. I didn't work on series in

Re: Unable to kill-controller

This just happened to me, too. Kill-controller needs to work if at all possible. That's the whole point. And yes, users may not hit specific problems, but devs do, and that wastes our time trying to figure out how to manually clean up the garbage. On Mon, Apr 4, 2016 at 8:33 AM Rick Harding

Re: Charm layers & Windows

On 4 April 2016 at 14:17, Andrew Wilkins wrote: > Hi, > > I would like to write a charm that should be mostly identical on Windows and > Linux, so I think it would make sense to have common code in the form of a > layer. > > Is anyone working on getting "charm

Re: Charm layers & Windows

>From what I've read, there's no server-side story to Ubuntu on Windows. It's purely desktop, and in fact, only installs on desktop versions of Windows 10. That could help with tooling for charm authors, but obviously the charm code itself still needs to run on vanilla Windows. The main tricky

Re: Unable to kill-controller

On Sun, Apr 3, 2016 at 6:56 PM Andrew Wilkins wrote: > In a non-beta release we would make sure that the config changes aren't > backwards incompatible. > I think this is the key thing. I think that kill-controller is an exception to this rule. I think we should

Re: Action return value too long for commandline

Thanks, this is interesting to know. The fact that we've fixed it in relation set means we have a pattern to move forward with. The team's slammed on 2.0 work right now, but I've set this up to be something we try to address across the board after the fact. We'll make sure to look for other -set

Re: Charm layers & Windows

I know that Gabriel and some of the CloudBase folks seemed interested in layers and possibly some tooling with powershell. I'm not sure how far that went but I thought they were experimenting during the charmer's summit. That would help with a charm build on windows, but not for some common code

Re: Unable to run a charm on KVM container

I fixed a bug last week where KVM containers were using the wrong parent device: https://bugs.launchpad.net/juju-core/+bug/1563853 This would definitely have been a problem if you were using more than one NIC. On 3 April 2016 at 08:19, John Meinel wrote: > My initial

Charm layers & Windows

Hi, I would like to write a charm that should be mostly identical on Windows and Linux, so I think it would make sense to have common code in the form of a layer. Is anyone working on getting "charm build", layers, and friends to work with Windows workloads? If not, I may look into it myself.