Please post an issue at
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/new
The issue template contains instructions for gathering debug info from the
cluster.
On Fri, Apr 27, 2018 at 11:37 AM, sSeBBaSs wrote:
> Hi Guys,
>
> Today I was able to correctly deploy a kubernetes
I've hit this too (https://github.com/conjure-up/conjure-up/issues/1392).
The important bit from the log is:
2018-04-26 16:42:13,390 [ERROR] conjure-up/canonical-kubernetes -
juju.py:741 - cannot change profile for the next exec call: No such file or
directory
The error happens when conjure-up run
Sorry for the confusion guys. This program is no longer active and the page
is being taken down.
If you (or others) come across links to http://developer.juju.solutions,
please let me know so I can remove them.
On Mon, Dec 18, 2017 at 12:03 AM, Nadeem Idrees
wrote:
> Agreed, if this program is
Hi Steven,
Sure, can you `charm publish` your charm please (it's not currently in the
the stable channel). See `charm publish -h` for more info.
Thanks,
Tim
On Mon, Dec 4, 2017 at 6:59 PM, Steven Sweeting
wrote:
> Hi,
>
>
>
> I’d like to respectively request that our new charm sme be considere
Done.
On Mon, Nov 20, 2017 at 8:01 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Hi all
>
>
> ~tengu-team/openvpn is a promulgated charm, but I'm not able to push an
> update to the store:
>
> $ charm release cs:~tengu-team/openvpn-10
> ERROR cannot release charm or bundle: access
On Mon, Sep 18, 2017 at 6:22 AM, James Page wrote:
> Resurrecting this thread; I think its a good time to push on with this
> work - anyone have any objections to targeting this week to complete the
> migration?
>
+1, no objections from me, thanks James!
> On Fri, 21 Jul 2017 at 19:55 David A
Fantastic, this is a great change - well done!
On Fri, Sep 8, 2017 at 2:39 PM, Cory Johns wrote:
> Greetings,
>
> Today we migrated the index of base and interface layers used to build
> charms over to the GitHub repository https://github.com/juju/layer-index.
> Hosting the index in GitHub provi
On Fri, Sep 8, 2017 at 2:44 PM, Tom Barber wrote:
> good effort devs!
>
+1, thanks Cory.
>
> On 8 Sep 2017 7:42 pm, "Cory Johns" wrote:
>
>> Greetings,
>>
>> I just wanted to make a quick announcement that the charm snap is now
>> strictly confined on the stable channel (rev 17). This fixes
The new bundle stuff is very useful, thanks Juju devs!
On Fri, Sep 8, 2017 at 3:43 AM, Burton Swan
wrote:
> ## New and Improved
>
> * The remove-machine command has a --keep-instance flag which allows the
> cloud instance to be left running when the machine is removed from the Juju
> model
>
> *
vsphere"
>
> cloud-config:
>
> - "/etc/vsphere/vsphere.conf"
>
> When triggering a containerized installation, only the /etc/origin and
> /var/lib/origin directories are mounted to the master and node container.
> Therefore, node-config.yaml must be in /etc/origin/no
Hi Micheal,
Have you enabled the vsphere cloud provider for kubernetes as documented
here: https://kubernetes.io/docs/getting-started-guides/vsphere/ ?
Tim
On Thu, Sep 7, 2017 at 4:06 AM, Micheal B wrote:
> While working through -- https://github.com/kubernetes/
> examples/tree/master/staging/
Hi Micheal,
1. The topology of the cluster is encoded as yaml in the bundle itself,
e.g.
https://api.jujucharms.com/charmstore/v5/~containers/bundle/canonical-kubernetes/archive/bundle.yaml
2. The yaml for the objects deployed in your cluster are typically kept in
your own source control repo.
3.
Hi Micheal,
You don't get the external IP automatically because the k8s cloud-provider
flag is not automatically set to vsphere for you (yet).
When you deploy to AWS with conjure-up, we set the k8s cloud-provider for
you so that you can use AWS features like ELBs and EBS. We intend to add
this na
Done.
On Tue, Sep 5, 2017 at 11:55 AM, Tom Haddon
wrote:
> Hi Folks,
>
> Could we get cs:~influxdb-charmers/influxdb promulgated?
>
> The code for the charm is https://code.launchpad.net/influxdb-charm and
> there's
> a team that maintains it https://launchpad.net/~influxdb-charmers. The
> charm
Done.
On Mon, Sep 4, 2017 at 5:35 AM, Tom Haddon wrote:
> Hi Folks,
>
> Could we get cs:~apache2-charmers/apache2 promulgated?
>
> The code for the charm is https://code.launchpad.net/apache2-charm and
> there's
> a team that maintains it https://launchpad.net/~apache2-charmers. The
> charm
> su
Awesome feature and write-up, thanks Stuart!
On Fri, Sep 1, 2017 at 10:28 AM, Stuart Bishop
wrote:
> Hi.
>
> The PostgreSQL charm has some point in time recovery features we have
> been using on production. I've put together a walk through of the
> feature for others who might be interested in u
This works for me:
kubectl run -it db2express-c --port=5 --env DB2INST1_PASSWORD=db2inst1
--env LICENSE=accept --image ibmcom/db2express-c:latest -- bash
On Thu, Aug 31, 2017 at 3:17 PM, Micheal B wrote:
> Trying to convert a Docker run to kubectl
>
>
>
> Working thru
>
>
>
> https://hub.do
It's been promulgated, thanks!
On Wed, Aug 30, 2017 at 7:08 PM, Haw Loeung
wrote:
> On Wed, Aug 30, 2017 at 02:38:42PM -0400, Tim Van Steenburgh wrote:
> > I checked with James Beedy and he's +1 on promulgating this one too.
> >
> > Looks like there's no b
Thanks Frode, welcome to ~charmers!
On Wed, Aug 30, 2017 at 4:10 PM, David Ames
wrote:
> Huge +1
>
> On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl
> wrote:
> > Dear Juju community,
> >
> > I would like to officially apply for membership of the Juju ~charmers
> team.
> >
> > Through the course
On Wed, Aug 30, 2017 at 6:27 AM, Haw Loeung
wrote:
> On Tue, Aug 22, 2017 at 08:54:14AM +0100, Tom Haddon wrote:
> > On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote:
> > [...]
> > > I checked with some of the ~onlineservices-charmers team and they were
> happy
> > > for https://jujucha
Done, thanks!
On Wed, Aug 30, 2017 at 4:38 AM, Tom Haddon
wrote:
> Hi Folks,
> Could we get cs:~prometheus-charmers/grafana promulgated?
>
> The code for the charm is https://code.launchpad.net/grafana-charm and
> there's
> a team that maintains it https://launchpad.net/~prometheus-charmers. Tha
Done, thanks!
On Thu, Aug 24, 2017 at 11:13 PM, Haw Loeung
wrote:
> Hi All,
>
> Could I get cs:~graylog-charmers/graylog promulgated?
>
> We're using it internally will maintain it.
>
> It's also set up as a new team in Launchpad so we could add community
> members on request.
>
>
> Regards,
>
>
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/
>> elas
There's already a top-level elasticsearch charm.
https://jujucharms.com/elasticsearch/
On Mon, Aug 14, 2017 at 12:13 PM, James Beedy wrote:
> Request for promulgation of Elasticsearch. The Elasticsearch charm can be
> found at cs:~jamesbeedy/elasticsearch-7.
>
> Thanks,
>
> James
>
> --
> Juju m
howing the amount of (successful) deploys or smth?
>
> On Aug 4, 2017 16:21, "Tim Van Steenburgh" com> wrote:
>
>> Hi All,
>>
>> I wanted to send a note about some changes in the way we handle charm
>> reviews and the top-level namespace of the charm st
Done.
On Fri, Aug 4, 2017 at 9:51 PM, Adam Stokes
wrote:
> Hi,
>
> Could I get cs:~adam-stokes/dokuwiki-32 promulgated?
>
> Thanks!
> Adam
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
--
Juju mailin
open reviews will be closed with a comment/email linking to this
explanatory post. Anyone with an open review that still desires
promulgation can request it with an email to this list.
If you have any questions or concerns, please reply to this post!
Thanks,
Tim Van Steenburgh
--
Juju mailing list
+1 and approved, thanks Billy.
On Fri, Jul 21, 2017 at 8:41 AM, Billy Olsen
wrote:
> Hello Charmers,
>
> My name is Billy Olsen and I've been a long time contributor to the
> OpenStack Charms, going back 3 years now. I'm currently a core member of
> the OpenStack charming community and have addi
Hi everyone,
We’re proud to announce support for Kubernetes 1.7 in the Canonical
Distribution of Kubernetes. This release includes the latest upstream
version of Kubernetes, along with various fixes and improvements to the
charms which comprise the Kubernetes bundles.
Here’s the simplest way to g
>
> But, I couldn't. The review form at https://review.jujucharms.com/ will
> respond with a empty response (Firefox says https protocol error. Chrome
> says empty response.)
> Where would I report that as a bug?
>
>
There's a "report bug" link at the bottom of the review queue web pages. I
went ah
On Thu, May 25, 2017 at 12:59 PM, Giuseppe Attardi wrote:
> I have written a charm for OpenStack Gnocchi.
> The service requires a postgresql database relation.
>
> The start hook fails, of course, because the relation is not set.
>
> I expected that, but I expected that when I issue
>
>
+1 from me, especially since James is volunteering. :D Thanks for getting
this ball rolling!
On Thu, May 25, 2017 at 8:57 AM, James Page wrote:
> Hi Charmers
>
> There has been a bubbling undercurrent of desire to move charmhelpers code
> hosting out of bazaar on Launchpad to git on github,com
em
>>> 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:
o
> ask to upgrade your quota.
>
> ++
> Sam
>
> On Mar 14, 2017 13:48, "Tim Van Steenburgh" com> wrote:
>
>> 2.1.1 juju client and controller, controller bootstrapped in
>> aws/us-east-1:
>>
>> juju deploy ./kubernetes-worker --constraints &
2.1.1 juju client and controller, controller bootstrapped in aws/us-east-1:
juju deploy ./kubernetes-worker --constraints
"instance-type=p2.xlarge" kubernetes-worker-gpu
Deploying charm "local:xenial/kubernetes-worker-1".
ERROR cannot add application "kubernetes-worker-gpu": invalid
constraint val
Hi everyone,
The most recent episode of The Juju Show features an introduction to the
new python library for Juju. The libjuju segment of the show is about 20
minutes long and starts here:
https://youtu.be/Lsbo7f7yMxY?t=14m
If you're interested in interacting with Juju from Python, check it out!
Yeah, thanks for bringing this up. I think that your strawman is the
correct approach. To make this happen we really just need to keep the old
facade versions around instead of blowing them away every time we
regenerate the facades for a new version of juju.
On Wed, Jan 18, 2017 at 2:38 PM, Adam C
ata&include=bundle-unit-count&
> include=bundles-containing&include=charm-actions&include=
> charm-config&include=charm-metadata&include=common-info&
> include=extra-info&include=revision-info&include=stats&
> include=supported-series&includ
You need to define the services in the deployment, even if they are already
deployed
by bundletester. So for example:
cls.deployment.add('docker')
cls.deployment.add('limeds')
On Mon, Jan 16, 2017 at 10:15 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Hi all
>
>
> Code: https://g
Hi everyone,
v0.1.0 of the new 'juju' library for Python has been released. Installation
instructions and documentation are available at
https://pythonhosted.org/juju/.
There is still plenty to do, but a number of people and projects are
already using the library in its current form. Please kick
y since OpenVPN doesn't work in LXD containers.
>
> 2016-12-06 17:53 GMT-05:00 Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com>:
>
>> Try installing python-jujuclient from ppa:tvansteenburgh/ppa. It has some
>> fixes
>> that aren't in stable yet.
>>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> python-jujuclient is already the newest version (0.50.5-0ubuntu1).
>
>
> 2016-12-06 17:46 GMT-05:00 Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com>:
>
>>
r.py",
> line 64, in parse_env
> 'password': account['password'],
> KeyError: 'password'
> /usr/local/lib/python3.5/dist-packages/path.py:1717: DeprecationWarning:
> path is deprecated. Use Path instead.
> warnings.warn(msg, DeprecationW
trick of the first error. Now I
> get a bunch of linter errors. I'll fix those and get back to you if I run
> into any more errors. The tox thing seems like a bug in bundletester.
> Shouldn't bundletester install tox if it is a dependency for all tests?
>
>
>
> K
The second error won't really matter once you get things working with
bundletester,
but that error generally happens when you run an amulet test (for a local
charm)
directly and your cwd is not the charm dir, or some dir beneath it. Try
running it from
the charmdir instead.
On Tue, Dec 6, 2016 at
The first problem is because `make test` runs tox, but tox isn't installed.
You can
add it to your packages list in tests.yaml. I would also recommend changing
the
shebang line of your 10-deploy test to #!/usr/bin/env python3
On Tue, Dec 6, 2016 at 4:25 PM, Merlijn Sebrechts <
merlijn.sebrec...@gm
Hi everyone,
To follow up on ideas discussed at the past Juju Charmer summit, we've been
working to improve the Juju Charm review queue experience. The Juju Charm
Store is no longer tied to Launchpad, and thus we no longer rely on branch
merges and auto-ingestion to get reviewed items into the s
Hi everyone,
Since we're working on an api client, I wanted to be able to run
post-commit tests against a real Juju controller or model, using Travis-CI.
One caveat with Travis-CI is that they don't support xenial vms yet, so you
have to use trusty. If you can live with that, here's a .travis.yml
trying to figure it out, but if anyone has any pointers that'd be
great.
On Sat, Nov 5, 2016 at 6:44 PM, Francesco Banconi <
francesco.banc...@canonical.com> wrote:
>
> > On 5 Nov 2016, at 23:07, Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com> wrote:
>
Identity manager and SSO with macaroons. You'll have them in
> ~/.go-cookies and ~/.local/share/juju/usso-store-token (or something like
> that).
>
> Feel free to ask in #jaas
>
> On Fri, Nov 4, 2016 at 6:51 PM, Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com>
If I `juju register` a shared controller and add a model to it, how does
the juju client authenticate to that model, since AFAICT there is no
password locally? I'm asking b/c I need to be able to make other clients
(python) work for this case. For the heck of it I tried with a blank
password but go
anks to the Saiku community we reached our Kickstart
> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
> goal, but you can always help by sponsoring the project
> <http://www.meteorite.bi/products/saiku/sponsorship>)
>
> On 1 November 2
Hi everyone,
We've been working on a new python client for Juju. It's still in
development,
but we wanted to share the first bits to illicit feedback:
https://github.com/juju/python-libjuju
Features of this library include:
* fully asynchronous - uses asyncio and async/await features of python
These new releases work with the latest juju-2.0 betas while maintaining
compatibility with juju-1.25.
They are currently available on PyPI and in ppa:tvansteenburgh/ppa, and
will likely be copied to ppa:juju/stable in the near future.
Find bugs? File here:
https://bugs.launchpad.net/python-jujuc
Have you tried including the db name when connecting, e.g.:
mysql -h db_host -u db_user -p db_pass -D `relation-get database`
Pretty sure you only get perms to the database created for you when you
join the relation.
On Mon, Jun 20, 2016 at 5:51 AM, Rajith P Venkata
wrote:
> Hi
>
> I am connec
rtbeat. If you want
> application specific monitoring, you'll need the NRPE agent or to implement
> it on the charm so it knows what to check.
>
> It does the bare minimum by default which i believe to be: "is the host
> still alive?"
>
> On Mon, May 16, 2016 at 9:33 AM
On Mon, May 16, 2016 at 6:44 AM, Tom Barber wrote:
> I should be able to say "hey, I'm gonna install this new charm" and know
> that I can hook it into our monitoring infrastructure without doing
> anything too crazy.
>
>
Isn't this already true? After seeing this thread, I took a brand new char
Hi,
It's just `charm create testcharm` (drop the leading juju).
On Sun, May 1, 2016 at 8:44 AM, Saranabasava 110
wrote:
> Hi,
>
> I have installed 2.0-beta6-xenial-s390x on Ubuntu 16.04 LTS by
> following https://jujucharms.com/docs/devel/getting-started. I can able
> to add the new m
elp by sponsoring the project
> <http://www.meteorite.bi/products/saiku/sponsorship>)
>
> On 15 March 2016 at 16:27, Tim Van Steenburgh <
> tim.van.steenbu...@canonical.com> wrote:
>
>> Hey Tom,
>>
>> 1. You can increase the wait time until it doesn'
gt;
>>
>> Okay I'll go back and try again.
>>
>> Tom
>>
>> --
>>
>> Director Meteorite.bi - Saiku Analytics Founder
>> Tel: +44(0)5603641316
>>
>> (Thanks to the Saiku community we reached our Kickstart
>> <h
On Wed, Mar 9, 2016 at 6:31 AM, Tom Barber wrote:
> Thanks Stuart.
>
> I do put a note in my charm message indicating the leader IP address so
> that users know which to connect to.
>
> So with juju wait, would I destroy a unit then execute juju wait? At which
> point it will hang until the leade
1. ppa:juju/devel
2. Use the layer!
On Tue, Feb 2, 2016 at 11:54 AM, Tom Barber wrote:
> Morning folks,
>
> What was the PPA for Juju 2.0?
>
> On a separate note, if I'm writing a charm to install a Java based package
> should I use layers to include openjdk from Kevins charm or somewhere or do
On Tue, Dec 8, 2015 at 6:43 AM, Tom Barber wrote:
> Hi guys,
>
> I'm trying to finally finish off this Saiku charm so I can submit it for
> validation.
>
> I want to write a few simple tests but I need a couple of pointers for
> help with Amulet as I'm not a python guy.
>
> d = amulet.Deployment(
Reviewed
https://code.launchpad.net/~jacekn/charms/precise/haproxy/haproxy-updates/+merge/272559
This branch makes a few improvements to the precise/haproxy charm:
- add SSL support
- add nagios_servicegroups config option
- multiple monitoring fixes
- add open_monitoring_port option
Changes look
On Fri, Sep 25, 2015 at 9:56 AM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> On Fri, Sep 25, 2015 at 9:15 AM, Tim Van Steenburgh
> wrote:
> > Hi everyone,
> >
> > I have a jenkins slave that's running charm and bundle tests on 5
> different
&
Hi everyone,
I have a jenkins slave that's running charm and bundle tests on 5 different
clouds pretty much all the time. My problem is that tests will randomly
fail after hitting this lock timeout.
Here's an example:
http://reports.vapour.ws/all-bundle-and-charm-results/charm-bundle-test-parent-
Yesterday evening I did a final review of the new zulu8 charm.
zulu8 is a subordinate charm which provides Azul Zulu, an open source
implementation of OpenJDK. It provides both the JRE and JDK. More
information at http://www.azulsystems.com/products/zulu
I'm happy to report that the charm passed
apache-kafka (https://bugs.launchpad.net/charms/+bug/1489488)
A truly excellent new charm submission from Kevin Monroe on the Juju Big
Data team. This is a great example of a clean, well-written python charm.
It's built on the `charmhelpers.core.charmframework`, uses the
`jujuresources` lib for fe
On Thu, Jul 23, 2015 at 3:25 PM, Joseph Liau wrote:
> On 2015-07-23 12:11 PM, Tim Van Steenburgh wrote:
>
> Hi Joseph,
>
> Here's one way to solve this:
>
> 1. Setup up the software manually one time.
> 2. Once it's set up, dump the database to a file.
>
Hi Joseph,
Here's one way to solve this:
1. Setup up the software manually one time.
2. Once it's set up, dump the database to a file.
3. Put that file in your charm, and use it to automatically load the
database when the db relation is joined.
For an example of this, check out
https://jujucharm
This morning I reviewed and merged the latest version of the docker
charm[1], which, among other improvements, raises the default docker
version to 1.7.0 and introduces a new config option for installing
docker-compose.
[1] https://code.launchpad.net/~charmers/charms/trusty/docker/trunk
--
Juju m
This morning I reviewed a change to the cassandra charm which takes
advantage of the leadership features of juju, and bumps the default
cassandra version to 2.1.7. [0]
The changes look great in general, although there are some test failures to
address before merging.
On a related note, a new `coo
Merged fixes:
https://code.launchpad.net/~paulgear/charms/trusty/ntp/fix-trusty-exceptions-psutil-1.2.x/+merge/260080
https://code.launchpad.net/~verterok/charms/trusty/mongodb/fix-data_directory-migration/+merge/260290
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
"This is a total rewrite of the Cassandra charm. It supports Apache
Cassandra 2.0, 2.1 and DataStax Enterprise 4.6.
It is not backwards compatible with the old precise/cassandra charm that
only supported earlier versions of Cassandra."
Many thanks to Stuart Bishop for his work on this charm!
--
After a final review, this new charm has been promulgated to the charm
store.
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Reviewed and merged:
[1] apache2 - Support apache-website interface.
[2] ntp - Fix divide by zero.
[3] nrpe - Fix nagios checks to handle haproxy 1.5
[4] squid-reverseproxy - Add visible_hostname to avoid excessive DNS queries
[5] mongodb - Add support for benchmarking mongodb with mongoperf, usi
https://code.launchpad.net/~nicopace/charms/trusty/sugarcrm/all-tests/+merge/251318
https://code.launchpad.net/~nicopace/charms/trusty/kibana/all-tests/+merge/251309
Rejected both for test failures, with comments on how to fix.
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubsc
Marco, I like your proposal with one change - we don't need the test.yaml
changes. Instead I would suggest we add 'unit-test' to the list of default
bundletester targets. So bundletester will run proof, lint, test, and
unit-test (charm author should choose test or unit-test, not both).
Bundletester
Merged:
fail2ban
https://code.launchpad.net/~jose/charms/trusty/fail2ban/tag-security/+merge/245923
mysql
https://code.launchpad.net/~niedbalski/charms/precise/mysql/precise-syncup/+merge/244436
Not merged: (sent back for further work or clarification from submitter)
python-django
https://code.l
# Features
- Test remote sources, e.g.: `bundletester -t cs:trusty/meteor`
Remote sources URL can point to the Charm Store, Launchpad, Github, or
Bitbucket. Full list with examples can be found in the README [1].
# Bug Fixes
- Fix bug that caused captured process output to be empty when using t
This morning I reviewed and merged the following:
https://code.launchpad.net/~jose/charms/precise/bitlbee/set-maintainer/+merge/243701
https://code.launchpad.net/~barryprice/charms/precise/bip/add_backlog_always_option/+merge/245145
https://code.launchpad.net/~corey.bryant/charms/trusty/mysql/rend
Today I reviewed this new charm submission:
https://bugs.launchpad.net/charms/+bug/1399228
Good-looking start, just needs a little cleanup. I posted a new branch with
my suggested changes and some comments to explain those changes.
-- Tim
--
Juju mailing list
Juju@lists.ubuntu.com
Modify setting
This morning I reviewed and merged the changes listed below. All of these
were minor changes: fixes for tests, typos, and proofing errors.
https://code.launchpad.net/~jorge/charms/precise/spip/fix-category/+merge/239378
https://code.launchpad.net/~jorge/charms/precise/couchdb/add-readme/+merge/239
This morning I did follow-up reviews on:
[1] samhain - instrusion alert subordinate
[2] rkhunter - rootkit scanner subordinate
[3] logrotate
All are quality submissions by Chris Stratford (thanks Chris!) with passing
Amulet tests. Each got a +1 from me, pending some minor suggested updates
to met
This morning I did two preliminary reviews on OpenAM and OpenDJ charms from
ForgeRock [1]. These charms are still in development but are off to a good
start. Both would benefit greatly from better usage instructions in the
READMEs. My review comments can be found in Launchpad [2].
[1] http://forge
>
> In my config-change hook when triggered after initial install, changes
> will have effect on some of the relationships already established. The
> relationship has to be broken/invalidated and reestablished.
>
> 1) How can I check what relations are established from within the
> config-changed h
u community and I'm excited
about the future of Juju! I hope I can further contribute to Juju by
becoming a Charmer and helping to maintain the Juju ecosystem in an
official capacity. Thanks for your consideration!
Tim Van Steenburgh
[1] https://jujucharms.com/precise/meteor-2/?text=me
Here's what I reviewed this morning:
[1] This merge brings encryption to the storage charm. A great addition but
lacks tests. Sent back requesting tests be added to cover the new
functionality.
[2] Bugfix for rabbitmq-server. Approved.
[3] Bugfix for cassandra. Approved.
---
[1]
https://code.la
>
> When we review a charm do we bring it up on various clouds? Do we have any
> way to verify that it works on, say, OpenStack and EC2?
>
We've been working on automated charm/bundle testing quite a bit recently.
Right now we kick off tests on AWS, HP, and LXC any time a charm is updated
in the s
Yesterday I reviewed devspace-simulator [1], a new charm submission. The
charm deploys successfully, but needs some clean-up [2] in order to meet
Charm Store poilcy and be eligible for promulgation.
[1] http://devspace.hsenidmobile.com/
[2] https://bugs.launchpad.net/charms/+bug/1353535/comments/1
>
> # Questions
> Should charm proof run lint check? Right now our docs say charms must
> pass proof (no warning or errors) to pass review, but it does not say
> the charm has to pass lint check. Thus, we should consider making lint
> errors not fail charm tests or have charm proof run lint (where
# TL;DR for Charm Authors (tips from today's reviews)
1. Make sure charm-proof, "testing" make targets (e.g. lint, test), and
amulet tests are passing. We are quickly approaching a day when all merge
proposals for charms and bundles will be gated on tests automatically, and
rejected if they fail.
I'm not a charmer either, but I'd give this a big +1 based on my
personal interactions with José. He's very active in #juju,
super-friendly, enthusiastic, and has put a ton of time into the
Juju ecosystem by charm-authoring, reviewing, and helping others.
Awesome job José, you rock!
On Mon, Aug
Today I reviewed an update [1] to the Cassandra charm that allows it to run
on ppc64le. It does so by installing a Cassandra .deb that is bundled with
the charm, modifying the java stack size, and removing a jvm option that
does not work on OpenJDK.
The charm can still be deployed on other archite
Hi Federico,
Yes, python is preferred. The Openstack charms have great unit tests - you
might start by looking at one of those (cinder, for example).
Tim
On Sat, Jun 14, 2014 at 6:18 AM, Federico Giménez Nieto
wrote:
> Hi list, this is my first message so greetings to all.
>
> Just a quick ne
Hi Xander,
Unfortunately there is no charmhelpers documentation right now other than
the source itself. Hopefully that will be rectified in the coming months.
To get started you may want to look at the rabbitmq-server charm, which has
a ceph relation and uses charmhelpers[1]. There is also a video
96 matches
Mail list logo
