
Config drive is processed by the deploy interface and written to the disk during post install of the deployment. The config drive is written to /var/lib/cloud/seed/config_drive on the disk. cloud-init should be able to process read config drive contents and take actions on firstboot. Change-Id: Id5a949e777e242d2f20966ec045ac319c61636ba
10 lines
461 B
YAML
10 lines
461 B
YAML
---
|
|
features:
|
|
- |
|
|
The anaconda deploy interface now handles config drive. The config drive
|
|
contents are written to the disk at /var/lib/cloud/seed/config_drive
|
|
directory by the driver via kickstart files %post section. cloud-init
|
|
should be able to pick up the the config drive information and process
|
|
them. Because the config drive is extracted on to disk as plain text files
|
|
tools like glean will not work with this deploy interface.
|