On 18 November 2014 09:25, Marco Ceppi ma...@ondina.co wrote:
I have a few charms that expect /mnt to be the ephemeral disk, while it
wouldn't be a huge headache and I certainly wouldn't want to stand in the
way of progress. It won't be trivial and I'll start to devise a way to test
all the
Hi all,
a bit of background: running Debian on a not-so-high-spec machine, the
most often suggested way of running Juju (vagrant) has not been the best
experience so far.
The VM eats most of my RAM (the few bits not taken up by Iceweasel
already) and takes ages to do the simplest of things. Yet
The Juju UI Engineering team is proud to announce the latest release of the
Juju GUI, version 1.2.4. This release comes with a new feature, the added
services bar. In short, it's a view in the left sidebar that allows you to
highlight, show, and hide services in your canvas and machine view.
Jeff
In this weeks blog post I try my hand at breaking down comprehension
barriers on some of the core components of the big data stack - part 1. How
the fit within the ecosystem. And expose some of the growing pains I
experienced just understanding the landscape as a non-data-scientist coming
into the
I *LOVE* this idea.
Great share Robert! I'm wondering (after some research/field testing) if we
don't turn this into a charm-helper for easy/quick consumption in charming,
then feature it in an upcoming charm school...
On Tue, Nov 18, 2014 at 12:26 PM, Robert Ayres robert.ay...@canonical.com
Would be an awesome candidate for a subordinate charm!
Great find, Robert!
--
José Antonio Rey
On Nov 18, 2014 12:38 PM, Charles Butler charles.but...@canonical.com
wrote:
I *LOVE* this idea.
Great share Robert! I'm wondering (after some research/field testing) if we
don't turn this into a
If you missed the 1411 UOS - the Juju team had some great sessions - one of
the most important being our community open forum for Q+A from the Juju
Charmers/Solutions team.
https://www.youtube.com/watch?v=7NHhLF9uewU
The video is 50 minutes of raw Q+A footage with the community where some
great
juju-core 1.21-beta3
A new development release of Juju, juju-core 1.21-beta3, is now available.
This release replaces 1.21-beta2.
Getting Juju
juju-core 1.21-beta3 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
On Tue, Nov 18, 2014 at 10:58 PM, David Britton david.brit...@canonical.com
wrote:
On Mon, Nov 17, 2014 at 8:25 PM, Marco Ceppi ma...@ondina.co wrote:
I have a few charms that expect /mnt to be the ephemeral disk, while it
wouldn't be a huge headache and I certainly
I'm in the same boat,
On 19 November 2014 09:50, Andrew Wilkins andrew.wilk...@canonical.com wrote:
Ideally that would not be /mnt, because otherwise we're going to end up
with a lot of charms that cannot be co-located. My point is that it can be
/mnt, and your charm will keep working without any changes to hooks.
On Wed, Nov 19, 2014 at 1:07 PM, Stuart Bishop stuart.bis...@canonical.com
wrote:
On 19 November 2014 09:50, Andrew Wilkins andrew.wilk...@canonical.com
wrote:
Ideally that would not be /mnt, because otherwise we're going to end up
with a lot of charms that cannot be co-located. My point
On 18 November 2014 12:23, Ian Booth ian.bo...@canonical.com wrote:
On 17/11/14 15:47, Stuart Bishop wrote:
On 17 November 2014 07:13, Ian Booth ian.bo...@canonical.com wrote:
The new Juju Status work planned for this cycle will hopefully address the
main
concern about knowing when a
On 18 November 2014 04:22, Tim Penhey tim.pen...@canonical.com wrote:
'ello 'ackers,
This is something that I have been meaning to add for quite some time.
We have been recording stack traces with the juju/errors library, but
until now, they have been of limited use.
One of the key places
On 18 November 2014 04:22, Tim Penhey tim.pen...@canonical.com wrote:
'ello 'ackers,
This is something that I have been meaning to add for quite some time.
We have been recording stack traces with the juju/errors library, but
until now, they have been of limited use.
One of the key places
Thanks John and Tim. I really like these ideas, especially because it means
the team doesn't need to learn a new way of working (and remember to keep
using the new way). In most cases, the thing returned by getCollection()
will be able to be used in the same way as before, even though it'll
juju-core 1.21-beta3
A new development release of Juju, juju-core 1.21-beta3, is now available.
This release replaces 1.21-beta2.
Getting Juju
juju-core 1.21-beta3 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
I'm coming across double spaces after a full stop in comments. Some
consider this an error, others an intentional style that makes the
comment cleaner to read.
Yes, it's a minor point but in the name of consistency and avoiding
future review ping pong on the issue, I'm calling for a vote:
To quote Butterick's
http://practicaltypography.com/one-space-between-sentences.html
I think two spaces look better so that’s what I’m going to use.
I’m telling you the rule. If you want to put personal taste ahead of
the rule, I can’t stop you. But personal taste doesn’t make the rule
I take that as +1 from Dave.
On 19/11/14 13:13, David Cheney wrote:
To quote Butterick's
http://practicaltypography.com/one-space-between-sentences.html
I think two spaces look better so that’s what I’m going to use.
I’m telling you the rule. If you want to put personal taste ahead of
the
+1 to the Third Way
(and to single space)
--
John Weldon
On Tue, Nov 18, 2014 at 4:15 PM, Jesse Meek jesse.m...@canonical.com
wrote:
I take that as +1 from Dave.
On 19/11/14 13:13, David Cheney wrote:
To quote Butterick's
http://practicaltypography.com/one-space-between-sentences.html
On Tue, Nov 18, 2014 at 3:19 AM, Kapil Thangavelu
kapil.thangav...@canonical.com wrote:
status per future impl helps, as does explicitly marking units.. but pending
cluster count is a missing and important property to properly establish
quorum in a peer rel from one to n that is only resolved
It should be a single space, unless the comments are being written on a
typewriter. To someone in the US. In the 1960s.
On Nov 18, 2014 6:15 PM, Jesse Meek jesse.m...@canonical.com wrote:
I take that as +1 from Dave.
On 19/11/14 13:13, David Cheney wrote:
To quote Butterick's
I vote for this is dumb and should not matter either way.
On Nov 18, 2014 7:22 PM, John Weldon johnweld...@gmail.com wrote:
+1 to the Third Way
(and to single space)
--
John Weldon
On Tue, Nov 18, 2014 at 4:15 PM, Jesse Meek jesse.m...@canonical.com
wrote:
I take that as +1 from Dave.
I learned to type on a typewriter (both mechanical and electric) back in
the 1980s, and it was two spaces then.
Personally I don't care and I'll go with whatever is suggested.
Tim
On 19/11/14 13:24, Nick Veitch wrote:
It should be a single space, unless the comments are being written on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.11.2014 02:10, Jesse Meek wrote:
I'm coming across double spaces after a full stop in comments.
Some consider this an error, others an intentional style that makes
the comment cleaner to read.
Yes, it's a minor point but in the name of
FWIW, this conversation has come up in the Go developer's
mailing list before. The decision was that either way is acceptable
in code, *but* that godoc turns a two space separator into a single space
separator with it format comments (that change was made as a result
of the conversation).
I
+0, as well.
On 19 Nov 2014, at 08:25, roger peppe roger.pe...@canonical.com wrote:
FWIW, this conversation has come up in the Go developer's
mailing list before. The decision was that either way is acceptable
in code, *but* that godoc turns a two space separator into a single space
27 matches
Mail list logo
