Non released streams was only supported in Azure for a time when there
weren't stable releases. It would be possible to implement and make it work
elsewhere, but it was underutilized and did cause some bugs.
The main workaround is to do custom stream data and reference the built
images (juju
Pinging is already suppressed in the 1.17 codebase.
John
=:-
On Jan 9, 2014 7:30 PM, Mark Shuttleworth m...@ubuntu.com wrote:
On 09/01/14 14:36, Steve Powell wrote:
1) the `debug-log` command is not documented very well: executing it
without parameters tails the log (forever) until ^C’d
Unfortunately the MaaS controller doesn't expose itself as a place that you
can deploy services, so having that machine as the only public machine
would make it difficult.
If you can put another machine on the public network, then you should be
able to put haproxy on it as a reverse proxy.
John
I'm pretty sure Quantum can't be deployed in LXC because it needs direct
access to block devices. I could be wrong.
John
=:-
On Mar 15, 2014 2:08 PM, brian mullan bmullan.m...@gmail.com wrote:
I thought I'd try using some of the cool new stuff.. so with latest lxc
1.0 JuJu JuJu-gui installed
in a kvm instance instead
On Sat, Mar 15, 2014 at 1:26 PM, John Meinel j...@arbash-meinel.com
wrote:
I'm pretty sure Quantum can't be deployed in LXC because it needs direct
access to block devices. I could be wrong.
John
=:-
On Mar 15, 2014 2:08 PM, brian mullan bmullan.m...@gmail.com
On Sat, Mar 15, 2014 at 1:11 AM, Curtis Hovey-Canonical
cur...@canonical.com wrote:
juju-core 1.17.5
A new development release of Juju, juju-core 1.17.5, is now available.
Getting Juju
juju-core 1.17.5 is available for trusty and backported to earlier
series in the following PPA:
thought we would publish on streams.canonical.com first,
and then sync the rest from there.
John
=:-
On Mon, Mar 17, 2014 at 12:18 PM, John Meinel j...@arbash-meinel.com wrote:
On Sat, Mar 15, 2014 at 1:11 AM, Curtis Hovey-Canonical
cur...@canonical.com wrote:
juju-core 1.17.5
A new development
As of right now (2014-05-19 11:20 UTC) streams.canonical.com no longer
lists 1.17.[1-5] as available. At least if I go here:
http://streams.canonical.com/juju/streams/v1/com.ubuntu.juju:released:tools.json
vs going here:
I would actually just use MaaS + LXC or KVM virtualization.
You should be able to bring up a MaaS environment, and then do:
juju deploy NEWSERVICE --to lxc:10
And Juju will create a new LXC container on machine 10 and deploy the
NEWSERVICE into it.
That gives you all the give me baremetal when
i think the issue he is mentioning is that you can use the GUI to set the
password to , but that doesn't actually unset the password in the
application.
John
=:-
On Wed, Mar 26, 2014 at 9:33 PM, Richard Harding rick.hard...@canonical.com
wrote:
On Wed, 26 Mar 2014, Anant wrote:
Hello
Known bug, though I thought the fix made it into 1.19.1.
To work around it, you use
juju bootstrap --upload-tools --series precise, trusty
John
=:-
On Apr 25, 2014 9:35 PM, Asif Iqbal vad...@gmail.com wrote:
I am using 1.19.1-trusty-amd64, installed from ppa:juju/devel
I am failing start
The peergrouper thing is a non fatal problem with the local provider (it is
only used for HA which is currently disabled for local). The problem with
default series is the local provider defaults to only making tools for your
host available (trusty). Which is why you specify the extra tools series
There is work being done this cycle to switch from using storage from the
Provider to instead using our own internal storage. I don't know that the
work will be done for another few months, though. I believe Tim Penhey is
going to be leading up that work as part of exposing Resources for charms
to
are just sending requests to some other
long-lived process over a socket, but I'd rather not have to run a full
service for every system we want to interact with.)
John
=:-
On Tue, May 6, 2014 at 8:33 AM, John Meinel j...@arbash-meinel.com wrote:
There is work being done this cycle to switch from
We certainly welcome more provider implementations to be part of core.
We've been working with a couple of other people in doing just that (Joyent
support was recently contributed by them, and there are a few others being
worked on today).
Most of the provider implementations we have today are
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1304407
It should be fixed in 1.18.3.
John
=:-
On Mon, May 12, 2014 at 9:36 PM, Henning Eggers henn...@keeeb.com wrote:
Hi!
I just noticed that I now have specify the arch constraint if I want amd64
instances. Without it, I get i386
I actually think this isn't about someone doing juju set-env but someone
just ssh'ing into the machine and changing things with a text editor.
Joey is the type of guy to be very concerned about people making changes
out of band that we wouldn't know about even if we had audit logging.
(Which we
FWIW, I've gotten bug requests from a user that did a regular bootstrap and
then was trying to juju upgrade-juju --upload-tools and was confused that
his local machine wasn't able to upgrade tools for his environment. (he was
running i386 locally, and bootstrap created an amd64 machine).
And while
FWIW, I think the byArch did a plain sort.Strings() which happens to pick
amd64 because it is before all other in a typographical fashion. IIRC, it
may have mutated a lot over time because the sorting was blocking bootstrap
from working on ppc64 which was why it was removed. Also, on MaaS, MaaS
I would generally think to model this as part of the relation data. Since
you want the individual units of your charm to connect to different units
of Mongo, then it sounds like you want a peer relation in your charm, and
each unit could then report what unit of mongo it is connecting to on the
Sounds great.
John
=:-
On Mon, Jun 2, 2014 at 1:34 PM, James Page james.p...@ubuntu.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Folks
As part of ongoing work to improve and sustain the quality of the
OpenStack Charms, we are going to start enforcing the linked policy
When you do juju add-machine it should print out a line like:
created machine 10
You should be able to then do:
juju add-unit SERVICE --to 10
John
=:-
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
My understanding was that some of this was possibly buggy charms, where you
don't want to start relating a charm to X until it is already related to Y
(front end vs backend sort of stuff).
John
=:-
On Mon, Aug 25, 2014 at 9:05 PM, Marco Ceppi marco.ce...@canonical.com
wrote:
My question is
Given CAP theorem any message can really only be at most once or at
least once. You can never guarantee exactly only once.
I'm sure juju is biased to the at least once for hooks (hence why it runs
at agent restart because it hasn't been around to know for sure that
nothing changed in the interim).
require 1.21, but I thought the IP address update changes
landed in 1.20)
John
=:-
On Wed, Oct 15, 2014 at 4:21 PM, Vasiliy Tolstov v.tols...@selfip.ru
wrote:
2014-10-15 11:08 GMT+04:00 John Meinel j...@arbash-meinel.com:
You could probably edit the /var/lib/juju/agents/unit-*/agent.conf and
/var
On Mon, Oct 20, 2014 at 12:53 PM, Malshan Peiris mals...@hsenidmobile.com
wrote:
Hi all,
When i deployed a bundle to an AWS instance, it had created an AWS
instance per charm, which is costly for the user.
1. Is it possible to deploy all charms of bundle to a single AWS instance
without
...
9. If you want to cancel a deployment that just started you need to keep
running remove-service forever. Juju will simply ignore you if it's still
running some special bits of the charm or if you have previously asked it
to cancel the deployment during its setting up. No errors, no other
You also need the CA certificate and the API server addresses.
I might recommend trying a new juju bootstrap of say a simple LXC
container (for manual) and then you can see what content we depend upon. I
don't think the GUI authenticates the HTTPS certificate that we present,
but definitely the
So the main caveats as I see them are:
1) since it didn't come from an official source we flag it as such (the
mechanism was originally developed to allow developers to test out their
in-progress code changes). So your version numbers I juju status won't
exactly match
2) if you ever need to
Unfortunately the Openstack that Rackspace exposes is not quite the same as
the official openstack releases. (I believe they don't expose storage, and
a couple of the other APIs aren't the same.)
John
=:-
On Wed, Jan 28, 2015 at 10:11 AM, Sajith Vijesekara
saji...@hsenidmobile.com wrote:
Hi
On Fri, Apr 3, 2015 at 7:47 AM, Richard Harding rick.hard...@canonical.com
wrote:
tl;dr
The new v4 API is out there go migrate to it. v3 API will be EOL'd at the
end of the year.
Doesn't that EOL the version of Juju that is in trusty? Yes we'll release a
new version, but people won't be
On Mon, May 4, 2015 at 8:49 PM, Katherine Cox-Buday
katherine.cox-bu...@canonical.com wrote:
Thanks for reaching out, Dinesh!
I have opened two bugs for these issues:
1.In *juju bootstrap. *It is *not downloading the disc image* itself.
But when I check juju status, it is showing
upgrade step set AvailZone in instanceData failed: no instances found
seems suspicious.
What version of MAAS are you running?
It is possible that it would come before MAAS availability zones?
Certainly we couldn't really find 0 instances in MAAS because the machine
this is running on has to be at
I would guess the point is that there is nothing wrong but he's showing
orchestrating docker containers in docker/* services.
Either that or there is a problem that the containers aren't getting TCP
ports opened.
John
=:-
On Sun, Jun 21, 2015 at 1:48 PM, Mark Shuttleworth m...@ubuntu.com wrote:
than trying to relate from juju ?
--
*From:* John Meinel j...@arbash-meinel.com
*Sent:* Tuesday, June 16, 2015 1:17 PM
*To:* Dinesh Kumar Senapaty (WT01 - Global Media Telecom)
*Cc:* juju
*Subject:* Re: Keystone error
I think I remember that keystone needs
I think I remember that keystone needs to be set up with its database
relation before anything else is related to keystone, as the charm doesn't
implement db migration.
John
=:-
On Mon, Jun 15, 2015 at 1:51 PM, dinesh.senap...@wipro.com wrote:
Hi ,
We have been trying to deploy
I believe there is work being done so that you can do juju get and send
that output directly into juju set or even juju deploy --config. And I
think that's a much better story around repeatable deployments than trying
to make sure the defaults never change. If they really care about
repeatable
Would this just be config on the charm that would eventually become config
on the relation?
John
=:-
On Aug 19, 2015 7:05 AM, Samuel Cozannet samuel.cozan...@canonical.com
wrote:
Hi All!
Our friends at Engineering are working on the SpagoBI charm set and it's
going very well.
They are
Juju 1.23 has some known issues with Lease operations. All of those have
been fixed in the 1.24.4 (5?) release. It is good practice to take a backup
before upgrading, and if you want we can try to help sort out the specific
growth to make sure it gets cleaned out after the upgrade. (Even just
I don't know the concrete details here, but I do believe there are a few
files that are shared in one JUJU_HOME. There is only one environments.yaml
and the new multi-environment code means there is another shared file that
holds the list of known servers and environments.
I would hope that the
Although given https://pad.lv/1467331 it would seem that we can easily
leave it stale if the client doesn't exit cleanly. This does sounds like a
case where using a lock file means we're going to need to provide some sort
of "break-lock" functionality. We could do something like inspect the lock
Are you looking for the user to 'ssh' as or the user to connect to the Juju
API?
After bootstrap there should be a ~/.juju/environments/ENV.jenv file.
There should be a user and password in there for the API. For SSH, you use
the "ubuntu" user with the ssh key that was found during bootstrap.
I think the question is whether it is available by default. Not whether it
could be installed. But as mentioned, if the answer is a short bash script
that ensures "apt-get install python3" and then everything else in Python3
that sounds like an answer.
John
=:->
On Mon, Jun 6, 2016 at 3:55 PM,
Using the workload message as a single location to convey information to
the outside world was certainly never intended. Generally those messages
were meant to convey information to a human who would be looking at them.
We've actually had quite a few conversations about opening up more avenues
I believe 'push' gives you a revision number, which the bundle can then
request. But that would need to recreate the bundle after each push. I
don't believe there is a handle for "latest unpublished version".
John
=:->
On Wed, Jun 15, 2016 at 5:02 PM, Merlijn Sebrechts <
>
> ...
>
> (*) It is called Synnefo ( synnefo.org ) and is an opensource IaaS
> developed by the Greek Research Network of Technology (GRNET). It powers
> ~okeanos ( okeanos.grnet.gr ), a large IaaS providing resources to the
> Greek and other European academic communities. Synnefo is OpenStack
gt; wrote:
> On 09/02/16 09:25, John Meinel wrote:
> > The more edge case is that charmhelpers itself is AGPL, so if your charm
> > imported charmhelpers, then that is more of a grey area. You likely need
> to
> > open source the actual charm, which sets up configuration, etc of th
n't running which explains why the connection refused
> error appears.
>
> Tom
>
> On 27 Feb 2016 11:56, "John Meinel" <j...@arbash-meinel.com> wrote:
>
>> Connection refused isn't the error you would be getting if it was the
>> current incompatibilities.
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
On Sat, Feb 27, 2016 at 4:55 PM, John Meinel <j...@arbash-meinel.com>
Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
> goal, but you can always help by sponsoring the proj
One thing you could try, "juju bootstrap test-lxd lxd --debug
--upload-tools --bootstrap-series trusty". It may be a difference based on
what the target series is.
John
=:->
On Sat, Feb 27, 2016 at 6:50 PM, John Meinel <j...@arbash-meinel.com> wrote:
> Is 10.0.3.94 the
It does feel like a good fit for resources, with the one caveat that he
wants to maintain a lock-step version of the resource across services.
There is slightly more work with the current designs for resources, in that
each charm will think about its version of the resource independently. But
we
...
>
> And now I think of it, can I stream resources? I don't want to
> provision a machine with 8TB of storage just so I can restore a 4TB
> dump. Maybe this is just a terrible example, since I probably couldn't
> be bothered uploading the 4TB dump in the first place, and would
> instead setup
Looks like the changes to Login broke compatibility. We are adding a Login
v3, but it looks like the new code will refuse to try to Login to v2. I'm a
bit surprised, but it means you'll need to bootstrap again if you want to
test it out with current trunk.
John
=:->
On Thu, Feb 18, 2016 at 2:47
Is there a reason to tell people to look at "controllers.yaml" rather than
having the official mechanism be something like "juju list-controllers
--format=yaml" ? I'd really like to avoid tying 3rd party scripts to our
on-disk configuration. We can keep CLI compatibility, but on-disk
structures
...
>
> > 3) Downloading from the internet. This issue has been common in
> > charmstore charms, and is discouraged, AIUI. But the same issue
> > applies for layers, and possibly with more effect, due to a layer's
> > composibility. We simply can not utilise any layer that downloads
> > things
If the subnets have logical differences, then they should be in different
spaces.
Examples for and against:
1) 2 network switches, one is 1GB for admin traffic, other is 10GB for
storage traffic, these should be different spaces
2) 2 racks, each configured identically. each rack has 2 switches as
Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
new lxd package and it seemed to get things working. Tycho added some
helpful prompts as part of "juju bootstrap" to point users in the right
direction if LXD looks to be improperly configured.
Does that mean master is unblocked?
John
=:->
On Sat, Mar 26, 2016 at 6:08 AM, Cheryl Jennings <
cheryl.jenni...@canonical.com> wrote:
> Hi Everyone,
>
> The release team has been working to get 2.0-beta3 released today, but due
> to some packaging issues, the release will be delayed until
At the moment I don't believe we do. We just use your access key and secret
key to identify you to EC2 when we make requests. We don't support using
temporary credentials via Assume role
For those of us wanting to know more here is AWS page
On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack <andr...@canonical.com>
wrote:
> On Wed, Apr 27, 2016 at 10:59 AM, John Meinel <j...@arbash-meinel.com>
> wrote:
>
>> ...
>>
>>
>>>
>>>> As noted, the number of times you have to boots
On Tue, Apr 26, 2016 at 10:41 PM, Andreas Hasenack <andr...@canonical.com>
wrote:
> On Tue, Apr 26, 2016 at 3:11 PM, John Meinel <j...@arbash-meinel.com>
> wrote:
>
>> I believe --config can take a file rather than just a 'key=value'
>> pairing. So you can save a
...
>
>> As noted, the number of times you have to bootstrap should be going down,
>> and if you are bootstrapping different-but-similar, then you again have a
>> single config that can be reused.
>>
>
> I'd love to be able to share a controller node with my colleagues. I tried
> setting that up
I believe --config can take a file rather than just a 'key=value' pairing.
So you can save all your config to a file and pass it in with '--config
myconf.yaml'
There was discussion of having a default search path for some of the
config, but I'm not sure if that got implemented, nor if it is
I'm curious if we've looked into throttling to improve things. I've done
some parallel testing in the past, and I've seen a few times where just
adding units sequentially was actually faster than parallel because of
contention.
I wonder if we might want to introduce some sort of rate limiting
...
> But where did the settings for scapestack get set up in the first place.
>> You're missing some of the original "edit ~/.juju/environment.yaml" to
>> insert the right information.
>>
>>
> The scenario is starting from an already configured cloud in both juju1
> and juju2, and my use case
Near the end of this is a line that says it couldn't find your region.
Generally Juju will need to know what region your cloud is in order to
determine what image is "trusty" or "xenial". It sounds like we need to get
the descriptions of your images. You can look at:
Interesting. With the new rework of some of the model config you can
probably set some of those in the cloud definition and set some with "juju
set-model-default" so it doesn't have to be set in every bootstrap and
add-model. I'm not sure if all of it has landed, but it should certainly be
in 2.0.
I thought in MAAS 2 they have a way to generate a file appropriate for
being a .maasrc file which Juju will use as a source for 'juju
autoload-credentials'. That doesn't do the steps of creating the MAAS user
itself, but it should help the 'configure juju' part. Though this will also
only be
>
> ...
>
> Sure, an example:
>
> A web application needs creds (secrets) in order to access a 3rd party
> api. These creds need to exist in a config file on the webserver/instance.
> As a user, you/I know what the secrets are, but now we need to share them
> with the web application, and only
You need Xenial if you want to use MAAS 2.0, but Juju can deploy to Trusty
just fine. I'm not sure about kvm_intel, but you can do "juju bootstrap
--bootstrap-series=trusty" to get a Trusty Controller, and then 'juju
deploy --series trusty APP" to select a Trusty series there as well.
John
=:->
bootstrap-series
>
> On Mon, Aug 8, 2016 at 1:59 PM, John Meinel <j...@arbash-meinel.com>
> wrote:
>
>> You need Xenial if you want to use MAAS 2.0, but Juju can deploy to
>> Trusty just fine. I'm not sure about kvm_intel, but you can do "juju
>> bootstrap --bo
My concern about your last configuration is that it appears to change your
squid deb proxy into an open proxy by which anything can make a request to
any website. At least that is my understanding of:
http_access allow all
(Its no longer a 'deb' proxy, its just a plain http proxy.)
That may be
I'm quite surprised to see an 'agent-state: stopped' and life: dead with an
'agent-status: ... executing'.
If the agent really is dead, then there is nothing for the hooks to run on.
Is this particular unit (nrpe/20) running on a machine that has other
services running on it, or was it the last
You're using local charms (./xenial/mongodb) so it's hard to know for sure
exactly what you're deploying without having the full set of files.
If it is the same as the "official" mongodb: https://jujucharms.com/mongodb/
Then it has several bindings that aren't listed in your bundle. Your bundle
There is model configuration that you can set to tell juju what the proxies
are. Normally you set them at bootstrap time with:
juju bootstrap --model-default http-proxy=http://... --model-default
https-proxy... --model-default no-proxy=
You can also put these settings into
>
> ...
>
> - Update with the information that context.Relations().peer returns? How
> is this different/better/worse then using leader to store the data, or unit
> data even? Because its data on the relation, which makes it fit the
> reactive model better/less cluttered?
>
> - I seem to be
We have a code snippet in deploy that says this:
if len(args.ConfigYAML) > 0 {
settings, err =
ch.Config().ParseSettingsYAML([]byte(args.ConfigYAML), args.ApplicationName)
} else if len(args.Config) > 0 {
// Parse config in a compatible way (see function comment).
>
> ...
>
> The ideal solution is of course to fix it in Juju, and have it stop
> throwing away perfectly valid configuration data :)
>
>
> AFAICT we fixed this in Juju 1.15, but there are 2 places you can pass
config. The old field uses the compatibility of "" means nil, the new field
handles nil
I'd like to give some feedback about how Juju should be using Facades and
versioning and how I'd expect it to be expressed in the client code.
As a base statement, my feeling is that if I write some code that talks
(via a bunch of intermediates) to Juju on the other end, there is going to
be a
Also, if you click the link, it tells you 404, maybe you want something
else. It looks like it switched from being called "kubernetes" to being
called "kubernetes-core", and the quick link didn't get updated.
John
=:->
On Mon, Jan 16, 2017 at 3:17 PM, Anthony Dillon <
ted.
John
=:->
On Mon, Jan 16, 2017 at 3:22 PM, Tom Barber <t...@spicule.co.uk> wrote:
> whilst we're on it
>
> Why when you click spark do you end up at: https://jujucharms.com/u/
> asanjar/spark/ and not cs:apache-spark or whatever the mainline one is?
>
> :)
>
> Tom
>
> ...
>
> +### tuple ### allow any 8000 0.0.0.0/0 any 0.0.0.0/0 in
> +-A ufw-user-input -p tcp --dport 8000 -j ACCEPT
> +-A ufw-user-input -p udp --dport 8000 -j ACCEPT
> +
>
>
If I'm reading this one correctly, it also means that anyone from *any* IP
address (not restricted to your local
Seems more like just a python thing, vs anything to do with Amulet.
https://github.com/kennethreitz/requests/issues/2214
Says you can do some magic around disabled warnings
A better goal might be to have the charm optionally take the config of a
cert to use and configure your tests to include
1.25 does not support LXD managed containers as it uses the old lxc-foo CLI
to manage containers (lxc-start is not the same as "lxc start").
juju-2.0 will use LXD managed containers but there are no plans to backport
that support to 1.25
John
=:->
On Sep 1, 2016 4:12 PM, "Daniel Bidwell"
I'm not sure if the unicode ellipsis would cause table alignment issues
depending on your terminal and font. We could consider it as it does give
quite a few characters back. The longest I can come up with that doesn't
feel just gratuitous is 15
10.10.10alpha10
But that might be going to far. I do
I do see this:
https://github.com/hashicorp/consul/issues/854
Which is that the output from consul is too large and doesn't conform to
the RFC which makes Go unable to read the DNS record.
It does feel like this is a stdlib issue. Are you able to do thinks like
python3 -c "import socket; print
; interfaces up it's still doesn't listen on 10.38.250.0/24.
>
> Thanks,
> Wayne
>
>
>
> On Mon, Nov 7, 2016 at 6:34 AM, John Meinel <j...@arbash-meinel.com>
> wrote:
>
>> What version of Juju are you running? Is it possible the devices didn't
>>
What version of Juju are you running? Is it possible the devices didn't
come up before Juju was up and running? Right now we are doing:
endpoint := net.JoinHostPort("", strconv.Itoa(info.APIPort))
listener, err := net.Listen("tcp", endpoint)
Which means we listen to ":17070". That should
Juju records a longer history in the database, but for ease of debugging we
also save to a plain text file, which gets rotated. It is set to rotate at
300MB and save at most 2 backups. Which means it should go to potentially
~1GB but not grow beyond that. We could compress on rotation, which we
>From what I can tell, there are a number of places where these manual
machines differ from our "standard" install. I think the charms can be
written defensively around this, but its why you're running into more
issues than you normally would.
1. 'noexec' for /tmp. I've heard of this, but as
FWIW I believe this is equivalent to vpc-id=... which is already supported
for EC2. What you're really asking for is being able to select the subnets.
Which we would want to aggregate into spaces so that we can span AZs.
John
=:->
On Nov 15, 2016 19:12, "James Beedy"
So logs in mongo and logs on disk should be capped, and purged when they
get above a certain size. 'audit.log' should never be automatically purged.
Charms in the blobstore are potentially local data that we can't reproduce,
so hard to automatically purge them. I think there has been some work
Right, the issue for test/development iterations is that "machine requested
to booted in cloud" for LXD is a lot closer to 10s. Especially if you set
"enable-os-refresh-update: false" and "enable-os-upgrade: false", which are
also likely to be set in a testing environment.
John
=:->
On Thu, Dec
Why can he not upload the resources? We have several mechanisms in place to
allow for gating charms based on things like "accepting terms", and a
general policy that "juju deploy SOFTWARE" should actually get you SOFTWARE
running in a functional manner. Telling people "do this deploy, but then go
I want to publish and I don’t want any
> resources uploaded on the charm store: https://jujucharms.com/u/
> cloudbaseit/azure-service-fabric/8
>
>
>
> Regards,
>
> Ionut
>
>
>
> *From:* juju-boun...@lists.ubuntu.com [mailto:juju-bounces@lists.
> ubuntu.com] *On Behalf
I don't know specifically about -n, but I do believe we pass unknown
options down to the underlying ssh binary.
John
=:->
On Dec 5, 2016 14:44, "Stefano Simonelli" wrote:
> Hi everyone,
> I work for Scaledb and I'm working on the integration between our solution
> and
That sounds like the juju client knows about the provider but the agent it
is installing (jujud) doesn't. You may need to change the version of the
client so it guarantees it tries to install the developer build of the
agent rather than an official released agent.
John
=:->
On Jan 4, 2017
On Sat, Jan 7, 2017 at 12:43 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Some questions, because this sounds like something perfect for us.
>
> Does this work on MAAS or only openstack?
>
> Does this mean that I can put the constraint "has to be connected to
> network x" on an
1 - 100 of 454 matches
Mail list logo