| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Pre-release changes perr our release documentation,
https://docs.openstack.org/ironic/latest/contributor/releasing.html.
Additionally, adds a prelude for our release notes.
Change-Id: Ib55eed3df4924860a970d0a1fbd43c182119de3e
|
|
|
|
|
|
|
|
|
|
|
| |
Adds API for retrieving node history events
via a node. Includes pagination and limitation
of the response set.
Story: 2002980
Tas: 42961
Change-Id: I22a92fa6c30d721f6a5dd0670b2e0a9cf76ad7b1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This commit add support for the fields query parameter to the GET /v1/drivers?fields=... and GET /v1/drivers/<driver_name>?fields=....
Story: 1674775
Task: 10581
Change-Id: I2ca4eb490e320e736a93851eed526ec862be901e
|
|/
|
|
|
|
|
|
|
| |
This patch provides basic data model change to support node history.
Batch removal is not included in this patch.
Change-Id: I5c7cebd585ee84b5b57bd4690d4074baf0d05699
Story: 2002980
Task: 22989
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Done:
- Node API endpoints expose
- RPC methods
- Conductor Manager methods
- Conductor utils new methods
- RBAC new policies
- Node API tests
- Manager Tests (+ some testing for utils methods)
- RBAC tests
- Docs (api-ref)
- REST API version history
- Releasenotes
Story: 2008567
Task: 41709
Change-Id: I2d72389edf546b99c536c6b130ca85ababf80591
|
|
|
|
| |
Change-Id: I8f33eefdce7a60fa8e48225ec20a801b3d1222f0
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Otherwise the upgrade fails because of old versions.
Change-Id: Ibd591ab6e17e26db0b2b4dde103fe3458e1536f5
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
* add fields to Node object
* expose them at endpoint `/v1/nodes/{node_ident}/states`
* update states on powersync / entering managed state.
* tests
* update api endpoint info in api-ref
Story: 2008567
Task: 41709
Change-Id: Iddd1421a6fa37d69da56658a2fefa5bc8cfd15e4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Release notes checked:
* releasenotes/notes/adding-security-param-clean-step-00d5548072a397f2.yaml
* releasenotes/notes/bios-interface-api-ref-ebf866cc7da2270b.yaml
* releasenotes/notes/bios-interface-api-ref-validate-ddb95461adb0e478.yaml
* releasenotes/notes/bios-registry-support-e7fd62908e9c222d.yaml
* releasenotes/notes/boot-validate-6b4b6b40c8e27273.yaml
* releasenotes/notes/bug-2007551-aliases-for-a-few-named-state-transitions-a32433ad65638706.yaml
* releasenotes/notes/bye-bye-iscsi-658920cf126db0b8.yaml
* releasenotes/notes/configdrive-render-8eb398d956393d60.yaml
* releasenotes/notes/create_node_indexes-841b679e6cf332fd.yaml
* releasenotes/notes/custom-agent-deploy-88989512c29a14c1.yaml
* releasenotes/notes/decomposed-steps-9644d3b5ccbad1ea.yaml
* releasenotes/notes/get-bios-registry-aadc74800e0770f7.yaml
* releasenotes/notes/irmc-append-params-380a281db43e6013.yaml
* releasenotes/notes/pxe-append-params-9cd5831959676371.yaml
* releasenotes/notes/redfish-append-params-4d28d922484c2731.yaml
* releasenotes/notes/redfish-deploy-iso-9671ae83108f6385.yaml
* releasenotes/notes/secure-rbac-policy-sanitization-performance-dc7886952144bb04.yaml
Change-Id: I8b27df7e9c9b7f8623aa22c82be77b74e7d183d8
|
|
|
|
|
|
|
|
|
|
| |
Provide the fields in the BIOS setting API -
``/v1/nodes/{node}/bios/{setting}``, and in the BIOS setting list API
when details are requested - ``/v1/nodes/<node>/bios?detail=True``.
Story: #2008571
Task: #42483
Change-Id: Ie86ec57e428e2bb2efd099a839105e51a94824ab
|
|
|
|
|
|
|
|
|
|
| |
This RFE proposes a new microversion that will provide
aliases to two poorly named provisioning verbs
to match the existing CLI commands
Story: #2007551
Task: #39402
Change-Id: Ifd14aebbfb4b17c5108f44092dac0b89d1c2c50a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
agent_status is used by anaconda ramdisk to inform the
conductor about state of the deployment. Valid agent
states are 'start', 'end' and 'error'. The agent_status_message
is used to describe the why the agent_status is set to a
particular state. Use of these parameters require API
version 1.72 or greater.
When anaconda finishes deployment the agent_status is
set to 'end'. When anaconda ramdisk is unable to deploy
the OS for some reason the agent_status is set to 'error'.
PXEAnacondaDeploy is implemented to handle the 'anaconda'
deploy interface. PXEAnacondaDeploy ties to together pieces
needed to deploy a node using anaconda ramdisk.
Co-Authored-By: Jay Faulkner <jay@jvf.cc>
Change-Id: Ieb452149730510b001c4712bbb2e0f28acfc3c2e
|
|
|
|
| |
Change-Id: I3a144aaaca60ce195ba22fa5af2d9c1e7b4d4bf4
|
|
|
|
|
|
|
|
|
| |
This patch increments the API version for the Secure RBAC
as was covered in the specification in order to signify to
API consumers that may need to be aware if the API surface
can support Secure RBAC policy configuration.
Change-Id: Ia659708bb89ff416b65367505d3e068c6d4a198f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a new argument disable_ramdisk to the manual cleaning API.
Only steps that are marked with requires_ramdisk=False can be
run in this mode. Cleaning prepare/tear down is not done.
Some steps (like redfish BIOS) currently require IPA to detect
a successful reboot. They are not marked with requires_ramdisk
just yet.
Change-Id: Icacac871603bd48536188813647bc669c574de2a
Story: #2008491
Task: #41540
|
|
|
|
|
|
| |
The deploy_steps change merged after they got updated for 16.2.
Change-Id: Ibc9e5707518243bda31135e4012877284dad72a4
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Story: 2008043
Task: 40705
Change-Id: I3dc2d42b3edd2a9530595e752895e9d113f76ea8
|
|/
|
|
| |
Change-Id: I6e5f0e560f3f125a83e0514c10bee664c17663f2
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
MAC address is not user friendly for port management, having
a name field is also a feature parity with other resources.
This patch implements db related change.
Change-Id: Ibad9a1b6bbfddc0af1950def4e27db3757904cb1
Story: 2003091
Task: 23180
|
|/
|
|
| |
Change-Id: Ia37075d4aa2f39ca0862b03ca02c85bac17400e5
|
|
|
|
|
|
| |
Fix the incorrect Ussuri release mapping.
Change-Id: I77589745a89104ddc948f084f21a60cef8265271
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Accepts the certificate from a heartbeat and stores its path in
driver_internal_info for further usage by the agent client (or
any 3rd party deploy implementations).
Similarly to agent_url, the certificate is protected from further
changes (unless the local copy does not exist) and is removed
on reboot or tear down (unless fast-tracking).
Change-Id: I81b326116e62cd86ad22b533f55d061e5ed53e96
Story: #2007214
Task: #40603
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes adds a virtual Deployment object that is backed by
a corresponding Node. This change skips two fields:
* boot_iso_ref (requires updating drivers)
* owner (requires careful thoughts, may be not needed)
Story: #2006910
Task: #38361
Change-Id: I0cacdfaea5d3ba58a0a97cbb5231c224a8f9428e
|
| |
| |
| |
| | |
Change-Id: I4a9890503cb2489755ad76b2a73b93a9541eb357
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update the function that checks for free ports/portgroups to
accept a port_like_obj_id parameter to match. This parameter
comes from the vif_info dictionary.
Story: 2007723
Task: 39872
Change-Id: I82efa90994325aa37cca865920d656f510a691b2
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new dictionary field `network_data` is added to the node object.
This new field can be populated by the operator with node static
network configuration.
Ironic API now performs formal JSON document validation of node
`network_data` field content against user-supplied JSON schema at
driver validation step.
As of this commit, the new `network_data` field is not actually
used by ironic, otherwise it should be perfectly functional. In
the following commits, network static configuration will be taken
from this field and handed over to ironic ramdisk bootstrapping
utilities.
Change-Id: I868b3b56a17f59e5aa1494b2e0ebc9c4e34ef173
Story: 2006691
Task: 36991
|
|
|
|
| |
Change-Id: Ia23868e3d8e8eae28081a80c45983317d799de0b
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds a `lessee` field to nodes, and exposes it
to policy. It also updates the non-admin node list API
to match for both owner and lessee; and updates the
allocation conductor to match owner allocations with nodes
with the appropriate lessee.
Change-Id: Ib31b49c7143ec8fd6cb486fc24038215b197c418
Story: 2006506
Task: 37930
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add network_type to the port objects local_link_connection field.
The network_type can be set to either managed or unmanaged. When
the type is unmanaged other fields are not required. Use
unmanaged when the neutron network_interface is required, but
the network is in fact a flat network where no actual switch
management is done.
Story: 2007315
Task: 39161
Change-Id: I00c5ea22a8163c27c9ce4470e3713c282d0eb131
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added REST API endpoints for indicator management:
* GET /v1/nodes/<node_ident>/management/indicators` to list all
available indicators names for each of the hardware component.
* GET /v1/nodes/<node_ident>/management/indicators/<indicator_ident>
to retrieve the state of given indicator.
* PUT /v1/nodes/<node_ident>/management/indicators/<indicator_ident>`
change state of the desired indicator.
This implementation slightly deviates from the original spec in
part of having component name in the URL - this implementation
flattens component out.
The spec: https://review.opendev.org/#/c/655685/7/specs/approved/expose-hardware-indicators.rst
Change-Id: I3a36f58b12487e18a6898aef6b077d4221f8a5b8
Story: 2005342
Task: 30291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to improve security of the lookup/heartbeat
endpoints, we need to generate and provide temporary tokens
to the initial callers, if supported, to facilitate the
verification of commands.
This is the first patch in an entire series which utimately
enables the endpoint communication to be better secured.
The idea behind this started in private story 2006634 which
is locked as a security related filing covering multiple
aspects of ironic/ironic-python-agent interaction centered
around miss-use and generally exposed endpoints. That story
will remain marked as a private bug because it has several
different items covered, some of which did not prove to be
actually exploitable, but spawned stories 2006777, 2006773,
2007025, and is ultimately similar to Story 1526748.
Operationally this is a minimally invasive security
enhancement to lay the foundation to harden interactions
with the agent. This will take place over a series of
patches to both Ironic and the Ironic-Python-Agent.
Also see "Security of /heartbeat and /lookup endpoints"
in http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010789.html
Story: 2007025
Task: 37818
Change-Id: I0118007cac3d6548e9d41c5e615a819150b6ef1a
|
|
|
|
| |
Change-Id: Ic8b019f9e02d41e128015859423c2e0b7b1562a2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds support for node retirement: nodes can
have additional properties 'retired' and 'retired_reason'
which change the way the nodes (can) traverse the FSM
and which operations are allowed. In particular:
- retired nodes cannot move from manageable to available;
- upon instance deletion, retired nodes move to manageable
(rather than available).
Story: #2005425
Task: #38142
Change-Id: I8113a44c28f62bf83f8e213aeb6704f96055d52b
|
|
|
|
|
|
|
|
|
|
| |
Add an owner to allocations. Depending on policy, a non-admin
can then create an allocation and have the owner set to their
project. Allocation processing then respects the owner.
Change-Id: I2965a4a601b9fa2c0212097da37b104a3e5514df
Story: #2006506
Task: #37540
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
configdrive can contain a vendor_data2.json file containing key/value
pairs injected by nova's vendordata mechanism[1].
This change lets Ironic accept a vendor_data key when configdrive is
provided as json, allowing parity with nova.
This change requires an openstacksdk release 0.37.0
[1] https://www.madebymikal.com/nova-vendordata-deployment-an-excessively-detailed-guide/
Change-Id: Id990b970619a113c5d5ead47fb550870d91b5e04
Task: 36756
Story: 2006597
Blueprint: nova-less-deploy
|
|
|
|
| |
Change-Id: I5f76edfe978968836ca2190bf770e4cea5c08375
|
|
|
|
|
|
| |
12.2.0 will be the first release in the Train cycle.
Change-Id: Ide12cb4f83f3216af82e0d1139dc2f4468f1e5cb
|
|
|
|
|
|
|
|
|
| |
This feature addresses the case of moving the already deployed nodes
under the allocation API.
Change-Id: I29d0bd3663e0d1b27727a700c0f0e0fb6ceac1d9
Story: #2005014
Task: #29491
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Change-Id: I435e9734f2517b959f8e6124e54fc473c683b702
Story: 2005126
Task: 29796
|
|/
|
|
|
|
|
| |
Thorough replacement of git.openstack.org URLs with their opendev.org
counterparts.
Change-Id: Ic19e45986e9f650c1deb297f463e679fd268ad97
|
|
|
|
|
|
|
| |
Also included the object information for 12.0, which was released
during the stein cycle.
Change-Id: I9aec8095a7844f0568b40c7cdf1e07e6dc024770
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extend the API with the ability to build config drives from meta_data,
network_data and user_data, where meta_data and network_data are JSON
objects, and user_data is either a JSON object, a JSON array or
raw contents as a string.
This change uses openstacksdk (which is already an indirect dependency)
for building config drives.
Change-Id: Ie1f399a4cb6d4fe5afec79341d3bccc0f81204b2
Story: #2005083
Task: #29663
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds deploy_templates REST API endpoints for retrieving, creating,
updating and deleting deployment templates. Also adds notification
objects for deploy templates.
Bumps the minimum WSME requirement to 0.9.3, since the lower constraints
job was failing with a 500 error when sending data in an unexpected
format to the POST /deploy_templates API.
Change-Id: I0e8c97e600f9b1080c8bdec790e5710e7a92d016
Story: 1722275
Task: 28677
|
|
|
|
|
|
|
|
|
|
| |
The original patch [1] to add DB & object support for deploy templates
did not include an 'extra' field for metadata. This patch adds the
field, and bumps the object version.
Change-Id: I95b4beae217704defc9eab851780fd9c42847c40
Story: 1722275
Task: 29698
|