Re: SLURM Charms New Upstream

[Kevin Monroe]

Hey James!

You asked for re-promulgation, but I don't see any existing promulgated
slurm charms (https://jujucharms.com/q/slurm).  I'm happy to promulgate the
~omnivector releases, but I noticed you're also a member of ~slurm-charmers
(https://launchpad.net/~slurm-charmers/+members), which also has releases
for these charms.

Please confirm which namespace you want promulgated -- either here or via
chat on the internet relay.

Thanks!
-Kevin

On Mon, May 21, 2018 at 11:48 AM, James Beedy  wrote:

> Request to have the 'slurm-node', and 'slurm-controller' charms
> re-promulgated under the omnivector org namespace.
>
> The new charm locations are
>
> cs:~omnivector/slurm-node
>
> cs:~omnivector/slurm-controller
>
> Thanks
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Elasticsearch Charm Promulgation

[Kevin Monroe]

Hey James!

First up, thanks so much for bringing the ES charm up to v5.x!  Can you
tell me if the source for cs:~jamesbeedy/elasticsearch-7 is the same as
what we've got here:

https://github.com/charms/charm-elasticsearch

Or is that source waiting on this PR to bring it in line with your es-7
charm:

https://github.com/charms/charm-elasticsearch/pull/2

The PR LGTM, so I'll merge it on your ack.  Let me know if there are other
outstanding bits that need to go into this repo.  Once that's done, I
propose we push this to the ~elastic-ops namespace of which you're a member:

https://launchpad.net/~elastic-ops

And then promulgate the ~elastic-ops charm rev.  As Rick and others have
mentioned, teams help distribute ongoing maintenance to people that have a
vested interest in certain charms.

@Simon / Bret:  you are on the ~onlineservices-charmers team that owns the
current promulgated ES charm.  Would you be willing to relinquish
maintainership to ~elastic-ops (and would you like to be members of that
team)?

Thanks!
-Kevin Monroe

On Mon, Aug 14, 2017 at 12:12 PM, Rick Harding <rick.hard...@canonical.com>
wrote:

> I'd also encourage you to test an upgrade path from the current charm to
> yours to help comfort any current users of the charm that if there's a
> change it'll go smoothly for users.
>
> On Mon, Aug 14, 2017 at 1:00 PM Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com> wrote:
>
>> Hey James, my point was that if you want to replace the existing
>> top-level ES charm with your own, we would need agreement from the
>> maintainers of the existing charm.
>>
>> On Mon, Aug 14, 2017 at 12:45 PM, James Beedy <jamesbe...@gmail.com>
>> wrote:
>>
>>> @tim yeah ... possibly I'm not looking for promulgation then, and just
>>> need to push it and grant everyone because its already promulgated?
>>>
>>> On Mon, Aug 14, 2017 at 9:29 AM, Tim Van Steenburgh <
>>> tim.van.steenbu...@canonical.com> wrote:
>>>
>>>> There's already a top-level elasticsearch charm.
>>>> https://jujucharms.com/elasticsearch/
>>>>
>>>> On Mon, Aug 14, 2017 at 12:13 PM, James Beedy <jamesbe...@gmail.com>
>>>> wrote:
>>>>
>>>>> Request for promulgation of Elasticsearch. The Elasticsearch charm can
>>>>> be found at cs:~jamesbeedy/elasticsearch-7.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> James
>>>>>
>>>>> --
>>>>> Juju mailing list
>>>>> Juju@lists.ubuntu.com
>>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>>>>> mailman/listinfo/juju
>>>>>
>>>>>
>>>>
>>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: is Hdp bundle still maintained/supported?

[Kevin Monroe]

Hi Patrizio,

Network resolvability of Hadoop cluster nodes is a painful requirement at
times.  We test to catch issues like this on clouds/containers, but it
sounds like we've missed an openstack case.  If you don't mind, please
describe the failing environment and your /etc/hosts fix in an issue here:

https://github.com/juju-solutions/layer-apache-bigtop-base/issues

I'm concerned to hear that the smoke tests are failing for you as well.
Our tests for hadoop-processing run the smoke-test actions for all
components and a teragen/terasort across all the clouds.  The latest
results from just a few hours ago lgtm:

http://162.213.34.190:5000/cwr_bundle_hadoop_processing/44/report.html

Please open an issue for any failing test and we'll find out what's going
on.  Thanks for the reports!
--
Kevin Monroe

On Tue, Jun 20, 2017 at 7:01 AM, Patrizio Bassi <patrizio.ba...@gmail.com>
wrote:

> Dear Samuel
>
> i deployed the hadoop-processing bundle successfully.
> I had some troubles because openstack instances didn't get the dns entry
> so hadoop-hdfs-namenode/datanode could not resolve their own addresses
> first, then the peers'.
>
> I did a fast hack just manually adding the entries in /etc/hosts while
> waiting for Designate service to be deployed and active.
>
> It would be great if you could add in the documentation the dns need.
>
> This said, i run the smoke tests and they all failed. HDFS storage is
> reported working instead.
> I'm totally newbie in hadoop clusters so i didn't start investigation, but
> i wanted to report in case you may check on your local working copy and
> verify it's fine upstream.
>
> Thank you
>
> Patrizio
>
>
>
>
> 2017-06-16 12:08 GMT+02:00 Patrizio Bassi <patrizio.ba...@gmail.com>:
>
>> Hi Samuel,
>>
>> thank you for fast and honest reply. I will start to take a look at
>> hadoop-processing bundle.
>> Regards,
>>
>> Patrizio
>>
>> 2017-06-16 9:54 GMT+02:00 Samuel Cozannet <samuel.cozan...@canonical.com>
>> :
>>
>>> Hi Patrizio,
>>>
>>> Thanks for reaching out. There is a list of more recent charms based on
>>> Big Top here: https://jujucharms.com/q/bigtop?type=charm
>>> The current strategy is to focus on big top, so products from
>>> Hortonworks are no longer supported as you could notice.
>>>
>>> The team to track is here : https://jujucharms.com/u/bigdata-charmers/
>>>
>>> In addition, there are 2 community teams actively involved in Big Data
>>> solutions via Juju, who can help for big data solutions:
>>> * http://spicule.co.uk/ (on IRC reach out to MagicalTrout)
>>> * http://tengu.intec.ugent.be/v1/ (reach out to
>>> merlijn.sebrec...@gmail.com)
>>>
>>> Best,
>>> Sam
>>>
>>>
>>>
>>>
>>> --
>>> Samuel Cozannet
>>> Cloud, Big Data and IoT Strategy Team
>>> Business Development - Cloud and ISV Ecosystem
>>> Changing the Future of Cloud
>>> Ubuntu <http://ubuntu.com>  / Canonical UK LTD <http://canonical.com> /
>>> Juju <https://jujucharms.com>
>>> samuel.cozan...@canonical.com
>>> mob: +33 616 702 389
>>> skype: samnco
>>> Twitter: @SaMnCo_23
>>> [image: View Samuel Cozannet's profile on LinkedIn]
>>> <https://es.linkedin.com/in/scozannet>
>>>
>>> On Fri, Jun 16, 2017 at 9:36 AM, Patrizio Bassi <
>>> patrizio.ba...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> looking at a hadoop distro in the jujucharms is found
>>>> https://jujucharms.com/hdp-hadoop/trusty/1 charm,
>>>> following the announcement in https://insights.ubuntu.com
>>>> /2015/02/19/ubuntu-hortonworks-and-microsoft-big-data-hosted-solution/
>>>>  .
>>>>
>>>>
>>>> I would like to know if it's still maintained, i don't see commits
>>>> since 2015, version is stuck to trusty for ubuntu and hdp at 2.1.3 while
>>>> upstream is on 2.2 series.
>>>> the Contact Information show a no more valid email address too.
>>>>
>>>> Is Canonical looking at Apache bundle only?
>>>>
>>>> Thank you
>>>>
>>>> Patrizio
>>>>
>>>> --
>>>> Juju mailing list
>>>> Juju@lists.ubuntu.com
>>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>>> an/listinfo/juju
>>>>
>>>>
>>>
>>
>>
>> --
>>
>> Patrizio Bassi
>> www.patriziobassi.it
>> http://piazzadelpopolo.patriziobassi.it
>>
>
>
>
> --
>
> Patrizio Bassi
> www.patriziobassi.it
> http://piazzadelpopolo.patriziobassi.it
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: un-promulgating big data charms next week

[Kevin Monroe]

Hey Guillermo,

On Mon, May 1, 2017 at 3:41 PM, Guillermo Gonzalez <
guillermo.gonza...@canonical.com> wrote:

> Hi,
>
> On Fri, Apr 28, 2017 at 8:34 PM, Kevin Monroe
> <kevin.mon...@canonical.com> wrote:
> > Hey Juju,
> >
> > TL;DR:  i'm proposing to un-promulgate 45 outdated big data
> charms/bundles
> > [0] next Friday, May 5th.
> >
> > Earlier this week, Merlijn mentioned improvements that would help users
> > searching for things like 'hadoop'.  The gist is that we still list
> outdated
> > charms as 'recommended', even though they are not.  To address this, I'm
> > proposing to un-promulgate 15 bundles and 30 charms as shown here:
> >
> > https://docs.google.com/spreadsheets/d/1TjWl86BTOWKSe8LBNHTQFAwMoeNG5
> sKz_9YdCl0BPkQ/edit?usp=sharing
>
> We are using cs:apache-spark-10 ATM, but have no problem (still not in
> a production deployment) on switching to the new promulgated charm,
> which seems to be cs:spark (cs:spark-34 as of today).
>

Correct, cs:spark-34 should replace cs:apache-spark.

Just tried to deploy the same cluster with the above charm and it's
> failing, with what it seems to be a missing dependency (gcc to build
> charm deps), log: http://paste.ubuntu.com/24494765/

Posting this here as the link to submit a bug int he charm store page
> points to spark bugtracker and not the charm's one.
>
> Please let me know if there is bugtracker for the charm and I'll be
> happy to file the bug there.


You found the bug tracker correctly :)  The spark charm lives in the
upstream repo, so issues are handled by Bigtop's bugtracker:

https://issues.apache.org/jira/secure/CreateIssue!default.jspa

It does require an Apache account to open a ticket.  If you find github
more convenient, you can file an issue in our bigtop fork and I'll make
sure appropriate JIRAs get linked:

https://github.com/juju-solutions/bigtop/issues

As for your original problem report, I think we're zero-ing in on it being
related to a restrictive network.  Let's handle that with an open
issue/jira as you like.

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

[ANN] Bigtop-1.2 charms/bundles have been released

[Kevin Monroe]

Hi folks!

After over a year in development, Apache Bigtop 1.2 was released earlier
this month.  Today, we released updated charms and bundles for this release
to the appropriate stable channels.

HIGHLIGHTS:

+ Software versions:
- hadoop-namenode 2.7.3
- hadoop-plugin 2.7.3
- hadoop-resourcemanager 2.7.3
- hadoop-slave 2.7.3
- hbase 1.1.3-1 **
- kafka 0.10.1.1-1
- mahout 0.12.2-1 **
- pig 0.15.0
- spark 2.1.0-1
- zeppelin 0.7.0
- zookeeper 3.4.6-1 **

** There is a planned bigtop-1.2.1 point release to bring in hotfixes.
This will likely include hbase-1.1.9, mahout-0.13, and zookeeper-3.4.10.
No charm changes are required; when these debs hit the upstream repo, the
charms will provide the new version.

+ Juju 2.0 or greater
- To leverage Juju Resources, bigtop-related charms now require Juju 2 or
greater.

+ Usability
- Refreshed READMEs and actions for a consistent UX

+ Hadoop-Spark
- Reduced resource requirements.  Spark is not in HA mode in this bundle,
so we removed 3 unnecessary zookeeper units.

+ Spark
- New configuration to change driver/executor memory at runtime.
- Improved spark reliability when changing execution mode (local,
standalone, yarn).


KNOWN ISSUES:

+ GCE
- https://bugs.launchpad.net/juju/+bug/1674871
- Most of our applications require a minimum of 7g ram.  We set a generic
memory constraint in our bundles for a consistent experience across all
clouds.  However, with GCE, mem=7G results in a "highcpu" instance type.
These are significantly more expensive than "standard" instance types.
- If "highcpu" instances are not required, workaround this issue by
modifying a local copy of bundle.yaml.  For example:

$ charm pull hadoop-processing
cs:bundle/hadoop-processing-58
$ cd hadoop-processing/
$ sed -ie 's/mem=7G/instance-type=n1-standard-2/' bundle.yaml
$ juju deploy ./bundle.yaml

+ Zeppelin
- https://issues.apache.org/jira/browse/BIGTOP-2742
- The init script for the zeppelin service is broken.  The charm will work
around this during install and relation changes, but users may find that
things like "sudo systemctl  zeppelin" on the unit do not work.
- We'll update the zeppelin charm once an appropriate fix lands upstream.


Please let me know if you have any questions or issues with the bigtop-1.2
release.  Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue]: elasticsearch (v5!) and general cleanup

