LXC deployments should be done serially so performance is not degraded

[Caio Begotti]

Talking to Marco Ceppi on the mailing list about a local LXC deployment with Juju:

----------
> 5. Juju should queue multiple deployment in order not to hurt performance, both of disk and network IO. More than 3
> deployments in parallel on my machine makes it all really slow. I just leave Juju for a while and go get some coffee because the
> system goes crazy. Or I have to break up manually the deployments, while Juju could have just queued it all and the CLI could
> simply display it as "queued" instead. I know it would need to analyse the machine's hardware to guess a number different from 3
> but think about it if your deployments have about 10 different services... things that take 20 minutes can easily take over 1 hour.

This does severely affect performance on the local provider, but juju is designed to run events asynchronously in an environment. File a bug/feature request for this at http://bugs.launchpad.net/juju-core/+filebug to request that LXC deployments be done serially.
----------

[Caio Begotti (caio1982)]

I would appreciate at least a short explanation why it's being closed as "won't fix" :-)

[Anastasia (anastasia-macmood)]

@Caio Begotti,
"juju-core" is an old Juju 1 project. We only accept Critical bugs here that may still need to be addressed in 1.25 series.

"juju" is the new project for bugs/issues/suggestions for Juju 2. An email went out couple of months ago saying that we will be moving some bugs over, the rest will be closed "eventually" unless people are interested in having us addressing their concerns in Juju 2. "Eventually" is now :D since Juju 2 was released last week \o/

I am happy to re-target this to "juju" if you would like us to keep it on "wish list" for scheduling.

Please note that Juju 2 uses LXD not LXC.