33bb2c248a
The use of the anaconda deployment interface can be confusing when using a standalone deployment model. Specifically this is because the anaconda deployment interface was primarily modeled for usage with glance and the inherent configuration of a fully integrated OpenStack deployment. The additional prameters are confusing, so this also (hopefully) provides clarity into use and options. Change-Id: I748fd86901bc05d3d003626b5e14e655b7905215
12 lines
526 B
YAML
12 lines
526 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Anaconda supports the ability to explicitly pass a URL instead
|
|
of a ``stage2`` ramdisk parameter. This has resulted in confusion
|
|
in use of the ``anaconda`` deployment interface, as a ``stage2``
|
|
ramdisk is typically not used, but made sense with Glance images in
|
|
a fully integrated OpenStack deployment. Now a URL to a path can be
|
|
supplied to the ``anaconda`` deployment interface to simplify the
|
|
interaction and use, and a redundant ``stage2`` parameter is no longer
|
|
required.
|