Add user data into general concept
This patch add brief introduction of user data, how nova offer it to end user and server consume it. blueprint complete-todo-in-api-concept-doc Change-Id: I3514247698bc4eeae358ae2a1ee9ad4e77d764fc
This commit is contained in:
parent
7bc2171869
commit
9485971ac3
|
@ -86,6 +86,17 @@ several key concepts:
|
||||||
reason. Such a separation is possible in Nova if an admin carefully sets up
|
reason. Such a separation is possible in Nova if an admin carefully sets up
|
||||||
availability zones for that, but it is not the default.
|
availability zones for that, but it is not the default.
|
||||||
|
|
||||||
|
- **User data**
|
||||||
|
A user data file is a special key in the metadata service that holds a file
|
||||||
|
that cloud-aware applications in the server can access.
|
||||||
|
|
||||||
|
Nova has two ways to send user data to the deploying instance, one is by
|
||||||
|
metadata service to let server able to connect to its metadata through
|
||||||
|
a predefined ip address (169.254.169.254), then other is to use config
|
||||||
|
drive which will wrap metadata into a iso9660 or vfat format disk so that
|
||||||
|
the new deployed server can consume it by active engines such as cloud-init
|
||||||
|
during its boot process.
|
||||||
|
|
||||||
Networking Concepts
|
Networking Concepts
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue