Great! Thanks for confirming. I'm happy to have helped de-obfuscate the
situation. I may or may not have caused that same little flavor overrun
"once" - cannot confirm. ;-)
Cheers,
Ryan
On Mon, Feb 19, 2018 at 4:42 PM, James Beedy wrote:
> I wanted to chime back in with the solution to the
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
In one case yesterday, with a full openstack-on-lxd deployed and in use, I
quickly hit the too-many-open-files issue.
I raised fs.inotify.max_user_instances on the host to 50 which
unblocked me for a while. I ended up raising both to 99 and have had
smooth sailing since. Currently, the h
This is good stuff. I think keeping it focused on Juju 2.0 and later,
completely free of legacy shims, is a good thing. I'd love to be using
this natively instead of the collective stack of [Amulet + Juju-deployer +
python-jujuclient], and plan to take it for a spin.
Cheers,
Ryan
On Tue, Nov 1
gt; Oriented Python library.
>
+1000 :-)
> Marco
>
> On Tue, Nov 1, 2016, 4:25 PM Ryan Beisner
> wrote:
>
>> This is good stuff. I think keeping it focused on Juju 2.0 and later,
>> completely free of legacy shims, is a good thing. I'd love to be using
>
As Zuul is an OpenStack project, I'd like to see this developed in line
with the other OpenStack Charms. I would be happy to help light the path
along the way to ensure that all efforts are as efficient as possible, and
that the resultant layer(s), interface(s) and charm(s) can leverage the
powerf
ie. Project repos would be born, developed and maintained here. :-)
https://github.com/openstack?query=charm
On Wed, Nov 2, 2016 at 12:28 PM, Ryan Beisner
wrote:
> As Zuul is an OpenStack project, I'd like to see this developed in line
> with the other OpenStack Charms. I would
Hi All,
Do we have an eta for zesty series recognition in the charm store? It
looks like it is already committed in master, so I imagine it's just a
matter of the store release schedule.
OpenStack Charm CI consumes cs: artifacts for our charm dev and test, and
all of the official OpenStack charm
Nice work, bdx :)
On Fri, Mar 31, 2017 at 8:06 PM, James Beedy wrote:
> The day has finally come for me to turn down the last of our Opsworks
> instances for our PRM application. This marks the completion of one of many
> Opsworks -> Juju conversion projects I've taken on. Thanks everyone for
>
