-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support topology v2 #2598
Support topology v2 #2598
Conversation
6d24e9e
to
55287af
Compare
@yannnz bit of a work in progress still -- but this is where we are at with Topology. Group Nodes is probably the biggest gap. I know we are probably not showing artifact sidebars quite perfectly -- we can iterate on these. |
@Gkrumbach07 @jpuzz0 feel free to start reviewing this... we may need to fix up some of it next week. I'll try to get more of it updated tomorrow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
State of things...
frontend/src/concepts/pipelines/content/pipelinesDetails/pipelineRun/runLogs/LogsTab.tsx
Outdated
Show resolved
Hide resolved
frontend/src/concepts/pipelines/content/pipelinesDetails/pipelineRun/PipelineRunDetails.tsx
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO
frontend/src/k8sTypes.ts
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably should delete all Tekton items -- but we may need it later for Edge -- so I'm torn tbh.
d426c6c
to
b80be31
Compare
Seems pods are having some issues getting proper logs -- so I've started a thread with the backend team. We should be down to a minor number of known issues. @Gkrumbach07 please take a look when you get a moment. |
// [PipelineRunNodeTabs.VISUALIZATIONS]: <>TBD 2</>, | ||
[PipelineRunNodeTabs.DETAILS]: <SelectedNodeDetailsTab task={task} />, | ||
[PipelineRunNodeTabs.VOLUMES]: <SelectedNodeVolumeMountsTab task={task} />, | ||
// [PipelineRunNodeTabs.VOLUMES]: <SelectedNodeVolumeMountsTab task={task} />, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is volumes removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not found a way to show them, if you have a Pipeline for them, let me know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found one, will implement again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#2598 (comment) yes, I am aware, fixing. They do weird spec things when it has volumes.
|
||
const { task_details: taskDetails } = runDetails; | ||
|
||
const thisTaskDetail = taskDetails.find(({ display_name: name }) => name === `${taskId}-driver`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you only look at driver. I cannot get an error node to apear then. For some reason if a node has an error, it is not setting the state for the driver task, just the children ones
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn, seems I might need to find a bunch of them -- I didn't at the start, but it doesn't show active states if I don't.
...d/src/concepts/pipelines/content/pipelinesDetails/pipelineRun/PipelineRunDrawerRightTabs.tsx
Show resolved
Hide resolved
b80be31
to
cfe9104
Compare
500a2f5
to
760c02b
Compare
i get this type of run graph |
/retest Seems like Cypress is having some issues. (got a TS error locally, fixed it -- not sure why I didn't see that on the cluster before Cypress) |
760c02b
to
8bf3cdd
Compare
8bf3cdd
to
b701e5e
Compare
b701e5e
to
eef0558
Compare
Known gaps (cc @Gkrumbach07):
|
This looks good to me. The known gaps are fine for now until we get the new topology rendering in. /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
https://issues.redhat.com/browse/RHOAIENG-2297
Description
Basically this will bring back the horizontal topology using DSPv2 data. It refactors a lot of what was in the sidebar and has some edge cases left. We may need to merge this as first implementation (after some cleanup) and then address reworking the artifact nodes to properly show up.
Screenshots
Pipeline
Run screen
Group nodes, not supported today (or for v1=>v2 parity)
Schedules
Gif
Notes:
Screen.Recording.2024-03-14.at.2.02.48.AM.mov
How Has This Been Tested?
You should be able to view any:
And get a topology graph. Statuses should reflect executions but have some quirks to them (see description).
Test Impact
WIP
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main