fwiw, i think this is an important issue for local provider, going to try
and resurrect at the sprint. i currently do a separately mounted ssd as
btrfs (msata), and get 0.4s to create and start a container (via lxc-clone
-s and lxc-start) compared to 3-5m on juju. This sort of
responsive/interactive behavior is exactly the sort of reason people like
tools like docker.
On Fri, Oct 11, 2013 at 7:53 PM, Curtis Hovey <email address hidden> wrote:
fwiw, i think this is an important issue for local provider, going to try interactive behavior is exactly the sort of reason people like
and resurrect at the sprint. i currently do a separately mounted ssd as
btrfs (msata), and get 0.4s to create and start a container (via lxc-clone
-s and lxc-start) compared to 3-5m on juju. This sort of
responsive/
tools like docker.
On Fri, Oct 11, 2013 at 7:53 PM, Curtis Hovey <email address hidden> wrote:
> ** Changed in: juju-core /bugs.launchpad .net/bugs/ 1203291 /bugs.launchpad .net/juju- core/+bug/ 1203291/ +subscriptions
> Importance: Medium => Low
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> local provider moar awesome with lxc-clone
>
> To manage notifications about this bug go to:
> https:/
>