Hi All,
I came across this thread when troubleshooting a similar problem, and
wanted to drop in the solution we came up with for posterity:
1) If you're dealing with an API, and the API comes back with an "incorrect
padding" error while parsing an SSL Cert, it usually means that the
formatting
Hi All,
I came across this thread when troubleshooting a similar problem, and
wanted to drop in the solution we came up with for posterity:
1) If you're dealing with an API, and the API comes back with an "incorrect
padding" error while parsing an SSL Cert, it usually means that the
formatting
ed). But that one is 2.3
> specific and I expect it to be fixed by early next week.
>
> John
> =:->
>
> On Thu, Oct 12, 2017 at 11:59 AM, Pete Vander Giessen <
> pete.vandergies...@canonical.com> wrote:
>
>> Hi All,
>>
>> > I think the inab
Hi Tilman,
People typically run juju tests with bundletester right now (despite its
name, it can be used to run a test on a single charm -- you'll need to
build the charm first if it is a layered charm). There's a section in the
docs about bundletester here:
I am also +1 to the effort (thank you, Merlijn!)
My first instinct would be to keep mycharm/builds as the default output
dir, as that matches the behavior of other tools (like Python's dist
tools). I see the arguments against it, though; it's probably better to
either do the "right" thing and
+1 from me :-)
On Wed, Apr 26, 2017 at 9:43 AM Charles Butler
wrote:
> I for one, cast my +1 vote
>
> It's been great working with tinwood regarding charms, layers, and
> reactive 2.0. His reviews have been on point and his helpful hand with the
> community has
Hiya Tom,
> Anyway, when we were in Gent Pete gave a cool demo of the Matrix testing
solution which is idea for the stuff we're working on, whats the status of
that? Are we likely to see a release any time soon?
Since Ghent, juju-matrix has acquired conjure-up support, been packaged in
a snap
Yesterday, Cory, Kevin and I took a trip through the review queue. Here's
what we did:
April 13, 2017: Cory, Kevin, Pete
-
Ibm-was-nd-dm
-
https://review.jujucharms.com/reviews/68?revision=153
-
Charm code review looks good, with a minor exception:
-
Hi All,
Konstantinos, Kevin, Cory and I took a trip through the review queue
yesterday. Here's what we did:
-
Ibm-was-nd
-
https://review.jujucharms.com/reviews/40?revision=277
-
I was able to deploy this successfully, but I’m not sure if that was
a good
).
~ PeteVG
On Thu, Feb 23, 2017 at 10:13 AM Pete Vander Giessen <
pete.vandergies...@canonical.com> wrote:
> On Thu, Feb 23, 2017 at 2:31 AM John Meinel <j...@arbash-meinel.com>
> wrote:
>
> AFAICT we fixed this in Juju 1.15, but there are 2 places you can pass
&g
to inspect the RPC calls you can also do so by
> checking out the JS API in the GUI and/or inspecting the WS in the GUI and
> performing the various actions to see the live interactions with Juju.
>
> [0] https://github.com/juju/juju-gui/pull/2527/files
>
> Hope this helps!
>
Hi All,
I'm currently working on getting python-libjuju to successfully deploy the
landscape-dense-maas bundle. It fails, as outlined in
https://bugs.launchpad.net/juju/+bug/1651260.
(python-libjuju is a Python client that talks to Juju's websocket API; I'm
currently using it inside the matrix
On Thu, Feb 23, 2017 at 2:31 AM John Meinel wrote:
> AFAICT we fixed this in Juju 1.15, but there are 2 places you can pass
> config. The old field uses the compatibility of "" means nil, the new field
> handles nil vs "" correctly. The Juju CLI should work correctly, it
> +1 for Pete :)
>
> Welcome aboard my man!
>
Awesome. Thank you, everyone. I will try to use my powers for good :-)
~ PeteVG
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
>
> I'll have a draft ready by the Charmer Summit that I will send to the
> list here and invite you and any others interested in charm/bundle
> testing. Perhaps if folks are able to attend the summit in person we
> can discuss further face-to-face.
>
Count me in for the discussion. I added the
Hi All,
The Big Data team (Konstantinos, Kevin, Cory and Pete) took a trip through
the review queue today, with a focus on wrapping things up in the old
queue, and preparing to move things to the new queue. Here's what we did:
-
IBM WAS Base
-
Hi All,
I took a trip through the review queue is week. Here's what I did:
Oct 27, 2016: Pete
-
MySQL
-
https://code.launchpad.net/~jillrouleau/charms/trusty/mysql/raise-max-conns-lp1382386/+merge/303638
-
I believe that the codebase for this charm has moved.
hnique if it came up in a code
review for a specific charm, though :-)
~ PeteVG
On Thu, Sep 1, 2016 at 4:48 AM Stuart Bishop <stuart.bis...@canonical.com>
wrote:
> On 30 August 2016 at 23:02, Pete Vander Giessen <
> pete.vandergies...@canonical.com> wrote:
>
> The probl
Hi All,
Some of you may recall, during a hangout a month or so ago, that I spoke
enthusiastically about a testing harness for Python-based layered charms
that we were working on in the Big Data team.
Unfortunately, that project ran into some technical blockers (details below
my sig, for the
Hi All,
This week, Kevin, Kostas, Cory and I reviewed the following:
-
ibm-http
-
https://bugs.launchpad.net/charms/+bug/1612535
-
-
gluster
-
https://bugs.launchpad.net/charms/+bug/1469213
-
Promulgated!
-
Docker
-
Hi Rajith,
What cloud are you installing to? Do the machines you installing on have
full network access? The version of mariadb in the store fetches mariadb
packages from a ppa provided by mariadb project. If you can't access that
ppa from the machine you're installing on, then things will break.
eteVG
On Sat, Jul 2, 2016 at 8:27 AM Stuart Bishop <stuart.bis...@canonical.com>
wrote:
> On 2 July 2016 at 03:06, Pete Vander Giessen
> <pete.vandergies...@canonical.com> wrote:
> > I wrote:
> >> I think that I figured this one out. charmhelpers does have PyYAML an
mmm ...
~ PeteVG
On Fri, Jul 1, 2016 at 2:29 PM Pete Vander Giessen <
pete.vandergies...@canonical.com> wrote:
> Hi All,
>
> I think that I figured this one out. charmhelpers does have PyYAML and six
> as dependencies, but the mariadb charm was deploying its own, probably
Hi All,
I think that I figured this one out. charmhelpers does have PyYAML and six
as dependencies, but the mariadb charm was deploying its own, probably out
of date version of charmhelpers. Telling it to install charmhelpers through
the juju tools, rather than stuff them into its own source tree
are the script -- I'd appreciate knowing
what else might be missing :-)
Thank you,
~ PeteVG
On Fri, Jul 1, 2016 at 11:23 AM Brad Crittenden <b...@canonical.com> wrote:
>
> > On Jul 1, 2016, at 11:15 , Pete Vander Giessen <
> pete.vandergies...@canonical.com> wrote:
&g
:31, Pete Vander Giessen <pet...@gmail.com> wrote:
> > Hello All,
> >
> > I'm currently working on writing a layered charm, and I had a question
> about
> > unit (or unit-ish) testing. Is it practical to write unit test for, say,
> > helpers for a reactive
te:
> I haven't validated this but you can try to remove the machine forcibly
>
> Juju remove-machine ## --force
>
> That should force removal of the container from the controller and let you
> destroy-service to remove it from the model.
>
>
>
> > On Apr 8, 2016,
Hi All,
Let's say that someone (okay, me) is experimenting with juju2 (develop)
locally, and I've rudely destroyed an lxc container that had a juju charm
deployed to it (lxc stop && lxc delete ).
Is there a way to convince juju that the charm is no longer deployed? juju
destroy-service and juju
Hi All,
Thank you very much for posting this thread. I've been following the
"getting started" developer's guide at
https://jujucharms.com/docs/devel/getting-started, and this info got me
unstuck.
I figured that I'd mention that, when I ran dpkg-reconfigure, I had to
create an ipv4 subnet,
29 matches
Mail list logo