[Kevin Monroe]

Hey Juju, I spent some time in the review queue today:


   -

   Cleanup
   -

  Moved reviews that were awaiting author feedback into “Needs Fixing”
  -

   Elasticsearch
   -

  https://review.jujucharms.com/reviews/103?revision=270
  -

  Minor README suggestions
  -

 http://paste.ubuntu.com/24420775/
 -

  Created new lp team to house this and other ELKy things:
  -

 https://launchpad.net/~elastic-ops
 -

  Recommended moving this charm to the above team.
  -

  Though this deployed and ES5 looks fine, I’m giving this a -1 for now
  while we work out the details for a new home.


Questions/comments?  Fire away in #juju on Freenode.

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

[Review Queue] landscape-dense, charmscaler, k8s-*, ibm-*

[Kevin Monroe]

Hi folks,

Konstantinos, Pete, Cory and I had some time in the queue today:


   -

   Landscape-dense
   -

  https://review.jujucharms.com/reviews/113?revision=307
  -

  Previous issue of insufficient machine constraints has been resolved.
  -

  This bundle does not include tests; however, we don’t consider this a
  blocker since bundletester invokes matrix, which performs a series of
  deployment tests.
  -

  Looks good, promulgated to:
  -

 https://jujucharms.com/landscape-dense/
 -

   charmscaler
   -

  https://review.jujucharms.com/reviews/96
  -

  A change in a related charm caused the automated test to fail;
  suggested locking the rev to ensure that doesn’t happen in the future
  -

   kubernetes*
   -

  Checked up on the charms -- still look great, other than missing
  tests.
  -

   Ibm-spectrum-scale-client
   -

  https://review.jujucharms.com/reviews/78
  -

  Ran into trouble installing locally to run tests. Left a comment.
  -

   Ibm-was-nd
   -

  https://review.jujucharms.com/reviews/63
  -

  This should be a base layer as we have seen for trusty (
  https://review.jujucharms.com/reviews/40)
  -

  We are waiting for the authors confirmation before closing the review.
  -

   Ibm-cinder-spectrumscale
   -

  https://review.jujucharms.com/reviews/80?revision=217
  - Checked off some policy basics; so far, so good.


Questions/comments?  Find us in #juju on Freenode.

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

Re: Cannot update bugs-url of promulgated charm

[Kevin Monroe]

You're all set Merlijn.

-Kevin

On Mon, Mar 6, 2017 at 11:21 AM, Jay Wren  wrote:

> The charm is promulgated and thus its write permissions are set to only
> "charmers".
>
> Will a member of charmers please set bugs-url for Merlijn?
>
> Alternatively, you could update a different charm, set its bugs-url and
> ask for it to be promulgated.
> --
> Jay
>
>
> On Mon, Mar 6, 2017 at 10:55 AM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>>
>> When I want to update the bugs-url of a promulgated charm I get an
>> unauthorized error. Is this a bug or am I doing something wrong?
>>
>> charm set cs:~tengu-team/eclipse-che bugs-url=https://github.com/te
>> ngu-team/layer-eclipse-che/issues
>> ERROR cannot update the set arguments provided: unauthorized: access
>> denied for user "merlijn-sebrechts"
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue]: giraph, ibm-*, mongodb, odoo, ntp

[Kevin Monroe]

Hi friends!

Cory, Kostas, Pete, and I have 2 weeks worth of reviews to note:

Feb 23, 2017:

   -

   giraph
   -

  https://review.jujucharms.com/reviews/82
  -

  This has been on our radar for a few review cycles now.  We added a
  proper giraph interface so this charm no longer needs to hijack
the mahout
  relation :)
  -

  We suggested general charm fixes with the following PR:
  -

 https://github.com/panagiotisl/bigtop/pull/3
 -

  Pending further discussion with the author, this should sail through
  to the store once a new revision is released.
  -

   ibm-was-nd
   -

  https://review.jujucharms.com/reviews/40
  -

  Issue with terms prevents testing.  This can be fixed in the charm,
  but I also opened https://github.com/juju/charmstore-client/issues/118
  to get clarification on the error it caused and why it’s an issue
  -

  Additional issues with handling resource upgrades and with test were
  spotted from code review
  -

   mongodb
   -

  https://review.jujucharms.com/reviews/91
  -

  We run into two issues during review.
  -

 Tests were failing
 -

 The proposed for promulgation revision does not belong to one of
 the maintainers.
 -

  We will have to wait for the author’s and maintainers’ input.
  -

   Ibm-dsm-base
   -

  https://review.jujucharms.com/reviews/56
  -

  We found a couple of issues that need the author’s input.
  -

  Most importantly there was a default password used that raises
  security concerns.
  -

   Ibm-wxs-catalog
   -

  https://review.jujucharms.com/reviews/41
  -

  Small linter error
  -

  Test not marked as executable (isn’t automatically picked up by
  bundletester)


