On 19/10/16 16:15, Marco Ceppi wrote:
>> 2. Don't colocate units if at all possible. In separate containers on the
>> same machine, sure. But there's absolutely no guarantee that colocated
>> units won't conflict with each other. What you're asking about is the very
>> problem colocation causes.
> Subordinate charms only make sense when collocated. And I would argue that
subordinates are extremely common, at least in production environments.
> In this context clean up is very important because it's not unusual for
> operators
to switch technologies. For example replace telegraf with node
The Juju QA & Release team is pleased to announce support for Amazon's
new US East (Ohio) Region, aka us-east-2.
To use it with 2.0.0, just run "juju update-clouds" once. You will see
the message:
Updated your list of public clouds with 1 cloud region added:
added cloud region:
- aws
On 20 October 2016 at 16:09, Rye Terrell wrote:
> > Subordinate charms only make sense when collocated. And I would argue that
> subordinates are extremely common, at least in production environments.
>
> > In this context clean up is very important because it's not unusual for
> > operators
> t
> Do you have a real world example at hand?
No, why?
On Thu, Oct 20, 2016 at 2:26 PM, Free Ekanayaka <
free.ekanay...@canonical.com> wrote:
> On 20 October 2016 at 16:09, Rye Terrell
> wrote:
>
>> > Subordinate charms only make sense when collocated. And I would argue that
>> subordinates are e
On 20 October 2016 at 23:16, Rye Terrell wrote:
> > Do you have a real world example at hand?
>
> No, why?
>
Easier to reason around a specific concrete case than talk about
theoretical situations. After looking at a few concrete situations we can
come up with a more realistic understanding of t
Thanks; I see what you mean - I'll see if I can find any examples.
On Thu, Oct 20, 2016 at 5:33 PM, Free Ekanayaka <
free.ekanay...@canonical.com> wrote:
> On 20 October 2016 at 23:16, Rye Terrell
> wrote:
>
>> > Do you have a real world example at hand?
>>
>> No, why?
>>
>
> Easier to reason ar
I used conjure-up to deploy openstack-novalxd on a Xenial system. Before
deploying, the operating system was updated. LXD init was setup with dir, not
xfs. All but one of the charms has a status of “unit is ready"
The lxd/0 subordinate charm has a status of: hook failed: "config-changed”.
Odd it looks like the container has a read only file system? I ran through
a full openstack-novalxd deployment today and one of the upstream
maintainers ran through the same deployment and didn't run into any issues.
On Thu, Oct 20, 2016, 10:02 PM Heather Lanigan wrote:
>
> I used conjure-up to
