Hi all,
I'm trying to deploy a Juju bundle and set of charms hosted on Github rather
than Launchpad, but I'm running into some problems. Although juju-deployer does
appear to support this, I haven't found many examples, so I'm not certain I'm
doing the right thing - if anyone has this working,
There's a few things going on. The charm key in the bundle should just be
the charm name. The git support has a bug (there's a pending merge proposal
for this) re parent dir/checkout dir which is the cause of those
tracebacks. The @ syntax works for revision and tags but not branches.
Given its com
t;"clearwater-sprout":
> charm: "clearwater-sprout"
> branch:
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";
> charms_subdirectory: "charms/precise/clearwater-sprout"
Thanks,
Rob
Fr
ry would get checked out, and set as the JUJU_REPOSITORY
for the rest of the services, ie. propagate for all local charms
automatically, but they could override as needed. patches welcome.
cheers,
Kapil
> Thanks,
> Rob
>
>
> From: Kapil Thangavelu [mailto:kap...@gmail.c
seem OK to you, or do you still prefer the single charm_repository
option?
Thanks,
Rob
From: Kapil Thangavelu [mailto:kap...@gmail.com]
Sent: 14 April 2015 13:26
To: Robert Day
Cc: juju@lists.ubuntu.com
Subject: Re: Deploying Juju charms from Github
On Tue, Apr 14, 2015 at 6:09 AM, Robert Day
ma
On 15/04/15 11:51, Robert Day wrote:
> I agree that not having juju-deployer handle the Git side of things, and just
> working locally from a Git checkout, would be simpler – but I don’t think
> that sort of bundle would work in the Juju GUI, because the extra steps
> needed mean that you can’t
>> From: Mark Shuttleworth [mailto:m...@ubuntu.com]
>> Sent: 16 April 2015 07:41
>> There's a current limitation with bundles in the GUI, because they are
>> actually deployed server-side, which makes the drag-and-drop interaction
>> awkward. However, I just saw a lighting talk demo of client-side
