Age | Commit message (Collapse) | Author | Files | Lines |
|
This reverts commit bf37b317496c80dc9a87f49356efdab8a3b50caa.
The current version of the stack doesn't prevent logging in and all
operations without overriding "Connection:" header.
This overriding is making it impossible to test any WebSocket-based
functionality (IP KVM, SOL, Virtual Media).
Tested: logging in, navigating the interface, using IP KVM and SOL
console.
Fixes: https://github.com/openbmc/webui-vue/issues/94
Change-Id: I6174c75e35784ff370f6adf7841c98ae78a26ceb
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
- We were calling a method that is not present in
@filtered. Fixed this by using the method that is
added for this purpose and not used.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
Change-Id: I26b4b7d9be00c79c17dba382c0df6a0f02e1cd89
|
|
When in Dev server mode, we the webpack dev server isn't capable of
understanding wildcards, and that index.html, and index.<hash>.html are
the same thing.
Disable the index file hashing when in dev mode.
Tested:
Launched dev server without bmc present. Observed UI could be loaded
correctly.
Change-Id: Ie2d3bfe4af0117681cec8c92f93d7e278b2071f2
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
At https://github.com/openbmc/webui-vue/projects/1 GitHub warns me:
"Projects (classic) will be sunset on August 23, 2024".
I don't see a benefit here GitHub issues can already be filtered.
Change-Id: I3debd3ff7e52bcd408ae0917f52a35539a74a9ef
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
A new version of prettier is flagging this. Fix the link.
Change-Id: Ibb376bed7472b697c59bcaee75e958a969a72e61
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
By allowing root user privilege changes to Operator or Read Only,
after login with root user seeing privilege access issues in some
pages and not possible to change administrator again.
Allowed root user to change password alone and disabled
the privilege changes
Change-Id: I2be93060fb30e1f08dc2ea20a30fb998dc83ee0f
Signed-off-by: aravinths1 <aravinths@ami.com>
|
|
After scrolling down a page and navigating from that page to
other pages, the page still shows the bottom of the page and does not
display the top of the page.
Scroll behavior added in the router, So when navigating from one page
to another page the top of the page will always display.
Change-Id: I883e8a9f6ae3f98846996883cac0961b4c24c62b
Signed-off-by: aravinths1 <aravinths@ami.com>
|
|
First, remove the preload plugin installed by default. Given that the
login page requires the complete javascript package to be loaded before
the page can be rendered, and doing the rendering inside of bmcweb
before javascript is loaded[1] doesn't seem to be desired by the
community, preloading it does us essentially no good. The DOM itself is
tiny.
This fixes a split second flash that's seen on refresh, where the DOM is
loaded, but the javascript has not, so there's no content to render.
Second, modify the html loader plugin to produce the hash of the file at
output, thus allowing the index file to be cached, and allowing the etag
machinery[2] to work.
[1] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/35456
[2] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/70644
Tested: After this patch, nearly all resources on refresh return 304,
not modified from bmcweb. This significantly reduces the requirements
for TLS encryption on the BMC.
Change-Id: I7189c6024cacba099705ff6d27e4567bf88f3df4
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
- Added success toast notification messages for identify
LEDs present at Inventory and LEDs page and Overview.
- Import of Toast was not present in Overview's Inventory
card and DIMM slot table, fixed it.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
Change-Id: If9ad84e66f6f15616cb8af51b1e84d8d06b1afd0
|
|
- The contents in the Power restore policies were not listed
in a new line for large or extra large screens, Fixed
this by using stacked prop.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
Change-Id: I30ec1206a929137fc6635d602944cd80d2c2805f
|
|
- Unable to generate Certificate Signing Request (CSR) when filling
optional field-Challenge password values on Certificate page.
- Hence, removed the Challenge password option from the Generate
CSR panel.
Change-Id: I862f024de84f34738be5e5cd22701b63c2309152
Signed-off-by: Vedangi Mittal <vedangimittal3004@gmail.com>
|
|
For accounts authenticated remotely (e.g. with LDAP or RADIUS) the API
endpoint (handled by bmcweb) can not provide any information about
RoleId currently, reporting 404 instead. This confuses the frontend and
it doesn't allow to navigate at all.
Fix this by lifting all frontend-side restrictions by assuming
'Administrator' role in this case. Since the backend verifies validity
of each and every request anyway this doesn't affect security anyhow.
Tested: logging in, out and incorrectly using local BMC and remote LDAP
users, reloading the page with an active session. In all cases frontend
behaved as expected, storing assumed RoleId after getting 404 not found
reply and using it for unrestricted routing decisions.
Change-Id: If17d06bf0b8a372acd1980f6777227e25d9c78d8
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Bmcweb supports the If-None-Match and etag headers on responses. While
for static files, we can do a direct set, for responses, there's no way
to cache values.
Add caching support by adding what seems to be a well supported axios
package. Note the intent is that the cache expires immediately, such
that the bmc will always be polled for results, and return 304 when not
modified. Additionally, we currently cache these values in the session
context, such that they can be reused on refresh.
Tested: webui loads properly. Upon navigating to a logs page, and back,
the network console shows the bmc returning nearly all redfish responses
with 304, not modified.
Change-Id: I2e8067a88a0352226db9f987d1508ab5bf266b92
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
The favicon is currently loaded directly by url. This commit changes it
to be loaded by file-loader. Note, the default vue webpack file loader
doesn't support ico file types (because it seems to expect to use a png
here), so add that to the file loader config.
This allows bmcweb [1] to provide caching headers for the favicon, and
avoid downloading a new favicon on every refresh.
Tested: Webui-vue loads, favicon in the network panel loads properly.
[1] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/70644
Change-Id: I27e5b459ff8822294ac9273220111e9944e8d1e5
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Considering that currently, there's no way to load the login page
without both the main json, and the 1 vendor chunk, chunking itself gets
us no extra performance, and makes it harder on the bmc, because we now
have to respond to two requests instead of one. These requests in
practice happen serially, so on high RTT connections, it can be a
negative on performance.
Simplify by changing the webpack settings to produce one chunk.
Tested: Webui loads properly. No errors on console when clicking
around.
Change-Id: Ida5bb748429137eb2414be1990168affe1d001af
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
To improve UX for users of accounts with restricted permissions the
frontend determines the current RoleId. Knowing that it can hide menus
and inhibit transitions that are not allowed by the backend in any case.
This patch unifies the handling by moving processing of the API reply
containing RoleId in the single place, right where
`authentication/getUserInfo` store gets it. This makes the program flow
easier to understand and change if needed without worrying of where
another copy of the code might be and how it would need to be amended.
No functional change.
Tested: logging in and out, navigating the pages, getting an error
message when wrong credentials are used, reloading the page with an
established session. All while observing Network and Console tabs in Web
Developer tools, no unexpected API requests are made and no unexpected
errors reported. Confirmed in debugger that the retrieved role gets
stored and used for routing restrictions.
Change-Id: Ia8782f44cb6bf813954d30b8bf3a620a626ad455
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Ideally we wouldn't have to pull down this file on every load, and we
could just inline it. This commit implements inlining. Note, that
this requires a minor modification to the unit test, as the inline
header remains when unit tests are run. It's not clear at this time
how to make inlining plugin operate on unit tests, but it doesn't seem
terribly important.
Tested: Loading the webui no longer shows a download of logo-header
Change-Id: Iaa5be5b5a84e0ad6e1f430113f929032835c9f1c
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Having this code is causing crashes for implementations that don't have
dbus-rest enabled in bmcweb, which is deprecated. This commit is
intended to start a discussion around this issue, and propose simply
removing it.
33a8c5369e0253a93dba2e70647bda1c7697b73b (checked in July 2020) points
this crash out, and adds a way to disable the feature. While we could
just make VUE_APP_SUBSCRIBE_SOCKET_DISABLED the default, this seems ill
advised, given the dbus-rest options deprecated status.
Change-Id: I6244f5e2ce895199d5d47cfca9eef36584e8f524
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Users of common WIMP GUIs (as opposed to interfaces primarily meant for
touch input) expect dialog boxes to have keyboard focus set on the
button for default action so that it can be executed by a single key
press. Usually that is chosen to proceed with the operation but in cases
where that leads to data loss the UI designers often pre-select Cancel
as a precaution.
This patch adds suitable property to all invocations of msgBoxConfirm()
method of `this.$bvModal` BootstrapVue object. For regular actions the
confirmation button is selected and can be activated by Enter or Space
bar. For actions deemed dangerous Cancel is focused instead so it takes
two key presses (first being Tab to shift the focus) to prooceed.
This also improves accessibility following the Web Content Accessibility
Guidelines (WCAG) published by W3C.
Tested: manually verified that modals are consistently shown with the
specified button focused, Enter and Space bar key presses produce the
same effect as left pointer button click: when Cancel is focused it just
closes the window, when OK is focused it sends the corresponding request
to the Redfish endpoint.
Change-Id: I66bfd02e48e08dc18994b11bbdd5d6b3ea27047f
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Having the SVG files loaded as a separate package significantly
increases the load time of the UI, as it forces the images to be
downloaded AFTER the page has loaded.
This commit adds the vue-svg-inline-loader, and appropriate config such
that the styles can be inlined, and a second trip to the BMC is not
required to load the login screen. This improves the "time to glass" of
the webui quite a bit.
Tested: Webui loads. Network tab shows svg files are not loaded. Webui
login page looks correct.
First load of the webui renders 500ms faster (1.9s vs 1.4s)
Change-Id: Iebcd9ab5df6edad0a1a5c53c028eccd2fda8f63c
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
The characters in the OpenBMC logo use class styles 1 and 6. SVGO for
whatever reason chokes on trying to deduplicate these, which causes a
template error when inlining the SVG, because style tags still exist.
Ideally in the future we would export our SVGs with inline styles, or
get SVGO to do it for us, but inline the styles manually for now.
Note, that build-on-openbmc-logo.svg has no style tags, and does this by
default, even though they are very similar images.
Tested: Loaded webui. Logo loads properly.
Change-Id: I21c7a24ba49c85559f07fce859d81ed96a40a04f
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
This file was likely exported out of Adobe Illistrator, which has some
less than desirable traits. Format the file such that it can be
modified.
Tested: Whitespace only. UI loads image correctly
Change-Id: I8689ff0193f54608391a4c81fa72b16ed21a04be
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Current Axios version was 0.21.4, this version has a CSRF vulnerability.
https://github.com/axios/axios/issues/6022.
v1.6.0 has fixed this problem, upgrade Axios to that version.
Reference: https://github.com/axios/axios/pull/6028
The package-lock.json was generated by pointing bitbake at my local repo
and building the image. devtool modify -n webui-vue <local repo>
This uses the npm version in yocto 10.4.0.
Tested: Loaded this on a p10bmc and GUI looked good.
Signed-off-by: Nikhil Ashoka <a.nikhil@ibm.com>
Change-Id: Ifb0d64c7d4d15d2396ee6d83d609ab8522d9e247
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Sivaprabu is working on webui-vue, been active in moving in Vue3 and
expressed interest in being a Reviewer.
Change-Id: I0b9d5404a8b88049aac52edbb76f8c2de920bd3e
Signed-off-by: Kiran Kumar <kirankumarb@ami.com>
|
|
Building the webui returns a warning that browserlist is out of date.
Do as the command asks, and run.
npx browserslist@latest --update-db
To update the package-lock.json to the latest.
Change-Id: Iffb9553e68be5a14e36e358a3c695e43048ff82e
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Switch Power Supply information to use information from the new
PowerSubsystem since bmcweb enabled this by default, any other modern
Redfish implementation should have this schema enabled.
Tested: On Ampere MtJade platform
1. Login to WebUI; Hardware Status; Inventory
2. Inventory information for power supplies is displayed.
Change-Id: Iad59d0145b47bcd5eb3cb4ff852e50da976a6005
Signed-off-by: HuyLe <hule@amperecomputing.com>
|
|
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>
|
|
Remove VUE_APP_FAN_DATA_FROM_THERMAL_SUBSYSTEM. Assume any Redfish
implementation we are using has the new ThermalSubsystem. bmcweb, the
only webserver, webui-vue supports today, enabled this by default at
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69228
ThermalSubsystem, PowerSubsystem has been out since 2020.4, so it is
reasonable to assume it is there in any modern Redfish
implementation.
Tested: Nabil tested and verified this worked.
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Change-Id: I4952daf30f9b654234dd0e838adebc38cc8c380f
|
|
Renuka is working on webui-vue, been active in moving in Vue 3 and
expressed interest in being a Reviewer.
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Change-Id: I87908758b3ad21ed29522b6855b63cb3f0fe3ce1
|
|
Add listener that checks username in local storage every 10 seconds.
If it's empty, listener closes kvm console.
Change-Id: I3cde71f4dc9772cddcf3a2f00f6e49f4d78f8383
Signed-off-by: Konstantin Maskov <sulwirld@gmail.com>
|
|
When a processor is present:
Old behavior: Health = Ok (green color)
New behavior: Health = Ok (green color), State = Enabled (green color)
In the absence of a processor:
Old behavior: Health = Critical (error red color)
New behavior: Health = Ok (green color), State = Absent (warning yellow)
Tested manually on my system with 1 CPU present and 1 CPU missing
Change-Id: I33f8d94cbb5dcfd6a33b4b3ca379d2323362caca
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
|
|
NPM warns that this package lock was built with an old version of npm.
So rebuild it with the version in yocto, 10.4.0
```
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN old lockfile vue-loader-v16: No matching version found for vue-loader-v16@16.1.2.
npm WARN old lockfile at module.exports (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm WARN old lockfile at RegistryFetcher.manifest (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:119:22)
npm WARN old lockfile at async Array.<anonymous> (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727:24)
npm WARN old lockfile Could not fetch metadata for vue-loader-v16@16.1.2 vue-loader-v16: No matching version found for vue-loader-v16@16.1.2.
npm WARN old lockfile at module.exports (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm WARN old lockfile at RegistryFetcher.manifest (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/pacote/lib/registry.js:119:22)
npm WARN old lockfile at async Array.<anonymous> (/home/ed/openbmc/build/tmp/work/all-openbmc-linux/webui-vue/1.0+git/recipe-sysroot-native/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727:24) {
npm WARN old lockfile code: 'ETARGET',
npm WARN old lockfile type: 'version',
npm WARN old lockfile wanted: '16.1.2',
npm WARN old lockfile versions: [
npm WARN old lockfile '16.0.0-beta.5',
npm WARN old lockfile '16.0.0-beta.5.1',
npm WARN old lockfile '16.0.0-beta.5.2',
npm WARN old lockfile '16.0.0-beta.5.3',
npm WARN old lockfile '16.0.0-beta.5.4'
npm WARN old lockfile ],
npm WARN old lockfile distTags: { latest: '16.0.0-beta.5.4' },
npm WARN old lockfile defaultTag: 'latest'
npm WARN old lockfile }
```
Change-Id: I5b630ddf809ccc5c3cd014c668b6a827136835bf
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
All changes should be whitespace, and were done using npm run-script
lint.
Change-Id: I943c6b435c5c872841af5affc1e89910468b5ca6
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Being on an old version of eslint is causing conflicts in our builds,
but because we pull in the @vue/cli-plugin-eslint plugin, we can't
upgrade. @vue is non trial to update, because webui-vue is on vue 4.X,
while the latest is 5.X.
This commit upgrades eslint to the latest version, and at the same time
disables @vue/cli-plugin-eslint. Not having a cli plugin doesn't seem
like it would be any amount of impact, as devs can just run eslint
manually.
At the same time, to fix a minor issue, update all of @vue to the latest
minor revision 4.5.12->4.5.19
Change-Id: I3ca9c7bbee5bdf9046d86e25e7130808b9caaa2b
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
New versions of the vue linter flag that this class has no effect. It
isn't clear what the intent was, so remove it so the linter can pass.
Tested: Upgraded linter now passes.
Change-Id: Icccc4d57714be313c958023c74e9d8508afed4ce
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
Format code is supposed to do just that... format code. npm ci is doing
much more than that, so it belongs in run-ci.
Change-Id: I4c4e94f1a53e04aa13289aea259098143377cc2c
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
New versions of vuex warn if there are modules that are used in an
element that haven't had their namespace defined. This module isn't
actually used in the test, so add an empty Vuex module that matches the
name of AuthenticationStore, so the test can pass.
Change-Id: I5bceb3e1e0bad603028cfb17fa95b020d68ceb4d
Signed-off-by: Ed Tanous <ed@tanous.net>
|
|
The commit "Add SNMP alerts page and test hooks"
(7c1cfe7e25957fc915fc9790bdf78887295b1fee) has added a new page to the
navigation, but didn't change the shanpshot. As a result this broke the
unit tests.
Perform "npx jest --updateSnapshot" to automatically correct the
AppNavigation snapshot.
Tested: Did npm run test:unit and it passed.
Change-Id: I9f9dbf235013d8736d958d5c8d19eb3d75c575ba
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Spanish was on the list, but the actual translation was missing
Change-Id: I36fd0542954f048fceea7c6ad7b1e0f207e70df8
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
|
|
With a large number of FANs, a list of names is much easier to read than
a list of IDs. Now the Name is in the header of the row, and the ID only
when expanded.
Change-Id: Ic8a08e28db7f747f9765f45dbbda504bf827fb25
Signed-off-by: Glukhov Mikhail <mikl@greenfil.ru>
|
|
I have multiple email addresses in my Gerrit account but as
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69506 shows my Preferred
email has to match the OWNERS file, do that.
More discussion in Discord at
[1] https://discord.com/channels/775381525260664832/817151035197358081/1209585278025601094
Tested: With https://gerrit.openbmc.org/c/openbmc/bmcweb/+/69549 my +2
means something again.
Change-Id: I56c3813cd3f5feb5f0b614786dea374efe19dc79
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Add russian translations that were missed in a commit
5d86af86e5dd0c4c7d9e902fc191c8b19ac890d1
("Add State to DIMM slot inventory summary").
Change-Id: I127fd05a2ceb621c3ba455b9caf89578b48e5cf9
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Add state information in DIMM slot inventory summary so that users can
know if the DIMM slot has DIMM plugged or not.
Change-Id: Id9b7ebb2079762b354b418d060d4a1223273b50d
Signed-off-by: HuyLe <hule@amperecomputing.com>
|
|
Issue: when clicking the Refresh button at top right corner of the
WebUI, sensors that were removed from Redfish are not removed from the
WebUI but still shown with old sensor values.
Root cause: current code keeps a list of sensors. Click on Refresh
button just checks and updates sensors returned by Redfish, it does not
check if sensors are still present or not. This is incorrect for
sensors on hot plug devices or PLDM sensors when the sensor source is
not available. In this case, sensors are completely removed instead of
just their values changed to n/a.
Solution: Initialize an empty array sensor state to retrieve
existing sensor data whenever loading sensors.
Change-Id: Ifb0c0586fdba22b6f446c58b3d5b937a3f3ee750
Signed-off-by: HuyLe <hule@amperecomputing.com>
|
|
- if isServerPowerOffRequired is true & !isServerOff is true
a warning will be shown that the server must be powered off
to switch images and update the firmware.
- When system power is on,
the switch to "running button" is disabled.
Signed-off-by: Kenneth Fullbright <kennyneedsmilky@gmail.com>
Change-Id: I65a24984c36f6ae39d715f4fa66e9884d031cb20
|
|
When the IPv4 address is in DHCP mode, hide the trashcan icon.
If the address is in static IPv4 mode, the trashcan icon will show
that the user can delete the IPv4 static address.
Change-Id: I27dc8dc64d93b1e2425de6143473a91f7bc0b104
Signed-off-by: Sivaprabu Ganesan <sivaprabug@ami.com>
|
|
As part of [1] There are deprecated login flows that webui-vue seems to
have copied from phosphor-rest. These were originally added because
phosphor-rest didn't look at response codes, but webui-vue does, so we
can use the normal version, which allows us to reduce the code in
bmcweb.
This needs to go the same time as [1].
Tested: Gunnar tested with 65810 and this works.
[1] https://gerrit.openbmc.org/c/openbmc/bmcweb/+/65810
Change-Id: I1e55f08cf1d7d44b6757ac4173a26546eaca72e5
Signed-off-by: Ed Tanous <edtanous@google.com>
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
This page will be included in Configuration section of the primary
navigation. The user will be able to delete and add alert destination.
Change-Id: I396d19a54ea11724f2c5aec67e20ba9abff947d3
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Just like the commit before it, enabling this on the env Intel, enable
VUE_APP_FAN_DATA_FROM_THERMAL_SUBSYSTEM and ThermalSubsystem for the fan
data.
Change-Id: Iaf8164ed622546579a379c707ebbc9660017379b
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Fan data API switch in Inventory and LEDs page based on
environment variable VUE_APP_FAN_DATA_FROM_THERMAL_SUBSYSTEM.
Backend Support PR:
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/57533
Change-Id: I95ac9f9cef97bdab84a179b3e318eb37ab11752b
Signed-off-by: Sivaprabu Ganesan <sivaprabug@ami.com>
|