This appears to be the first time we've done this since just before the
xena release.
This includes a fix for firmware-interface being a file in
not-implemented/ instead of in approved/ and symlinked in.
Change-Id: Iad890a729b219946d510fd28ae3685e133d8b77b
Spec ilo-uefi-iscsi-boot.rst which was proposed and
approved causes Gerrit Zuul CI linter failure in
newly proposed spec.
Change-Id: If0044f325184185acc54fd5d5c73ddab98b88004
Fixing a few typos and make some changes which I noted in the
specification as it was being reviewed.
Nothing major, just clean-up.
Change-Id: Ic8b3b371488d97396f413168dd1720d4ec47c73c
This change addresses the problem with updating the filters immediately
on starting inspection. The proposed approach has limitations and poses
a compromise between usability and not inflating the scope of this work.
Change-Id: I7771e2a3a81756bc222385e862911a647f68fbc4
Adds a framework for modifying an existing deployed system in the same
model of existing deployment, verification, and cleaning steps.
Change-Id: I1a488dbffa2f82cc6c3bbe34ef5295ada13b596b
This specification revisits the original smartnic work
in order to attempt to move the needle to account for newer
technology which is on the horizon.
It is also important to note that supporting a model such
as is proposed in this spec, also addresses some of the
various discussions which have occured in the past few
years in terms of addressing more compelx models and
interactions by nesting the model and enablling the
nested model to be interacted with.
Change-Id: I57a2130da64056655fd57522ca76b8a2a727da88
Snapshot support is expected to come via the newly designed Service
Steps, which is providing a generic framework for performing actions on
ACTIVE Ironic nodes -- including snapshotting.
Ironic contributors will write a new spec about implementing snapshot
via Service Steps once that work is completed.
Story: 2008033
Task: 40689
Change-Id: I288c77eba746c855c0bc9b9fd89ae557cbfddd7a
We've been keeping a backlog of specs which are entirely outdated
and will never be implemented. And we should also indicate when
a specification document is no longer applicable at all. As such
this change adds a retired folder, enumeration, and moves four
documents to the retired folder to indcate they are no longer
applicable to Ironic so end users have appropriate context should
they discover the documents in the future.
Change-Id: I1ab7d6726dc45283ca72df1df1d3c18e8ae8ea94
In practice, we often skip bugfix branch releases if we do not have
downstream consumers for those releases or do not have significant
changes. Ensure our docs are clear on this.
Change-Id: I336b437f1914c0b18ca299dff9dd022628e5f445
This spec describes an idea we had about how to implement an
event subscription API that works for redfish.
Story: 2008366
Task: 41275
Change-Id: I2b2c4921b92469cccaf80435c2c9a4e12e522988
This spec proposes support for retrieving the BIOS Registry from
Sushy and exposing it through the ``nodes/<node>/bios`` API.
Story: 2008571
Task: 41722
Change-Id: Ib93e62076207e3e25960111bd0b46b83fe481c69
Proposes change to align with the Secure RBAC changes being
discussed upstream as part of the larger community.
Change-Id: I6e29ac3a7d7fa32cd7129d58e2367c6ef87ae472
Currently ironic uses one last_error field to record error information
when an operation failed. The field is easily overwritten and we don't
have a traceback on what happened in the past, the only way is to check
service logs.
The proposal is to introduce a new table named node_history, and record
important node events that helps bare metal maintenance and troubleshooting.
Change-Id: I3b8832a945183ce3ed41ea79838fc9f682bfc547
Story: 2002980
Task: 22989
The initial proposal of supporting a branch with all fixes only
6 months was too harsh and does not seem to reflect how we actually
handle stable branches. Based on personal observation that we mostly
maintain the last two stable branches (e.g. right now Train is still
actively maintained), the windows is increased to 12 months.
Also added a formal policy and completely abandoning EM branches.
Change-Id: Ibefde7ed15932964c366c605b7ca03bce4d66e5b