On 21 August 2015 at 01:45, Cory Johns wrote:
> Even as a proxy charm, this could be improved (it could use actions to
> enable per-service configuration, for example), but it should give you the
> basic idea.
>
>
The main limitation is that this approach only supports proxying a single
unit se
I took a look at the plumgrid stack which after an architectural
refactoring is very close to being accepted. There are simple nitpick final
round revisions to the project meta that need to be cleaned up so we ensure
they have a good segway into the OIL labs and they should be good to go.
Unfortun
Hi everyone,
Juju office hours kind of snuck up on us today and we were busy with
our heads down. We could have just done it on the spot but we prefer
to give people a heads up so they can show up to participate, so we're
going to move this one to this Monday.
20:00 UTC. You can tune in at http:/
Hi guys
As soon as I added the group I was then told I needed to sort out my bzr
launchpad login, did that and it worked straight away, so probably is worth
pointing out in the docs.
Thanks for the help!
Regards,
Tom
On 20 August 2015 at 19:28, Nick Veitch wrote:
> Let us know if that was th
Sam, Ana, and Alberto,
We tend not to have good examples of a proxy charm because they are much
more limited than full charms and they also tend to be specific to
particular use-cases. Thus, they are often one-off charms that don't end
up in the store.
If you're referring to https://jujucharms.c
Let us know if that was the problem! I will take a pass through the docs
and see if there is anything we should add/clarify on that page
On 20 August 2015 at 18:58, Tom Barber wrote:
> Thanks Nick, Marco
>
> I've joined the team I'll give it a try.
>
> Tom
> On 20 Aug 2015 18:55, "Marco Ceppi"
Thanks Nick, Marco
I've joined the team I'll give it a try.
Tom
On 20 Aug 2015 18:55, "Marco Ceppi" wrote:
> This is a launchpad error, not a bazaar one. I believe you will need to
> first be a member of https://launchpad.net/~charm-contributors in order
> to create new "packages" in launchpad.
This is a launchpad error, not a bazaar one. I believe you will need to
first be a member of https://launchpad.net/~charm-contributors in order to
create new "packages" in launchpad.
Thanks,
Marco Ceppi
On Thu, Aug 20, 2015 at 1:41 PM Nick Veitch
wrote:
> Hi
>
>
>
>> I followed the instructions
Hi
> I followed the instructions on the juju charm page to submit my charm to
> my namespace but all I get is
>
> bzr: ERROR: Invalid url supplied to transport:
> "lp:~f-tom-n/charms/trusty/saikuanalytics/trunk": No such source package
> saikuanalytics.
>
are you running:
bzr push lp:~f
Hello again,
I'm a git user and bzr/launchpad is confusing the hell out of me.
I followed the instructions on the juju charm page to submit my charm to my
namespace but all I get is
bzr: ERROR: Invalid url supplied to transport:
"lp:~f-tom-n/charms/trusty/saikuanalytics/trunk": No such source pa
Hi guys,
Having taken Matt's advice I've blatantly ripped off OpenMRS's cham to get
Saiku into a generic tomcat.
https://github.com/OSBI/saiku/tree/development/charm/trusty/saikuanalytics
The files are still uploading to dropbox so don't try and run it for the
next couple of hours(my ADSL sucks)
I'd just like to chime in with a comment about the benefits and trade-offs
of each approach. I don't think either approach is inherently more or less
"Juju-ish". I think it just depends on your use-case.
Using a structured data value for the config has the benefit that the
current configuration
Hi Ana,
If you have multiple servers, you'll have multiple relations.
The administrator running the environment will have a knowledge of all the
relations, thus of the servers and names.
Your charm shall be able to match relation counterparts and config options
and log the potential errors witho
Back at ya, Matt. Thank you for your work on that as well!
Cheers,
Ryan
On Wed, Aug 19, 2015 at 5:31 PM, Matt Bruzek
wrote:
> The mysql charm was failing some of our automated tests. Ryan Beisner
> took some time to fix these issues. In addition to passing OSCI tests they
> pass the blockers
Thanks John!
Allow me to rephrase as I am not sure I am following. Are saying we could
have a declarative format in the configuration of the charm that would
apply to relations created like:
"datasources" : [
{ "name": "mysql",
"datasets": [ "ds1", "ds2", ... ],
},
{ "name": "mongodb",
15 matches
Mail list logo