bd82ead580
Currently direct deploy only works if temp urls are enabled or if a HTTP image URL is given. This patch enables Ironic to serve images directly from the conductor's HTTP server to the agent so that we can enable agent deploy with out temp urls. This also has the added benefit for standalone that the conductors will cache the HTTP URL images and serve them into the provisioning network meaning the provisioning network has no need for connectivity to the outside world. Story: #1598852 Task: #24639 Co-Authored-By: Kaifeng Wang <kaifeng.w@gmail.com> Change-Id: Iae6798616f29d876b274d9e0b44a1eb0f24e1747
16 lines
916 B
YAML
16 lines
916 B
YAML
---
|
|
features:
|
|
- Adds the ability to provision with ``direct`` deploy interface and custom
|
|
HTTP service running at ironic conductor node. A new configuration option
|
|
``[agent]image_download_source`` is introduced. When set to ``swift``,
|
|
the ``direct`` deploy interface uses tempurl generated via the Object
|
|
service as the source of instance image during provisioning, this is the
|
|
default configuration. When set to ``http``, the ``direct`` deploy
|
|
interface downloads instance image from the Image service, and caches the
|
|
image in the ironic conductor node. The cached instance images are
|
|
referenced by symbolic links located at subdirectory
|
|
``[deploy]http_image_subdir`` under path ``[deploy]http_root``. The custom
|
|
HTTP server running at ironic conductor node is supposed to be configured
|
|
properly to make IPA has unauthenticated access to image URL described
|
|
above.
|