Activity log for bug #1037727

Date Who What changed Old value New value Message
2012-08-16 19:00:39 Scott Moser bug added bug
2012-08-16 19:01:11 Scott Moser cloud-init (Ubuntu): status New Triaged
2012-08-16 19:01:13 Scott Moser cloud-init (Ubuntu): importance Undecided High
2012-08-16 21:44:41 Eric Hammond bug added subscriber Eric Hammond
2012-08-22 19:31:11 Launchpad Janitor branch linked lp:cloud-init
2012-08-23 05:07:58 Launchpad Janitor branch linked lp:ubuntu/cloud-init
2012-08-23 05:10:23 Launchpad Janitor cloud-init (Ubuntu): status Triaged Fix Released
2012-10-05 15:02:12 Scott Moser nominated for series Ubuntu Precise
2012-10-05 15:02:12 Scott Moser bug task added cloud-init (Ubuntu Precise)
2012-10-05 15:10:22 Scott Moser cloud-init (Ubuntu Precise): status New Triaged
2012-10-05 15:10:25 Scott Moser cloud-init (Ubuntu Precise): importance Undecided High
2012-11-06 21:47:48 Launchpad Janitor branch linked lp:~smoser/ubuntu/precise/cloud-init/sru
2012-11-08 19:24:54 Scott Moser description currently, the ec2 datasource has some code that selects the mirror location by looking at the availability-zone. I think this is generally a pretty good idea. I'd like to extend that to other datasources, and not limit to ".ec2.archive.ubuntu.com". The goal would be to basically check for a mirror at: <availability-zone>[.<cloud>][dns-subdomain] dns subdomain would default to '.cloud.archive.ubuntu.com'. if the datasource provided the 'cloud' value, we'd use that, but otherwise just use availability-zone. This would fit in with what we're currently doing on ec2, but would extend to others. I'd just treat the "cc-direction-[0-9]" availability-zones specially, to know that this is an ec2 one. Then basically append ".ec2" in that case. === Begin SRU Information === [Impact] * Currently, local mirror selection is done specifically for EC2 instances in the DataSource code. cloud-init will select 'us-east-1a.ec2.archive.ubuntu.com' as a mirror in EC2. However, in other clouds, there is no way to get a local mirror selected. The change here is to allow mirrors to be specified in configuration based on templates that can include the "availability-zone". This makes the EC2 code generic and allows a cloud provider to have cloud-init select a local mirror simply by presenting 'availability-zone' in the metadata. With this change, if a cloud provider puts 'region-1.mycloud' into their datasource metadata as the availability-zone, cloud-init will select a mirror at 'region-1.mycloud.clouds.archive.ubuntu.com'. By default, Canonical's dns will return that as a wildcard for archive.ubuntu.com, but the information is availble now in the dns request to specify the address of a local mirror. [Test Case] * This is really a feature backport. There is no specific bug here. However, the behavior change is easily seen by running an instance on a openstack cloud. Previously, the mirror selected would be 'archive.ubuntu.com'. With the change in place, the mirror will be: 'nova.clouds.archive.ubuntu.com' as by default openstack provides the string 'nova' as the availability-zone. [Regression Potential] * Mirror selection will change. It is possible that users relying on the old behavior will have to modify something. [Other Information] * We want this behavior brought back to 12.04 so that LTS images can "just work" to select a local mirror simply by a change in DNS records. It will enable large clouds to provide local mirrors easily. === End SRU Information === currently, the ec2 datasource has some code that selects the mirror location by looking at the availability-zone. I think this is generally a pretty good idea. I'd like to extend that to other datasources, and not limit to ".ec2.archive.ubuntu.com". The goal would be to basically check for a mirror at:   <availability-zone>[.<cloud>][dns-subdomain] dns subdomain would default to '.cloud.archive.ubuntu.com'. if the datasource provided the 'cloud' value, we'd use that, but otherwise just use availability-zone. This would fit in with what we're currently doing on ec2, but would extend to others. I'd just treat the "cc-direction-[0-9]" availability-zones specially, to know that this is an ec2 one. Then basically append ".ec2" in that case.
2012-12-10 23:04:25 Steve Langasek cloud-init (Ubuntu Precise): status Triaged Fix Committed
2012-12-10 23:04:26 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2012-12-10 23:04:28 Steve Langasek bug added subscriber SRU Verification
2012-12-10 23:04:31 Steve Langasek tags verification-needed
2012-12-12 19:09:38 Scott Moser tags verification-needed verification-done
2013-01-08 19:15:42 Clint Byrum tags verification-done
2013-01-08 19:15:43 Clint Byrum tags verification-needed
2013-01-09 00:24:05 Scott Moser tags verification-needed verification-done
2013-01-16 14:20:25 Colin Watson removed subscriber Ubuntu Stable Release Updates Team
2013-01-16 14:20:17 Launchpad Janitor cloud-init (Ubuntu Precise): status Fix Committed Fix Released
2013-08-28 11:32:39 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-proposed