summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Changes made to enrollment documentationkkillsfirst2021-06-091-1/+1
| | | | | | * Fixed typo Change-Id: I6e1246712ea2ccb13538f040f2cdb1e91b7a3feb
* Changes made to release documentation:kkillsfirst2021-06-021-2/+0
| | | | | | | * Removed sushy-cli from Client libraries * Removed molteniron from Independent Change-Id: I2c2f87e372348760654563d34906829082f93d9f
* Merge "Trivial: Fix version number in comment"Zuul2021-06-011-1/+1
|\
| * Trivial: Fix version number in commentBob Fournier2021-06-011-1/+1
| | | | | | | | | | | | Fix the version number in comment. Change-Id: Iffa4bd7d15fb999e3d60539f630873d95057e44e
* | Merge "Add bifrost-benchmark-ironic job"Zuul2021-06-011-0/+2
|\ \
| * | Add bifrost-benchmark-ironic jobJulia Kreger2021-06-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Utilizes a simple bifrost job to stand up a simple ironic deployment where fake nodes will be created added, and a simple benchmark will then be executed. Change-Id: I33e29ee303b2cf4987b36c7aad2482bc3673f669
* | | Merge "Secure RBAC - Efficent node santiziation"Zuul2021-06-013-16/+70
|\ \ \ | |_|/ |/| |
| * | Secure RBAC - Efficent node santiziationJulia Kreger2021-05-243-16/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An investigation of performance issues in Ironic revealed that the policy checking was performing extra un-needed work which performed excess computational overhead when parsing the result data. In this specific case, the Secure RBAC work added some additional policy checks around individual the fields. Change-Id: I77b6e0e6c721f2ff1f8b9f511acde97fcdb21a39 Story: 2008885 Task: 42432
* | | Follow-up to Include bios registry fields in bios APIIury Gregory Melo Ferreira2021-06-013-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | This commit is a follow-up to Ie86ec57e428e2bb2efd099a839105e51a94824ab Story: #2008571 Task: #42546 Change-Id: I6fa4658180772ff9c4ff00f95b28cf8a1b5d4223
* | | Include bios registry fields in bios APIBob Fournier2021-05-2724-47/+613
| |/ |/| | | | | | | | | | | | | | | | | 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
* | Merge "Delay rendering configdrive"Zuul2021-05-2615-90/+384
|\ \
| * | Delay rendering configdriveDmitry Tantsur2021-05-1915-90/+384
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the configdrive input is JSON (meta_data, etc), delay the rendering until the ISO image is actually used. It has two benefits: 1) Avoid storing a large ISO image in instance_info, 2) Allow deploy steps to access the original user's input. Fix configdrive masking to correctly mask dicts. Story: #2008875 Task: #42419 Change-Id: I86d30bbb505b8c794bfa6412606f4516f8885aa9
* | | Update project conundrum related docsJulia Kreger2021-05-261-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Yes, project conundrum is a code-name for our transition to OFTC as we do not want to put anything into freenode IRC which may abruptly result in the channel being siezed or shutdown by the new owners/operators of freenode Change-Id: I45c07e0b2138f6643f865d58155c64317114fd02 See: http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022718.html
* | | Merge "Add basic tools for benchmarking"Zuul2021-05-263-0/+307
|\ \ \
| * | | Add basic tools for benchmarkingJulia Kreger2021-05-243-0/+307
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a horribly written, just hacked together little tool to help provide sizing insight into an ironic deployment's state and underlying performance. Key data: * Queries the list of node from a pure python interface level with the database and reports timeing for the list of nodes to be returned. This information helps convey how long a periodic hits the database just for the query. * Requests *all* nodes using the query pattern/structure of the nova resource tracker, and uses the marker to make any additional requsts. The data is parsed, and collected, and counts identified vendors, if any. * Collects basic data on conductors in terms of running, conductor groups as well as currently loaded drivers in the deployment. All of this information provides operational insight into *what* conditions exist within the deployment allowing developers to try and identify solutions based on the unique circumstances of larger deployments. Also adds a utility to generate and semi-randomize data to allow us to create a benchmark job in CI. Change-Id: Iae660aea82db8f1c4567ee2982595ccfdf434fe3
* | | | Merge "Remove inventory time workaround for WS-man BIOS"Zuul2021-05-254-89/+11
|\ \ \ \
| * | | | Remove inventory time workaround for WS-man BIOSAija Jauntēva2021-05-194-89/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The workaround was necessary for older versions to be backportable. Change-Id: Ifd0d66ad4ed191fafd58090f92e4ee44814f4b86
* | | | | Merge "Update min version of tox to use allowlist"Zuul2021-05-251-4/+4
|\ \ \ \ \
| * | | | | Update min version of tox to use allowlistRiccardo Pittau2021-05-181-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The min version of tox is updated to 3.18.0 to replace whitelist_externals with allowist_externals option [1] [1] https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23 Change-Id: Icf821d49d2543be2a37dffc686ae7ab4163b04cc
* | | | | | Merge "CI: Collect a snapshot of network connections"Zuul2021-05-253-6/+9
|\ \ \ \ \ \
| * | | | | | CI: Collect a snapshot of network connectionsJulia Kreger2021-01-123-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A recent magnum bug (https://storyboard.openstack.org/#!/story/2008494) when running with uwsgi has yielded an interesting question if Ironic is orphaning rpc clients or not. Ironic's code is slightly different but also very similar, and similar bugs have been observed in the past where the python garbage collection never cleans up the old connection objects and effectively orphans the connection. So we should likely at least try to collect some of the information so we can determine if this is the case in our CI jobs. Hence this change and attempt to collect that data after running CI. Change-Id: I4e80c56449c0b3d07b160ae6c933a7a16c63c5c5
* | | | | | | Merge "Add missing bios_interface to api-ref for validate API"Zuul2021-05-243-0/+12
|\ \ \ \ \ \ \ | |_|_|_|/ / / |/| | | | | |
| * | | | | | Add missing bios_interface to api-ref for validate APIBob Fournier2021-05-213-0/+12
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixing another case of bios interface missing from the api-ref documentation, this one for the validate API. Change-Id: I8ae3212f04a8d150af8adde5f5f87e5a5451da14
* | | | | | Merge "Add additional node indexes"Zuul2021-05-215-0/+202
|\ \ \ \ \ \ | | |_|_|_|/ | |/| | | |
| * | | | | Add additional node indexesJulia Kreger2021-05-185-0/+202
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Secure RBAC, along with numerous periodics, and even some common API access patterns heavily access the ironic database and sometimes cause queries across multiple columns to match nodes to return. None of this is bad, but what is bad is we didn't have indexes on these columns. This change adds docs, and the schema upgrade to create the column indexes, and a release note to provide more visible documentation for operators. It must be stressed that this does *not* improve query times when all records are asked for on a database connection. Also adds an upgrade check in to raise a warning for operator visibility. Story: 2008863 Task: 42392 Change-Id: I76821c032180a58d0f99d31110fbe0f844c0cb3f
* | | | | | Merge "Expand the deployment guide"Zuul2021-05-213-63/+173
|\ \ \ \ \ \
| * | | | | | Expand the deployment guideDmitry Tantsur2021-05-123-63/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add optional Glance and Neutron integration. * Migrate and expand the configdrive section from the install guide. * Explain how to use cloud-init boot scripts. * Explain allocations and mention metalsmith as an easy CLI. * Use more realistic URLs and checksums in the examples. * Remove a reference to local boot, it's the default nowadays. * Replace the iLO note with a more generic one. * Small fixes and clean ups. Change-Id: I28ac60da6722b9ca2c2b571511070010145958f6
* | | | | | | Merge "Trivial: comment why we don't check retired in allocations"Zuul2021-05-201-0/+2
|\ \ \ \ \ \ \
| * | | | | | | Trivial: comment why we don't check retired in allocationsDmitry Tantsur2021-05-201-0/+2
| | |_|/ / / / | |/| | | | | | | | | | | | | | | | | | | Change-Id: I31e128f5273cc50bf7662a62080251d8f226f6c5
* | | | | | | Merge "Rename redfish_deploy_iso -> deploy_iso"Zuul2021-05-206-30/+108
|\ \ \ \ \ \ \
| * | | | | | | Rename redfish_deploy_iso -> deploy_isoDmitry Tantsur2021-05-196-30/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We should only use prefixed driver_info parameters when they are either unique to the driver or have different meanings for different drivers. This is not the case for deploy_iso, but we use vendor prefixes for historical reasons. This change migrates the redfish-virtual-media boot interface and creates helpers to fascilitate migration of other boot interfaces. Change-Id: I698d1c90592e8de2cb24d6e2cf819e7f6ac3911f Story: #2008880 Task: #42425
* | | | | | | | Merge "Retrieve BIOS registry from sushy"Zuul2021-05-204-8/+259
|\ \ \ \ \ \ \ \ | |_|/ / / / / / |/| | | | | | |
| * | | | | | | Retrieve BIOS registry from sushyBob Fournier2021-05-194-8/+259
| | |_|_|_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Get the BIOS Registry from Sushy and store the fields in the Ironic DB with the corresponding entry in the BIOS setting. Story: #2008571 Task: #42484 Change-Id: I606c5de9077931707ebd15c3adf506badd95ea29
* | | | | | | Merge "Clean up kernel_append_params for Redfish and iLO"Zuul2021-05-196-24/+73
|\ \ \ \ \ \ \
| * | | | | | | Clean up kernel_append_params for Redfish and iLODmitry Tantsur2021-05-176-24/+73
| | |/ / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently handling of kernel_append_params is very inconsistent. This change applies a straightforward process: 1. instance_info[kernel_append_params] 2. driver_info[kernel_append_params] 3. [$driver]kernel_append_params The existing ilo_kernel_append_params is declared but never implemented, so it's removed without deprecation in favor of the new option. Story: #2008902 Task: #42470 Task: #42471 Change-Id: I0fcd7c63a4bc41110eb7f4cd4031580ef98d9a19
* | | | | | | Merge "Clean up kernel_append_params for iRMC"Zuul2021-05-194-12/+115
|\ \ \ \ \ \ \
| * | | | | | | Clean up kernel_append_params for iRMCDmitry Tantsur2021-05-174-12/+115
| |/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently handling of kernel_append_params is very inconsistent. This change applies a straightforward process: 1. instance_info[kernel_append_params] 2. driver_info[kernel_append_params] 3. [$driver]kernel_append_params Story: #2008902 Task: #42472 Change-Id: Ib83594743ae58ea26dbd9875c98ab169dd5ab009
* | | | | | | Merge "Clean up kernel_append_params for PXE/iPXE"Zuul2021-05-1912-17/+86
|\ \ \ \ \ \ \ | |/ / / / / / | | / / / / / | |/ / / / / |/| | | | |
| * | | | | Clean up kernel_append_params for PXE/iPXEDmitry Tantsur2021-05-1712-17/+86
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently handling of kernel_append_params is very inconsistent. This change applies a straightforward process: 1. instance_info[kernel_append_params] 2. driver_info[kernel_append_params] 3. [pxe]kernel_append_params (renamed from pxe_append_params). Also adds a helper for subsequent fixes in other drivers. Change-Id: I79bcf4d8ef1f0f55a82e0991dd5bb1685b3f7957 Story: #2008902 Task: #42469
* | | | | Merge "Rework the user guide"Zuul2021-05-189-616/+646
|\ \ \ \ \ | |/ / / / |/| / / / | |/ / /
| * | | Rework the user guideDmitry Tantsur2021-05-109-616/+646
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently it only contains (outdated) explanations how Ironic works. Move them one level deeper and migrate the content relevant to users: * Preparing instance images from the installation guide * Deploying nodes from the standalone guide Compatibility shims are provided for migrated pages. Change-Id: I8468da377b7878eb3d1a61e6a6bcd4ac8a5f06d7
* | | | Merge "Add bios_interface to api-ref spec"Zuul2021-05-172-0/+8
|\ \ \ \
| * | | | Add bios_interface to api-ref specBob Fournier2021-05-142-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a doc change to add bios_interface to the api reference. Its included in the detailed node list and node show but wasn't shown in the api-ref. Change-Id: I8735d10db1644f8a2c872c75c156c75c06b79c0c
* | | | | Merge "setup.cfg: Replace dashes with underscores"Zuul2021-05-161-4/+4
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | setup.cfg: Replace dashes with underscoreslikui2021-05-121-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: If07c53b62d32d2bc3d519b4f541f267995e522fe
* | | | | Merge "[doc] Update documentation about force_persistent_boot_device"Zuul2021-05-111-9/+19
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | [doc] Update documentation about force_persistent_boot_deviceArne Wiebalck2021-05-101-9/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apparently, this was missed when the new options were introduced. Story: #2004846 Change-Id: I04be5a5a8fa962bafa68f0ea93ee127b1610c20f
* | | | | Merge "Upgrade guide: remove ancient versions and group with Installation"Zuul2021-05-112-128/+1
|\ \ \ \ \ | |/ / / / |/| / / / | |/ / /
| * | | Upgrade guide: remove ancient versions and group with InstallationDmitry Tantsur2021-05-102-128/+1
| | | | | | | | | | | | | | | | Change-Id: Ida2d1003eb99f012be0eca6ebde4fe2f935b2880
* | | | Merge "Avoid unnecessary validation in boot interfaces"Zuul2021-05-106-90/+78
|\ \ \ \ | |/ / / |/| | |