| 7a2b464a | 19-Nov-2025 |
Jae Hyun Yoo <jae.yoo@oss.qualcomm.com> |
Add forceUpdate option for uploadFirmwareMultipartHttpPush
Add the forceUpdate option for the uploadFirmwareMultipartHttpPush call so that ForceUpdate can be set through it.
Change-Id: I4d1f326963e
Add forceUpdate option for uploadFirmwareMultipartHttpPush
Add the forceUpdate option for the uploadFirmwareMultipartHttpPush call so that ForceUpdate can be set through it.
Change-Id: I4d1f326963e87f024037001c964ab72c90ccb8e1 Signed-off-by: Jae Hyun Yoo <jae.yoo@oss.qualcomm.com>
show more ...
|
| cfbd678d | 28-Apr-2025 |
Jae Hyun Yoo <jae.yoo@oss.qualcomm.com> |
Add applyTime option for uploadFirmwareMultipartHttpPush
Add the applyTime option for the uploadFirmwareMultipartHttpPush call and set its default value to ‘Immediate’.
Change-Id: I7e9a442ef0bd4487
Add applyTime option for uploadFirmwareMultipartHttpPush
Add the applyTime option for the uploadFirmwareMultipartHttpPush call and set its default value to ‘Immediate’.
Change-Id: I7e9a442ef0bd4487b67b921761b51b603a77d9ed Signed-off-by: Jae Hyun Yoo <jae.yoo@oss.qualcomm.com>
show more ...
|
| d36ac8a8 | 03-Nov-2025 |
jason westover <jwestover@nvidia.com> |
Migrate to Bootstrap 5 and remove Vue compat plugin
Complete migration from Bootstrap 4 (bootstrap-vue) to Bootstrap 5 (bootstrap-vue-next) and remove the @vue/compat plugin to finalize the Vue 3 mi
Migrate to Bootstrap 5 and remove Vue compat plugin
Complete migration from Bootstrap 4 (bootstrap-vue) to Bootstrap 5 (bootstrap-vue-next) and remove the @vue/compat plugin to finalize the Vue 3 migration.
Bundle size impact: - Before (Bootstrap 4 + bootstrap-vue): 535 KiB gzipped - After (Bootstrap 5 + bootstrap-vue-next): 511 KiB gzipped - Reduction: 24 KiB (4.5% smaller)
Package updates: - Update bootstrap 4.6.2 -> 5.3.8 - Update bootstrap-vue 2.23.1 -> bootstrap-vue-next 0.40.8 - Remove @vue/compat plugin - Update vue 3.4.29 -> 3.5.24 and related packages - Add mitt 3.0.1 for global event bus - Add vue-demi 0.14.10 for library compatibility
Bootstrap 5 CSS updates: - Replace directional classes: ml/mr/pl/pr -> ms/me/ps/pe - Replace text-left/right -> text-start/end - Replace sr-only -> visually-hidden / visually-hidden-focusable - Update media breakpoint xs -> sm (Bootstrap 5 removed xs) - Update color functions: gray("700") -> $gray-700 - Add form-switch border-radius for curved toggles - Update alert, table, toast, form, and button styles
Bootstrap-Vue-Next API changes: - Use createBootstrap() for plugin registration - Update modal footer slots: #modal-footer -> #footer - Fix form select events: @change -> @update:model-value - Add v-model bindings to modals instead of manual show()/hide() - Update toast system with custom plugin wrapping useToast() - Register components and directives explicitly
Vue 3 specific updates: - Replace $root.$emit with mitt event bus (eventBus.js) - Update render function from h(App) to createApp(App) - Add emits option to components - Use h() instead of $createElement in mixins - Add Vue 3 compile-time feature flags with documentation - Update event listeners: $on/$off to eventBus methods - Add beforeUnmount cleanup for event listeners
New components and significant additions: - src/plugins/toast.js - Custom toast plugin wrapping useToast() for Options API compatibility - src/components/Global/ConfirmModal.vue - Global confirmation dialog shim to replace Bootstrap 4's removed bvModal.msgBoxConfirm - src/eventBus.js - mitt-based event bus with Vue 2-compatible API - Navigation state preservation on page refresh implemented
Critical fixes: - Add global API interceptor to strip Vue reactivity from payloads - Preserve binary data (File, Blob, FormData) in API requests - Fix Generate CSR modal v-model binding for proper open/close - Remove debug logging and fix jest configuration - Fix responsive text visibility in AppHeader - Update BVTableSelectableMixin for proper row selection - Fix BVToastMixin VNode rendering for Vue 3
Vue 3 modal fixes (lazy-loaded components): - Add v-model support to network modals (ModalIpv4, ModalIpv6, ModalDns, ModalHostname, ModalMacAddress, ModalDefaultGateway) by adding modelValue prop, watcher on modelValue that triggers show(), and update:modelValue emit in resetForm - Remove lazy loading from TableIpv4, TableIpv6, TableDns to ensure modal component refs are available when v-model triggers - Fix modal title accessibility by adding title prop to modals (ModalAddDestination, ModalUser, ModalAddRoleGroup, etc.)
i18n fixes (computed properties): - Fix computed properties using i18n translations in ModalAddRoleGroup, ModalUser, and ModalUploadCertificate - Move useI18n() call from data() to setup() and return i18n object - Use i18n.t() instead of $t in computed properties and templates - Prevents "this.$t is not a function" and "_ctx.$t is not a function" errors in Vue 3
Toast notification fixes: - Fix toast progress bar visibility by setting progressProps to undefined (documented way to opt-out) instead of false - Change modelValue prop to interval for auto-dismiss timing - Remove temporary CSS display:none hack from _toasts.scss
Network settings fixes: - Fix checkbox @change event sending Vue reactive proxy object instead of boolean by casting with !! operator in changeDomainNameState and related methods in NetworkGlobalSettings.vue - Ensures API receives plain boolean values in PATCH requests
Navigation fixes: - Fix nav-link styling for navigation items without children by replacing b-nav-item with router-link in AppNavigation.vue - Prevents blue font color from .nav-link CSS class
Configuration updates: - Remove vue-compat webpack configuration - Add Vue 3 feature flags (__VUE_OPTIONS_API__, etc.) - Add .cursor to .gitignore
Accessibility improvements: - Add autocomplete attributes to password and credential inputs - Add modal title props for screen reader support
Build completes successfully and UI behavior matches pre-migration.
Extracted features (to be submitted in follow-up PRs): The following features were removed from this migration PR to keep it focused on the Bootstrap 5 upgrade. They will be submitted separately: 1. UnresponsiveModal - Server connectivity watchdog with auto-retry 2. Auth token persistence - sessionStorage support for X-Auth-Token 3. Hardware store error handling - try/catch, dynamic discovery 4. Login page connecting indicator - Backend polling with spinner 5. Test updates - Jest setup and snapshot updates for Bootstrap-Vue-Next 6. Documentation updates - Vue 3 and Vue I18n v9+ API documentation 7. Enhanced ConfirmModal - Feature-rich confirmation dialog with custom actions
Change-Id: Ib76a58f324b3c926cf536e6e4626e4271639de38 Signed-off-by: Jason Westover <jwestover@nvidia.com>
show more ...
|
| 85b2d315 | 12-Nov-2024 |
Shane Lin <hslin@nvidia.com> |
Rename host firmware to bios firmware
Problem: - Host firmware naming was inconsistent with actual functionality
Changes: - Rename hostFirmware to biosFirmware in store - Update component names and
Rename host firmware to bios firmware
Problem: - Host firmware naming was inconsistent with actual functionality
Changes: - Rename hostFirmware to biosFirmware in store - Update component names and references - Modify i18n translation keys
Tested: - Verified store mutations/actions - Confirmed component rendering - Checked i18n translations - npx eslint without error related to 'host'
Change-Id: Ib97e4682f649d4a52f65e69df50422d84f23e916 Signed-off-by: Shane Lin <hslin@nvidia.com>
show more ...
|
| de23ea23 | 11-Jul-2024 |
Surya V <suryav@ami.com> |
Vuelidate, I18n, and filter are upgraded to vue3
While navigating to the pages i18n, vuelidate, and filters errors occurred. i18n, and vuelidate code changes in each page adapted to vue3. Filter glo
Vuelidate, I18n, and filter are upgraded to vue3
While navigating to the pages i18n, vuelidate, and filters errors occurred. i18n, and vuelidate code changes in each page adapted to vue3. Filter global function for date and time format implemented in the main.js file and those files which as called the filter functions.
Change-Id: If1a2ee22d47750faef1c35ef2c263299067d9a20 Signed-off-by: Surya Venkatesan <suryav@ami.com>
show more ...
|
| ccf5c5c8 | 12-Sep-2024 |
jason westover <jwestover@nvidia.com> |
Add default Target to MultipartHttpPush
When no targets are provided, webui will now default to the BMC: i.e. "/redfish/v1/Managers/bmc"
The current version of bmcweb requires the Targets parameter
Add default Target to MultipartHttpPush
When no targets are provided, webui will now default to the BMC: i.e. "/redfish/v1/Managers/bmc"
The current version of bmcweb requires the Targets parameter. bmcweb will be updated for multipart to match the behavior of simpleupdate: if Targets is empty or missing, default to the BMC.
Also, the fwupdate page will be updated soon to allow the selection of Targets from the FirmwareInventory list.
This should be a temp webui fix until we are comfortable with the upcoming changes to bmcweb.
Change-Id: I630dcb40068b98aad8e1d276d17fe9af4793e788 Signed-off-by: jason westover <jwestover@nvidia.com>
show more ...
|
| e2c716a9 | 28-Jul-2024 |
Leo Xu <yongquanx@nvidia.com> |
Add support for MultipartHttpPushUri in fw push
According to the Redfish Firmware Update Whitepaper [1] due to the vendor-specific details of this operation, HttpPushUri has been deprecated in f
Add support for MultipartHttpPushUri in fw push
According to the Redfish Firmware Update Whitepaper [1] due to the vendor-specific details of this operation, HttpPushUri has been deprecated in favor of multipartHTTP push updates.
Availability of update methods is determined from the UpdateService response.
If MultipartHttpPushUri is found it will be preferred over HttpPushUri
Tested: -Firmware update by performed via MultipartHttpPushUri
[1]: https://www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.1.pdf
Change-Id: I184a889514d5f9f9598f35b2281404335bc0bc82 Signed-off-by: Leo Xu <yongquanx@nvidia.com>
show more ...
|
| bc49e091 | 11-Jun-2024 |
Nikhil Ashoka <a.nikhil@ibm.com> |
Removed TFTP code update option
- Removed TFTP server firmware update ability in the UI.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com> Change-Id: Icbeddc7a3faa262f12e85268206ae70850f37905 |
| 08039ab7 | 26-Jun-2024 |
Sean Zhang <xiazhang@nvidia.com> |
fix reboot BMC error message
Remove getLastBmcRebootTime after post BMC reboot action since BMC connection will be lost after reboot. The last BMC reboot time will be got after reboot BMC page loadi
fix reboot BMC error message
Remove getLastBmcRebootTime after post BMC reboot action since BMC connection will be lost after reboot. The last BMC reboot time will be got after reboot BMC page loading, and after BMC reboot, user need reload the WEB UI, so there is also no need to send Redfish request to get the last BMC reboot time just after the post the BMC reboot action.
Change-Id: Ic5d0cbca23a61610cc387a4046b85e9c20c255ea Signed-off-by: Sean Zhang <xiazhang@nvidia.com>
show more ...
|
| 8841b7d4 | 15-Jun-2024 |
Sean Zhang <xiazhang@nvidia.com> |
Replace fixed paths with response from API
Currently, the Redfish request used fixed URIs, modify the code to use the BMC and System paths got from response of API calls. For CertificateStore, since
Replace fixed paths with response from API
Currently, the Redfish request used fixed URIs, modify the code to use the BMC and System paths got from response of API calls. For CertificateStore, since it was using the URL for constant variable assignment, changed the constant CERTIFICATE_TYPES to method call.
Change-Id: I330b7272083e3e6993aae5705aae170b8e9a4659 Signed-off-by: Sean Zhang <xiazhang@nvidia.com>
show more ...
|
| ccb71f0b | 18-Jun-2024 |
Jagpal Singh Gill <paligill@gmail.com> |
remove setApplyTimeImmediate and its usage
BMCWeb is dropping the support for patch for ApplyOptions, hence remove the setApplyTimeImmediate and its corresponding usage from webui. The related patch
remove setApplyTimeImmediate and its usage
BMCWeb is dropping the support for patch for ApplyOptions, hence remove the setApplyTimeImmediate and its corresponding usage from webui. The related patch from bmcweb is as under - https://gerrit.openbmc.org/c/openbmc/bmcweb/+/72150
Change-Id: I4ef64485103db843e1280bc5b8bd8be63813c368 Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
show more ...
|
| 5c2f61a5 | 07-Mar-2024 |
Konstantin Aladyshev <aladyshev22@gmail.com> |
Correct Actions/Manager.ResetToDefaults parameter name
According to the Redfish Data Model specification the correct parameter name for the '/Actions/Manager.ResetToDefaults' action is not 'ResetToD
Correct Actions/Manager.ResetToDefaults parameter name
According to the Redfish Data Model specification the correct parameter name for the '/Actions/Manager.ResetToDefaults' action is not 'ResetToDefaults' but 'ResetType'. Change parameter name to match with the specification.
Tested: Reset operation still works as expected.
Change-Id: I111001800bb812ccb32f51f78f2e02c5f4d10e7c Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
show more ...
|
| 8132399c | 27-Feb-2024 |
Ed Tanous <ed@tanous.net> |
Reformat files with new linter
All changes should be whitespace, and were done using npm run-script lint.
Change-Id: I943c6b435c5c872841af5affc1e89910468b5ca6 Signed-off-by: Ed Tanous <ed@tanous.ne
Reformat files with new linter
All changes should be whitespace, and were done using npm run-script lint.
Change-Id: I943c6b435c5c872841af5affc1e89910468b5ca6 Signed-off-by: Ed Tanous <ed@tanous.net>
show more ...
|
| 6b424f99 | 10-Mar-2023 |
greenfil <mikl@greenfil.ru> |
Added the use of HttpPushUri
According to the Redfish specification, the address to update the firmware is set in redfish/v1/UpdateService with the HttpPushUri variable. ``` https://github.com/openb
Added the use of HttpPushUri
According to the Redfish specification, the address to update the firmware is set in redfish/v1/UpdateService with the HttpPushUri variable. ``` https://github.com/openbmc/bmcweb/commit/4dc23f3fb6c9a7cef84658f8ab3b703d29ec7d57 ```
Change-Id: I29566a8ab2d06b658ab62f61c34be00fbbba0571 Signed-off-by: greenfil <mikl@greenfil.ru>
show more ...
|
| 05887b50 | 10-Jan-2022 |
Sandeepa Singh <sandeepa.singh@ibm.com> |
Add Key clear page under Operations section
This page will allow privileged user to clear encrypted keys. - Only admin and CE login user will be able to see the page - The UI will be different for b
Add Key clear page under Operations section
This page will allow privileged user to clear encrypted keys. - Only admin and CE login user will be able to see the page - The UI will be different for both, admin and CE login user(service) - This page is IBM only
Signed-off-by: Sandeepa Singh <sandeepa.singh@ibm.com> Change-Id: Ic6fe3454de815629a6b2250daa99ab21f2b316c3
show more ...
|
| c9cb8d43 | 03-Sep-2021 |
Grzegorz Raguza <grzegorzx.raguza@intel.com> |
Change filtering virtual media
When Virtual Media image was configured and connected entry did not appear on the UI after opening in the new tab or after page refresh. The cause was filtering predic
Change filtering virtual media
When Virtual Media image was configured and connected entry did not appear on the UI after opening in the new tab or after page refresh. The cause was filtering predicate. Proxy devices has transferProtocolType eq to 'OEM', legacy the onces that has no transferProtocolType. For mouting from the share the property exists and has value of 'CIFS'. I added object with all protocols (see docs), and change the filtering for legacy devices. New condition is all accept 'OEM'.
Signed-off-by: Grzegorz Raguza <grzegorzx.raguza@intel.com> Change-Id: I7ba123f19f924536f131ec40d15715b7f50fc985
show more ...
|
| 3145d4d9 | 18-Aug-2021 |
Dixsie Wolmers <dixsie@ibm.com> |
Move PowerControlStore to ResourceManagement folder
Store module structure should match the view folder structure The Power page is under the Resource management section, so the store should also be
Move PowerControlStore to ResourceManagement folder
Store module structure should match the view folder structure The Power page is under the Resource management section, so the store should also be in a similarly named folder. This makes it easier to find when looking for the correct store.
Signed-off-by: Dixsie Wolmers <dixsie@ibm.com> Change-Id: Iada30056eb738b91f35dc4c6b9b42b6b2be8d55c
show more ...
|
| f67f769f | 19-Jul-2021 |
Sandeepa Singh <sandeepa.singh@ibm.com> |
IA update: Update configuration to settings
This is the fourth update to information architecture changes and has the following changes:
- The configuration section is updated to settings - The dat
IA update: Update configuration to settings
This is the fourth update to information architecture changes and has the following changes:
- The configuration section is updated to settings - The date and time settings page is updated to date and time - The network settings page is updated to network - The power restore policy page in operations section is moved to settings section
Signed-off-by: Sandeepa Singh <sandeepa.singh@ibm.com> Change-Id: I6f5ab25f5227530be430bd39a4d9629b3bf09d8b
show more ...
|
| 68cbbe90 | 14-Jul-2021 |
Sandeepa Singh <sandeepa.singh@ibm.com> |
IA update: Update control section to operations
This is the third update to the information architecture changes and has the following changes:
- The control section has been updated to operations
IA update: Update control section to operations
This is the third update to the information architecture changes and has the following changes:
- The control section has been updated to operations - The server led page has been removed - The firmware page is moved to operations section
Signed-off-by: Sandeepa Singh <sandeepa.singh@ibm.com> Change-Id: I2e23da447890d7bee51892e1f782d5f2db6dded4
show more ...
|