| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
@vuelidate/validators ^2.0.0 does not support literal strings as
references for sameAs. They instead treated as literal strings and it
means that the password confirmation must exactly match the passed
string which is obviously incorrect.
This essentially is just a correction of some artifacts caused by the
upgrade to Vue 3.
Change-Id: I41f6a1764c2dd3fcfbfd96d2da9b48e6e409fef0
Signed-off-by: Vladimir Novikov <MeVladimirNovikov@gmail.com>
|
|
Importing the obmc-custom style adds over 700KB to the binary size. This
import was not there with Vue 2, so remove the import to restore the Vue
2 implementation and reduce the binary size.
Change-Id: I0a32003da26c5e1e055b952ca502190068f9960e
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
The i18n.t method changed to i18n.global.t for vue3 support, so this
comment is no longer valid.
I found this on the Intel router and am pushing this for completeness,
but I didn't test this environment.
Tested:
Did not test
Change-Id: Ieba177977583bf05f6444466a630f4e6f83af91f
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
The size override to a height of 60 is not working in my environment.
This updates to override style instead.
Change-Id: I7df8f724f822f60bf555a8ec8fd9e0bf9979dbd5
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
The change from i18n.t method to i18n.global.t for vue3 support was
missed in the page-title guide. I found this on the Intel router and am
pushing this for completeness.
Change-Id: I97c993e36caa07af6df7c1ae3124e4f9380c493b
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
The change from i18n.t method to i18n.global.t for vue3 support was
missed in the IBM router. I found this on the Intel router and am
pushing this for completeness, but I didn't test this environment.
Tested:
Did not test
Change-Id: Iee1f32a82b2a2bf9e30362572486a7c109586fea
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
The change from i18n.t method to i18n.global.t for vue3 support was
missed in the Intel router and caused the pages to fail to load.
Tested:
Confirmed that pages all load correctly.
Change-Id: I9d922f0f4d5016b8a12fd48a97192a95aa646472
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
|
|
Show the Time and Timezone in the overview page instead of showing date
twice. Format the date using the formatTime filters to display the
proper date and time in the overview page.
Before it shows date twice, In the place of time it shows date.
Change-Id: Ibd8211530750091c03f788106bfb78097be2b2d8
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
In case there is a need to include font, you can contact me.
BR, Ekaterine.
Change-Id: I878a0f7ea3ffc163ebc71e0278bac9c0a6323dd9
Signed-off-by: Ekaterine Papava <papava.e@gtu.ge>
|
|
Configure sass in the vue.config.js file and remove the
import of the scss file from each page. The styles are
handled by the css loaderOptions in the config file.
Every component and page has the appropriate style applied.
The appearance adjusts to the openBmc webui in Vue 2.
Change-Id: I3773c063646185b80b7bd61d05aa80a993cbd121
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
Some corrections for the translations added in the commit
918526f20c16a05c261a56814657942a707323dd
("Fix power operations as per DMTF redfish spec").
Change-Id: I0e88ffc3bc3904cbf4b36dd3bae4b5aeb06dcfba
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add russian translations that were missed in a commit
582e954ecff4edf58c143dc644a21b15005e8109
("Fix single event entry download").
Change-Id: I8dbca4d4ab0b3b0776422c5deb58c5f9f79178f3
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add russian translations that were missed in a commit
db47b7e1f4b8174698b1894edabf57d022fac609
("Add support for IPv6 network setting").
Change-Id: I373a9ee6b6cc66324f2677917c960089ad692717
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add russian translations that were missed in a commit
f11a190192115fbb798dc0ded02d3f383e407922
("Added toast notification for identify LEDs").
Change-Id: I0169f24bd2b27a72156273fe091a2597270f572f
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
The functionality of initiating and displaying dumps is not enabled by
default in bmcweb but it's used by at least Facebook, Fii and IBM. While
IBM has their own overview page and router code which makes it
accessible the others do not.
I do not know what the policy should be about exposing features like
that, please comment. Guess ideally webui should discover available
features on startup and add to the menu dynamically, any takers?
Change-Id: I9c85ecaba009547c69166c5cbaba62a005d75f48
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
The commit [1] added oneTimeBootEnabled as condition to display
he Boot settings menu. It is not reasonable as the option is disabled
by default [2] and users can configure for a selected boot option to
be applied once or permanent.
This commit removes the check so that the menu is displayed when the
boot source option is supported.
Tested:
1. Log in to BMC Web and go to the server-power-operations page
2. The boot settings options are shown.
[1]: https://github.com/openbmc/webui-vue/commit/918526f20c16a05c261a56814657942a707323dd
[2]: https://github.com/openbmc/openbmc/blob/f8b0a12a3781e1f771630cad1244016b1ed6f8cd/meta-phosphor/recipes-phosphor/settings/phosphor-settings-manager/boot_type.override.yml#L19
Change-Id: I1efd2ae0c201744076e3fb00229c81847e940687
Signed-off-by: Huy Le Anh <hule@amperecomputing.com>
|
|
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>
|
|
This follows 883a0d597962dfd30d6c48319b8b33e2d0f98606 approach when the
Dumps code was somehow missed during the refactoring.
The change fixes operation for the page showing list of dumps, before it
was blank due to an exception.
Change-Id: I49daa4fdaea1e8d98e4964acff9cb0bda5d8d573
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
SerialConsole was deprecated in Manager v1_10_0 and has been
removed in bmcweb [1].
Because the SerialConsole values were not available anymore, the
Managers were not displayed because "setBmcInfo" couldn't find the
"SerialConsole" properties. THe following error will be logged:
```
TypeError: Cannot read properties of undefined (reading 'ConnectTypesSupported')
at Wa.setBmcInfo (app.25e72670.js:58:745295)
at app.25e72670.js:50:2774
at app.25e72670.js:50:10113
at Array.forEach (<anonymous>)
at app.25e72670.js:50:10092
at Wa._withCommit (app.25e72670.js:50:11953)
at Wa.commit (app.25e72670.js:50:10066)
at Wa.commit (app.25e72670.js:50:9518)
at o.commit (app.25e72670.js:50:2216)
at app.25e72670.js:58:745747
```
[1]: https://github.com/openbmc/bmcweb/commit/fa800c8a141aa4b209269e0fb50cae34aa24f75d
Tested: BMC manager being listed in the inventory and serial console
variables being displayed for the system.
Change-Id: I1a24178717805ca50eef2c89042c0bd9ede1d5bc
Signed-off-by: Tan Siewert <tan@siewert.io>
|
|
Starting with version 10 of the `vue-i18n` package, using % signs in
format strings is considered deprecated. This change removes all
occurrences of % signs from the source code
Change-Id: I0b3057cfc74576bc8b03196437b9879652d26132
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
|
|
The web page stopped loading due to a Content Security Policy violation
error caused by the use of the "new Function" construct in vue-i18n
version 9.13.1. Upgrading to vue-i18n version 10.0.5 resolves this issue
Change-Id: I57fa72a4ee8edc282a122e42358a77e254c7943f
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
|
|
The regex formula for formatting dates is no longer correct after
upgrading to Vue3. This commit corrects it by adding a `$` sign to the
end of the date pattern to avoid wrongly validate date in wrong
format.
Tested:
1. Log in to BMC Web and go to the date-time setting
2. Click "Manual" to fill Date field with the following
format: 2025-06-112
3. Can't save and show "Invalid format"
Change-Id: Ia1ff1e9cc9885772e6145732dab177949be60969
Signed-off-by: Huy Le Anh <hule@amperecomputing.com>
|
|
When using createWebHistory method in Vue 3, we may encounter a 404
error when reloading a page or accessing a specific URL directly due to
a server configuration that does not properly support HTML5 history,
references at [1] and [2]. Switching to createWebHashHistory method
avoids a 404 error when reloading a page, as it doesn't require a server
configuration to handle navigation. By using the # sign in the URL, the
browser processes everything after the # sign without sending it to the
server, which helps maintain the application state smoothly when
reloading the page.
Tested:
1. Go to the Obmc web page.
2. Switch between different pages.
3. Reload the website by pressing the reload button on the web browser.
4. The Obmc web page reloads normally, without any errors
5. Go to the KVM page and press "Open In New Tab"; the new KVM screen
window displays normally, without 404 error.
6. Go to the SOL page and press "Open In New Tab"; the new SOL screen
window displays normally, without 404 error.
[1]: https://router.vuejs.org/guide/essentials/history-mode.html
[2]: https://stackoverflow.com/questions/66514813/error-404-on-page-reload-with-vue3-routing
Change-Id: I6f4dbd2b27888c852b627d74471671352ee43a39
Signed-off-by: Huy Le Anh <hule@amperecomputing.com>
|
|
On user management page fix the error while save the account policy
settings with the automatic after timeout.
while changing the timeout duration the value is in string but the
payload should be integer.
Add the parseInt in the timeout duration value while save the account
policy settings with the automatic after timeout.
Change-Id: I69ab13af3fd34e4128d3f01b71b0ffd092fe9a06
Signed-off-by: suryav9724 <suryav@ami.com>
|
|
Problem:
Clicking on Refresh button present on UI top panel does not
refresh active notifications or toast messages.
Only success notifications gets hidden automatically after 10s,
error, info notifications remains active on UI even after refresh
webui.
Solution:
Clear all types of active toast messages upon refresh click.
Changes:
In refresh method, using querySelectorAll on document object
and for each toast currently active, call bvToast.hide to clear.
Change-Id: I47ba416a6b8e8e9872b4b4867abf96bbbef7c0f1
Signed-off-by: Shubhi Garg <shgarg@nvidia.com>
|
|
Update to api function for MessageIDs - PaswordChangeRequired
This patch is just a small tweak while still assuming the current
X.Y.Z version format.
When searching for a standard Registry string from @Message.ExtendedInfo
-which is an array of Message objects-,
we should stick to the default namespace.
For example,
if someone added OpenBMC.0.5.0.PaswordChangeRequired it could be
erroneous to assume that it has the same meaning, since
semantically it is a different message.
For our use, trying to do something useful with version portion
seems problematic, so I am fine with ignoring them as already done
with code being updated here.
The search function has been made generic to allow reuse,
and some IntelliSense sugar was added.
Tested, as Paul documented:
Tested: logging in, navigating, logging out with non-expired password.
Logging in, navigating, then running `passwd -e <accountname>` via ssh
leads to functional password change page on the next request and then
navigating proceeds normally, and logging out too. If password is
expired before logging in the user gets redirected to the password
change page automatically after logging in.
Change-Id: I306ace2024efea13f25e24528a048d0955b2f95b
Signed-off-by: j-westover <jwestover@nvidia.com>
|
|
During the upgrade to Vue 3 [1], the initialization of the selector,
including the definitions of height, display type, background, overflow,
etc., was ignored, resulting in the KVM screen not displaying the
terminal interface. This commit helps to import these properties for the
KVM from the _kvm.scss file to fix bug [2].
Tested:
1. Go to the OBMC web page.
2. Go to the KVM page and check that it works normally
3. By minifying and zooming in on the web browser, the KVM screen
adjusts automatically.
4. Switch between different pages.
5. Return to the KVM page and check that it works normally.
[1]. https://github.com/openbmc/webui-vue/blob/master/src/App.vue#L38
[2]. Bug: https://github.com/openbmc/webui-vue/issues/128
Change-Id: I1842c914e27dd5c68fe20f49999712b68c1e93a5
Signed-off-by: Huy Le Anh <hule@amperecomputing.com>
|
|
Currently webui-vue has a hardcoded list of pages and sidebar menu items
restricted to a specific Redfish role (from a predefined default set).
To disallow navigating to restricted pages and to hide disallowed menu
items the application needs to know the roles assigned to the session.
bmcweb only implements a single role identity per session so the Roles
array returned within a Session object always has just one element.
This patch changes the mechanism used to retrieve the current role from
buggy direct query to AccountService (which can only return information
about BMC local users) to extracting it from standard Redfish Session
object.
In case the role is not available (e.g. when backend implementation
predates #Session.v1_7_0.Session) the application assumes Administrator
role which is meant as a best effort to continue working given the
circumstances. This doesn't pose a security risk because all validation
is always performed by the backend itself, so the worst that can happen
is end user getting error messages trying to access something without
enough privileges.
Tested: logging in and out of accounts with different roles without
reloading the page, observing the list of queries made, the role
variable assignments and presence of the menu items depending on
account, navigating to different pages. Also tested reloading the page
and confirmed the correct role was retrieved without going through login
again. Also tested deleting and mangling localStorage variable
sessionURI prior to doing page reload, in those cases redirect to login
page was observed.
Change-Id: I8b6c84060a987489cc1d35c46c1b00618a88b607
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
[Problem Description]:
1) Power Operations page uses "Orderly" and "Immediate" strings
for "Graceful reboot/shutdown" and "Force reboot/shutdown".
These names do not align according to redfish spec and causes
user confusion.
2) For boot settings, if "BootSourceOverrideEnabled" flag is false,
WebUI allows to modify boot options.
[Changes]:
1) Changed reboot/shutdown naming convention as per DMTF redfish spec
to view correct names on WebUI.
2) Added info-tooltip to give detailed information on Reboot/Shutdown
options.
Information is referenced from:
https://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/ResetType
3) Added "oneTimeBootEnabled" condition check to render BootSettings if
condition is true. "oneTimeBootEnabled" checks BootSourceOverrideEnabled
flag, if true then BootSettings will be able to modify boot options.
[Testing]:
1) Load WebUI with the changes and go to Power operations page.
2) Check reboot shutdown names have changes to Graceful
reboot/shutdown" and "Force reboot/shutdown".
3) Check if BootSettings template renders as expected.
Change-Id: I5a86e05ee03167ebb93ffd381af3a47c277990fd
Signed-off-by: Shubhi Garg <shgarg@nvidia.com>
|
|
Fix i18n issue in the Power restore policy, Inventory LEDs, and User
management page.
After merge the vue3 code to master the i18n Power restore policy,
Inventory LEDs, and User management page got conflicts and old code
retrieved in master. So unable to render the Power restore policy,
Inventory LEDs and unable to disable the user in user management page
change the i18n.t method to i18n.global.t for the vue3 support.
Change-Id: I46f3f56632308ceaee321dd896e16e922d964b60
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
Invalid feedback element if condition change, Helper import change
in date time page and table date filter global component.
Change-Id: I1f01943229b78d4dff36f3905fe3781ba696d528
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
For required, invalid format, minlength, maxlength, date, pattern
validation if condition change in the few components
Change-Id: Id8eebc140301e48dde833a604ca92426ebf77c9c
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
In LDAP loading declare outside the form, form validation condition
change, server power operation page validation added and i18n method
changed in the event log store.
Change-Id: I903b4dec7da1a5a2cc8441c65693c57201405d70
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
In vue3 i18n is not return the object value from the locale, so
unable to do the for loop in Setting list. Remove the for loop and
implement the separate list for reset bios and reset to default.
And implement the useVuelidate in the factory reset page.
Change-Id: I10833742475b90f7c5349a5b995ff04e93c306de
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
While use i18n.locale it is undefined so those pages use the
storedLanguage that page gets failed to load.
Change-Id: I11b45f42d06bb355f561d5c1e93f7516775b1c81
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
In network page invalid if condition changed, added validations and i18n
function changed based on the vue 3 support.
Change-Id: If5b9c00f6da722984f1c568cfbcb6b34537c3df1
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
While add a file in the form file vuelidate error occurs and global
component form file not return a file, by emit the $event in form file
fix the issue.
Change-Id: Icbeddc7a3faa262f12e85268206ae70950f37905
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
A password can expire at any moment during session lifetime and bmcweb
starts returning 403 Forbidden errors to the requests made after that.
The response contains clear indication of the condition in the standard
`@Message.ExtendedInfo` attribute which is an array of Message objects.
Previously the code was trying to detect this condition by querying
AccountService after logging in but this approach doesn't work when
password expires mid-session. Also it was limited to BMC-managed
accounts and used hardcoded account URIs in violation of Redfish spec.
This patch adds to the interceptor of 403 error so that the user is
automatically redirected to the password change page as soon as the
condition is detected.
The same message is also present in the session creation POST response
201 if the password expired before the log in attempt, in this case the
session is created as usual but the user is automatically redirected to
password change page before any further requests are made.
Tested: logging in, navigating, logging out with non-expired password.
Logging in, navigating, then running `passwd -e <accountname>` via ssh
leads to functional password change page on the next request and then
navigating proceeds normally, and logging out too. If password is
expired before logging in the user gets redirected to the password
change page automatically after logging in.
Fixes: https://github.com/openbmc/webui-vue/issues/118
Change-Id: I03f5ee2526a4bb1d35d3bbea1142fea077d6bfed
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
helpers and sameAs validations are not working in vue3 so the helpers
and sameAS are imported from vuelidate/lib/validators. Invalid
validation field like required are not show so the if condition for
invalid feedback alert field changed. Add user and delete user are
working in the user management page.
Change-Id: I0133e02357048ffbc6206382b2a0a5c162e2384d
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
- Removed TFTP server firmware update ability in the UI.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
Signed-off-by: Surya Venkatesan <suryav@ami.com>
Change-Id: Icbeddc7a3faa262f12e85268206ae70850f37905
|
|
Vue3 has deprecated "hash" and recommends moving to contenthash. Also
remove source maps when not in development mode, so the build fits on
the bmc again.
Change-Id: I55b480d9b722c22b3670b19ec699a76fce07d1a5
Signed-off-by: Ed Tanous <etanous@nvidia.com>
|
|
Ipv6 got added. Make the updates to make it build for vue3.
Change-Id: Ifaa4b8e46200a8431c5d9ca9b8e3e279cc868f26
Signed-off-by: Ed Tanous <etanous@nvidia.com>
|
|
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>
|
|
1. Configuration of i18n legacy as false.
2. Translation function t is called using the useI18n.
3. Used the i18n.global.t() function from i18n instead of this.$t()
4. Event bus error that occurred during logout.
5. Implemented vue-router 4.4.0 and vuex upgrade to 4.1.0
Change-Id: I9464d82c76dcc1445ce271983ea3ab9d7b03d265
Signed-off-by: Surya Venkatesan <suryav@ami.com>
|
|
Start the process of porting everything to Vue 3. I have most things
working. npm run-scripts build works, npm install works. prettier
passes. Styles load, login works, webui loads.
This was primarily done using the linked documents below. It makes the
following design decisions:
1. Vue is put in compat 2 mode, which allows most of the components to
work as-is.
2. Bootstrap v4 is used along with bootstrap-vue to keep our components
working.
3. Minor changes are made to load the latest versions of vue-router,
vuex, and vue-i18n.
I suspect this patchset is good enough to start with, and we can clean
up the broken things one patchset at a time. The things that need to
happen are:
1. Get remaining features working again. This primiarily is vue-i18n
for mixins, and non vue components. This likely needs to be done by
not pulling in i18n into the non vue components, then using the .Vue
files to do the internationalization in the component context, NOT in
the mixin context. Alternatively, we could drop MixIns alltogether.
2. Get custom styles working again. Previously, we used some path
hackery in vue.config.js to optionally pre-load styles. This stops
working now that we're required to @import our modules. Likely we
need some rearangement of the paths such that custom styles are a
complete replacement (possibly importing the original) rather than
additive with overrides. That's a guess, but I don't really see
anyone else doing customization the way we've defined it here.
3. Bootstrap 5 no longer requires ANY custom vue modules, as it has
dropped the jquery dependency. We won't be able to pull in bootstrap
5 all at once, so pull in bootstrap 5 under an alias, like
"bootstrap5" that we can optionally import 5 or 4.
4. One at a time, start porting components over to Vue3 syntax and
bootstrap 5. This will be the bulk of the manual work and review.
The only thing I think left is getting unit tests passing, which I
commented out the pre-commit hook to make this PR.
Tested: Code builds. Needs better testing.
[1] https://router.vuejs.org/guide/migration/
[2] https://vue-i18n.intlify.dev/guide/migration/vue3
[3] https://vuelidate-next.netlify.app/migration_guide.html#package-name-and-imports
Change-Id: I5bb3187b9efbf2e4ff63e57994bc528756e2a981
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
- Previously, we used to get the values for power restore policy page
from“JsonSchemas/ComputerSystem/ComputerSystem.json”. Now we have
removed the hardcoded API call and are fetching the values from
the JsonSchemas/ComputerSystem’s URI because we would have versioned
ComputerSystem.json in the redfish response.
Change-Id: I1a25cbbb3dfc536485a6f71a359ae32c6eadf5f7
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
|
|
Event entry should be downloaded with specific http header of "Accept:
application/octet-stream" or "*/*", but the default http header is set
to "Accept: application/json", so need to specify the header for event
downloading.
Refer: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/40136
Tested:
Event entry data can be downloaded with the fix.
Change-Id: Ia45123340da79a54fc4229470e6822206b8df808
Signed-off-by: Sean Zhang <xiazhang@nvidia.com>
|
|
- The Dumps count in the overview page is not displaying the count of
all
the entries. Updated to display count of all entries.
- The registration of Dumps store is in multiple locations,
store -> index.js and env -> store -> ibm.js.
Causing error in IBM machines because of duplicate
registration.
Removed from env folder.
Change-Id: Idc57a85db090d1b1d3211c01e658b181a7fc1177
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
|
|
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>
|
|
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>
|
