juju-core

  1. Bug #1053419
  2. Activity log

Activity log for bug #1053419

Date Who What changed Old value New value Message
2012-09-20 14:03:05 William Reade bug added bug
2012-09-20 14:06:24 Gustavo Niemeyer description <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/ - v1/ - v2/ - machine-0 -> ./v2 - principal-0 -> ./v1 - subordinate-0 -> ./v1 - agents/ - principal-0/ - <unit stuff> - subordinate-0/ - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/ - v1/ - v2/ - machine-0 -> ./v2 - containers/ - principal-0/ - var/lib/juju/ - tools/ - v1/ - principal-0 -> ./v1 - subordinate-0 -> ./v1 - units/ - principal-0/ - <unit stuff> - subordinate-0/ - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes. <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - principal-0 -> ./v1   - subordinate-0 -> ./v1 - agents/   - principal-0/     - <unit stuff>   - subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - unit-principal-0/     - var/lib/juju/       - tools/         - v1/         - unit-principal-0 -> ./v1         - unit-subordinate-0 -> ./v1       - units/         - unit-principal-0/           - <unit stuff>         - unit-subordinate-0/           - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes.
2012-09-20 14:06:42 Gustavo Niemeyer description <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - principal-0 -> ./v1   - subordinate-0 -> ./v1 - agents/   - principal-0/     - <unit stuff>   - subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - unit-principal-0/     - var/lib/juju/       - tools/         - v1/         - unit-principal-0 -> ./v1         - unit-subordinate-0 -> ./v1       - units/         - unit-principal-0/           - <unit stuff>         - unit-subordinate-0/           - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes. <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - unit-principal-0 -> ./v1   - unit-subordinate-0 -> ./v1 - agents/   - unit-principal-0/     - <unit stuff>   - unit-subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - unit-principal-0/     - var/lib/juju/       - tools/         - v1/         - unit-principal-0 -> ./v1         - unit-subordinate-0 -> ./v1       - units/         - unit-principal-0/           - <unit stuff>         - unit-subordinate-0/           - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes.
2012-09-20 14:16:28 William Reade description <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - unit-principal-0 -> ./v1   - unit-subordinate-0 -> ./v1 - agents/   - unit-principal-0/     - <unit stuff>   - unit-subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - unit-principal-0/     - var/lib/juju/       - tools/         - v1/         - unit-principal-0 -> ./v1         - unit-subordinate-0 -> ./v1       - units/         - unit-principal-0/           - <unit stuff>         - unit-subordinate-0/           - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes. <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - principal-0 -> ./v1   - subordinate-0 -> ./v1 - agents/   - principal-0/     - <unit stuff>   - subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - principal-0/     - tools/       - v1/       - principal-0 -> ./v1       - subordinate-0 -> ./v1     - units/       - principal-0/         - <unit stuff>       - subordinate-0/         - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes.
2012-09-20 14:20:49 Gustavo Niemeyer description <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - principal-0 -> ./v1   - subordinate-0 -> ./v1 - agents/   - principal-0/     - <unit stuff>   - subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - principal-0/     - tools/       - v1/       - principal-0 -> ./v1       - subordinate-0 -> ./v1     - units/       - principal-0/         - <unit stuff>       - subordinate-0/         - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes. <capturing lisbon discussion & agreement> At the moment we have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2   - principal-0 -> ./v1   - subordinate-0 -> ./v1 - agents/   - unit-principal-0/     - <unit stuff>   - unit-subordinate-0/     - <unit stuff> ...but this mixes stuff-in-container with stuff-outside-container. We should actually have: /var/lib/juju/ - tools/   - v1/   - v2/   - machine-0 -> ./v2 - containers/   - unit-principal-0/     - tools/       - v1/       - unit-principal-0 -> ./v1       - unit-subordinate-0 -> ./v1     - units/       - unit-principal-0/         - <unit stuff>       - unit-subordinate-0/         - <unit stuff> ...and ensure that the machiner, when it deploys a new container, actually *copies* its tools into the container; this chroot-without-actually-chrooting style will make it much easier to switch over to *isolated* containers when the time comes.
2012-12-22 19:00:20 William Reade juju-core: status New Won't Fix