Merge ~utlemming/cloud-init:ubuntu/devel into cloud-init:ubuntu/devel

Proposed by Ben Howard on 2016-10-03
Status: Merged
Merged at revision: f52be63b1bc67c6600507ca9ee071d33a60f5511
Proposed branch: ~utlemming/cloud-init:ubuntu/devel
Merge into: cloud-init:ubuntu/devel
Diff against target: 16 lines (+3/-3)
1 file modified
debian/cloud-init.templates (+3/-3)
Reviewer Review Type Date Requested Status
Scott Moser 2016-10-03 Pending
Review via email: mp+307391@code.launchpad.net

Description of the Change

Enabled DigitalOcean datasource by default. This change is entirely safe as the DigitalOcean datasource used dmi data to identify if its on DigitalOcean. I put it be before Azure as it it does not have an dependencies other than checking DMI data.

To post a comment you must log in.
Scott Moser (smoser) wrote :

Generally speaking, we want commit messages on the merge proposal in "git style"
   subject
   <blank line>
   details

Scott Moser (smoser) wrote :

Pretty sure that you need to add a entry to 'Choices' as well as 'Choices-C'.
Please test and dpkg-reconfigure cloud-init to verify functional.

Also, I went ahead and added DigitalOcean to the deafult datasource list in settings.py in cloud-init.

~utlemming/cloud-init:ubuntu/devel updated on 2016-10-18
61a7777... by Ben Howard on 2016-10-18

Merge remote-tracking branch 'upstream/ubuntu/devel' into ubuntu/devel

1112741... by Ben Howard on 2016-10-18

debian/cloud-init.templates: enabled DigitalOcean by default

Added DigitalOcean to the default templates as enabled by default.
This allows cloud-init to work out of the box on DigitalOcean droplets.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/debian/cloud-init.templates b/debian/cloud-init.templates
2index f056f05..494c27a 100644
3--- a/debian/cloud-init.templates
4+++ b/debian/cloud-init.templates
5@@ -1,8 +1,8 @@
6 Template: cloud-init/datasources
7 Type: multiselect
8-Default: NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, Ec2, CloudStack, None
9-Choices-C: NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, Ec2, CloudStack, None
10-Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: Reads data from Openstack Config Drive, OpenNebula: read from OpenNebula context disk, Azure: read from MS Azure cdrom. Requires walinux-agent, AltCloud: config disks for RHEVm and vSphere, OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu MAAS, GCE: google compute metadata service, OpenStack: native openstack metadata service, CloudSigma: metadata over serial for cloudsigma.com, SmartOS: Read from SmartOS metadata service, Ec2: reads data from EC2 Metadata service, CloudStack: Read from CloudStack metadata service, None: Failsafe datasource
11+Default: NoCloud, ConfigDrive, OpenNebula, DigitalOcean, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, Ec2, CloudStack, None
12+Choices-C: NoCloud, ConfigDrive, OpenNebula, DigitalOcean, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, SmartOS, Ec2, CloudStack, None
13+Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: Reads data from Openstack Config Drive, OpenNebula: read from OpenNebula context disk, DigitalOcean: reads data from Droplet datasource, Azure: read from MS Azure cdrom. Requires walinux-agent, AltCloud: config disks for RHEVm and vSphere, OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu MAAS, GCE: google compute metadata service, OpenStack: native openstack metadata service, CloudSigma: metadata over serial for cloudsigma.com, SmartOS: Read from SmartOS metadata service, Ec2: reads data from EC2 Metadata service, CloudStack: Read from CloudStack metadata service, None: Failsafe datasource
14 Description: Which data sources should be searched?
15 Cloud-init supports searching different "Data Sources" for information
16 that it uses to configure a cloud instance.

Subscribers

People subscribed via source and target branches