Feb 16, 2017:

   -

   odoo
   -

  https://review.jujucharms.com/reviews/23
  -

  Another ping put out to the author, as there is a provided PR which
  resolves the only issue blocking this review
  -

   ntp
   -

  https://review.jujucharms.com/reviews/85
  -

  Charm was already promulgated, so closed review
  -

   Ibm-xcat
   -

  https://review.jujucharms.com/reviews/38
  -

  During review a number of issues came up. Namely:
  -

 Dead code and assumptions on the unit networking
 -

 Tests failing, README improvements
 -

  We would like the author to review some of the issues reported.
  -

   Ibm-mobilefirst-server
   -

  https://review.jujucharms.com/reviews/39?revision=75
  -

  We did a quick review and spotted a couple of blockers
  -

 Use unpromulgated charms during tests and failing lint errors
 - We will need to wait for the author to address these issues


Find us in #juju on freenode with any questions/concerns. Thanks!
-Kevin
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue]: ghost, znc, IBM-*

[Kevin Monroe]

Hi Juju,

Cory, Kostas, Pete, and I waded through https://review.jujucharms.com/ this
week.  Here's what we found:


   -

   ghost
   -

  https://review.jujucharms.com/reviews/62
  -

  Ghost is a simple, powerful publishing platform.
  -

  The charm is in a good shape (24th revision).
  -

  There are a few more points that require the author’s attention,
  mainly in the tests.
  -

  We will have to wait the authors input for now.
  -

   znc
   -

  https://review.jujucharms.com/reviews/24
  -

  Refactored to use Ruby instead of Perl as the charm language, but has
  a test failure
  -

   Ibm-platform-lsf-server
   -

  https://review.jujucharms.com/reviews/18
  -

  Left some comments after code review, requesting improvements to
  error handling (currently, the charm can behave unpredictably,
and does not
  check for several error conditions)
  -

   Ibm-im
   -

  https://review.jujucharms.com/reviews/47?revision=106
  -

  We noticed an unhandled exception when deploying without a proper
  resource and committed a minor fix.  With this and previous +2,
this looks
  good.
  -

  Promulgated: https://jujucharms.com/ibm-im/
  -

   Ibm-was-base
   -

  https://review.jujucharms.com/reviews/74?revision=164
  -

  Our previous review was accidentally against the xenial version
  (under development).  We opened this one to review updates to the stable
  trusty revision.
  -

  We added a repo key and cleaned up minor readme/test issues.
  -

  Rebuilt to pull in recent ibm-im changes.  Deployed / functioned as
  documented in the readme.  +1.
  -

  Promulgated: https://jujucharms.com/ibm-was-base/trusty


Find us on Freenode in #juju with any questions/concerns.

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

support for local resources in bundles?

[Kevin Monroe]

I've got a bundle.yaml that defines a local charm, e.g.:

...
  mycharm:
charm: "/home/ubuntu/charms/builds/mycharm"
num_units: 1
...

Does the bundle spec allow for attaching resources to mycharm?  If so, can
the resource be local?

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

What's with all the test talk? (aka, give me CI already)

[Kevin Monroe]

Hi Juju!

>From Matrix [0] to Review Queue [1] to Amulet [2] to Charm Author Workflows
[3], you'd think December was the month we all remembered the importance of
software testing.  There are oodles of test tools for charms/bundles, and
if you know about all of them, you're probably putting out thoughtful,
well-tested charms (thanks stub!).

One thing that we've found missing is a nice charm CI/CD system that
leverages these tools to automatically give developers confidence in their
code and handle the release cycle from a source repo to the charm store,
soup to nuts.  Wouldn't it be nice if you could commit a charm update to
github and automatically have Cloud Weather Report kick off Jenkins jobs on
all your clouds, which in turn called Bundletester to handle deployment,
which in turn called Amulet and Matrix to run specific tests?  Taking it a
step further, it'd be nice if that system could automatically push
charms/bundles to your edge channel (if their tests pass), and if you tag
source with a release tag, build/test/release it to your stable channel.

This kind of system is what the Big Software team has been working on
recently, and we're open to feedback!  Our goal is to deliver a system (as
a bundle) that answers the question, "how should I do CI/CD for my charms
and bundles?"  We're also working on a variation that includes the Review
Queue -- it will eventually become the brains behind
https://review.jujucharms.com and will be available for anyone wanting a
CI/CD + Source Review system in-house.

If you're interested, development is happening at
https://github.com/juju-solutions/bundle-cwr-ci.  Have a look at the readme
for more details and let us know what you think.  The bundle yaml files are
currently deployable, buy I have a nasty habit of committing straight to
master, so bear with us as development is moving fast at the moment.  Watch
this space for updates on our progress.

[0] - https://lists.ubuntu.com/archives/juju/2016-December/008260.html
[1] - https://lists.ubuntu.com/archives/juju/2016-December/008287.html
[2] - https://lists.ubuntu.com/archives/juju/2016-December/008288.html
[3] - https://lists.ubuntu.com/archives/juju/2016-December/008302.html

Thanks!
--
Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] IBM Platform RTM, LSF, Symphony, and Websphere Base

[Kevin Monroe]

Hi folks,

Cory, Kostas, Pete, and myself had a look at the following this week:


   -

   IBM Platform RTM
   -

  https://bugs.launchpad.net/charms/+bug/1510216
  -

  Minor issues with config (offered suggestions) and readme
  instructions (fixed)
  -

  Amulet test needs work
  -

  Charm store policy violations.  As a reminder, recommended charms
  need to abide by the policy outlined here:
  -

 https://jujucharms.com/docs/stable/authors-charm-policy
 -

  -1 for now.
  -

   IBM Symphony Master
   -

  https://review.jujucharms.com/reviews/15
  -

  Finished a read-through of code, and checked off most of the boxes in
  our new review queue.
  -

  Rebuilt the charm locally and re-ran the tests. Am still seeing
  linter errors (though there are fewer, now that the storage
layer has been
  rebuilt).
  -

   IBM Platform LSF Master
   -

  https://review.jujucharms.com/reviews/17
  -

  Did a quick review of metadata, and set the section to green
  -

  Noticed some items in during code review that should be addressed;
  commented at https://bugs.launchpad.net/charms/+bug/1578271
  -

   IBM Platform LSF Server
   -

  https://review.jujucharms.com/reviews/18
  -

  Did a quick review of metadata, and set the section to green
  -

  Noticed some items during code review that should be addressed;
  commented at https://bugs.launchpad.net/charms/+bug/1578273
  -

   IBM Platform LSF Storage
   -

  https://bugs.launchpad.net/charms/+bug/1462212
  -

  Noticed some issues with status messages, required deployment names
  for related applications, and the use of “exit” in bash reactive handlers


   -

   IBM Websphere Base
   -

  https://bugs.launchpad.net/charms/+bug/1446966
  -

  We went though the build process and the instructions through the
  readme. Here are some issues we found and may need the authors attention:
  -

 Unregistered interfaces
 -

 Code style errors
 -

 Minor README fixes needed
 -

 Tests using charms from private namespace


Any questions or comments?  Please find us in Freenode #juju.  Thanks!
-Kevin
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue]: IBM NFS Storage and IBM Platform Master interfaces

[Kevin Monroe]

Matt and I took a look at the following interfaces from IBM today:


   -

   IBM NFSStorage interface
   -

  https://bugs.launchpad.net/charms/+bug/1578166
  -

  +1 from us after lint fixes
  -

   IBM PlatformMaster interface
   -

  https://bugs.launchpad.net/charms/+bug/1578173
  -

  Needs similar lint fixes, so we opened the following MP:
  -


 
https://code.launchpad.net/~mbruzek/interface-ibm-platformmaster/lint-fixes/+merge/308836


As a reminder, all interfaces need to pass flake8 so they don't cause lint
errors in charms that include them.

Questions or concerns?  Find us in Freenode #juju.  Thanks!
-Kevin
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: getting lxd forkstart error while doing bootstrap

[Kevin Monroe]

Hi Rajith,

I see you are running kernel-3.16.  According to these bugs, you'll need
kernel-4.4 to use juju with lxd on ppc64le:

https://bugs.launchpad.net/juju-core/+bug/1600311
https://bugs.launchpad.net/juju/+bug/1605714

If you can upgrade your system to Xenial (16.04), that will give you the
most up-to-date environment for using juju/lxd on ppc64le.  If you must
remain on Trusty (14.04), perhaps you can upgrade your kernel to v4.4 [1]:

sudo apt-get install --install-recommends linux-generic-lts-xenial

I can confirm that juju/lxd work great on a power8 running xenial.  If you
have trouble after upgrading, please add your findings to the above bugs.

