We just validated across the board some good usability updates for
Kubernetes and its fellow bundles. Below are the highlights from the
milestones we closed out.
Observable Kubernetes Release Notes - Rev4
juju deploy observable-kubernetes
-
Revs to Kubernetes to 8 which fixes master mes
Hello everyone,
The folks who brought you the wonderful event in Ghent are at it again,
this time with a one day config management camp and then Berlin DevOpsDays,
November 15-17.
http://cfgmgmtcamp.eu/berlin-2016/
https://www.devopsdays.org/events/2016-berlin/welcome/
CFPs for both events are n
Exactly.
On Friday, September 2, 2016, Casey Marshall
wrote:
> 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
> waitin
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
This is one of the reasons we always make you type out the controller name
for destroy controller. Because
juju destroy-controller production-website
should ring a bell. Simply adding a long flag doesn't really help you
remember if you're killing something important or not, because you always
h
Oh my god, how did I miss this!
On Thu, Sep 1, 2016, 7:22 PM Andrew Wilkins
wrote:
> On Fri, Sep 2, 2016 at 3:26 AM Marco Ceppi
> wrote:
>
>> On Thu, Sep 1, 2016 at 3:10 PM Nicholas Skaggs <
>> nicholas.ska...@canonical.com> wrote:
>>
>>> A new development release of Juju, 2.0-beta17, is here!
It seems to me that this kind of thing is exactly what "blocks" are
designed for. An explicit unblock command seems better to me than either an
explicit flag or an extra prompt, both of which are vulnerable to typing
without thinking. Particularly if "throwaway" controllers created for
testing purp
Hi,
I am able to deploy the charms now.
Please ignore the previous mail.
Thanks & Regards,
Anita.
From: Anita Nayak1/India/IBM@IBMIN
To: juju@lists.ubuntu.com
Date: 09/02/2016 12:52 PM
Subject:Getting Error while deploying charm from charmstore in terms
Sent by:juju-bo
Hi,
The affected service has been restarted and you should be able to deploy that
charm now..
Best regards,
Ales Stimec
> On 02 Sep 2016, at 09:21, Anita Nayak1 wrote:
>
> Hi,
>
> While deploying charms from charm store, I am getting following error.
>
> root@c277-pkvm-vm48:~# juju dep
Hi
Thank you for bringing this issue to our attention. We are investigating the
issue and will bring the affected service back online as soon as possible.
We apologise for the inconvenience and will send you an update once our
services are restored.
Best regards,
Ales Stimec
> On 02 Sep 2
Hi,
While deploying charms from charm store, I am getting following error.
root@c277-pkvm-vm48:~# juju deploy cs:~ibmcharmers/trusty/ibm-im
ERROR storing charm for URL "cs:~ibmcharmers/ibm-im-7": cannot get
discharge from "https://api.jujucharms.com/terms": third party refused
discharge: cannot
11 matches
Mail list logo