Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 138
    • Issues 138
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #233

Closed
Open
Opened Apr 14, 2020 by Marcin Siodelski@marcinMaintainer

Create data model for daemons

Our UI seems to become "daemon centric". The lists we're aiming to present in the dashboard contain daemons and their statuses rather than apps and their statuses. When clicking on the given app the user is taken to the view where we have multiple tabs, each one for each daemon. Configurations are per daemon, rather than per app and so forth.

This all implies that daemons already deserve their own SQL table(s) so as the daemon specific information (e.g. LPS stats) can be associated with them. In fact, the HA status is also presented per daemons. This ticket should introduce the new tables and fill them in with the daemon specific information upon adding a new app or refreshing an existing app. It should also handle deletion of the app. The service tables should be adopted to provide the relations to the daemon table(s) rather than app tables.

Edited Apr 14, 2020 by Marcin Siodelski
Assignee
Assign to
0.7
Milestone
0.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#233