Activity log for bug #1380989
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2014-10-14 09:50:23 | Evan | bug | added bug | ||
| 2014-10-14 09:50:33 | Evan | bug task added | juju-deployer | ||
| 2014-10-14 09:50:50 | Evan | tags | ubuntu-engineering | ||
| 2014-10-14 10:18:52 | Evan | description | If I have a deployer service config like the following: services: B: constraints: mem=8192M A: constraints: mem=1024M And then do: juju add-machine --constraints=mem=8192M juju add-machine --constraints=mem=1024M I end up with a 8GB machine 1, and 1GB machine 2. Now, running juju-deployer over the deployment config pushes service A to machine 1 (8GB) and spawns a third instance with 8GB of RAM. I had expected juju would attempt to place each service on the smallest instance it could find that met the constraints. In this circumstance, I would expect it to use the two machines provided that exactly match the constraints. juju-core 1.20.1 juju-deployer 0.4.3 | If I have a deployer service config like the following: services: B: constraints: mem=8192M A: constraints: mem=1024M And then do: juju add-machine --constraints=mem=8192M juju add-machine --constraints=mem=1024M I end up with a 8GB machine 1, and 1GB machine 2. Now, running juju-deployer over the deployment config pushes service A to machine 1 (8GB) and spawns a third instance with 8GB of RAM. I had expected juju would attempt to place each service on the smallest instance it could find that met the constraints. In this circumstance, I would expect it to use the two machines provided that exactly match the constraints. Running juju add-machine in the order expected by deployer works around this issue. juju-core 1.20.1 juju-deployer 0.4.3 | |
| 2014-10-15 05:04:37 | John George | juju-core: importance | Undecided | High | |
| 2014-10-15 05:04:49 | John George | juju-core: status | New | Triaged | |
| 2014-10-15 05:05:43 | John George | tags | ubuntu-engineering | constraints deployer ubuntu-engineering | |
| 2014-10-15 15:05:14 | Curtis Hovey | juju-core: importance | High | Medium | |
| 2014-10-29 00:12:39 | Kapil Thangavelu | summary | juju/deployer placement dependent on ordering | juju picking randomly from available machines instead of best fit | |
| 2014-10-29 00:14:43 | Curtis Hovey | juju-core: milestone | 1.21 | ||
| 2014-10-29 00:14:45 | Curtis Hovey | juju-core: importance | Medium | High | |
| 2014-11-12 13:36:34 | Curtis Hovey | juju-core: milestone | 1.21 | 1.22 | |
| 2015-01-13 14:38:23 | Canonical Juju QA Bot | juju-core: milestone | 1.22-alpha1 | 1.23 | |
| 2015-02-03 12:45:04 | Kapil Thangavelu | juju-deployer: status | New | Invalid | |
| 2015-04-21 14:00:29 | Curtis Hovey | juju-core: importance | High | Medium | |
| 2015-04-21 14:00:31 | Curtis Hovey | juju-core: milestone | 1.23 | ||
| 2016-10-18 13:28:03 | Anastasia | bug task added | juju | ||
| 2016-10-18 13:28:11 | Anastasia | juju: status | New | Triaged | |
| 2016-10-18 13:28:14 | Anastasia | juju: importance | Undecided | Medium | |
| 2016-10-18 13:28:16 | Anastasia | juju: milestone | 2.1.0 | ||
| 2016-10-18 13:28:20 | Anastasia | juju-core: status | Triaged | Won't Fix | |
| 2017-02-17 14:29:27 | Curtis Hovey | juju: milestone | 2.1-rc2 | ||
| 2022-11-03 16:45:44 | Canonical Juju QA Bot | juju: importance | Medium | Low | |
| 2022-11-03 16:45:46 | Canonical Juju QA Bot | tags | constraints deployer ubuntu-engineering | constraints deployer expirebugs-bot ubuntu-engineering |
