This feature is builtin to juju-core for a few months, via juju deploy
--force-machine=$machine_id $charm_spec
On Fri, Jul 12, 2013 at 1:19 PM, Logan McNaughton <<email address hidden>
> wrote:
> This is a fairly big problem, it is holding a lot of people back from
> using MAAS/Juju to deploy OpenStack. I really hope this makes it into
> juju by the time Havana is released. Without this support, Mirantis'
> Fuel looks like a much better option.
>
> --
> You received this bug notification because you are subscribed to juju.
> https://bugs.launchpad.net/bugs/806241
>
> Title:
> It should be possible to deploy multiple units to a machine (unit
> placement)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/806241/+subscriptions
>
This feature is builtin to juju-core for a few months, via juju deploy machine= $machine_ id $charm_spec
--force-
On Fri, Jul 12, 2013 at 1:19 PM, Logan McNaughton <<email address hidden>
> wrote:
> This is a fairly big problem, it is holding a lot of people back from /bugs.launchpad .net/bugs/ 806241 /bugs.launchpad .net/juju/ +bug/806241/ +subscriptions
> using MAAS/Juju to deploy OpenStack. I really hope this makes it into
> juju by the time Havana is released. Without this support, Mirantis'
> Fuel looks like a much better option.
>
> --
> You received this bug notification because you are subscribed to juju.
> https:/
>
> Title:
> It should be possible to deploy multiple units to a machine (unit
> placement)
>
> To manage notifications about this bug go to:
> https:/
>