Question about simplestreams and imagemetadata
Jeroen Vermeulen
jeroen.vermeulen at canonical.com
Tue Aug 6 05:58:17 UTC 2013
On 06/08/13 12:03, Scott Moser wrote:
> I'll talk to be on this today. When we first did the data for azure,
> this difference was by design, as I didn't consider sure images to be
> the same product as other Ubuntu cloud images. They behaved
> differently at boot because cloud-init did not drive initial
> provisioning.
Hi Scott,
Thanks for following up. I suppose that the images being inside the
cloud makes their differences a non-problem... As long as images are
confined to a cloud, there's no reasonable way to specify e.g. an EC2
image for an Azure VM by mistake.
> Since we now have that fixed (at least for saucy) we can update the
> product id. ideally we'd wait to do so on precise until the SRUs have
> gone through.
What are the reasons for waiting? Do we know of any other,
Azure-supporting simplestreams clients that might be affected?
I'm asking because I'm not only eager to get this working, but also
anxious about third-party code starting to rely on the current IDs
before we change them.
Jeroen
More information about the Juju-dev
mailing list