Re: Unit name issue with SFTP command.

You can get the full unit name with: unit_name = d.sentry['ibm-db2'][0].info['unit_name'] d.action_do(unit_name, ...) We should perhaps consider moving action_do to the UnitSentry so that it could instead be called as: d.sentry['ibm-db2'][0].action_do(...) On Fri, Nov 27, 2015 at

Re: [Ecosystem-engineering] The future of Charm Helpers

On Mon, Nov 23, 2015 at 1:37 AM, Billy Olsen wrote: > Secondly, I'm mildly concerned with the namespace of choice (using the > shared charms. as the parent namespace). There may be a magical python 3ism > that resolves the mixed development + packaged use of common

Python 3 default for all layered / reactive charms

https://github.com/juju-solutions/reactive-base-layer/issues/5 I am for using Python 3 in the base layer, but we need to address the effect that would have on the charms currently written using layers. I don't think the community effort to handle the switch at this point would be large, but we

[Review Queue] etcd, apache2, kibana, neutron-calico, bird

Greetings. The big data team (myself, Kevin, and Andrew) spent some time on the review queue yesterday and worked on the following reviews: - etcd - https://code.launchpad.net/~kubernetes/charms/trusty/etcd/trunk/+merge/275768 - This is a fairly simple update

Re: UOS 15.11 - Big Data session

to hearing from you with questions or feedback. On Wed, Nov 4, 2015 at 1:02 PM, Antonio Rosales < antonio.rosa...@canonical.com> wrote: > Thanks Cory, I am also forwarding onto the Juju list if folks aren't > yet on the bigdata list. > > -thanks, > Antonio > > > On Wed, Nov 4

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

You can accomplish most of this with the existing plugin system. You can't override existing commands, but you can easily create thin wrappers around them with your desired default args, and given the discussion around --no-aliases, it seems like this is actually a benefit. And plugins provide

Re: [charms.reactive] http relation.available gets called on upgrade-charm hook, gives error.

rec...@gmail.com> wrote: > Hi Cory > > > Thanks for the explanation. Is there a way to override the scope of the > http relation without forking the interface? > > > > Kind regards > Merlijn > > 2015-10-26 18:21 GMT+01:00 Cory Johns <cory.jo...@canonical.com>

Re: Inconsistencies between juju debug-hooks and "normal" hook environment

14:47:11 INFO config-changed A boilerplate environment >> configuration file has been written to /home/ubuntu/.juju/environments.yaml. >> >> Likewise if you want to create artifacts for the ubuntu user, use the "su >> - ubuntu" command. >> >> Hop

[Review Queue]

The Big Data team, including Kevin, Andrew, and myself, spent some time on the review queue today: - openbook - https://code.launchpad.net/~talligent/charms/trusty/openbook/trunk/+merge/267885 - This update changes web access URLs to use https. -

[Review Queue] Suitecrm, and IBM XL C/C++

The Big Data team was able to get in some Review Queue time this week amongst preparing for our presence at Strata NY: Suitecrm https://bugs.launchpad.net/charms/+bug/1479471 The author addressed issues in our previous review. +1 promulgated. Welcome to the charmstore, SuiteCRM!

Re: [Juju] Proxy Charm examples

smarts in the proxy charm, it can be handled more gracefully than I did in my example. On Fri, Aug 21, 2015 at 10:08 AM, Cory Johns cory.jo...@canonical.com wrote: Stuart, Excellent points. Supporting separate different data for different services is exactly what I was thinking of when I

Re: [Juju] Proxy Charm examples

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

Re: [Juju] Multiple sub service with a relation

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

Re: [Ecosystem-engineering] The future of Charm Helpers

On Wed, Aug 12, 2015 at 7:38 AM, Marco Ceppi marco.ce...@canonical.com wrote: I can see how this helps for discoverability for those already pretty intimate with the code base, but a lot of the key complaints we've gotten around new authors getting started is there is just an overwhelming

Re: i want in (to ~charmers)

I'm not a ~charmer yet, but if I were, Kevin would definitely get my +1. On Mon, Aug 10, 2015 at 2:08 PM, Matt Bruzek matthew.bru...@canonical.com wrote: Another person who delayed the charmer application too long! Kevin forgot to mention he is also a concierge for the IBM charmers. That has

[Review Queue] etcd, storage, postgresql (and some from last week)

Greetings. The Big Data team (myself, Kevin, and Amir) got in some Review Queue time today. We also apparently forgot to send out an email for the RQ items we got to last week, so those are included below, as well. + etcd https://bugs.launchpad.net/charms/+bug/1474061 Mostly good, Amir had a

Re: Juju Compose

On Tue, Jul 14, 2015 at 4:45 PM, Marco Ceppi marco.ce...@canonical.com wrote: I think you're on the right train of thought as to what this is, but miss a few important issues this helps address. It's is trivial to copy code around, and we talk about it all the time in charm schools find a charm

