# juju-core 1.21.0
A new proposed stable release of Juju, juju-core 1.21.0, is now available.
This release may replace 1.20.14 on Thursday January 29 after a period
of evaluation.
## Getting Juju
juju-core 1.21.0 is available for utopic and backported to earlier
series in the following PPA:
Attached are the meeting notes that came from the ~charmer quorem that took
place today. We encourage your feedback on any meeting items discussed, and
welcome proposed agenda items for the next meeting.
I'm attaching Markdown inline, and there is a PDF attachment for anyone who
doesn't enjoy read
On Thu, Jan 22, 2015 at 04:57:36PM +, Marco Ceppi wrote:
> test: lint unit-test functional-test
-1, I'd rather 'test' be unit testing only. Many charms have this
already and it seems like unecessary busy work to change it.
> ```
> makefile:
> - code-lint
> - unit-test
> ```
-1, vote
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
We can also add Makefile checking to charm proof, for an even greater
redundancy.
To avoid multiple invocations of charm proof (not terrible, IMO) lint could
be broken down further:
lint: proof code_lint
proof:
charm proof
code_lint:
# Your code here
Then have bundle tester sniff out c
On 22 January 2015 at 16:36, Simon Davy wrote:
> On 22 January 2015 at 16:29, David Britton
> wrote:
> > On Thu, Jan 22, 2015 at 04:17:26PM +, Simon Davy wrote:
> >> On 22 January 2015 at 15:13, David Britton
> wrote:
> >> >
> >> > lint:
> >> > - make lint
> >> >
> >>
> >> Could we also m
Same here, the OpenStack charms have charm proof in the lint target. I
expect it would be run twice in that case.
On Thu, Jan 22, 2015 at 10:36 AM, Simon Davy wrote:
> On 22 January 2015 at 16:29, David Britton
> wrote:
> > On Thu, Jan 22, 2015 at 04:17:26PM +, Simon Davy wrote:
> >> On 2
On 22 January 2015 at 16:29, David Britton wrote:
> On Thu, Jan 22, 2015 at 04:17:26PM +, Simon Davy wrote:
>> On 22 January 2015 at 15:13, David Britton
>> wrote:
>> >
>> > lint:
>> > - make lint
>> >
>>
>> Could we also make[1] the charm linter lint the makefile for the
>> presence of ta
On Thu, Jan 22, 2015 at 04:17:26PM +, Simon Davy wrote:
> On 22 January 2015 at 15:13, David Britton
> wrote:
> >
> > lint:
> > - make lint
> >
>
> Could we also make[1] the charm linter lint the makefile for the
> presence of targets agreed in the outcome of this thread?
"charm proof"
I
Yep absolutely, we want to make sure we're in line with the existing
tools. After talking with Tim, the way I understand it, bundletester
doesn't use the Makefile for amulet tests. Instead, it execs everything
which is +x in the tests dir (a la juju test).
On Thu, Jan 22, 2015 at 9:51 AM, Charl
On 22 January 2015 at 15:13, David Britton wrote:
>
> lint:
> - make lint
>
Could we also make[1] the charm linter lint the makefile for the
presence of targets agreed in the outcome of this thread?
[1] Pun fully intended :)
--
Simon
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settin
On Thu, Jan 22, 2015 at 10:13 AM, David Britton wrote:
> functional tests:
> - make functional-test
>
We need to be careful about things like this - as bundletester is already
looking in tests/ for the amulet suite and might end up running the
integration tests multiple times according to the m
+1, but I would propose using hyphens for word separators, not
underscores -- at least for the recommendation. I would also recommend
*not* having multiple default names.
As mentioned, the yaml control file I think can be used to override all
this, so it still leaves room for individual preferenc
On 01/22/2015 03:57 PM, Ryan Beisner wrote:
> Thanks for pointing out the yaml control file, that could be useful. But
> before we make any modifications to the OpenStack charms, I think it would
> be helpful to have an agreed-upon convention for the following in terms of
> Makefile target names:
Thanks for pointing out the yaml control file, that could be useful. But
before we make any modifications to the OpenStack charms, I think it would
be helpful to have an agreed-upon convention for the following in terms of
Makefile target names:
- nose / unit tests
- make test
- ma
There are two distinct features aiming for 1.21 which address your needs:
* multiple environments in a single juju server
* multiple users in a single juju server
The combination will allow you to:
* bootstrap Juju once (perhaps across a few servers for HA)
* create several user accounts on
1. The following branch adds a simple backup mechanism to mysql. +1 (I
would land it but since it's one of my first reviews I'll wait for
feedback on here before I do).
https://code.launchpad.net/~jacekn/charms/trusty/mysql/mysql-backups/+merge/245343
2. This branch adds an optional apt source to
17 matches
Mail list logo