[1] - https://wiki.ubuntu.com/Kernel/LTSEnablementStack

Thanks,
-Kevin

On Thu, Sep 22, 2016 at 7:11 AM, Rajith P Venkata 
wrote:

> Hi
>
> I am getting error while doing bootstrap
>  I am getting ERROR failed to bootstrap model: cannot start bootstrap
> instance: Error calling 'lxd forkstart juju-4fce6d-0
> /var/lib/lxd/containers /var/log/lxd/juju-4fce6d-0/lxc.conf': err='exit
> status 1'
>
> this error is on root@:/var/log/lxd/juju-4fce6d-0# uname -a
> Linux c277-pkvm-vm54 3.16.0-70-generic #90~14.04.1-Ubuntu SMP Wed Apr 6
> 22:57:48 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
>
>
>
>
>
> Rajith
>
> IBM AIX Certified, OCPCertified
> 
>
> Cell- 9901966577
> Email: rajith...@in.ibm.com
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] IBM IM, Pubphoto, Wordpress, Bip

[Kevin Monroe]

Last week, Kostas, Pete, and I reviewed the following:


   -

   IBM Installation Manager
   -

  https://bugs.launchpad.net/charms/+bug/1575746
  -

  Good example of a charm utilizing Resources and Terms.
  -

  Deployed with trusty and xenial and successfully exercised install
  and upgrade.
  -

  We don’t have an automated way of supplying proprietary resources and
  accepting terms, but we successfully ran through the tests manually.
  -

  +1, promulgated to https://jujucharms.com/ibm-im/
  -

   Pubphoto
   -

  https://bugs.launchpad.net/charms/+bug/1574772
  -

  +1, promulgated to https://jujucharms.com/pubphoto/
  -

   Wordpress
   -


  
https://code.launchpad.net/~jamesbeedy/charms/trusty/wordpress/apache2_trusty_fix/+merge/297720
  -

  We already approved this last time around, but the charm needs to be
  moved out of the ~charmers namespace. Pinged the maintainer to remind him
  to do so.
  -

   Bip
   -


  
https://code.launchpad.net/~josvaz/charms/trusty/bip/charmhelpers-cleanup/+merge/301499
  -

  Code looks good, tests pass.
  - Charm needs to be moved out of ~charmers namespace before it can be
  promulgated, however.


Questions/comments?  Please find us in #juju on irc.freenode.net.  Thanks!
--
Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] multiple IBM designs

[Kevin Monroe]

Hi folks, the IBM Charmers have adjusted several of their in-flight designs
to use Juju 2.0 features (specifically, Terms and Resources).  Matt and I
took a look at the following:

- IBM Installation Manager :
https://docs.google.com/document/d/1qBzMO_Zgy35ty6NCBfdI5Utn7B4I4sTX3_FtPs3UndY/pub
- IBM HTTP Server :
https://docs.google.com/document/d/1PQjZofa9aK4s9m2yKcvMkqsLT_esgZ2iJVf-DnVdNEU/pub
- IBM WAS Base :
https://docs.google.com/document/d/1O7J_SLDdCD-D7J8xG7k_9hAGTo8j7BcfCXbA3iTtkR8/pub
- IBM Platform LSF :
https://docs.google.com/document/d/1f0UxATIym7v1rq6qFqTA6Lhpp2ABpBTl5BiU1LgVW4A/pub
- IBM Platform Symphony :
https://docs.google.com/document/d/1gDH4YkNh3xV2UAkUx9cq4MndFdS3DYrs3Pdiu-8Bf_c/edit
- IBM Spectrum Scale :
https://docs.google.com/document/d/15VPxSNZWnEZTDbxdpne5IHiDpyVhK29d3kQ5uZ5oPaA/edit?usp=sharing
- IBM WAS ND :
https://docs.google.com/document/d/17Uh_EghiBKZiDf8ZiM6T-VQzVfoTj4gOlwTl9oieBwc/pub
We made a few comments/suggestions, but overall, these look good and have a
+1 from us to implement.

As a reminder, we like reviewing designs just as much as "normal" charm
reviews.  I think we can all agree that the earlier we catch potential
pitfalls, the better.  Big props to IBM for requesting feedback so early in
their charm development cycle.

If you have notes on a napkin, a google doc, a gist, or a charming idea
floating between your head and the keyboard, put into a medium we can
digest and we'll take a look!

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

Re: Charmers membership request!

[Kevin Monroe]

Since last December, I've been on 18 tours through the Review Queue with
Kostas.  We've seen the good, the bad, and a little bit of ugly together.
We're in such a harmony now that his 'ack' is really just busy work for a
~charmer to come behind and mash the buttons.

Couple his dedication to the rev queue with his Big Data charm
contributions, and this is an easy +1 for me.  Thanks for the application
Kostas; you'll be a great addition to ~charmers.
--
Kevin Monroe

On Tue, May 31, 2016 at 12:21 PM, Charles Butler <
charles.but...@canonical.com> wrote:

> A big +1 to this application. You keep me honest, and always make me
> contribute higher quality submissions. Even if you have to lend a hand
> where my python-fu falls over. I look forward to having you join the ranks
> as a Charmer Konstantinos!
>
> On Mon, May 30, 2016 at 11:33 AM Konstantinos Tsakalozos <
> kos.tsakalo...@canonical.com> wrote:
>
>> Hi,
>>
>> This is to request membership to ~charmers.
>>
>> I have been working with the Bigdata team for some time now. You can
>> find my contributions in the respective charms & bundles on https://
>> github.com/juju-solutions. Also, I've been taking part in the regular (
>> normally weekly) review sessions of the team so I am very familiar with
>> the process.
>>
>> Thank you,
>> Konstantinos Tsakalozos
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
> --
> Juju Charmer
> Canonical Group Ltd.
> Ubuntu - Linux for human beings | www.ubuntu.com
> Juju - The fastest way to model your service | www.jujucharms.com
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] cassandra (x2), openjdk, logstash, ganglia-node

[Kevin Monroe]

Hi folks,

Cory, Kostas, new guy Pete, and myself took a trip down the queue today.
Here's what we found:


   -

   cassandra (fix disk checks)
   -


  
https://code.launchpad.net/~stub/charms/trusty/cassandra/fix-diskchecks/+merge/283760
  -

  +1, merged
  -

   cassandra (wait for joining)
   -


  
https://code.launchpad.net/~stub/charms/trusty/cassandra/wait-for-joining/+merge/286993
  -

  Seems like there is potential for deadlock; timeout suggested
  -

   Openjdk
   -

  https://github.com/juju-solutions/layer-openjdk/pull/3
  -

  Pass java relation data to other subordinates on a principal
  -

  +1, merged
  -

   Logstash
   -

  https://bugs.launchpad.net/charms/+bug/1560167
  -

  New charm submission. Logstash is designed to efficiently process a
  growing list of log, event, and unstructured data sources for
distribution
  into a variety of outputs, including Elasticsearch.
  -

  This is the second round of review for this charm. The authors have
  revised their charm and addressed all comments.
  -

  +1, now available at https://jujucharms.com/logstash/
  -

   Ganglia-node
   -


  
https://code.launchpad.net/~kwmonroe/charms/trusty/ganglia-node/remove-memcached/+merge/295769
  -

  Remove memcached from the unit test since it is not needed.
  -

  Ran tests, which executed successfully.
  -

  +1, merged.


Questions or comments?  Let us know in #juju on freenode.

Thanks, and welcome Pete!!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: information needed for Mariadb Enterprise edition

[Kevin Monroe]

I recently took a look at the mariadb charm on ppc64le and ran across some
interesting bits.  I'm looping in the charm maintainer (dbart) for extra
insights.

