Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Research architecture of console.redhat.com #178

Closed
7 tasks done
Tracked by #175
lachmanfrantisek opened this issue Apr 26, 2023 · 1 comment
Closed
7 tasks done
Tracked by #175

Research architecture of console.redhat.com #178

lachmanfrantisek opened this issue Apr 26, 2023 · 1 comment
Assignees
@lachmanfrantisek
Labels
area/rhel-ecosystem RHEL & CentOS stream complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Apr 26, 2023 •
edited
Loading

The goal of this task is to have a clear understanding of what is needed to incorporate Packit into console.redhat.com ( #175). Specifically:

  • What is the architecture?
    • How are services connected to each other?
    • How do services communicate?
  • How are the services deployed?
  • What are the formal/technical requirements?
  • Gather the information above and present the finding to the team.
    • Show the team example of the existing service.

You can also meet people behind the console and/or developers of other services to get the information.

This issue is part of the #175 epic.
@lachmanfrantisek lachmanfrantisek added area/rhel-ecosystem RHEL & CentOS stream complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. labels Apr 26, 2023
@lachmanfrantisek lachmanfrantisek mentioned this issue Apr 26, 2023
Open
10 tasks
@lachmanfrantisek lachmanfrantisek moved this from new to ready-to-refine in Packit Kanban Board Apr 26, 2023
@lachmanfrantisek lachmanfrantisek mentioned this issue Apr 26, 2023
Closed
6 tasks
@lachmanfrantisek lachmanfrantisek added the kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. label Apr 26, 2023
This was referenced Apr 26, 2023
Closed
Closed
@TomasTomecek
Copy link
Member

I suggest reaching out to the image builder team: Ondrej, Tomas or Sanne.

@lbarcziova lbarcziova moved this from ready-to-refine to refined in Packit Kanban Board Apr 27, 2023
@lachmanfrantisek lachmanfrantisek self-assigned this May 9, 2023
@lachmanfrantisek lachmanfrantisek moved this from refined to in-progress in Packit Kanban Board May 9, 2023
@lachmanfrantisek lachmanfrantisek moved this from in-progress to in-review in Packit Kanban Board Aug 25, 2023
@lachmanfrantisek lachmanfrantisek moved this from in-review to done in Packit Kanban Board Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lachmanfrantisek lachmanfrantisek

Labels
area/rhel-ecosystem RHEL & CentOS stream complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TomasTomecek @lachmanfrantisek