Service should be restored now. Let us know in #juju on Freenode if you
have any issues, but all should be well.
On Mon, Jul 2, 2018 at 3:36 PM, Casey Marshall wrote:
> We're currently dealing with an outage this afternoon in JAAS. Users will
> be temporarily unable to add models
We're currently dealing with an outage this afternoon in JAAS. Users will
be temporarily unable to add models until it is resolved; however, existing
models are not impacted.
Will provide an update when status changes. Hopefully will not be too much
longer..
-Casey
--
Juju mailing list
Juju@list
sion of Juju I'm running is
> 2.2.6-xenial-amd64
>
>
> Spicule Ltd
>
> Tel: 01603 327762
>
>
>
> www.spicule.co.uk
>
> On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall <
> casey.marsh...@canonical.com> wrote:
>
>> On Tue, Nov 28, 2017 at 1
g, just exported from the gui, Ste
> can provide it if you need it.
>
Thanks for clarifying. One last question, what version of Juju was used on
the command line when trying to deploy the exported bundle?
>
> Tom
>
>
> On 28 Nov 2017 6:00 pm, "Casey Marshall"
&g
On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie
wrote:
> Thanks. I have tried running juju agree spiculecharms/pdi-terms/1 and it
> states terms already agreed?
>
> When trying to deploy in the GUI it returns the error message cannot
> create bundle: already exists. It appears that it creates th
On Tue, Nov 28, 2017 at 5:59 AM, John Meinel wrote:
> Do you know what terms you need to accept? You should be able to 'juju
> accept termname'.
> The other thing to check is if your local clock time is fairly accurate.
> I believe we filed a bug recently that the term server gives out temporary
age exceeds these expectations, we will post updates on our status &
progress.
Thank you,
Casey Marshall
Canonical - Cloud Online Services
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
With juju 2, you can also use --force-units to upgrade the charm even in an
error state:
juju upgrade-charm --path /path/to/mycharm --force-units mycharm
The unit agent will then usually retry the hook that's failing
automatically, but you can use `juju resolved` on the unit(s) without the
--no-r
On Fri, Jun 9, 2017 at 12:29 PM, Uros Jovanovic <
uros.jovano...@canonical.com> wrote:
> Quick instructions on how the new azure credentials flow works in Juju
> 2.2-RC2:
>
> # install az client using a snap
> $ sudo snap install azure-cli --classic --edge
>
I've pushed the snap to stable, so you
Hi Simon,
I'm glad you asked about this. The need for certain services to operate on
the controller for autoscaling and other purposes has come up before.
Juju's considering exposing different aspects of the controller as
applications -- for monitoring, log access and other aspects of operating
th
On Thu, Dec 1, 2016 at 6:53 AM, Marco Ceppi
wrote:
> On Thu, Dec 1, 2016 at 5:00 AM Adam Collard
> wrote:
>
>> On Thu, 1 Dec 2016 at 04:02 Nate Finch wrote:
>>
>> On IRC, someone was lamenting the fact that the Ubuntu charm takes longer
>> to deploy now, because it has been updated to exercise
On Mon, Oct 24, 2016 at 6:15 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> +1 for "which charms use this layer" queries. This has a number of uses:
>
> - for finding what the quality of a layer is (more use in recommended
> charms = better quality)
> - for the maintainer of a layer
On Mon, Oct 24, 2016 at 3:51 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Sun, Oct 16, 2016 at 12:07 AM Casey Marshall <
> casey.marsh...@canonical.com> wrote:
>
>> With a much appreciated recent contribution from James Beedy (bdx) our
>> Matter
With a much appreciated recent contribution from James Beedy (bdx) our
Mattermost charm cs:~cmars/mattermost[1] is working again!
This encouraged me to add some followup improvements to the charm to make
it even easier to deploy with secure defaults -- automatic registration
with Let's Encrypt.
I
I’m pleased to announce Juju Metrics, new in Juju 2.0!
Knowing an application's configuration isn’t enough to effectively operate
and manage it. Consider that a well-designed application will have as few
configurable parameters as possible. As an operator, you may find yourself
wanting to know mor
Awesome idea! Probably more of a wishlist thing at this point.. but can we
also add SSHFP records for all the units?
-Casey
On Sat, Sep 24, 2016 at 11:47 AM, Marco Ceppi
wrote:
> Hey everyone,
>
> I'm currently working on a charm for NS1, which is a DNS service
> accessible via API. There are q
Hi Tom,
Sorry to hear you're having trouble.. I think there might be something
interesting in the controller logs that could help us fix it.
If you can ssh into the controller machine, could you tar up the logs in
/var/log/juju and attach to a Launchpad bug (
https://bugs.launchpad.net/juju/+fileb
My main use case for killing controllers is development & testing. For
this, I have a script that force deletes all the juju-* LXC containers, and
then unregisters all controllers with cloud: lxd. It's *much* faster than
waiting for each juju controller to tear itself down. It's also nothing I'd
pr
I decided it'd be easier & safer to host squid-deb-proxy in a LXD container
rather than the host. My host doesn't route inbound to LXD from other
networks, and all the Juju machines can see it.
On Tue, Aug 16, 2016 at 12:30 AM, John Meinel
wrote:
> ...
>>
>
>
>> +### tuple ### allow any 8000 0.0
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 M
I need some help with understanding the best way to manage relation info
across an application's lifecycle with the reactive framework.
I'll start with the situation that brings me here:
I have a reactive charm that provides some fairly static relation info:
nagios checks over the nrpe-external-m
On Wed, Jun 15, 2016 at 11:52 AM, Jay Wren wrote:
> On Tue, Jun 14, 2016 at 5:50 PM, Charles Butler <
> charles.but...@canonical.com> wrote:
>
>> - There is currently no way to disable TLS wrapped endpoints on Etcd (we
>> want to keep our coordination data secure don't we?)
>>
>>
> For our use ca
On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer <
alexis.bruem...@canonical.com> wrote:
>
> Hi All,
>
> As recently highlighted in bug https://bugs.launchpad.net/bugs/1566589 the
> latest LXD will not work with Juju 2.0-beta3. This is a result of LXD
> moving to use a default bridge of lxdbr0 and
On Wed, Mar 16, 2016 at 7:52 PM, Marco Ceppi
wrote:
> Hello everyone!
>
> This is an email I've been meaning to write for a while, and have
> rewritten a few times now. With 2.0 on the horizon and the charm ecosystem
> rapidly growing, I couldn't keep the idea to myself any longer.
>
> # tl;dr:
>
Simon,
You raise some very interesting questions and good points.
I've also been developing charms with layers, run into some of these same
issues, and developed a pragmatic approach that has helped me manage it
pretty well so far. In a more mature layer/interface ecosystem, it might
not be the op
up my laptop this morning, opened a bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854
>
> thanks,
> -serge
>
> Quoting Casey Marshall (casey.marsh...@canonical.com):
> > On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber
> wrote:
> >
> > > Seemingly
On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber wrote:
> Seemingly the image name and key are the same, LXD and Juju are the same,
> so you've either done something magic or I'm confused with its now seeming
> happiness of the kernel debug mountpoint! :)
>
I ran into a similar issue today. xenial ho
On Wed, Oct 21, 2015 at 1:49 PM, Cory Johns
wrote:
> Matty,
>
> I do think that a bug should be opened for it, and I will do so. Is LP
> still the better place to open the bug vs GitHub?
>
Yes, please open the bug in Launchpad.
Thanks,
Casey
>
> On Wed, Oct 21, 2015 at 5:48 AM, Matthew Willi
On Fri, Oct 16, 2015 at 2:29 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> On Fri, Oct 16, 2015 at 2:06 PM, Casey Marshall
> wrote:
> > I just upgraded to 1.24.7 and tried bootstrapping, got this message:
> >
> > Starting new instance for initial stat
I just upgraded to 1.24.7 and tried bootstrapping, got this message:
Starting new instance for initial state server
WARNING failed to find 1.24.7 tools, will attempt to use 1.24.6
Is there a problem with the publish to 'proposed' simple-streams?
-Casey
On Thu, Oct 15, 2015 at 3:14 PM, John Geor
All,
I'd like to share a small set of juju plugins I've developed:
https://github.com/cmars/juju-nat
The juju nat-* commands automate the tedious process of port forwarding
and routing for services deployed into LXC containers.
I like to use it with the manual provider for my personal stuff, or
On 01/29/2014 05:26 PM, Sean Feole wrote:
> Hey Everyone,
>
> I've been looking at the following wiki page in attempt to use Canonistack
> with juju. Are these wiki instructions up-to-date ??
>
> https://wiki.canonical.com/InformationInfrastructure/IS/CanonicalOpenstack/CanonistackWithJujuCore
>
When I'm debugging a charm, I'll often deploy, debug, destroy & redeploy
that charm until I get it right. In my OpenStack environment, each time
I deploy a service, by default it provisions a new machine for the new
unit. However, when I destroy the service, the existing machines are
left running i
33 matches
Mail list logo
