[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
Agree with Eric- this will be less expensive in the long run, though potential to use CDN for the mirror is intriguing. One last point in support of CNAMEs- in case there is unease with relying on the CNAME solution (as Canonical does not control routing in EC2), rest assured that this method is supported and recommended by EC2 engineering team and is used by virtually every large deployment on EC2. One additional benefit is that, with a low time-to-live value, you can easily replace a troubled repo server with a simple ec2-associate- elastic-ip command. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
Agree with Eric- this will be less expensive in the long run, though potential to use CDN for the mirror is intriguing. One last point in support of CNAMEs- in case there is unease with relying on the CNAME solution (as Canonical does not control routing in EC2), rest assured that this method is supported and recommended by EC2 engineering team and is used by virtually every large deployment on EC2. One additional benefit is that, with a low time-to-live value, you can easily replace a troubled repo server with a simple ec2-associate- elastic-ip command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
Hi Folks, To whoever manages DNS for this repository: a more elegant solution not requiring an package patches would have been to follow this practice for DNS on EC2. Try to use CNAMES to the fully-qualified domain name EC2 instead of A records. For example, at the moment you are using: us-west-1.ec2.archive.ubuntu.com. 600 IN A 10.162.150.127 This address is apparently not routable from the outside world (perhaps to avoid bandwidth charges?) Had you used a routable EC2 Elastic IP, and a CNAME record pointing to the EC2 assigned FQDN, lookup requests by VPC servers would have the public elastic IP returned like this: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 108.20.220.125 Lookup requests by VPC servers would have the public elastic IP returned, while instances launched normally in EC2 would receive the private address: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 10.252.111.96 I've made these addresses up, of course, and I understand you have multiple servers for each hostname, but we use this method with weighted round robin DNS on EC2 as well and it works as in the example above. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615545] Re: Instances launched in a VPC cannot access ec2.archive.ubuntu.com
Hi Folks, To whoever manages DNS for this repository: a more elegant solution not requiring an package patches would have been to follow this practice for DNS on EC2. Try to use CNAMES to the fully-qualified domain name EC2 instead of A records. For example, at the moment you are using: us-west-1.ec2.archive.ubuntu.com. 600 IN A 10.162.150.127 This address is apparently not routable from the outside world (perhaps to avoid bandwidth charges?) Had you used a routable EC2 Elastic IP, and a CNAME record pointing to the EC2 assigned FQDN, lookup requests by VPC servers would have the public elastic IP returned like this: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 108.20.220.125 Lookup requests by VPC servers would have the public elastic IP returned, while instances launched normally in EC2 would receive the private address: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 10.252.111.96 I've made these addresses up, of course, and I understand you have multiple servers for each hostname, but we use this method with weighted round robin DNS on EC2 as well and it works as in the example above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392532] Re: apache2.2-common: /etc/init.d/apache2 script is empty
Ran into this in EC2 instance as well, where symlink for log directories to an EBS mount point is preferred practice (for post crash analysis). I can live without rotated logs, but it's added several steps in the apt- get upgrade process (remove symlink, move directory back to /var/log, run upgrades, re-create symlinks). -- apache2.2-common: /etc/init.d/apache2 script is empty https://bugs.launchpad.net/bugs/392532 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 392532] Re: apache2.2-common: /etc/init.d/apache2 script is empty
Ran into this in EC2 instance as well, where symlink for log directories to an EBS mount point is preferred practice (for post crash analysis). I can live without rotated logs, but it's added several steps in the apt- get upgrade process (remove symlink, move directory back to /var/log, run upgrades, re-create symlinks). -- apache2.2-common: /etc/init.d/apache2 script is empty https://bugs.launchpad.net/bugs/392532 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