First, MariaDB has both enterprise and community versions available for
this charm to deploy.  Rajith, as you saw in the readme, you should be able
to obtain credentials from the MariaDB Portal (
https://mariadb.com/user/login?destination=my_portal/download).  However,
there was a recent change in the package signing key [0] that may affect
installation.  Daniel, are these "enterprise.yaml" creation instructions in
the charm readme still valid?:

http://bazaar.launchpad.net/~charmers/charms/trusty/mariadb/trunk/view/head:/README.md#L46

Second, line 382 of Rajith's log (http://paste.ubuntu.com/16514402/) shows
that if the configured repo is ignored, the charm will continue to install
mariadb-[server|client] from the trusty archives.  This will put
mariadb-5.x on the unit, which may or may not be intended.  Perhaps the
charm should warn the user if mariadb is installed from a location other
than the configured repo?

Third, I was able to reproduce the behavior seen in Rajith's log where
mariadb did not start successfully.  I think the default dataset-size
configuration is too aggressive in some scenarios.  I've opened a bug [1]
to track this.

Rajith, I know you specifically asked about the enterprise edition, and
hopefully Daniel will be able to assist there.  That said, I have verified
the community edition works when deploying from the charm store to a
ppc64le container.  Let me know if I can be of any help to get that running
in your environment.

[0] https://jira.mariadb.org/browse/MDEV-9781
[1] https://bugs.launchpad.net/charms/+source/mariadb/+bug/1583834

Thanks,
-Kevin

On Thu, May 19, 2016 at 8:01 AM, Mark Shuttleworth  wrote:

>
> Looks like MariaDB have an enterprise version which requires you to agree
> to their terms and download the software from them using a private password
> dedicated to you.
>
> This might be related to specific config settings (i.e. if you've told the
> charm to use an enterprise version) or it may just be the default behaviour
> of that charm.
>
> We are working towards a simpler mechanism to handle this sort of use
> case, will ask that MariaDB try that instead.
>
> Mark
>
>
> On 19/05/16 03:10, Rajith P Venkata wrote:
>
> Hi
> I am installing Mariadb Enterprise edition by following below steps from
> charm store, I am getting hook fail error,
>
>
> Obtain a username/password from the MariaDB Portal and you will then have
> access to the MariaDB Enterprise repository.
> Next create a file called enterprise.yaml with the following contents,
> replacing username:password with your actual username and password:
> mariadb:
>   enterprise-eula: true
>   key: 0xd324876ebe6a595f
>   source: "deb 
> https://username:passw...@code.mariadb.com/mariadb-enterprise/10.0/repo/ubuntu
> trusty main"
> Lastly, deploy MariaDB as normal but with the addition of the yaml file
> juju deploy --config ./enterprise.yaml mariadb
>
>
>  please let me know steps for getting username and password .  Is username
> and password same as site username and password.
>
> Rajith
>
> IBM AIX Certified, OCPCertified
> 
>
> Cell- 9901966577
> Email: rajith...@in.ibm.com
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] ibm-java

[Kevin Monroe]

Matt and I took a look at the ibm-java charm today.

We had trouble deploying this as it requires a 3rd party to host the
installer (something which will be a thing of the past with juju
resources!).  We sorted our issues and were able to verify this charm
deployed and worked successfully.

Working through this, we had suggestions on smoothing the rough edges and
put together the following MP:

https://code.launchpad.net/~kwmonroe/charms/trusty/ibm-java/may-2016/+merge/294984

We look forward to these changes being accepted and making ibm-java another
alternative for java relations in the juju ecosystem.

Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] ibm-xCAT, ibm-was-nd

[Kevin Monroe]

Matt and I spent some time reviewing the design documents for the ibm-xCAT
and ibm-was-nd layered charms today:

xCAT:
https://docs.google.com/document/d/1DgK79jsP2mnxfu_5uHWDSgMriy1VN3kYUK2On2OCSU8/edit#

WAS ND:
https://docs.google.com/document/d/17Uh_EghiBKZiDf8ZiM6T-VQzVfoTj4gOlwTl9oieBwc/edit


As before, these are good examples of layered designs that use the reactive
framework.  Sorting out details at this stage should make for smooth
sailing through implementation and future review -- a big thanks to IBM for
putting their designs out there!

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

Re: Query on IBM-Installtion Manger Charm Layer

[Kevin Monroe]

Hi Shruthima,

If you have a local ibm-im layer in your LAYER_PATH, an ibm-was layer
should find it during 'charm build' and any ibm-im states should be usable
in ibm-was.  If you can commit your ibm-im and ibm-was layers to
lp:~ibmcharmers,
i'd be happy to take a look.  If that's not possible, please send the
output of 'charm build -l DEBUG' from your layer-ibm-was directory.  That
should tell us where it's pulling the ibm-im layer from and might give us
clues where to look next.

Thanks,
-Kevin

On Mon, Mar 28, 2016 at 6:51 AM, Shruthima Almavar <salma...@in.ibm.com>
wrote:

> Hi Kevin,
>
> As you suggested we have made all the changes to IBM Installation Manger
> layer (*https://github.com/kwmonroe/layer-ibm-installation-manager*
> <https://github.com/kwmonroe/layer-ibm-installation-manager>) locally (
> in ./reactive/ibm-installation-manager.sh)  to make it is a functional
> layer and we are able to deploy IBM-IM successfully.
>
> But when we are trying to install IBM-WAS on top of IBM-IM layer,  IM
> layer states like 'im.installed' is not recognized in IBM-WAS layer.
> Although we have set LAYER_PATH and  included IBM-IM Layer in layer.yaml:
>
> includes: ['layer:ibm-installation-manager']
>
> Could you please suggest us is there anything to be added to use IBM-IM
> layer in other products eg:WAS...!!
>
>
> Regards,
> Shruthima Almavar.
>
>
>
> From:Shruthima Almavar/India/IBM
> To:Kevin Monroe <kevin.mon...@canonical.com>
> Cc:juju <juju@lists.ubuntu.com>, Matt Bruzek <
> matthew.bru...@canonical.com>
> Date:03/22/2016 03:51 PM
> Subject:Re: Query on IBM-Installtion Manger Charm Layer
> --
>
>
> Hi Kevin,
>
> Thanks for providing your thoughts on IBM Installation Manager layer ...!!
>
> Will work on this and if any doubts will check with you.
>
> Regards,
> Shruthima.
>
>
>
>
> From:Kevin Monroe <kevin.mon...@canonical.com>
> To:Matt Bruzek <matthew.bru...@canonical.com>
> Cc:Shruthima Almavar/India/IBM@IBMIN, juju <juju@lists.ubuntu.com>
> Date:02/11/2016 05:23 AM
> Subject:Re: Query on IBM-Installtion Manger Charm Layer
> --
>
>
>
> Hi Shruthima,
>
> We came up with what we think an IBM Installation Manager base layer might
> look like:
>
> *https://github.com/kwmonroe/layer-ibm-installation-manager*
> <https://github.com/kwmonroe/layer-ibm-installation-manager>
>
> This is not a functional layer yet (ie, it needs to do the actual IBM IM
> installation in ./reactive/ibm-installation-manager.sh), but we think this
> is a good starting point for a layer that can be extended by other IBM
> software (eg: WebSphere) that utilizes IBM IM for their install.  Check out
> the README at the above repo to see how we envision other charm layers
> using this IBM IM base layer.
>
> Take a look and let us know if you have any questions or concerns with
> this approach to providing a common IBM IM layer for others to extend.
>
> Thanks,
> Kevin
>
> On Fri, Feb 5, 2016 at 3:18 AM, Matt Bruzek <
> *matthew.bru...@canonical.com* <matthew.bru...@canonical.com>> wrote:
> Hello Shurthima,
>
> Thanks for reaching out to the Juju list. The layered approach is the way
> to write all new charms. We do recommend that you use the basic layer when
> creating a new base level feature such as IBM Installation Manager. To do
> that the layer.yaml should look like this:
> includes: ['layer:basic']
>
> As far as interface, I would have to know more about what services IBM IM
> can use or interact with. If IBM IM can talk to a database it should have a
> database relation. If the product has an web interface it should implement
> the http interface. You as the author knows the product better than I
> would. Interface layers make it very easy to use juju interfaces.
>
> We have some documentation about how to write layered charms, for more
> information please read:
>
> *https://jujucharms.com/docs/devel/developer-getting-started*
> <https://jujucharms.com/docs/devel/developer-getting-started>
>
> Please email the list if you have any more specific questions.  Thanks!
>
>- Matt Bruzek <*matthew.bru...@canonical.com*
> <matthew.bru...@canonical.com>>
>
> On Tue, Feb 2, 2016 at 12:34 PM, Shruthima Almavar <*salma...@in.ibm.com*
> <salma...@in.ibm.com>> wrote:
> Hello Team,
>
> I am working on IBM-Installation Manager charm and I will be developing
> this charm from layers .
>  i have explored on layers and thought to use basic layer which is present
> in "*http://int

[Review Queue] minecraft, rsyslog-fowarder-ha, zulu8, rlec, haproxy, apache2 (x2), fiche, midonet-gateway, collectd

[Kevin Monroe]

Hey Juju,

Andrew, Kostas, Cory, and I made our way through a slew of reviews.  It
went something like this:


   -

   minecraft
   -

  https://bugs.launchpad.net/charms/+bug/1523896
  -

  This is a rewrite of the precise minecraft charm, now using layers
  and targeting trusty.
  -

  We found a problem with the author’s ./trunk branch (possibly due to
  bzr artifacts between ‘charm build’ attempts), and suggested some test
  changes via a PR.  The author addressed both of these issues and
all looks
  good.
  -

  +1, promulgated, https://jujucharms.com/minecraft/trusty is live!
  -

   rsyslog-forwarder-ha
   -


  
https://code.launchpad.net/~johnsca/charms/trusty/rsyslog-forwarder-ha/lint/+merge/288469
  -

  Fixes lint issues
  -

  Previously, ‘make test’ would pollute the system with a version of
  PyYAML that was incompatible with ‘charm proof’. The author has
