Activity log for bug #1971190
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2022-05-02 18:51:50 | Simon Déziel | bug | added bug | ||
| 2022-05-02 18:51:59 | Simon Déziel | bug | added subscriber Ubuntu containers team | ||
| 2022-05-02 18:52:05 | Simon Déziel | tags | lxd-cloud | ||
| 2022-06-06 10:42:14 | Vitaly Antonenko | tags | lxd-cloud | constraints lxd-cloud | |
| 2022-06-06 10:42:22 | Vitaly Antonenko | juju: importance | Undecided | Wishlist | |
| 2022-06-06 10:42:31 | Vitaly Antonenko | tags | constraints lxd-cloud | constraints feature lxd-cloud | |
| 2022-06-06 10:42:36 | Vitaly Antonenko | bug | added subscriber Vitaly Antonenko | ||
| 2022-06-06 10:46:43 | Vitaly Antonenko | juju: status | New | Triaged | |
| 2023-03-28 19:32:39 | Simon Déziel | summary | Machine constrain to target a cluster member when deploying to LXD | Machine constraint to target a cluster member when deploying to LXD | |
| 2023-03-28 19:32:51 | Simon Déziel | description | When launching instances on a LXD cluster, one can either let the cluster decide on the instance's placement or request a specific cluster member to be the target. Here is how to do the explicit targeting with `lxc`: ``` lxc launch images:ubuntu/jammy my-lxd-cluster: --target nodeA ``` Having a Juju machine constrain to accomplish the same would be useful. | When launching instances on a LXD cluster, one can either let the cluster decide on the instance's placement or request a specific cluster member to be the target. Here is how to do the explicit targeting with `lxc`: ``` lxc launch images:ubuntu/jammy my-lxd-cluster: --target nodeA ``` Having a Juju machine constraint to accomplish the same would be useful. |
