Goal:

• Reduce the amount of required maintenance by using cloud-init modules instead of shell scripts
• Improve compatibility with cloud environments that enforce limits on the size of the provided cloud-init configuration
• Simplify user workflows by providing fewer templates to select from

Acceptance Criteria:

• Features of all Linux userdata templates in app/views/unattended/provisioning_templates/user_data/*.erb are merged into app/views/unattended/provisioning_templates/user_data/userdata_default.erb
• The features are implemented using native cloud-init modules and not with shell like today

Open questions:

• Should Compute Resources know the size limits enforced in the Clouds and raise errors before the template is sent to the cloud?
• Should app/views/unattended/provisioning_templates/cloud_init/cloud_init_default.erb and app/views/unattended/provisioning_templates/user_data/userdata_default.erb be unified too?