You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/using-cloud-init.md
+8-23Lines changed: 8 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,8 @@ ms.author: srijangupta
13
13
# cloud-init support for virtual machines in Azure
14
14
15
15
> [!CAUTION]
16
-
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
17
-
16
+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and plan accordingly.
17
+
>
18
18
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Flexible scale sets
19
19
20
20
This article explains the support that exists for [cloud-init](https://cloudinit.readthedocs.io) to configure a virtual machine (VM) or Virtual Machine Scale Sets at provisioning time in Azure. These cloud-init configurations are run on first boot once the resources have been provisioned by Azure.
@@ -61,11 +61,6 @@ There are two stages to making cloud-init available to the supported Linux distr
61
61
62
62
* All other CentOS SKUs starting from CentOS 7 (version 7.7) and CentOS 8 (version 8.1) including both Gen1 and Gen2 images are provisioned using cloud-init. CentOS 6.10, 7.4, 7.5, and 7.6 images don't support cloud-init.
63
63
64
-
> [!NOTE]
65
-
> OpenLogic is now Rogue Wave Software
66
-
67
-
68
-
69
64
### Oracle
70
65
71
66
Publisher / Version| Offer | SKU | Version | image cloud-init ready | cloud-init package support on Azure|
@@ -84,23 +79,13 @@ There are two stages to making cloud-init available to the supported Linux distr
Currently Azure Stack will support the provisioning of cloud-init enabled images.
@@ -130,7 +115,7 @@ The following example creates a resource group named *myResourceGroup* in the *e
130
115
az group create --name myResourceGroup --location eastus
131
116
```
132
117
133
-
The next step is to create a file in your current shell, named *cloud-init.txt* and paste the following configuration. For this example, create the file in the Cloud Shell not on your local machine. You can use any editor of your choice. Enter `sensible-editor cloud-init.txt` to create the file and see a list of available editors. In this example, we're using the **nano** editor. Choose #1 to use the **nano** editor. Make sure that the whole cloud-init file is copied correctly, especially the first line:
118
+
The next step is to create a file in your current shell, named *cloud-init.txt* and paste the following configuration. For this example, create the file in the Cloud Shell not on your local machine. You can use any editor of your choice. Enter sensible-editor cloud-init.txt to create the file and see a list of available editors. Use the editor of your choice. Some typical choices are [nano](https://linux.die.net/man/1/nano), [vim](https://linux.die.net/man/1/vi), or [ed](https://linux.die.net/man/1/ed). Make sure that the whole cloud-init file is copied correctly, especially the first line:
134
119
135
120
SLES| Ubuntu | RHEL
136
121
|:--- |:--- |:---
@@ -140,7 +125,7 @@ The next step is to create a file in your current shell, named *cloud-init.txt*
140
125
> [!NOTE]
141
126
> cloud-init has multiple [input types](https://cloudinit.readthedocs.io/en/latest/topics/format.html), cloud-init will use first line of the customData/userData to indicate how it should process the input, for example `#cloud-config` indicates that the content should be processed as a cloud-init config.
142
127
143
-
Press <kbd>Ctrl + X</kbd> to exit the file, type <kbd>y</kbd> to save the file, and press <kbd>Enter</kbd> to confirm the file name on exit.
128
+
Exit the file and save the file according to the editor. Verify file name on exit.
144
129
145
130
The final step is to create a VM with the [az vm create](/cli/azure/vm) command.
146
131
@@ -170,7 +155,7 @@ For more details of cloud-init logging, see the [cloud-init documentation](https
170
155
## Telemetry
171
156
cloud-init collects usage data and sends it to Microsoft to help improve our products and services. Telemetry is only collected during the provisioning process (first boot of the VM). The data collected helps us investigate provisioning failures and monitor performance and reliability. Data collected doesn't include any identifiers (personal identifiers). Read our [privacy statement](https://go.microsoft.com/fwlink/?LinkId=521839) to learn more. Some examples of telemetry being collected are (this isn't an exhaustive list): OS-related information (cloud-init version, distro version, kernel version), performance metrics of essential VM provisioning actions (time to obtain DHCP lease, time to retrieve metadata necessary to configure the VM, etc.), cloud-init log, and dmesg log.
172
157
173
-
Telemetry collection is currently enabled for most of our marketplace images that uses cloud-init. It is enabled by specifying KVP telemetry reporter for cloud-init. In most Azure Marketplace images, this configuration can be found in the file /etc/cloud/cloud.cfg.d/10-azure-kvp.cfg. Removing this file during image preparation will disable telemetry collection for any VM created from this image.
158
+
Telemetry collection is currently enabled for most of our marketplace images that use cloud-init. It is enabled by specifying KVP telemetry reporter for cloud-init. In most Azure Marketplace images, this configuration can be found in the file /etc/cloud/cloud.cfg.d/10-azure-kvp.cfg. Removing this file during image preparation will disable telemetry collection for any VM created from this image.
0 commit comments