| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The webui was using a websocket to subscribe the events from BMC for
server status and logging.
It uses a debouncer of 2.5 to limit the events, however, it causes the
loss of the events, so the power change status event could be missed by
the webui, causing the `Power` status is not really consistent.
There was an issue in the property change handler as well that it
assumes the `CurrentHostState` is there. However, certain event could be
fired without `CurrentHostState` change, e.g. the "ForceWarmReboot" will
get an host event of `RequestedHostTransition` without
`CurrentHostState`'s change, the code will get an undefined
`CurrentHostState` and the `Power` status becomes undetermined.
Remove the 2.5 debouncer, and only set the power status when
`CurrentHostState` is really received to fix the issue.
Tested: Verify the `Power` status is consistent with the server status.
Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I732069fff954a2b8b1de4848115641903a8bc904
|
|
This patchset focuses on the global store use for server power
operations and impacts several pages in the interface.
For consistency, both in the UI and the code base, we are replacing
the term host with server. This change impacts both the user and the
developer experience. Maintaining consistency in naming allows both
developers and users to form a mental model of the overall system
and will help remove confusion when interacting with the UI and
editing the interface.
Testing:
1. Tested shutdown, power on, and reboot and verified the icons and
page sections in the site header and the server power operations page
update as expected during power operations.
2. Verified the one-time boot operations alert is displayed to the
user when changing the boot settings on the server power operations page
3 Tested factory reset and validated the correct information message
is displayed to the user with the server power off and on when
performing the factory reset functions.
4. Verified the SOL Console status icon updates correctly during
power operations.
5. Verified the alert message is displayed on the firmware update page
when the server is powered on.
Signed-off-by: Derick Montague <derick.montague@ibm.com>
Change-Id: I88499a746364ab80f16a8b350d550407d094e95d
|
|
- 99% of changes were small syntax changes that were changed by the
lint command. There were a couple of small manual changes to meet the
property order patterns established as part of the vue:recommended
guidelines.
There are rules that were set from errors to warnings and new stories
are being opened to address those issues.
Testing:
- Successfully ran npm run serve
- Successfully ran npm run lint
- Verified functionality works as expected, e.g. success and failure use cases
- Resolved any JavaScript errors thrown to the console
Signed-off-by: Derick Montague <derick.montague@ibm.com>
Change-Id: Ie082f31c73ccbe8a60afa8f88a9ef6dbf33d9fd2
|
|
Removing .on() function because it is not a valid method and is causing
errors:
Uncaught TypeError: ws.on is not a function
The onerror event listener is already logging the error.
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
Change-Id: I6ccfa9a3a6beba93668b8c209b59560f4bf7b4bc
|
|
Intel does not support subscribe socket yet.
I don't want to try to connect with this socket
becuase it crashes entire app in development mode.
Signed-off-by: Mateusz Gapski <mateuszx.gapski@intel.com>
Change-Id: I09d66474480dcb37393ecff5d46c4ee0e9052f99
|
|
Changes to WebSocketPlugin to dispatch event log GET request
when new event interfaces are received.
By re-fetching the Redfish logs the health status icon in the
application header will always reflect the visible event logs.
The plugin was previously only updating the header status, so
it was possible for the header status and event logs to be
out of sync.
- Changed to use Redfish endpoint for event log GET request
/redfish/v1/Systems/system/LogServices/EventLog/Entries
- Update AppHeader Health status icon to reflect changes
made with Redfish log Severity property
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
Change-Id: I73a3a441dcbbb3a29ef9a51f961c062689cb5add
|
|
Resolves HTTP authentication failure when attempting to make
a websocket connection.
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
Change-Id: Ie833f1cd281dd3b7124ac798eb5318b24df0ed8f
|
|
Added logging path and interface to websocket subscription
data filter, to dynamically indicate Health status in the
app header.
- Update OverviewEvents to use highPriorityEvents data
- Refactor EventLogStore
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
Change-Id: I35ad30b005c70625a5f6a69488d45db0fa049374
|
|
- Create WebSocket and get host state changes from server
- Changed webpack devServer to https to allow for
secure WebSocket creation (wss)
- Updates to AppHeader to visually indicate changes
in host state
- Cleaned up api.js file
- Check if user is logged in when creating WebSocket
- Adds check if user is already authenticated so WebSocket
is created when browser refreshed.
- Add appliation header styles
- Add sass loader config changes to allow sass variables to
be used in single file components
URL must use https protocol when running locally or the page
will not load.
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
Signed-off-by: Derick Montague <derick.montague@ibm.com>
Change-Id: I35e89bdc09e1aa35a6215ef952409a8ed16dd9e1
|
