e78f123ff8
Ironic has a lot of logic built up around use of images for filesystems, however several recent additions, such as the ``ramdisk`` and ``anaconda`` deployment interfaces have started to break this mold. In working with some operators attempting to utilzie the anaconda deployment interface outside the context of full OpenStack, we discovered some issues which needed to be make simpler to help remove the need to route around data validation checks for things that are not required. Standalong users also have the ability to point to a URL with anaconda, where as Operators using OpenStack can only do so with customized kickstart files. While this is okay, the disparity in configuraiton checking was also creating additional issues. In this, we discovered we were not really graceful with redirects, so we're now a little more graceful with them. Story: 2009939 Story: 2009940 Task: 44834 Task: 44833 Change-Id: I8b0a50751014c6093faa26094d9f99e173dcdd38
22 lines
1004 B
YAML
22 lines
1004 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where ``root_gb`` became a required field when using the
|
|
``anaconda`` deployment interface, with a recent bug fix as the code path
|
|
largely expected all deployment operations to utilize images, which is
|
|
not the case. The case handling for non-image based deployments is now
|
|
explicitly in internal parameter validation code.
|
|
- |
|
|
Fixes handling of ``image_source`` parameters where internal validations
|
|
would not gracefully handle received redirects and treat it as a failure.
|
|
We now no longer explicitly fail when a redirect is received.
|
|
- |
|
|
Fixes an issue where an ``image_source`` could not be set to a mirror URL
|
|
to facilitate deployments using a mirror with the ``anaconda`` deployment
|
|
interface. Ironic still presently has an explicit requirement on a
|
|
``stage2`` parameter to be explicitly defined.
|
|
other:
|
|
- |
|
|
Adds documentation of standalone deployment use case with the ``anaconda``
|
|
deployment interface.
|