File tree Expand file tree Collapse file tree 2 files changed +26
-3
lines changed Expand file tree Collapse file tree 2 files changed +26
-3
lines changed Original file line number Diff line number Diff line change @@ -25,7 +25,14 @@ the :ref:`cells V2 guide <cells-v2-layout-metadata-api>`.
25
25
added in Stein. For versions prior to this release, you should not use the
26
26
standalone :program: `nova-api-metadata ` application for multiple cells.
27
27
28
- Guests access the service at ``169.254.169.254 ``. The networking service,
28
+ Guests access the service at ``169.254.169.254 `` or at ``fe80::a9fe:a9fe ``.
29
+
30
+ .. versionchanged :: 22.0.0
31
+
32
+ Starting with the Victoria release the metadata service is accessible
33
+ over IPv6 at the link-local address ``fe80::a9fe:a9fe ``.
34
+
35
+ The networking service,
29
36
neutron, is responsible for intercepting these requests and adding HTTP headers
30
37
which uniquely identify the source of the request before forwarding it to the
31
38
metadata API server. For the Open vSwitch and Linux Bridge backends provided
Original file line number Diff line number Diff line change @@ -72,8 +72,24 @@ The metadata service
72
72
73
73
The *metadata service * provides a way for instances to retrieve
74
74
instance-specific data via a REST API. Instances access this service at
75
- ``169.254.169.254 `` and all types of metadata, be it user-, nova- or
76
- vendor-provided, can be accessed via this service.
75
+ ``169.254.169.254 `` or at ``fe80::a9fe:a9fe ``. All types of metadata,
76
+ be it user-, nova- or vendor-provided, can be accessed via this service.
77
+
78
+ .. versionchanged :: 22.0.0
79
+
80
+ Starting with the Victoria release the metadata service is accessible
81
+ over IPv6 at the link-local address ``fe80::a9fe:a9fe ``.
82
+
83
+ .. note ::
84
+
85
+ As with all IPv6 link-local addresses, the metadata IPv6
86
+ address is not complete without a zone identifier (in a Linux
87
+ guest that is usually the interface name concatenated after
88
+ a percent sign). Please also note that in URLs you should
89
+ URL-encode the percent sign itself. For example, assuming
90
+ that the primary network interface in the guest is ``ens2 ``
91
+ substitute ``http://[fe80::a9fe:a9fe%25ens2]:80/... `` for
92
+ ``http://169.254.169.254/... ``.
77
93
78
94
Using the metadata service
79
95
~~~~~~~~~~~~~~~~~~~~~~~~~~
You can’t perform that action at this time.
0 commit comments