-1 IBM Java SDK - https://bugs.launchpad.net/charms/+bug/1477067
The charm is progressing nicely as a first iteration, there is still some
cleanup to be done here around the charm project files, and the
comprehensive amulet testing.
Charles Butler charles.but...@canonical.com - Juju Charmer
I reviewed the IBM DB2 charm today. This is another charm that requires a
lot of error prone setup before it will deploy, such as downloading the
binary and hosting it on a web server. This will be very hard for
customers to accept when they have mysql or postgresql that deploy directly
from
It sure took you long enough to apply Cory! You almost get a negative one
from me just on waiting so long!
My vote is +1 on Cory.
His anchor tells me he is very good at documentation, and we need all the
help on docs that we can get!
Welcome aboard Cory.
- Matt Bruzek
Gustavo
Thank you for your response. I'll explain two TOSCA concepts I find very
interesting and would like to use in Juju.
# Separation of Topology VS Plans.
In TOSCA, you can define a topology (what services you want and how to
connect them) independent from Plans (How to implement these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
We're in currently developing more comprehensive networking features
in Juju, so soon you'll be able to configure this with Juju the way
you like it.
In the meantime, please ignore the --networks argument - it was
implemented partially as a
# juju-core 1.22.7
A new proposed supported release of Juju, juju-core 1.22.7, is now available.
This release may replace version 1.22.6 on Thursday August 13.
The 1.20.x series of Juju is supported, though it is an older version than
the current stable version. The current stable of juju is
Cory has done a lot to improve the developer experience and has shown an
extensive breadth of knowledge about Juju and its ecosystem. He has a +1
from me.
On 2015-08-07 12:29 PM, Cory Johns wrote:
Dear Charmers,
I would like to apply for membership to https://launchpad.net/~charmers
I have
Thanks for these details Melijn,
So you want to be able to describe a topology without deploying it, and you
also want to be able to record that topology so that it can be reused.
Both of these are good ideas, and the juju concept that supports both of
these at once is called stacks. It's not
