This is a follow up to https://review.openstack.org/59621 to get
broader discussion..
So at the moment we capture a bunch of details in the image - what
parameters the image was built with and some environment variables.
Last week we were capturing everything, which there is broad consensus
was t
Hi
On 4 December 2013 22:19, Robert Collins wrote:
> So - what about us capturing this information outside the image: we
> can create a uuid for the build, and write a file in the image with
> that uuid, and outside the image we can write
+1
I think having a UUID inside the image is a specta
On Wed, Dec 4, 2013 at 5:19 PM, Robert Collins
wrote:
> This is a follow up to https://review.openstack.org/59621 to get
> broader discussion..
>
> So at the moment we capture a bunch of details in the image - what
> parameters the image was built with and some environment variables.
>
> Last week
On 12/05/2013 08:38 AM, James Slagle wrote:
On Wed, Dec 4, 2013 at 5:19 PM, Robert Collins
wrote:
This is a follow up to https://review.openstack.org/59621 to get
broader discussion..
So at the moment we capture a bunch of details in the image - what
parameters the image was built with and s
Excerpts from Robert Collins's message of 2013-12-04 14:19:44 -0800:
> So - what about us capturing this information outside the image: we
> can create a uuid for the build, and write a file in the image with
> that uuid, and outside the image we can write:
> - all variables (no security ramificat
On 12/06/2013 02:36 PM, Clint Byrum wrote:
Excerpts from Robert Collins's message of 2013-12-04 14:19:44 -0800:
So - what about us capturing this information outside the image: we
can create a uuid for the build, and write a file in the image with
that uuid, and outside the image we can write:
