Charles Plessy wrote:
>
> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/cloud-init.templates
>
>
> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cloud-init/saucy/view/head:/debian/control
The Ubuntu template has a couple of extra choices; diffing against the
version we first saw:
-Default: NoCloud, ConfigDrive, OVF, MAAS
+Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
-Choices-C: NoCloud, ConfigDrive, OVF, MAAS, Ec2
+Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
-Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive:
Reads data from Openstack Config Drive, OVF: Reads data from OVF Transports,
MAAS: Reads data from Ubuntu MAAS, Ec2: reads data from EC2 Metadata service
+Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive:
Reads data from Openstack Config Drive, AltCloud: config disks for RHEVm and
vSphere, OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu
MAAS, Ec2: reads data from EC2 Metadata service, CloudStack: Read from
CloudStack metadata service, None: Failsafe datasource
But what's the reason for this change?
-_Description: Which data sources should be searched?
+Description: Which data sources should be searched?
I can try to reimpose the logic of Christian's debconf-best-practice
changes, but I'm not clear what "AltCloud: config disks for RHEVm and
vSphere" is saying. I'm going to guess that the corrected version
should just offer to read from "AltCloud config disks".
Oh, except that a search suggests that these AltCloud config disks are
either virtual floppies or compact discs. Maybe it should just be
"AltCloud user data"?
Then the control file... has a bizarrely shrunken description. As far
as I can see the best option is to throw it out and substitute our
edited version.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru old/cloud-init.templates new/cloud-init.templates
--- old/cloud-init.templates 2013-06-08 09:02:02.972669186 +0100
+++ new/cloud-init.templates 2013-06-08 09:38:22.702410176 +0100
@@ -2,11 +2,11 @@
Type: multiselect
Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
-Choices: NoCloud: Reads info from /var/lib/cloud/seed only, ConfigDrive: Reads
data from Openstack Config Drive, AltCloud: config disks for RHEVm and vSphere,
OVF: Reads data from OVF Transports, MAAS: Reads data from Ubuntu MAAS, Ec2:
reads data from EC2 Metadata service, CloudStack: Read from CloudStack metadata
service, None: Failsafe datasource
-Description: Which data sources should be searched?
+__Choices: /var/lib/cloud/seed only, Openstack Config Drive, AltCloud config
disks, OVF Transports, Ubuntu MAAS, EC2 Metadata service, CloudStack metadata
service, Failsafe datasource
+_Description: Data sources to read from:
Cloud-init supports searching different "Data Sources" for information
that it uses to configure a cloud instance.
.
- Warning: Only select 'Ec2' if this system will be run on a system with
- the EC2 metadata service present. Doing so incorrectly will result in
- a substantial timeout on boot.
+ Please note that "EC2 Metadata service" should be used only if
+ the EC2 metadata service is present. Otherwise, it will trigger
+ a very noticeable timeout on boot.
diff -ru old/control new/control
--- old/control 2013-06-08 09:02:47.811372794 +0100
+++ new/control 2013-06-08 09:43:41.929332550 +0100
@@ -35,9 +35,14 @@
Replaces: ec2-init (<<0.5.3)
Conflicts: ec2-init (<<0.5.3)
XB-Python-Version: ${python:Versions}
-Description: Init scripts for cloud instances
- Cloud instances need special scripts to run during initialisation
- to retrieve and install ssh keys and to let the user run various scripts.
+Description: configuration and customization of cloud instances
+ Cloud-init provides a framework and tool written in Python to handle early
+ initialization of a cloud instance. It can for example set a default locale
+ and hostname, generate SSH private host keys, add SSH keys to a user's
+ authorized_keys so they can log in, and set up ephemeral mount points.
+ .
+ Cloud-init's behavior can be configured via data given by the user at
+ instance launch time.
Package: grub-legacy-ec2
Depends: debconf (>= 1.5.19) | cdebconf,
Template: cloud-init/datasources
Type: multiselect
Default: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
Choices-C: NoCloud, ConfigDrive, AltCloud, OVF, MAAS, Ec2, CloudStack, None
__Choices: /var/lib/cloud/seed only, Openstack Config Drive, AltCloud config
disks, OVF Transports, Ubuntu MAAS, EC2 Metadata service, CloudStack metadata
service, Failsafe datasource
_Description: Data sources to read from:
Cloud-init supports searching different "Data Sources" for information
that it uses to configure a cloud instance.
.
Please note that "EC2 Metadata service" should be used only if
the EC2 metadata service is present. Otherwise, it will trigger
a very noticeable timeout on boot.
Source: cloud-init
Section: admin
Priority: extra
Maintainer: Scott Moser <smo...@ubuntu.com>
Build-Depends: cdbs,
debhelper (>= 5.0.38),
po-debconf,
pyflakes,
pylint,
python (>= 2.6.6-3~),
python-mocker,
python-nose,
python-setuptools
XS-Python-Version: all
Standards-Version: 3.9.4
Package: cloud-init
Architecture: all
Depends: cloud-utils,
ifupdown (>= 0.6.10ubuntu5),
procps,
python,
python-argparse,
python-boto,
python-cheetah,
python-configobj,
python-oauth,
python-requests (>= 0.8.2),
python-prettytable,
python-yaml,
software-properties-common,
${misc:Depends},
${python:Depends}
Provides: ec2-init
Replaces: ec2-init (<<0.5.3)
Conflicts: ec2-init (<<0.5.3)
XB-Python-Version: ${python:Versions}
Description: configuration and customization of cloud instances
Cloud-init provides a framework and tool written in Python to handle early
initialization of a cloud instance. It can for example set a default locale
and hostname, generate SSH private host keys, add SSH keys to a user's
authorized_keys so they can log in, and set up ephemeral mount points.
.
Cloud-init's behavior can be configured via data given by the user at
instance launch time.
Package: grub-legacy-ec2
Depends: debconf (>= 1.5.19) | cdebconf,
ucf,
util-linux (>= 2.15-1),
${misc:Depends}
Conflicts: grub
Suggests: grub-legacy-doc
Architecture: all
Description: Handles update-grub for ec2 instances
EC2 instances that use grub-legacy as a bootloader need a way to keep
/boot/grub/menu.lst up to date while not conflicting with grub-pc.
This package provides that.
Package: ec2-init
Depends: cloud-init, ${misc:Depends}
Architecture: all
Description: package renamed -> cloud-init
This package has been renamed to 'cloud-init'.
