On 08/18/11 - 01:37:16PM, Hugh Brock wrote:
> > The short is, I wouldn't be unhappy if it went into
iwhd.
>
> I wouldn't be unhappy either, but I'm still not clear on what status is
expected in the warehouse for these objects.
>
> Storing an image in the warehouse is the very last thing the factory does when
building. We do not upload any image or set any metadata on that image until after we
have built the image. So the only state that imagefactory would set the status attribute
to would be "COMPLETED" or "FAILED" assuming uploading to the
warehouse worked or not. If we're seeing failures on the upload step, maybe we should
just be cleaning up after ourselves.
Is this a feature, an architectural restriction, or just "the way we
currently do it"? It seems to me that if we're going to use the
warehouse as *the* datastore for this stuff, then creating the image
record in the warehouse should be the first thing the factory does
when building (even though that record might be empty). Now there's
only one place Conductor has to look to learn everything it needs to
know about the image, and there's no need for the connection between
Conductor and Factory to be persistent or have any state or anything
like that.
Is there something dramatically wrong with doing things this way?
Yeah, storing a placeholder option in iwhd when factory initially gets the
build request is the solution we've been kicking around for this. I don't
really know enough of the ins and outs of the factory->warehouse interaction
to say whether that is a problem, though (besides the obvious possibility of
leaving artifacts in the warehouse).
--
Chris Lalancette