Comment 15 for bug 1374166

@Ben,

As soon as time is available, I will test the -proposed package (if possible, on the old Azure VMs that have been used for testing).

I will add the following test: testing the 0.7.6 version on Ubuntu Trusty (14.04.1 LTS)

Please note that I just received the message, implying that I have not been able to verify what is changed in the 0.7.5 version (the standard version on Trusty) and/or whether swap file cloud-config options have been backported.

Also note that cloud-init documentation with respect to

- cloud-config examples, and/or
- Azure custom AND standard disk_setup and fs_setup settings

can be adjusted for the reasons that disk_setup and fs_setup settings for attached disks, in the form of

#cloud-config
disk_setup:
    [ .. ephemeral config lines .. ]
    /dev/sdc:
        table_type: mbr
        layout: True
        overwrite: True
fs_setup:
    [ .. ephemeral config lines .. ]
    - device: /dev/sdc1
      filesystem: ext4

suffice to setup and format attached disk at VM creation time (instead of manually partitioning and formatting afterwards).

Note that the "overwrite: True" at /dev/sdc disk setup does not have any impact, in the sense that data on the disk is not lost (!).

@Ben: for the sake of clear cloud-init standard settings, it would propably be desirable to remove the alias "ephemeral" in Azure standard settings, since this removal cannot do harm and makes more easy to reference the /dev/sda (ephemeral) disk. Is this a change to be considered?

@Ben: if I am not mistaken, it should be easy for cloud-init to automatically detect attached disks (Azure devices) and assign a "standard" disk_setup and fs_setup settings (as provided above). The standard settings can than be easily overruled by custom cloud-config settings. However, I am not completely sure whether this is desirable behavior for cloud-init, what do you think?

@Stephen: the walinuxagent (waagent script) should be able to create a custom cloud-config file for the automatic detection, setup and formatting of the attached disks (Azure devices), in order to have formatted disks (after creation of the VM) that are persistent across (normal) restarts AND shutdown/start sequences (the latter is normally a problem, not in this case). Can we expect some adjustment of the walinuxagen (waagent script)?

Kind regards....