Hi folks,
Amir, Cory, and I had a delightful time in the queue today:
+ cleaning house
Nicolás (~nicopace) did a great job adding new tests to lots of
charms. These were originally submitted as individual Merge Proposals, but
later consolidated into a single MP per charm. This decreased the
Suddenly all my deploys stopped working with following errormessage:
Traceback (most recent call last):
File"/usr/bin/juju-deployer", line 9, in
load_entry_point('juju-deployer==0.4.3', 'console_scripts','juju-deployer')()
File"/usr/lib/python2.7/dist-packages/deployer/cli.py", line
All published. The source and signed data are now in agreement.
On Fri, Feb 27, 2015 at 2:16 PM, Curtis Hovey-Canonical
wrote:
>>> ahh. The json was not signed! The signed json is from the previous
>>> release. We will look into this now. I will reply with an update soon.
>
> We queued the resign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jake,
Can you provide some more information:
- - your environments.yaml file
- - machine-0.log, machine-1.log, and machine-2.log from /var/log/juju/
on each machine
Before sending these, please make a quick check to remove any
sensitive info from t
Hi,
I am using juju 1.21.1-trusty-i386 and deploying to a manual environment,
and had a problem deploying wordpress following the getting started page
here [1]. When I tried to view wordpress with a browser it gave me an
"Error establishing a database connection", and from a little bit of
dig
>> Index2 was updated on Thu, 26 Feb 2015 15:09:44 +
>> and the devel product file on Thu, 26 Feb 2015 15:09:44 +
>>
>> ahh. The json was not signed! The signed json is from the previous
>> release. We will look into this now. I will reply with an update soon.
We queued the resigning. The
Awesome talk! thanks for share :)
Em Wed Feb 25 2015 at 9:03:59 PM, David Cheney
escreveu:
> Nice work Chuck!
>
> On Thu, Feb 26, 2015 at 4:47 AM, Charles Butler
> wrote:
> > If you missed out on FOSDEM 2015 and the awesomeness of the Configuration
> > Management room talks, don't fret! The vid
No - I can browse to the sjson file and there is no 1.22-beta4 entry.
It does show up in the .json file though..
Jason
On 02/27/2015 12:34 PM, Curtis Hovey-Canonical wrote:
> Could caching be an issue?
>
> On Fri, Feb 27, 2015 at 1:17 PM, Ryan Beisner
> wrote:
>> Ditto, also seeing that.
>>
>>
Could caching be an issue?
On Fri, Feb 27, 2015 at 1:17 PM, Ryan Beisner
wrote:
> Ditto, also seeing that.
>
> On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs
> wrote:
...
Thanks,https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:devel:tools.sjson
>>
>> or
>>
>>
>> https://streams
Ditto, also seeing that.
On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs
wrote:
> Hi Curtis,
>
> On 02/26/2015 01:47 PM, Curtis Hovey-Canonical wrote:
> > juju-core 1.22-beta4
> >
> > Development releases use the 'devel' simple-streams. You must configure
> > the 'agent-stream' option in your envi
Hi Curtis,
On 02/26/2015 01:47 PM, Curtis Hovey-Canonical wrote:
> juju-core 1.22-beta4
>
> Development releases use the 'devel' simple-streams. You must configure
> the 'agent-stream' option in your environments.yaml to use the matching
> juju agents.
>
> agent-stream: devel
There don't se
Maybe this can help (thanks to Serge):
The simplest way is to use
cgm getvalue memory '' memory.usage_in_bytes
as that only requires cgmanager on the host and in the container.
You can also use lxcfs. You can use it on trusty, but it requires having
ppa:ubuntu-lxc/daily. You'd do
su
Hi.
I've seen several bug reports and workarounds for charms that need to
tune memory settings, which tends to fail horribly when using the
local provider or deploying to lxc containers. It seems to be
impossible to infer how much RAM a service should be using. The end
result is extra configuratio
13 matches
Mail list logo
