Question about simplestreams and imagemetadata

Scott Moser scott.moser at canonical.com
Tue Aug 6 05:03:33 UTC 2013


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. 

 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. 

On Aug 6, 2013, at 12:37 AM, Ian Booth <ian.booth at canonical.com> wrote:

>> 
>> I'm trying to figure out why simplestreams isn't working for the Azure provider.
>> 
>> The problem lies in matching the product IDs.  From the image constraint we
>> pass, the imagemetadata code decides that we're looking for product IDs like
>> 
>>    com.ubuntu.cloud:server:12.04:amd64
>> 
>> The structure of that ID is encoded in ImageConstraint.Ids(), in
>> environs/imagemetadata.
>> 
>> But the product IDs in the simplestream data look like:
>> 
>>    com.ubuntu.cloud:server:12.04:amd64:azure
>> 
>> (See
>> http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:azure.json
>> for these).
>> 
>> Does anyone know how this is supposed to work?  Am I doing something wrong, or
>> does something outside our provider need to change?
> 
> 
> The product IDs generated for Azure images are not consistent with what's been
> used for EC2 and Openstack. The extra ":azure" part at the end is not recognised
> by Juju.
> 
> The scripts used to generate the Azure simplestreams metadata need to be changed
> to produce output that is consistent with the format used for other cloud vendors.
> 
> Scott, who do we need to talk to about this?



More information about the Juju-dev mailing list