fixed this
  with tox.
  -

  +1, merged
  -

   zulu8
   -

  https://bugs.launchpad.net/charms/+bug/1519858
  -

  This is a layered bash charm that implements the java interface to
  provide a Zulu java environment.
  -

  Testing was successful, and while we created an MP for minor tweaks
  (e.g. decreasing log noise), this didn’t warrant holding it up
for further
  review.
  -

  +1, this is the first promulgated charm leveraging the java interface
  layer!
  -

   rlec (new redis charm)
   -

  https://bugs.launchpad.net/charms/+bug/1551133
  -

  Missing crypto hash verification of the download
  -

  Issues with handling of leadership and node registration
  -

  Some erroneous boilerplate from `charm create` template
  -

  We also offered relation suggestions
  -

  -1 for now while the author considers these points
  -

   haproxy (new statistics interface)
   -


  
https://code.launchpad.net/~verterok/charms/trusty/haproxy/statistics-interface/+merge/288005
  -

  Bundletester (still) works fine, make build with new test works too.
  However, I manually deployed and related to telegraf and couldn’t see any
  hooks fired related to statistics so have asked the author for
instructions
  to test further…
  -

  Author replied almost immediately and suggested I test against a
  different telegraf MR - it did and it worked, so +1 for merging.
  -

   Apache2 (timeouts fix)
   -


  
https://code.launchpad.net/~kwmonroe/charms/trusty/apache2/timeouts/+merge/287222
  -

  Adding some slack in the unit deployment timeout.
  -

  Tests pass.
  -

  +1 for merging
  -

   Apache2 (ensure_package_status fix)
   -


  
https://code.launchpad.net/~lutostag/charms/trusty/apache2/fix-extra-package-hold/+merge/287224
  -

  This fix is for a check on extra package installations that was
  producing a warning.
  -

  We reviewed the code and run a couple of tests.
  -

  +1, merged


   -

   fiche (new charm)
   -

  https://bugs.launchpad.net/charms/+bug/1530976
  -

  The author addressed our comments. However we asked for the layer
  that is used to build the charm.
  -

  Adam Israel jumped in to finish the review and promulgate (thanks
  Adam!)
  -

   midonet-gateway (new charm)
   -

  https://bugs.launchpad.net/charms/+bug/1541735
  -

  Review items addressed
  -

  Unable to run tests, but James offered to do so and give final sign
  off.
  -

  Otherwise, looks good from review.  +1
  -

   collectd (new charm)
   -

  https://bugs.launchpad.net/charms/+bug/1538573 and layer at
  https://code.launchpad.net/~jacekn/canonical-is-charms/collectd-composer
  -

  This is the third iteration over the collectd charm, and we
  appreciate the author’s dedication to addressing our comments!
  -

  Unfortunately, we spotted a small typo in the templating section that
  needs to be fixed. We also had some suggestions to improve the
README.  We
  submitted an MP to address both of these issues.
  - We’ll wait for the author’s input on our MP, but feel this is very
  close to promulgation.


Thanks for all the submissions - we found lots of great new additions
during this review.  Questions or comments?  Let us know in #juju on
freenode.  If we're not playing minecraft, we'll be right with you :)

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

[Review Queue] collectd, mysqltest, apache2 (x2)

[Kevin Monroe]

Hi folks,

Kostas, Cory, and I had some RQ time last week.  Here's what we found


   -

   collectd
   -

  https://bugs.launchpad.net/charms/+bug/1538573
  -

  The author addressed the comments we had on the previous review round.
  -

  A few minor issues still remain. We offered a small patch that
  addresses those as well. We should be able to  promulgate the charm soon.
  -

   mysqltest
   -

  https://bugs.launchpad.net/charms/+bug/1513863
  -

  Suggested changes were made, and it has now been promulgated!
  -

   apache2 (add-logs-interface)
   -


  
https://code.launchpad.net/~evarlast/charms/trusty/apache2/add-logs-interface/+merge/278222
  -

  Suggested changes were made, and it has now been merged!
  -

   apache2 (add apt config options)
   -


  
https://code.launchpad.net/~evarlast/charms/trusty/apache2/trunk/+merge/278220
  -

  Jay thoughtfully fixed test errors (even though he didn’t introduce
  them) in the ‘add-logs-interface’ merge mentioned above.
  -

  There are a couple more (i think small) test / logic issues that we
  had questions about, so we requested Jay’s input on those.


Questions/concerns?  We're in #juju on irc.freenode.net.  Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Query on IBM-Installtion Manger Charm Layer

[Kevin Monroe]

Hi Shruthima,

We came up with what we think an IBM Installation Manager base layer might
look like:

https://github.com/kwmonroe/layer-ibm-installation-manager

This is not a functional layer yet (ie, it needs to do the actual IBM IM
installation in ./reactive/ibm-installation-manager.sh), but we think this
is a good starting point for a layer that can be extended by other IBM
software (eg: WebSphere) that utilizes IBM IM for their install.  Check out
the README at the above repo to see how we envision other charm layers
using this IBM IM base layer.

Take a look and let us know if you have any questions or concerns with this
approach to providing a common IBM IM layer for others to extend.

Thanks,
Kevin

On Fri, Feb 5, 2016 at 3:18 AM, Matt Bruzek 
wrote:

> Hello Shurthima,
>
> Thanks for reaching out to the Juju list. The layered approach is the way
> to write all new charms. We do recommend that you use the basic layer when
> creating a new base level feature such as IBM Installation Manager. To do
> that the layer.yaml should look like this:
>
> includes: ['layer:basic']
>
>
> As far as interface, I would have to know more about what services IBM IM
> can use or interact with. If IBM IM can talk to a database it should have a
> database relation. If the product has an web interface it should implement
> the http interface. You as the author knows the product better than I
> would. Interface layers make it very easy to use juju interfaces.
>
> We have some documentation about how to write layered charms, for more
> information please read:
>
> https://jujucharms.com/docs/devel/developer-getting-started
>
> Please email the list if you have any more specific questions.  Thanks!
>
>- Matt Bruzek 
>
> On Tue, Feb 2, 2016 at 12:34 PM, Shruthima Almavar 
> wrote:
>
>> Hello Team,
>>
>> I am working on IBM-Installation Manager charm and I will be developing
>> this charm from layers .
>>  i have explored on layers and thought to use basic layer which is
>> present in "http://interface.juju.com; but not sure about it ??
>>  Could you please suggest me  which layer and interface i can use for
>> charming IBM-IM product. Thanks.
>>
>>
>> Regards,
>> Shruthima
>>
>>
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

jujubigdata 6.0.0 is released

[Kevin Monroe]

(x-post to juju for awareness of library incompatibility affecting Big Data
charms)

Hi folks, the jujubigdata 6.0.0 release is now generally available:

https://pypi.python.org/pypi/jujubigdata/6.0.0

All charms referencing "jujubigdata>=6.0.0,<7.0.0" will pick up the most
recent 6.x.x release during deployment.  This major release includes MapReduce
compression and logging configuration that makes it incompatible with
charms that require jujubigdata < 6.

If there are no objections from users of charms in the ~bigdata-dev
development namespace, we will move ~bigdata-dev charms from v5 to v6 later
this week.  Promulgated Big Data charms will continue to use v4 while v6 is
scrutinized -- there are no plans to promulgate charms using jujubigdata v5.

Commit log from 5.0.0 - 6.0.0:

342d86f [Kevin W Monroe] bump VERSION for major release
81bbcb2 [Kevin W Monroe] fix e731 lint error
e67499e [Kevin W Monroe] remove unused envars
87cd5d9 [Kevin W Monroe] mapred changes: use log_dir, remove unused
pid_dir, add config so historyserver shows job history
8e3fade [Andrew McLeod] added compression to core-site.xml and
mapred-site.xml
7de5f4f [Cory Johns] Enable DistConfig to accept data as param instead of
file
896cf62 [Cory Johns] Fixed HDFS.configure_client for layered charms
c80cc87 [Kevin W Monroe] bump VERSION for bugfix release
b3fc4ce [Kevin W Monroe] charmhelpers docs lie! getrange does not return an
empty dict, nor is there an unset range method. fix both instances where we
were lead astray.
526f923 [Kevin W Monroe] bump version for minor release
93e67a2 [Cory Johns] Fixed java version handling if release not in version
b7dc0f0 [Cory Johns] Fixed typo in method name
56b04a7 [Cory Johns] Update remove_kv_host(s) helper
91a902b [Cory Johns] Fix backwards compatibility
977823f [Cory Johns] Fix error in hack-around
f21e9fd [Cory Johns] Added remove_kv_hosts helper
0279cb9 [Cory Johns] Added helpers for layered charms
359c75e [Cory Johns] Fixes for the hadoop-base and apache-hadoop-namenode
495ccc3 [Kevin W Monroe] bump VERSION for bugfix release
fd5b14a [Konstantinos Tsakalozos] Iterate over dict items in a py2 & py3
compatible way
0ffb495 [Andrew McLeod] re-fixed as per PR # 26 req
3d87a03 [Andrew McLeod] re-fixed as per PR # 26 req
e51e117 [Andrew McLeod] added decode of utf8 for split
fbfb109 [Kevin W Monroe] bump VERSION for major release

