Resending this to the list, rather than just Jorge, sorry.
On 1 April 2014 20:07, Jorge O. Castro wrote:
> Hi everyone,
>
> Matt Bruzek and I have been doing some charm testing on a machine that
> does not have general access to the internet. So charms that pull from
> PPAs, github, etc. do not w
On 3 September 2014 13:12, Michael Nelson wrote:
> On Wed, Sep 3, 2014 at 9:57 PM, Darryl Weaver
> wrote:
>> Hi All,
>>
>> I am still a little confused as to when Juju decides to run hooks.
>> Obviously hooks run when something changes.
>> However, I see juju rujnning config-changed hooks at time
On 3 September 2014 13:42, Darryl Weaver wrote:
> Thanks the IRC logs are pretty helpful.
> We are seeing the same issue here at Sky,
> config-changed hook runs "At random times".
> This is when there are no user changes to the Juju config and no reboots
> happening.
> It is possible the juju agen
Arg, resending reply to list
On 3 September 2014 14:27, José Antonio Rey wrote:
> Even if the config-changed hook was run when it was not supposed to, it
> shouldn't have caused any changed if values were not moved to anything
> different. If it did, then I believe we're having an idempotency pro
On 8 September 2014 15:40, Matt Bruzek wrote:
> José
>
> I just had a conversation about that with the Ecosystems team. You are
> correct, the revision file in the charm directory is no longer used and we
> can delete those files on future updates.
So this is interesting, as we are looking to st
Hi Sebastian
On 5 September 2014 18:54, Sebastian wrote:
> - Subordinated charms, when and how to use it. Conflicts with Ansible
> Charms.
Can you give more details on "Conflicts with Ansible Charms"?
We use the ansible support in charm-helpers a lot, for both principle
charms and subordinates,
On 8 September 2014 16:10, Kapil Thangavelu
wrote:
>
> you need to keep in mind the revision file will never match a local charm
> version in the state server (it will at min be at least one higher than
> that). This goes back to removing the need for users to manage the revision
> file contents w
On 8 Sep 2014 16:51, "Stuart Bishop" wrote:
>
> I think you are better off using a service configuration item to hold
> the version for now, at least until the dust settles. Juju is good
> about incrementing the number in the revision file when it needs to,
> which is probably not when you want it
On 9 September 2014 18:45, Sebastian wrote:
> Hey Simon!
>
> For example, imagine you have an Ansible charm which inside are some php
> settings applied like php memory limit, and then you relate a subordinated
> charm to it, that creates a new php.ini with custom configurations that the
> project
This is what I have:
Host 10.0.3.*
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
ForwardAgent yes
LogLevel ERROR
ControlMaster auto
ControlPath /tmp/ssh_mux_%h_%p_%r
ControlPersist 8h
LogLevel ERROR is nice, means you don't get any key warnings.
HTH
--
Simo
On 3 October 2014 13:21, Simon Davy wrote:
> This is what I have:
>
> Host 10.0.3.*
> StrictHostKeyChecking no
> UserKnownHostsFile /dev/null
> ForwardAgent yes
> LogLevel ERROR
> ControlMaster auto
> ControlPath /tmp/ssh_mux_%h_%p_%r
> C
On 17 October 2014 10:13, saurabh wrote:
> Hi All,
>
> I need to communicate password from one charm instance to another instance
> in order to authenticate services.
> Please suggest me a way to do that.
Hi Saurabh
I assume by "one charm instance to another" you mean two units in the
same servi
what charmhelper is doing right now.
>
>
> Yes! I think making reusable roles for common tasks in juju charms is
> really worthwhile [1]. We do have a bunch of public shareable roles
> that Simon Davy and I (mainly) are reusing and improving for some
> internal services [2]. Please take a
On 2 December 2014 at 17:04, sheila miguez wrote:
> Hi all,
>
>
> Pip wishes
>
> * pip_extra_args support so that I can use --no-index
> --find-links=/path/to/wheels (this is in my fork)
> * remove --upgrade --use-mirrors, leave it up to the user (in my fork)
First class support for wheels in the
On 5 December 2014 at 01:54, Sebastian wrote:
> Hey guys!
Hi Sebastian
I've been looking at using a juju charm as the default dev env for one
of our services, login.ubuntu.com.
It's mostly working, but we haven't switched to it yet, as it needs
some more polish but we'd like to at some point.
On 22 January 2015 at 15:13, David Britton wrote:
>
> lint:
> - make lint
>
Could we also make[1] the charm linter lint the makefile for the
presence of targets agreed in the outcome of this thread?
[1] Pun fully intended :)
--
Simon
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settin
On 22 January 2015 at 16:29, David Britton wrote:
> On Thu, Jan 22, 2015 at 04:17:26PM +0000, Simon Davy wrote:
>> On 22 January 2015 at 15:13, David Britton
>> wrote:
>> >
>> > lint:
>> > - make lint
>> >
>>
>> Could we also ma
On 4 March 2015 at 13:45, Jorge O. Castro wrote:
> Hi everyone,
>
> Sometimes people deploy things like a complex bundle on a cloud and it
> doesn't work. Having to wrangle the person to find out which units
> broke, juju sshing in and manually digging around logs and refiring
> off hooks, etc. is
On 2 March 2015 at 17:46, Marco Ceppi wrote:
> # Charm Authors
>
> - Avoid symlinks in charm
/me blinks
I assume you don't mean symlinks in hooks/ dir?
Anything documenting why this is a bad idea?
--
Simon
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https:
On 8 May 2015 at 14:28, Gustavo Niemeyer wrote:
>
> - The requirement of running an action across all units but without
> executing in all of them at once also sounds very common. In fact, it's so
> common that it should probably be the default when somebody dispatches an
> action to all units of
On 16 August 2015 at 19:41, Mark Shuttleworth wrote:
> On 14/08/15 04:56, Stuart Bishop wrote:
>> I've discussed similar things with regard to the PostgreSQL charm and
>> autotuning, with the decision being that charm defaults should be set
>> so things 'just work' in a development environment.
>
On 9 November 2015 at 18:19, Rick Harding wrote:
> Thanks Katherine. That's looking great. One request, next demo I'd be
> curious to see how easy it is to run multiple lxd environments locally. I
> know it's been possible with lxc before with a bunch of config.
Just an FYI, I have a tool to mana
On 13 November 2015 at 13:50, Mark Shuttleworth wrote:
>
> Thanks Sunitha. Matty, deeper question is - was this an intended change
> in behaviour, and what's the rationale?
One possibility is that the juju environment is no longer being torn
down between tests? That would result in this behaviour
On 13 November 2015 at 15:02, Matthew Williams
wrote:
> Hi Mark, Sunitha,
>
> My apologies, I should have included the explanation in the original email.
>
> This was a change to address a long standing bug:
> https://bugs.launchpad.net/juju-core/+bug/1174610
Ah - I must have been remembering the
On 10 November 2015 at 20:46, Mark Shuttleworth wrote:
> On 10/11/15 11:06, Simon Davy wrote:
>> We've been using lxd with the manual provider, really been impressed
>> with what lxd brings to the table.
>
> Yes, it's a really dramatic leap forward in distributed s
On 16 November 2015 at 17:07, Rick Harding wrote:
> On Mon, 16 Nov 2015, Simon Davy wrote:
>
>> Some uses cases OTTOMH:
>>
>> - mounting specific code branches into the lxd for development
>
> This is a feature we're looking at Juju adding to support sharing
On 18 November 2015 at 17:15, Katherine Cox-Buday
wrote:
> Simon, I've gone ahead and added you as a subscriber to the blueprint for
> this feature. That was as things develop you can stay in the loop.
>
> Would you be willing to give feedback on how this feature is shaping up when
> we begin deve
On 25 November 2015 at 16:02, Marco Ceppi wrote:
> ## Wheel House for layer dependencies
>
> Going forward we recommend all dependencies for layers and charms be
> packaged in a wheelhouse.txt file. This perform the installation of pypi
> packages on the unit instead of first on the local machine
On Thursday, 26 November 2015, Marco Ceppi
wrote:
> On Wed, Nov 25, 2015 at 4:08 PM Simon Davy wrote:
>>
>> On 25 November 2015 at 16:02, Marco Ceppi
wrote:
>> > ## Wheel House for layer dependencies
>> >
>> > Going forward we recommend all dependencies
On Friday, 27 November 2015, Marco Ceppi wrote:
> On Thu, Nov 26, 2015 at 3:05 AM Simon Davy wrote:
>>
>> On Thursday, 26 November 2015, Marco Ceppi
wrote:
>> > On Wed, Nov 25, 2015 at 4:08 PM Simon Davy
wrote:
>> >>
>> >> On 25 November 201
Hi all
My team (Online Services at Canonical) maintains >20 private charms
for our services, plus a few charmstore charms.
Most of these charms are written with charmhelpers ansible support, or
with the Services framework. We would like to move towards
consolidating these approaches (as both have
On Mon, Mar 14, 2016 at 1:05 PM, John Meinel wrote:
> ...
>
>>
>>
>> > 3) Downloading from the internet. This issue has been common in
>> > charmstore charms, and is discouraged, AIUI. But the same issue
>> > applies for layers, and possibly with more effect, due to a layer's
>> > composibility.
On Mon, Mar 14, 2016 at 2:28 PM, Cory Johns wrote:
> On Tue, Mar 8, 2016 at 9:19 AM, Simon Davy wrote:
>>
>> 1) Is there a roadmap for reactive? A target for a stable 1.0 release,
>> or similar? We'd ideally like a stable base to build from before
>> committin
Lots of interesting ideas here.
Some other ideas (apologies if these have already been proposed, but I
don't *think* they have)
a) A small one - please can we have 'juju get '? See
https://bugs.launchpad.net/juju-core/+bug/1423548
Maybe this is already in the config schema work, but it would *r
On Mon, May 16, 2016 at 2:49 PM, Tim Van Steenburgh
wrote:
> Right, but NRPE can be related to any charm too. My point was just that the
> charm doesn't need to explicitly support monitoring.
It totally does, IMO.
process count, disk, mem usage are all important, and should be
available out of t
On Sun, Sep 25, 2016 at 2:25 AM, Casey Marshall <
casey.marsh...@canonical.com> wrote:
> Awesome idea! Probably more of a wishlist thing at this point.. but can we
> also add SSHFP records for all the units?
>
Great idea!
> -Casey
>
> On Sat, Sep 24, 2016 at 11:47 AM, Marco Ceppi
> wrote:
>
On Thu, Feb 23, 2017 at 2:48 AM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> A new release of Juju, 2.1.0, and Conjure-up, are here!
>
>
> ## What's new in 2.1.0
>
> - Model migration
> - Interactive `add-cloud`
> - Networking changes
> - Conjure-up
> - LXD credential changes
> - Chang
On Fri, Feb 24, 2017 at 11:14 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Fri, Feb 24, 2017 at 6:51 PM Mark Shuttleworth wrote:
>
>> On 24/02/17 11:30, Andrew Wilkins wrote:
>>
>> On Fri, Feb 24, 2017 at 6:15 PM Adam Collard
>> wrote:
>>
>> On Fri, 24 Feb 2017 at 10:07 Adam Is
38 matches
Mail list logo