I don't think this is a bug with juju. Canonistack is ill. Juju CI has tested on the cloud for 6 moths.
3 months ago a simple wordpress stack could be stood up in 5 minutes. Juju CI was located in canonistack at the time and the lxc tests took about 5 minutes.
But when canonistack became over-resourced, Juju CI was moved to a different cloud. We will test in canonistack.
It now take 25 minutes to do *less* work than it used to do in 5 minutes. We do less work by not deploying wordpress since it doesn't work on private clouds. http://juju-ci.vapour.ws:8080/view/Providers/
I don't think this is a bug with juju. Canonistack is ill. Juju CI has tested on the cloud for 6 moths.
3 months ago a simple wordpress stack could be stood up in 5 minutes. Juju CI was located in canonistack at the time and the lxc tests took about 5 minutes.
But when canonistack became over-resourced, Juju CI was moved to a different cloud. We will test in canonistack. juju-ci. vapour. ws:8080/ view/Providers/
It now take 25 minutes to do *less* work than it used to do in 5 minutes. We do less work by not deploying wordpress since it doesn't work on private clouds.
http://