If you'd like to discuss these changes, chime in on bigd...@lists.ubuntu.com
or find us in #juju on Freenode.

Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] nfs, zulu8, saiku, nuage, quobyte, apache2

[Kevin Monroe]

Happy 2016 folks!

The Big Data team has been rocking the queue this year, and I had the
pleasure of announcing our RQ time last week.  Unfortunately, I didn't get
the note sent out, so I got the chance to cover this week's RQ time as
well!  Here's what we found:

Jan 14, 2016:

   -

   nfs
   -


  
https://code.launchpad.net/~freyes/charms/trusty/nfs/lp1433036/+merge/280365
  -

  known not to work in lxc on trusty, bundletesting on AWS
  -

  test attempts to deploy ‘precise/owncloud’ charm from the store which
  appears to be broken:
  -

 0.shared-fs-relation-changed logger.go:40
 
/var/lib/juju/agents/unit-owncloud-0/charm/hooks/shared-fs-relation-changed:
 line 55: [: missing `]
 -

  Asked the author if an owncloud change is needed to support this
  update
  -

   zulu8
   -

  https://bugs.launchpad.net/charms/+bug/1519858
  -

  missing tests, so we requested Azul dupe the recent openjdk tests:
  -


 
https://code.launchpad.net/~kwmonroe/charms/trusty/zulu8/add-tests/+merge/282681



Jan 8, 2016:

   -

   saiku analytics - enterprise
   -

  https://bugs.launchpad.net/charms/+bug/1524715
  -

  Found 2 issues causing test failures; suggested fixes
  -

   nuage-vrs
   -

  https://bugs.launchpad.net/charms/+bug/1420995
  -

  All charm proof issues resolved
  -

  Conditional restart logic added and seems good
  -

  Tests (unit) added, look good, and pass
  -

  Provided some feedback and suggested improvements, the with the main
  suggestions dealing with how to avoid a charm error state when
blocked was
  intended, and how to avoid an immutable config option
  -

  Unfortunately, we can’t fully test the charm without access to the
  repos
  -

   quobyte new charms
   -

  quobyte-webconsole https://bugs.launchpad.net/charms/+bug/1527679
  -

  quobyte-api https://bugs.launchpad.net/charms/+bug/1527676
  -

  quobyte-metadata https://bugs.launchpad.net/charms/+bug/1527674
  -

  quobyte-registry https://bugs.launchpad.net/charms/+bug/1527672
  -

  quobyte-data https://bugs.launchpad.net/charms/+bug/1527673
  -

  The charms above deploy the Quobyte Storage System availubale at
  https://code.launchpad.net/~3-bruno/charms/trusty/quobyte-metadata/trunk
  -

  At this point we cannot proceed with the above charms primarily
  because there is no adequate testing.
  -

  We suggested two options to the authors, add tests and/or create a
  bundle that would deploy all services and test the storage system as a
  whole.
  -

   apache2 - add-logs-interface
   -


  
https://code.launchpad.net/~evarlast/charms/trusty/apache2/add-logs-interface/+merge/278222
  - Test concern was addressed, but a possible corner-case was spotted
  and the README should be updated to document this new interface.


Questions/concerns?  We're in #juju on freenode.  Thanks!
-Kevin
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Query on Mariadb Charm Deployment on Ubuntu Power ppc64le

[Kevin Monroe]

Hi Prabakaran,

If you executed these commands as written, you were trying to run mysql on
your juju host machine (versus the mariadb unit):

*Commands:*
*juju deploy mariadb*
*juju set mariadb dataset-size="256M"*
*mys**ql -u root -p$(sudo cat /var/lib/mysql/mysql.passwd)*

I think you just need to preface that 3rd command with 'juju run
--service=mariadb'.  I was able to deploy, set config, and verify on
ppc64le using this in place of your 3rd command:

$ juju run --service=mariadb 'mysql -u root -p$(sudo cat
/var/lib/mysql/mysql.passwd) -e status'
--
mysql  Ver 15.1 Distrib 5.5.46-MariaDB, for debian-linux-gnu (ppc64le)
using readline 5.2

Connection id: 28
Current database:
Current user: root@localhost
SSL: Not in use
Current pager: stdout
Using outfile: ''
Using delimiter: ;
Server: MariaDB
Server version: 5.5.46-MariaDB-1ubuntu0.14.04.2-log (Ubuntu)
Protocol version: 10
Connection: Localhost via UNIX socket
Server characterset: latin1
Db characterset: latin1
Client characterset: latin1
Conn.  characterset: latin1
UNIX socket: /var/run/mysqld/mysqld.sock
Uptime: 38 sec

Hopefully that helps!
-Kevin

On Wed, Dec 9, 2015 at 5:25 AM, Prabakaran Chandrasekaran <
praba...@in.ibm.com> wrote:

> Hello Team,
>
> I have deployed Mariadb charm from charm store on Ubuntu Power ppc64le.
>
> Post deployment I got it into the container where mariadb is installed and
> tried to access Mariadb by running the command "*mysql -u root -p$(sudo
> cat /var/lib/mysql/mysql.passwd)*" and I was getting an error stating "*ERROR
> 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)*". Below are the command which i ran to
> deploy and check mariadb.
>
> *Commands:*
> * juju deploy mariadb*
> * juju set mariadb dataset-size="256M"*
> *mys**ql -u root -p$(sudo cat /var/lib/mysql/mysql.passwd)*
>
> *Charm Link* : https://jujucharms.com/mariadb/
>
> Can you give me some directions on how to resolve this issue? And also
> advise should i raise bug against this charm?
>
> *Note:* *I am facing this issue while deploying mariadb charm in Power
> machine only*
>
> Thanks and Regards,
> Prabakaran
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] wordpress, mysqltest, mediawiki, haproxy

[Kevin Monroe]

Hi!

The Juju Big Data team had some time in the review queue today.  It was
especially exciting as this was our first review session with our newest
team member, Konstantinos!  Here's what we found:


   -

   wordpress
   -


  
https://code.launchpad.net/~tvansteenburgh/charms/trusty/wordpress/test-fixes/+merge/276894
  -

  Fixes for tests
  -

  Applied cleanly, all tests passed
  -

  +1, this has been merged and should be in the charm store shortly
  -

   mysqltest
   -

  https://bugs.launchpad.net/charms/+bug/1513863
  -

  This is a new charm that provides functional tests for mysql
  -

  Currently failing automated CI, and has some other questions and
  concerns to be addressed
  -

  -1 for now
  -

   mediawiki
   -


  
https://code.launchpad.net/~tvansteenburgh/charms/trusty/mediawiki/test-fixes/+merge/277054
  -

  Fixes for tests
  -

  Applied cleanly, all tests passed
  -

  +1, this has been merged and should be in the charm store shortly
  -

   haproxy
   -


  
https://code.launchpad.net/~verterok/charms/trusty/haproxy/restart-rsyslog-after-install/+merge/268981
  -

  Restart rsyslog if haproxy config changes
  -

  Needed to tweak tests to reference units correctly
  -

 d.sentry[‘haproxy’][0] instead of d.sentry.unit[‘haproxy/0’]
 -

  Applied cleanly, all tests passed
  -

  +1, this has been merged and should be in the charm store shortly


Questions/comments?  We're in #juju on irc.freenode.net.

Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

charm license requirements with multi-licensed payloads

[Kevin Monroe]

Hi folks,

Our big data charms (apache licensed) deploy Hadoop (apache licensed).
Hadoop supports various compression codecs, with one of the more popular
being lzo.  lzo is GPLv2 licensed and therefore not distributed with Hadoop.

As a charm author, what is my licensing obligation if I want my charm to
install lzo on top of Hadoop?  Fwiw, the charm would fetch both hadoop.tgz
and lzo.tgz from an external repo at install-time, so neither payload is
bundled into the charm.  I assume this absolves me of any special licensing
in my charm source, but I'd like to get a +1 on that.

As the maintainer of an external repo, are there licensing obligations for
hosting charm payloads?  I assume I could put a NOTICE in the root of the
repo that says "hadoop.tgz is apache licensed (link to license).  lzo.tgz
is gplv2 (link to source and license)."

The sticky part to me is that no one would likely find my NOTICE in the
repo, so I'm curious if I should put it directly in the charm source.  Is
anyone else dealing with charm payloads of differing licenses?  How did you
handle it?

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

[Review Queue] Zulu8, XL Fortran, xCAT

[Kevin Monroe]

Hi folks - Amir, Andrew, and I took a look at the following this week:

+ Zulu8
https://bugs.launchpad.net/charms/+bug/1477661

This is a followup from last week. We're mighty close to landing this
OpenJDK fork in the store.  We had some minor issues with the copyright
file and an unused hook, so we suggested updates to resolve them.
Apologies to the charm author for not spotting these in the initial review!


+ IBM XL Fortran
https://bugs.launchpad.net/charms/+bug/1489345

PRINT *, "There were a couple minor problems here (missing icon, tests only
possible with a local juju environment).  The charm author was very
responsive and has already committed fixes for these, so we look forward to
trying this out soon!"
END


+ xCAT
https://bugs.launchpad.net/charms/+bug/1441622

We couldn't get very far with this one as the config-change hook failed to
retrieve packages required for test.  We notified the author about the 404s
and hope to see these resolved for the next go-round.


Questions/comments?  We're in #juju on freenode.  Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

i want in (to ~charmers)

[Kevin Monroe]

Hey Charmers,

I was waiting for a sufficient amount of time to pass after aisrael applied
to ~charmers because no one can follow that...  But then cory_fu threw his
hat in the ring.  These guys are giants in our space, and I'm humbled to
get to work with them.

That said, I'm ready to apply to ~charmers myself.  I've been with the Juju
Eco team for about a year now.  If you compared my first charm (all 1GB of
db2 express) to my latest Apache Flume offerings, you'd +1 me for most
improved without hesitation.  Like Cory, I'm mostly focussed on Big Data
charms (for which I've authored a metric boat load).  I'm also proud of my
contributions to the ecosystem with doc merges, speaking at local meetups,
charm schools, and ISV work.

I've done my fair share of Review Queue work over the last year, and like
pornography, I know what a good charm looks like.  I'd be honored to change
my lower third to 'Juju Charmer' if you'll have me.

Thanks for your consideration!
-Kevin
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] gluster, docker, and new big data (spark/zeppelin/pig/hive)

[Kevin Monroe]

Hi folks!  Cory and I hit a couple review queue items today:

+ gluster
https://bugs.launchpad.net/charms/+bug/1469213

This was a real treat.  Not only have I been looking for a reason to try
out this fancy network filesystem, but I've also been wondering what's so
great about rust.  This charm helped me on both fronts (yup, it really has
a rust component [1]).  I'm happy to say we didn't hit any segfaults, but
unfortunately can't +1 it at this time.

Though the deployment was successful, we had reservations on a missing
config-changed hook and would like to see the readme and tests polished a
bit more prior to hitting the store.  Overall, this is a great submission
and I look forward to working more with Chris to see this through
promulgation.

+ docker
https://code.launchpad.net/~lazypower/charms/trusty/docker/trunk/+merge/260867

This was a refresh to v0.1.3 of the docker charm.  We noted some missing
hooks in the review, but overall deployment and amulet tests looked good.

We were stumped by a mysterious docker_opts.py module in this ansible
charm, but luckily had Whit to explain this was a mechanism to translate
hook events into docker runtime options. We requested this be documented a
bit better in the class and have some unit tests to make its utility more
obvious [2].

+ Big 'ol Data
I forgot to fire off a note to the list about our Q time last week.  For
those that don't know, Amir, Cory, and I make up the Big Data charmers team
at Canonical.  Last week we spent some time polishing our own bits and
we're excited to shepherd these into the store:
  - apache-spark: a fast big data processing engine
https://bugs.launchpad.net/charms/+bug/1463012
  - apache-zeppelin: notebook for interactive data analytics
https://bugs.launchpad.net/charms/+bug/1463026
  - apache-hive: data warehouse for query and analytics (think sql)
https://bugs.launchpad.net/charms/+bug/1468769
  - apache-pig: data analysis with the high-level Pig language
https://bugs.launchpad.net/charms/+bug/1468768


That's a wrap from us.  It's been a pleasure!  Find us on freenode #juju
(asanjar, cory_fu, kwmonroe) with any questions/comments.

Refs:
[1]
http://bazaar.launchpad.net/~xfactor973/charms/trusty/gluster/trunk/view/head:/src/main.rs
[2] https://github.com/chuckbutler/docker-charm/issues/54

Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue] python-django, rabbitmq-server, nrpe

[Kevin Monroe]

Hello friends!  Amir, Cory, and I had some 'que last week:

+ python-django
https://code.launchpad.net/~nicopace/charms/trusty/python-django/allowed_host_patch/+merge/254958

This was a bugfix MP from Nico.  An empty config option was not being
handled correctly, resulting in page request failures.  Nico fixed this by
properly setting defaults when the config option is empty, and we were able
to verify successful page requests with his changes merged.  +1

+ nrpe
https://code.launchpad.net/~gnuoy/charms/trusty/nrpe/services-rewrite/+merge/253799
https://bugs.launchpad.net/charms/+bug/1430732

This is a trusty rewrite for precise/nrpe-external-master and the current
trusty/nrpe.  We consolidated the bug and MP into a single review queue
item with future discussion about this charm taking place in the MP.  There
are a couple lint and test issues that Adam has raised in the bug, but the
refactor looks good overall.  We were successful in using nrpe from this
branch in testing a rabbitmq MP (below).  Once lint and test have been
resolved, we're confident in giving our +1.

+ rabbitmq-server
https://code.launchpad.net/~thedac/charms/trusty/rabbitmq-server/queue-monitoring/+merge/255025

This MP adds support for queue monitoring by nagios. This is dependent on
the Trusty rewrite of nrpe (above) -- we were able to get the included test
to pass using the nrpe branch under review.  That said, we'd like to see
the manual instructions encapsulated in an Amulet test so auto-testing can
exercise this functionality. We also noted 2 upstream bugs, and while
they're not directly related to this MP, they will need to be fixed to get
this charm 100% passing.

Thanks!
-Kevin Monroe
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

[Review Queue]: mysql x 2, elasticsearch

[Kevin Monroe]

Hey folks,

Amir, Cory, and I tackled a few reviews in the queue:

+ mysql (shared-db refactor)

https://code.launchpad.net/~hopem/charms/trusty/mysql/contrib-database-mysql/+merge/248743
Cory manually deployed and related to the lamp charm to exercise this
relation. It looks good, so we think the azure failure was due to a network
hiccup. +1.

+ mysql (scaling test)

https://code.launchpad.net/~nicopace/charms/trusty/mysql/scaling-test/+merge/245433
Test failure is valid and exposes an issue in the MySQL charm.  Policy
has been to approve such test MPs.
Amir requested that the issue be tested against Maria DB as well.

+ elasticsearch

https://code.launchpad.net/~evarlast/charms/trusty/elasticsearch/add-version-config/+merge/237916
We chatted with Jay about this one, and for now, the feature is no
longer needed.
Kevin commented in the MP to recommend its closure, and also noted
potential immutable config concerns if this feature is ever re-visited.

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

[Review Queue] Openbook

[Kevin Monroe]

Openbook is a cloud billing solution from Talligent.  They charmed it up
and are proposing it for inclusion in the charm store.

The charm is really well documented and relates to mariadb and tomcat.
While peer reviewing with Cory, we noticed the relation to tomcat was over
the implicit juju-info.  Though this is common for subordinate charms
relating to tomcat, it isn't ideal -- it makes openbook capable of
colocating on any unit (since all units provide juju-info). See Cory's RQ
note from this morning for more info.  When tomcat is updated, we'll circle
back to all tomcat subordinates and suggest an updated relation.

Back to openbook -- following the readme was simple, and deployment went
smoothly.  This charm didn't include tests, so we can't recommend it in the
store just yet.  I proposed a simple test for inclusion and offered
suggestions in case they want to expand on mine.  I look forward to
re-reviewing once tests fall into place.

https://bugs.launchpad.net/charms/+bug/1411402

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

A charmer's first 5 minutes

[Kevin Monroe]

Good day,

Earlier this month, an elite squad of Rosales henchmen assembled in a war
room in Western Europe. Led by Randall Ross, their objective was to define
a new charm author's first five minute experience.

Code named a new charm author's first five minute experience, the gist of
their secret meeting has been leaked:

https://gist.github.com/kwmonroe/bbafc23c1f04f756ba22

Please take a moment to read over that and provide feedback.  The intent is
to have 1 walk-through for new charmers.  It's simple, takes 5(ish)
minutes, and hopefully leaves the reader wanting more -- which is where our
in-depth walk-throughs will take over.

The motivation here is that our current docs have multiple places that take
a reader through creating a charm (one for vagrant, one in the charm
walk-through, etc).  We want to fix that and control the new charm author's
experience a bit better.

Questions I could use answers to:

1 - we're installing apache and changing the homepage.  is that too
simple?  can we show off more complexity and still fit in our 5 minute
window?

2 - run through the exercise.  does it take 5 minutes?  if it's too long,
can you identify some verbosity that can be removed?

3 - spelling/grammar/layout problems?  please comment.

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