support deploy with -n 0
Bug #1262750 reported by
Kapil Thangavelu
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
With manual placement integration efforts, we often separately create an application from placement of that application on to a machine, as machine allocation and workload placement can be separately managed then application config/charm properties. To support this juju would need to support deploying/creating an application with zero units.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: deploy manual-provider |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
description: | updated |
To post a comment you must log in.
An alternative that would be viable would be an api only mechanism for
add-service.
On Sat, Dec 21, 2013 at 10:02 AM, Curtis Hovey <email address hidden> wrote:
> ** Changed in: juju-core /bugs.launchpad .net/bugs/ 1262750 /bugs.launchpad .net/juju- core/+bug/ 1262750/ +subscriptions
> Status: New => Triaged
>
> ** Changed in: juju-core
> Importance: Undecided => High
>
> ** Tags added: deploy manual-provider
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> support deploy with -n 0
>
> To manage notifications about this bug go to:
> https:/
>