[Review Queue] redis, plumgrid-director, neutron-iovisor, and PlumGrid Bundle

Greetings! The Big Data team did some RQ time together today: + redis https://bugs.launchpad.net/charms/+bug/1459345 This looks like a rewrite of the redis-master and redis-slave charms to combine them into a single charm. We ran into some issues getting bundletester to run to test the charm.

Re: [Plugin] sync-watch: Edit locally, run in the cloud

of juju's architecture helped and hindered you? -eric On Fri, Apr 24, 2015 at 6:34 AM, Cory Johns cory.jo...@canonical.com wrote: Last week, while in Nuremberg, Ben and I were able to create a new plugin to enable a much better charm development workflow. Once the Juju Plugins bundle (https

[Review Queue] was-base, was-nd, and galera-cluster

Hello all. Kevin and I reviewed the following charms yesterday: * websphere base https://bugs.launchpad.net/charms/+bug/1446966 In addition to a few small concerns, such as using the template icon, we noted some immutable config and ran into trouble testing the charm due to not being able to

[Plugin] sync-watch: Edit locally, run in the cloud

Last week, while in Nuremberg, Ben and I were able to create a new plugin to enable a much better charm development workflow. Once the Juju Plugins bundle (https://github.com/juju/plugins) is installed, you can now run `juju sync-watch unit` to enable local editing of a remote charm. This works

Re: Tests Best Practices

José, That's a good point that we definitely need recommended best practices for writing charm tests. I am also behind using the built-in unittest[1] library to organize and structure the tests. I am also behind encouraging combining tests inside test cases where possible, with the caveat that

Re: New Docker goodies

Thanks. :-) I do hope we can also to get local provider working inside the container as well, since it will provide a cleaner set of instructions for new charmers to test their charms, or just play around with Juju. But the --net=host workaround gives us immediate wins in CI, review, and

[Review Queue] kibana nagios tests (follow-up)

Following up on previous reviews, I took a look at test additions by nicopace to both the kibana and nagios charms. Both had some minor issues causing failures, but I created secondary MPs with suggested fixes to help get these reviews finalized.

[Review Queue] docker, flannel-docker, kibana, nrpe

Hey all, Kevin, Amir, and I took on a few reviews, mainly focused on the new Docker charm submissions by Charles Butler, but also continuing to address the slew of test additions by nicopace, as well as some follow-ups to our previous reviews. + docker

Juju Resources (a tool / library)

Hi all, (cross-posting to juju juju-dev) I've created a tool / library for organizing and managing resources (binary blobs, tarballs, Python packages, and, eventually, apt packages) required by a charm. The idea is to be an interim tool, and a test-bed for the resource features that have been

Juju Resources (a tool / library)

Hi all, (cross-posting to juju juju-dev) I've created a tool / library for organizing and managing resources (binary blobs, tarballs, Python packages, and, eventually, apt packages) required by a charm. The idea is to be an interim tool, and a test-bed for the resource features that have been

Re: Juju Resources (a tool / library)

Per request, the documentation is now also available on ReadTheDocs.org: http://jujuresources.readthedocs.org/ On Wed, Feb 11, 2015 at 11:25 AM, Cory Johns cory.jo...@canonical.com wrote: Hi all, (cross-posting to juju juju-dev) I've created a tool / library for organizing and managing

Re: Juju Resources (a tool / library)

resource implementations and taking over important namespaces such as resources.yaml might introduce unnecessary confusion down the road. Instead, the project might have a nice non-generic name, and its configuration file could also be named after it. On Wed, Feb 11, 2015 at 4:17 PM, Cory Johns

Re: Unable to deploy a working 10 node hadoop cluster

Ken, Unfortunately, this is due to an upstream change in the openjdk package. A bug has been filed[1] and it has been noted that this breaks all of the Big Data charms in the store. Please indicate on that bug that this is affecting you. There is a symlink work-around mentioned on the bug, but

[Review Queue] ksplice, and python-django

Kevin and I worked together yesterday to review a new charm submission for KSplice / Uptrack [1], and a merge proposal to (re?)add pip_extra_args support to the trusty python-django charm [2]. The KSplice charm had an issue with the provided test requiring manual input, which would break the

[Review Queue] Tomcat interface improvement, and MySQL test additions

While helping with the OpenBook review, we discovered that the Tomcat charm was did not have clearly described ways for ingesting Java webapps, so I decided to submit a patch[1] to improve that. I also reviewed two test submissions to the trusty MySQL charm, one of which passed easily[2], and the

Re: An Open Question: Charm Dependency Management

I think that it's important that we have tooling (i.e., bundletester) that sets up a (consistent) environment that is exactly the same as what the automated test runner uses (i.e., a fresh container or vm in which the tests are run) and that charm authors and reviewers alike use it. With that,

