-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/07/2014 05:09 AM, Adam Stokes wrote:
I read through the docs/api.txt to try and get an understanding of
how to connect to juju's api server and what I've come up with so
far is the following:
#!/usr/bin/env perl
use Mojo::UserAgent; use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
We should probably set up a new environment with a current juju
after fixing up the tarmac charm to have some more of the things we
needed to manually hack in last time around.
Martin
I would agree, except I have to do the whole thing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-01-30 5:49, Sameer Zeidat wrote:
Hello,
I'm relatively new to juju, and starting to write some charms.
One thing I'm missing is relation dependency. Say service A can
join a relation with B and C. I would like for juju to stop A from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-01-23 10:33, Gandhi, Ibha (HP Software) wrote:
Hi,
I want to deploy application on a specific VM and don?t want to
provision a new VM.
This is something I have been doing with chef, please let me know
if it?s possible to deploy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-01-06 5:30, Tim Penhey wrote:
Hi folks,
We have a rather nebulous work item called closed network support
where we mention supporting proxies.
Do we have a list of what proxies we need to support and where we
currently fall down?
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-12 22:09, Curtis Hovey-Canonical wrote:
I think the number of open critical and high bugs is inflated. The
open critical bugs are an incentive to release soon, but many of
the critical bugs were really closed the moment trunk merged the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-12 22:16, Curtis Hovey-Canonical wrote:
On Thu, Dec 12, 2013 at 1:09 PM, Curtis Hovey-Canonical
cur...@canonical.com wrote:
We close bugs when we know we have delivered a fix to the
affected users. Our practice of targeting to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-10 4:11, max cantor wrote:
Thanks. Filed a report at
https://lists.ubuntu.com/archives/juju/2013-December/003323.html
max
I think that was just a copypaste error, as that is a link to
Robbie's email to you. I think you meant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
Did you check the 'mgo' source as well? I thought I remember when
you first connect it uses eval to get date stamps to check for
clock skew.
I think you might be thinking of the state/presence package there,
which uses eval for pre-2.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So I'm trying to finish the work to maintain compatibility between
trunk and 1.16 for all commands.
I think I've finished everything except for manual provisioning.
However, this rabbit hole keeps getting deeper, so I wanted to ask how
much we really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-06 6:24, David Cheney wrote:
Ok, good news first.
gccgo compiled tools work fine.
statically linking libgo also makes the tools as self contained as
our gc compiled ones.
Bad news,
jujud is 40mb, -Os or -O2 effect, in fact the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
Also landed recently is a KVM option for the local provider.
For the truly trivial, add container: kvm to the local
configuration.
Is it possible to mix LXC and KVM containers under the local
provider?
I can think of one use case where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-02 13:01, James Page wrote:
Morning folks
so far I have requests for:
mongo (default shell)
mongoexport (used in new juju backup plugin)
mongodump/mongorestore (useful)
I'm keen we don't bloat out the 'server' package to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-02 13:01, James Page wrote:
Morning folks
so far I have requests for:
mongo (default shell)
mongoexport (used in new juju backup plugin)
mongodump/mongorestore (useful)
I'm keen we don't bloat out the 'server' package to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-02 16:39, roger peppe wrote:
On 2 December 2013 11:40, Ian Booth ian.bo...@canonical.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
I don't fully understand the difference from mongoexport vs
mongodump (it looks like dump
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-28 17:54, Peter Waller wrote:
Hi All,
We needed to attach an elastic IP to some of our machines, and it
seems juju hasn't recognized that they have new addresses.
How can I force juju to notice?
Thanks,
- Peter
I know in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-28 18:58, Peter Waller wrote:
Our clients are 1.16. How do I check the version of the thing which
does the addressupdatering and how do I update it?
If it's the bootstrap node, how do I find the juju binary? It
doesn't seem to be in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-28 21:03, Peter Waller wrote:
On 28 November 2013 16:54, Kapil Thangavelu
kapil.thangav...@canonical.com
mailto:kapil.thangav...@canonical.com wrote:
$ juju upgrade-juju is used for updating the agents within the
environment. What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should be able to force a version with juju upgrade-juju
- --version=$XYZ, but the client should have detected what versions
were available before setting the target version.
It is possible you are running into the problem of jumping too many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-28 21:28, Mark Shuttleworth wrote:
On 28/11/13 17:25, Peter Waller wrote:
Is it safe to run that whilst my agents appear to be spinning as
I described in my previous e-mail?
A very good question.
If updates are required to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
5) So if we found a way to pipeline requests, and get rid of gaps,
instead of taking 10 RTT, we could potentially get down to 5 RTT.
(2 gaps, calling Upgrade + Login + SetEnvironmentConstraints
immediately rather than waiting for responses,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to bring up the discussion of what guidelines we're using
when we design CLI commands. There are 2 commands that just came up
that I'd like to use as examples, and see what we think of as a team.
1) juju set-constraints [-s service]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was curious, so I did some benchmarking of CLI performance. The good
news is that we're doing a lot better in Trunk than in 1.16, and we
have a clear win coming up.
For testing I just did:
time for i in `seq 10`; do juju set-constraints mem=4G;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-20 20:15, Curtis Hovey-Canonical wrote:
On Tue, Nov 19, 2013 at 8:43 PM, Tim Penhey
tim.pen...@canonical.com wrote:
It was my understanding that the api server needs to be at least
as advanced as any client.
This means that a 1.18
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-18 10:47, Andrew Wilkins wrote:
All,
I'm in the process of landing the following MP which removes the
--source flag from juju bootstrap; this should go into the
release notes. As discussed, you can still use --source with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-11 10:19, Ian Booth wrote:
So I'd like to see what people think of this: - Keep juju
bootstrap --upload-tools, but make that the only time we attempt
to upload during juju bootstrap. There will not be any
automatic upload if tools
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-08 14:15, roger peppe wrote:
On 8 November 2013 08:47, Mark Canonical Ramm-Christensen
mark.ramm-christen...@canonical.com wrote:
I have a few high level thoughts on all of this, but the key
thing I want to say is that we need to get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did one last round of scale testing before handing this over to Dave.
I was using trunk @2037 with 2 patches (one to set GOMAXPROCS, and one
to allow juju add-unit -n X --to Y.)
I started with:
juju bootstrap --constraints=mem=7G cpu-cores=4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-07 17:18, John Arbash Meinel wrote:
I did one last round of scale testing before handing this over to
Dave.
...
But that says 7000 agents + nrpe-external-master has killed the
machine. But probably smaller than that we'd be ok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
Long term, I'd like to deprecate the root as a way of talking to
the API and mandate (for instance) /api as a URL path. Short term,
we can't do that, but we *can* treat, for instance /charm
differently and serve PUT (and potentially GET
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
I would be perfectly happy with PUT if we were already a RESTful
API, but it seems a bit strange to just tack that on, and will be
a one-more-special case that we run into when trying to debug,
etc. (logs will likely be different, working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
api-endpoints: (I don't recall why we put this in the list at all?
What needs to be done here?)
juju api-endpoints is a CLI command, seems like it should use
APIAddresses via the API so that it can return all possible API servers.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So I managed to instrument a jujud with both CPU and Mem profiling
dumps. I then brought up 1000 units and did some poking around.
The results were actually pretty enlightening.
1) Guess what the #1 CPU time was. I know I was surprised:
Total:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to put together a quick summary of what I've found out so
far with testing juju in an environment with thousands (5000+) agents.
1) I didn't ever run into problems with connection failures due to
socket exhaustion. The default upstart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
- From what I can tell, all units take out a watch on their
service so that they can monitor its Life and CharmURL. However,
adding a unit to a service triggers a change on that service,
even though Life and CharmURL haven't changed. If we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
4) If I bring up the units one by one (for i in `seq 500`; do for j
in `seq 10` do juju add-unit --to $j ; time wait; done), it ends
up triggering O(N^2) behavior in the system. Each unit agent seems
to have a watcher for other units of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-30 18:11, Nate Finch wrote:
On Wed, Oct 30, 2013 at 9:23 AM, John Arbash Meinel
j...@arbash-meinel.com mailto:j...@arbash-meinel.com wrote:
2) Agents seem to consume about 17MB resident according to 'top'.
That should mean we can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
The log size didn't come up again in this email. Not sure if you
meant separately or just got lost in the message length.
I didn't explicitly enumerate it, but it is because of section (4).
Namely, bringing up 1000 units triggers 1000*1000
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-29 16:38, Andreas Hasenack wrote:
Hi,
There is this charm with a db-admin relation to postgresql. In
this relation, the charm gets access to a super user in postgresql
and can do whatever it wants with it.
When the first unit of
=:-
On 2013-10-29 10:25, David Cheney wrote:
Not lgtm. The number of CPU cores available on the default ec2
bootstrap machine is 1.
On Tue, Oct 29, 2013 at 5:07 PM, John Arbash Meinel
j...@arbash-meinel.com wrote: Do we want to enable
multiprocessing for Jujud? I have some evidence
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The conversation I remember from SFO was that in order to get armhf
builds on non-virtualized builders, we needed to a have a highly
restricted team which would build into a semi-private ppa and then
copy the binaries from there into the devel/stable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-10-07 11:47, Mike Sam wrote:
Thanks. This is actually for when I have deployed a unit on ec2
machine but within a new lxc on that machine so not for local. Does
this still apply? I am not quite sure how these network bridges
need to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
Is that actually intended to be part of the workflow? It ends up
with several more clicks and delays for round trips (you have to
wait for your patch to land, then click back through and close
the Rietveld ticket, etc.)
I just takes a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(forwarded from Andrew who summarized what the other group discussed)
Here's what we found today. I've left off the list so we don't prejudice
anyone who hasn't yet reviewed.
- - State is not a very meaningful name. One possible alternative that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-08-30 14:28, Peter Waller wrote:
For the record, I sent the link privately. The run took about 22s
but I have measured 30s to 1m.
Some thoughts, nothing that I can give absolute confirmation on.
1) Next week we have a group sprinting on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since Roger was kind enough to do this one in advance, this week's
code review will be:
state/constraints.go
Remember, we'd like you to spend about an hour going over that file
and its associated tests. Thinking about things that you would comment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-08-27 0:51, Nate Finch wrote:
The Windows installer for juju is complete, modulo what might be
asked for in response to this email. I went with Inno Setup on
John's suggestion, since the learning curve was minimal, it does
everything we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm implementing juju get via the API. In doing so, I moved over one
of our tests which did (pseudocode)
set value=int64(0)
DeepEquals(result, value)
And it used to work when ServiceGet was connecting directly to State.
Now that it goes via the
48 matches
Mail list logo
