blob: 607b70f3729f731e0ac7a6a60bdb9139d3eb31c1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
.. _datasource_openstack:
OpenStack
=========
This datasource supports reading data from the
`OpenStack Metadata Service
<http://docs.openstack.org/admin-guide/compute-networking-nova.html#metadata-service>`_.
Configuration
-------------
The following configuration can be set for the datasource in system
configuration (in `/etc/cloud/cloud.cfg` or `/etc/cloud/cloud.cfg.d/`).
The settings that may be configured are:
* **metadata_urls**: This list of urls will be searched for an OpenStack
metadata service. The first entry that successfully returns a 200 response
for <url>/openstack will be selected. (default: ['http://169.254.169.254']).
* **max_wait**: the maximum amount of clock time in seconds that should be
spent searching metadata_urls. A value less than zero will result in only
one request being made, to the first in the list. (default: -1)
* **timeout**: the timeout value provided to urlopen for each individual http
request. This is used both when selecting a metadata_url and when crawling
the metadata service. (default: 10)
* **retries**: The number of retries that should be done for an http request.
This value is used only after metadata_url is selected. (default: 5)
An example configuration with the default values is provided as example below:
.. sourcecode:: yaml
#cloud-config
datasource:
OpenStack:
metadata_urls: ["http://169.254.169.254"]
max_wait: -1
timeout: 10
retries: 5
Vendor Data
-----------
The OpenStack metadata server can be configured to serve up vendor data
which is available to all instances for consumption. OpenStack vendor
data is, generally, a JSON object.
cloud-init will look for configuration in the ``cloud-init`` attribute
of the vendor data JSON object. cloud-init processes this configuration
using the same handlers as user data, so any formats that work for user
data should work for vendor data.
For example, configuring the following as vendor data in OpenStack would
upgrade packages and install ``htop`` on all instances:
.. sourcecode:: json
{"cloud-init": "#cloud-config\npackage_upgrade: True\npackages:\n - htop"}
For more general information about how cloud-init handles vendor data,
including how it can be disabled by users on instances, see `Vendor Data`_.
.. vi: textwidth=78
|
