Hi,
We're making a handful of changes around model- and cloud-related APIs.
Some of these will be broken in beta16, and some will be deprecated then
and broken directly after.
The first change is to ModelManager.DestroyModel. This method is now
deprecated, and replaced with the pluralised
On Mon, Aug 15, 2016 at 2:13 PM Andrew Wilkins
wrote:
> Hi,
>
> We're making a handful of changes around model- and cloud-related APIs.
> Some of these will be broken in beta16, and some will be deprecated then
> and broken directly after.
>
> The first change is to
So if you pull master you'll no longer need to use upload-tools.
Juju will Do the Right Thing*, when you type:
$ juju bootstrap mycontroller aws|lxd|whatever
or
$ juju upgrade-juju
*so long as your $GOPATH/bin is in your path (as a developer).
1. As a user, you bootstrap a controller using a
Hi Menno,
Thanks for putting this together, great tips. I recently ran into an issue
which others could see as well.
One may need to adjust the following for large bundle deployments on LXD.
A bundle deployment fails with errors about "Too many files open." This
will increase number of max
There is a PR that's soon to land that will change the Juju
API so that controller-level RPC calls can no longer
be executed on a model-specific connection.
https://github.com/juju/juju/pull/5986
This is a breaking API change.
The affected facades are the following:
AllModelWatcher
Ian, can you describe how Juju decides if it's running for a developer or
an end user? I'm worried this could trip people up who are both end users
and happen to have a juju development environment.
On Mon, Aug 15, 2016 at 11:29 AM Mark Shuttleworth wrote:
> On 15/08/16 08:27,
On 15/08/16 08:27, Ian Booth wrote:
> So if you pull master you'll no longer need to use upload-tools.
> Juju will Do the Right Thing*, when you type:
Thanks Ian, this is a lovely simplification.
Mark
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
OK, I think I've got it now.
On 16/08/16 15:19, Ian Booth wrote:
On 16/08/16 12:58, Tim Penhey wrote:
On 16/08/16 10:50, Ian Booth wrote:
On 16/08/16 03:09, Nate Finch wrote:
Ian, can you describe how Juju decides if it's running for a developer or
an end user? I'm worried this could
Menno,
This is great and thanks for sharing!
In case anyone else runs into this.. charms that install from PPAs will
fail with this squid-deb-proxy setup. You'll need to allow archive mirrors
for this to work. See
https://1337.tips/ubuntu-cache-packages-using-squid-deb-proxy/ for an
example.
On
Thanks Rafael. Would you mind adding this to the wiki page?
On 16 August 2016 at 02:31, Rafael Gonzalez
wrote:
> Hi Menno,
>
> Thanks for putting this together, great tips. I recently ran into an
> issue which others could see as well.
>
> One may need to adjust
Good catch Casey. I've just updated the config in the gist to allow access
to any mirror or PPA (in a cleaner way than in the blog article IMO). It
seems to work well (apt-get download is nice way to test).
On 16 August 2016 at 09:27, Casey Marshall
wrote:
>
Yes thanks for doing the work to share this menn0. It is much appreciated.
I also needed to change the following in squid-deb-proxy (even though I
added a bunch of domains to
/etc/squid-deb-proxy/mirror-dstdomain.acl.d/10-default):
--- a/squid-deb-proxy/squid-deb-proxy.conf
+++
On 16/08/16 03:09, Nate Finch wrote:
> Ian, can you describe how Juju decides if it's running for a developer or
> an end user? I'm worried this could trip people up who are both end users
> and happen to have a juju development environment.
>
It's not so much Juju deciding - the use cases
On 16/08/16 12:58, Tim Penhey wrote:
>
>
> On 16/08/16 10:50, Ian Booth wrote:
>>
>> On 16/08/16 03:09, Nate Finch wrote:
>>> Ian, can you describe how Juju decides if it's running for a developer or
>>> an end user? I'm worried this could trip people up who are both end users
>>> and happen
>
> ...
>
> +### tuple ### allow any 8000 0.0.0.0/0 any 0.0.0.0/0 in
> +-A ufw-user-input -p tcp --dport 8000 -j ACCEPT
> +-A ufw-user-input -p udp --dport 8000 -j ACCEPT
> +
>
>
If I'm reading this one correctly, it also means that anyone from *any* IP
address (not restricted to your local
15 matches
Mail list logo