[Review Queue] chamilo, bitlbee, python-django, rabbitmq-server

* chamilo: -1 (test failure due to race; submitted fix) * bitlbee: +1 * python-django: +1 * rabbitmq-server: -1 (merge conflict; tried to resolve but wasn't confident in my resolution) https://code.launchpad.net/~jose/charms/precise/chamilo/add-tests/+merge/241363

[Review Queue] Charm testing: distcc, stackmobile, firefox-sync, shelrtv

I did reviews of four charm testing / red-to-green merge proposals: * distcc: -1 (install hook failure) (fixed) * stackmobile: -1 (install hook failure) (SSL handshake error) * firefox-sync: -1 (install hook failure) * shelrtv: -1 (install hook failure) (PPA issue) I was able to add a fix for

[Review Queue] Charm testing / RTG: chef-server, thinkup, couchbase, and couchdb

I did reviews of four charm testing / red-to-green merge proposals: * chef-server: +1 * thinkup: -1 (charm proof) * couchbase: -1 (install hook failure) * couchdb: -1 (install hook failure) I submitted fixes for all of the failures, since they were relatively small fixes.

[Review Queue] mongodb rs.initiate(), python-django, and bip

Yesterday and today, I reviewed the following merge proposals: * [approve] mongodb, explicitly using public-address for rs.initiate() to resolved issues with unresolvable host name on MAAS

Re: charm-helpers fetch apt_install optimization

Reiterating my comment on the MP, I agree with Marco that, due in part to the fixed-point usage pattern of charm-helpers and in part to the specifics of the change, I don't see it as having much potential for breakage. That said, I'm certainly not against testing it before merging. On Thu, Nov

[Review Queue] storage (encryption) and nfs (trusty)

I reviewed Chris's addition to the storage charm to add encrypted file-system support. He added tests per Tim's request, which were good, but I had issues running them as we as encountering a few small test breakages in the existing tests. I also reviewed Matt's test additions to get the nfs

[Review Queue] ForgeRock OpenAM OpenDJ, and Wildfly (MP)

Today I did a follow-up to Tim's review of the ForgeRock charms for OpenAM and OpenDJ [1]. I noted two items that need to be improved: required config options causing error state instead of simply blocking, and better handling of the requirement of a full domain name as opposed to an IP address.

[Review Queue] rkhunter, logrotate, and mongodb/auth_experiment

Yesterday and today, I reviewed a couple of new charms by Chris Stratford, and an improvement to the MongoDB charm by Matthew Williams. Chris submitted a charm for the rkhunter rootkit detection package which, but for a config option value being hard-coded in one spot, looked very good. He also

[Review Queue] storage and zabbix-agent (personal namespace) followup

https://code.launchpad.net/~tribaal/charms/precise/storage/refactor-mount-volume/+merge/232236 I had some back-and-forth discussion with Chris and David regarding this refactor, which looks like a great change to me. I have personally reserved my +1 due to some tests that were necessarily

[Review Queue] hdp-tez and zabbix-agent

Yesterday evening, I reviewed two items from the new Review Queue[1]: a new Big Data charm, hdp-tez, for adding YARN support to Hadoop, as well as a zabbix-agent charm change that was submitted to the Review Queue but specifically noted as being for a personal namespace. Amir's hdp-tez charm[2]

[Review Queue] pgbouncer follow-up, NTP MP, Diaspora

I did a follow-up review for the pgbouncer merge proposal since Stuart addressed my comments from last week, and gave it my +1. [1] I also took a look at a merge proposal for the NTP charm which also got my +1. [2] Finally, I attempted to review Jason's improved Diaspora charm branch, but ran

Re: Application for Juju Charmer Status

While I'm not an official charmer myself, my vote would be a solid +1 as well. I've always found José's reviews to be thorough and insightful, and his charm contributions to be excellent. On Thu, Aug 21, 2014 at 12:11 PM, Marco Ceppi marco.ce...@canonical.com wrote: Hi Jose! Thank you so much

[Review Queue] PyBossa, and refactoring pgbouncer to use charmhelpers

. Thanks, Cory Johns -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju

Re: Bundles proposal

On Thu, Jun 19, 2014 at 6:52 PM, Richard Harding rick.hard...@canonical.com wrote: On Thu, 19 Jun 2014, Benjamin Saller wrote: Haven't we talked about this type of content as a different data type though than a bundle? Is this something we should work towards at this time? I think that is

Charms and admin passwords

Hi all, I was wondering about the right way to handle admin passwords for user-facing apps in a charm? Obviously, we don't want to have static default admin passwords, as that leads to insecure default setups. However, I haven't seen an easy, secure way for the charm to communicate a password

<    1   2