You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Scott Moser(smoser) wrote on 2011-11-29T13:55:04.384203+00:00
currently, in EC2, there is logic to select a mirror based on existence of a dns name that matches the region. Ie
* cloud-init checks ec2 metadata for availability zone (like us-east-1a)
* take off the 'a',
* check for dns name of us-east-1.ec2.archive.ubuntu.com
* use that as mirror if available or fall back to default.
This is good enough for EC2, but not so good for private clouds.
A private cloud may have either a proxy or a full mirror, and want to use that without requiring custom user data on every launch or modifications to the stock images.
To support this, I propose:
* if user-data specifies 'apt_mirror' or 'apt_proxy' use that.
* if a dnsname exists for $availability-zone.archive in the default domain, use that.
* if a dnsname exists in default domain for 'apt-proxy' then configure apt to use that as the proxy
* if a dnsname exists in default domain for 'ubuntu-mirror' then configure apt to use that mirror
This allows the owner of a private cloud to set up dns entries so that cloud guest images "just work", but also allow for user configuration via cloud-config data like:
apt_proxy: http://192.168.1.1:3128/
Related bugs:
bug 974509: cloud-init selects wrong mirror with dns server redirection
The text was updated successfully, but these errors were encountered:
Launchpad user Andreas Hasenack(ahasenack) wrote on 2012-07-05T17:00:14.007899+00:00
This breaks those customers with (already broken) ISPs that have wildcard domains, because "ubuntu-mirror.localdomain" resolves to an actual internet IP, but it's just to show the user a nice html page saying that the domain was not found. Maybe with ads.
This bug was originally filed in Launchpad as LP: #897688
Launchpad details
Launchpad user Scott Moser(smoser) wrote on 2011-11-29T13:55:04.384203+00:00
currently, in EC2, there is logic to select a mirror based on existence of a dns name that matches the region. Ie
* cloud-init checks ec2 metadata for availability zone (like us-east-1a)
* take off the 'a',
* check for dns name of us-east-1.ec2.archive.ubuntu.com
* use that as mirror if available or fall back to default.
This is good enough for EC2, but not so good for private clouds.
A private cloud may have either a proxy or a full mirror, and want to use that without requiring custom user data on every launch or modifications to the stock images.
To support this, I propose:
* if user-data specifies 'apt_mirror' or 'apt_proxy' use that.
* if a dnsname exists for $availability-zone.archive in the default domain, use that.
* if a dnsname exists in default domain for 'apt-proxy' then configure apt to use that as the proxy
* if a dnsname exists in default domain for 'ubuntu-mirror' then configure apt to use that mirror
This allows the owner of a private cloud to set up dns entries so that cloud guest images "just work", but also allow for user configuration via cloud-config data like:
apt_proxy: http://192.168.1.1:3128/
Related bugs:
The text was updated successfully, but these errors were encountered: