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
| 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
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
Hi James,
This is an interesting approach, thanks for taking a shot at solving this
problem!
I thought of doing something similar a few months ago. The problematic
aspect here is the assumption of having a provider/substrate already
present for MAAS to be deployed - this is the chicken or the egg
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
