Update Snappy Alpha1 references

[Ben Howard]

On [1], please update the Snappy Alpha1 references for clouds with new Alpha-02 references

Azure [2]:

   Replace: b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-core-devel-amd64-<DATE>-89-en-us-30GB
   With: b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-core-devel-amd64-alpha-02-en-us-30GB

Amazon [3]:

   Replace the AMI table with:

    HVM Instance-Store eu-central-1 = ami-34417229
    HVM Instance-Store sa-east-1 = ami-4b358856
    HVM Instance-Store ap-northeast-1 = ami-449d8045
    HVM Instance-Store eu-west-1 = ami-6347c414
    HVM Instance-Store us-west-1 = ami-a6baa4e3
    HVM Instance-Store us-west-2 = ami-895d03b9
    HVM Instance-Store ap-southeast-2 = ami-05a6d33f
    HVM Instance-Store ap-southeast-1 = ami-cc6b409e
    HVM Instance-Store us-east-1 = ami-cc364fa4
    HVM SSD eu-central-1 = ami-84417299
    HVM SSD sa-east-1 = ami-1d348900
    HVM SSD ap-northeast-1 = ami-1e9a871f
    HVM SSD eu-west-1 = ami-9945c6ee
    HVM SSD us-west-1 = ami-c4b8a681
    HVM SSD us-west-2 = ami-b15b0581
    HVM SSD ap-southeast-2 = ami-97a1d4ad
    HVM SSD ap-southeast-1 = ami-24684376
    HVM SSD us-east-1 = ami-3e2f5656

    Replace the example AMI ID of ami-6c0a6704 w/ ami-3e2f5656

GCE is still forthcoming due to a bug.

[1] https://developer.ubuntu.com/en/snappy/
[2] http://www.ubuntu.com/cloud/tools/snappy#snappy-azure
[3] http://www.ubuntu.com/cloud/tools/snappy#snappy-amazon

[Peter Mahnke (peterm-ubuntu)]

David,

I have fixed #2 and #3, but #1 is for you guys.

Can you look and let me know?

Thanks,

Peter

[David Planella (dpm)]

> On [1], please update the Snappy Alpha1 references for clouds with new Alpha-02 references

Could someone point me exactly to where we're mentioning alphas on https://developer.ubuntu.com/snappy ?

This can be fixed in a matter of minutes, but we'd need more detailed info.

[Daniel Holbach (dholbach)]

[1] needs to be fixed in http://www.ubuntu.com/cloud/tools/snappy - I'll add a task for the website.

[Peter Mahnke (peterm-ubuntu)]

I am assuming this is fixed now. re-open if we missed anything.