Dmitrii,
Thanks for the response.
When taking into account the overhead to get MAAS deployed as charms, it
definitely makes the LXD provider method you have described seem very
appealing. Some issues I've experienced trying to get MAAS HA deployed are
such that it seems like just a ton of infrast
Hello everyone!
I try to deploy an application to lxd container on manually attached machine
(ubuntu-xenial)
and container do not start, with the error - «Missing parent 'docker_gwbridge’
for nic ‘eth2’».
I see in the logs, that juju tries to add docker interfaces to the container,
though on a
It does seem like Juju operating the LXD provider, but spanning multiple
machines would be an answer. I do believe that LXD itself is introducing
clustering into their API in the 18.04 cycle. Which would probably need
some updates on the Juju side to handle their targeted provisioning (create
a con
| I can also see that it took a few attempts to get there (the last machine
is #40 :)
It was a trying process to say the least - possibly I am one of few users
who would stick around to see it through. which is actually great
because it creates a market for people to provide the service of pro
Oo possibly I'm on to something (last item/very bottom)
https://imgur.com/a/6Wyd0
On Mon, Nov 27, 2017 at 5:53 AM, James Beedy wrote:
> | I can also see that it took a few attempts to get there (the last
> machine is #40 :)
>
> It was a trying process to say the least - possibly I am on
Looking at the jujucharms page for my team namespace [0], I see a place
where models may be shared with the team. Is this something that is in the
works, or is there existing functionality where models can be shared
with/owned by a team?
Thanks
[0] https://imgur.com/a/7xint
--
Juju mailing list
So models shared with you are currently possible, but I believe everything
is still owned as an individual user, rather than at a team scope. You
should be able to add other users as 'admin' on an existing model, but
we're still working through a backlog of places that treat "owner"
differently tha
On 23 November 2017 at 21:37, Tilman Baumann
wrote:
> On 22.11.2017 23:26, Haw Loeung wrote:
>> Hi Tilman,
>>
>> On Wed, Nov 22, 2017 at 04:02:08PM +0100, Tilman Baumann wrote:
>>> However, that doesn't seem to work. Juju complains the relation doesn't
>>> exist.
>>> $ juju add-relation cassandra-
On 22 November 2017 at 01:58, Junien Fridrick
wrote:
> I was also thinking that maybe the snap layer could save which
> application installed which snap, and if said application is removed,
> then remove said snap. Would that be a good idea ?
Your subordinate charm doesn't know it is the only ch
