[feature-request] Add non-x86 Ubuntu EC2 mirrors in to default cloud-init configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned |
Bug Description
With the announcement of EC2s A1 instances we'd (CPC) like to be able to rely on cloud-init to configure archive mirrors for non-x86 architectures.
Currently the AMIs have the mirrors configured using /etc/cloud/
```
# Add archive mirrors for non-x86 architectures
system_info:
package_mirrors:
- arches: [i386, amd64]
failsafe:
primary: http://
security: http://
search:
primary:
- http://
- http://
- http://
security: []
- arches: [armhf, armel, default]
failsafe:
primary: http://
security: http://
search:
primary:
- http://
- http://
- http://
security: []
```
See http://
So the feature request is that coud-init configure the above mirrors automatically without us having to write /etc/cloud/
Please let me know if you would like me to spin up instances for testing instead or if you need any further info.
Related branches
- Server Team CI bot: Approve (continuous-integration)
- cloud-init Commiters: Pending requested
-
Diff: 1245 lines (+556/-145)23 files modifiedChangeLog (+54/-0)
bash_completion/cloud-init (+4/-1)
cloudinit/cmd/devel/net_convert.py (+10/-5)
cloudinit/cmd/main.py (+4/-16)
cloudinit/config/cc_write_files.py (+6/-1)
cloudinit/dhclient_hook.py (+72/-38)
cloudinit/net/eni.py (+15/-14)
cloudinit/net/netplan.py (+3/-3)
cloudinit/net/sysconfig.py (+21/-4)
cloudinit/sources/DataSourceAzure.py (+2/-2)
cloudinit/sources/DataSourceNoCloud.py (+31/-1)
cloudinit/sources/helpers/vmware/imc/config_nic.py (+2/-3)
cloudinit/tests/test_dhclient_hook.py (+105/-0)
cloudinit/version.py (+1/-1)
config/cloud.cfg.tmpl (+11/-1)
debian/changelog (+16/-0)
tests/cloud_tests/releases.yaml (+16/-0)
tests/unittests/test_cli.py (+8/-8)
tests/unittests/test_datasource/test_nocloud.py (+66/-34)
tests/unittests/test_handler/test_handler_write_files.py (+12/-0)
tests/unittests/test_net.py (+44/-6)
tests/unittests/test_vmware_config_file.py (+52/-6)
tox.ini (+1/-1)
- Chad Smith: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 23 lines (+11/-1)1 file modifiedconfig/cloud.cfg.tmpl (+11/-1)
description: | updated |
summary: |
- [feature-request] Add support for adding adding archive mirrors for - non-x86 architectures on ec2 + [feature-request] Add non-x86 Ubuntu EC2 mirrors in to default cloud- + init configuration |
Changed in cloud-init: | |
importance: | Undecided → Medium |
@Phillip,
We have two possible paths here: %(ec2_region) s.ec2.ports. ubuntu. com/ubuntu- ports/ %(availability_ zone)s. clouds. ports.ubuntu. com/ubuntu- ports/ %(region) s.clouds. ports.ubuntu. com/ubuntu- ports/
a.) make 'default' use the 'search/primary' list:
- http://
- http://
- http://
b.) add a 'arches: [armhf, armel]' that uses the above search list
and leave the 'default' to fall back to ports.ubuntu.com
The choice is based on whether or not the infrastructure at archive. ubuntu. com and *.clouds. archive. ubuntu. com
*.ec2.
support arches other than armhf and armel..
I suspect that they do support arm64, but do they support others? paste.ubuntu. com/p/D6wW4JqJr W/ paste.ubuntu. com/p/hwnmFxJsM v/
* yes: http://
* no: http://
Also relevant is the question of whether or not we want to have 1.ec2.ports. ubuntu. com or us-east- 1a.clouds. ports.ubuntu. com .
user's mirror selection change through an SRU. Even though the
official mirrors may support it, the customer may have put up
a 'ports.ubuntu.com' mirror and even dns-hijacked that, but
their infrastrucutre likely would not support requests to
us-east-