Right, I think it has to *know* about the target, which is obviously an
issue here. But we still do *heavily* encourage (probably just outright
require) cloud-archive:tools for running Juju agents on Precise.
John
=:->
On Mon, Sep 1, 2014 at 10:46 AM, Andrew Wilkins <
andrew.wilk...@canonical.co
On Mon, Sep 1, 2014 at 2:04 PM, John Meinel wrote:
> I thought --target-release was supposed to just change the priorities and
> prefer a target, not require it.
> We need it because we add cloud-archive:tools but we explicitly pin it to
> lower priority because we don't want to mess up charms th
The goal I have been tasked with is breaking the interdependency
between the state package and the _client_ api types in
state/api/params.
I don't have any opinion on adding additional layers assuming that
their dependancies flow downwards, ie
labix.org/mgo <- juju/state <- juju/apiserver
On Mon
I thought --target-release was supposed to just change the priorities and
prefer a target, not require it.
We need it because we add cloud-archive:tools but we explicitly pin it to
lower priority because we don't want to mess up charms that we are
installing.
John
=:->
On Mon, Sep 1, 2014 at 9:5
FWIW I'd favor 3 layers, though it does mean you have to do copying between
structs that would likely otherwise be almost identical. A State layer for
saving in the DB, an API layer for communication, and a Model layer for use
in the Agents/Clients.
John
=:->
On Mon, Sep 1, 2014 at 9:40 AM, Dav
On Mon, Sep 1, 2014 at 1:50 PM, John Meinel wrote:
> The version of mongodb in Precise is too old (2.2.4?),
>
Ah, so it is. The entry in apt-cache I was looking at has "main" in it, but
it's actually from the juju/stable PPA.
> we require a version at least 2.4.6 (which is in cloud-archive:too
The version of mongodb in Precise is too old (2.2.4?), we require a version
at least 2.4.6 (which is in cloud-archive:tools and is what we use when
bootstrapping Precise instances in the cloud).
It is recommended that if you are running local on Precise that you should
have cloud-archive:tools in y
Hello,
This is an introductory email to explain my upcoming series of pull requests.
The theme is simple: state must not depend on the api server.
This is currently not true, state depends on api/params because some
of the api types have leaked into the state package and are being
directly store
On Mon, Sep 1, 2014 at 12:53 PM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> Works fine on my trusty laptop, but I'm also getting a new error when I
> try bootstrapping on precise:
>
> 2014-09-01 04:51:27 INFO juju.utils.apt apt.go:132 Running: [apt-get
> --option=Dpkg::Options::=--for
Works fine on my trusty laptop, but I'm also getting a new error when I try
bootstrapping on precise:
2014-09-01 04:51:27 INFO juju.utils.apt apt.go:132 Running: [apt-get
--option=Dpkg::Options::=--force-confold
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
--target-relea
i went with a different approach and wrote a charm to do the overlay
network using coreos's newly released rudder
http://bazaar.launchpad.net/~hazmat/charms/trusty/rudder/trunk/view/head:/readme.txt
it works across all providers (including manual and the digitalocean and
softlayer manual based pl
11 matches
Mail list logo
